[Kernel-packages] [Bug 1828133] Re: Intel CyclonePeak wifi firmware
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1828133 Title: Intel CyclonePeak wifi firmware Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Released Bug description: [Impact] New Intel CyclonePeak Wifi cards require new firmware to enable. [Fix] To update the firmware we want only, backport the following 2 commits from iwlwifi tree for-upstream branch[1], and remove all 9000 series related firmwares. 95a93535 iwlwifi: update -46 firmwares for 22260 and 9000 series 68040ceb iwlwifi: add firmware for 22260 and update 9000 series -46 firmwares 1. git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux- firmware.git [Test Case] Verified on AX200NGW & 22560NGW chips & Killer 1653 card, wifi works well. [Regression Risk] Low. This firmware is for new cards and new ABI, it won't affect current Intel wifi cards, and won't take effect on Bionic(4.15) kernel. Only iwlwifi DKMS driver or oem-osp1 kernel loads this firmware. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1828133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835436] Re: linux-azure: 4.18.0-1025.27~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow - derivatives: bug 1834885 (azure-kernel), bug 1834887 (linux-azure-edge), - bug 1835435 (azure-kernel) + derivatives: bug 1834885 (azure-kernel), bug 1834887 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1835438 phase: Ready for Promote to Proposed phase-changed: Friday, 05. July 2019 14:14 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1835436 Title: linux-azure: 4.18.0-1025.27~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834885 (azure-kernel), bug 1834887 (linux-azure- edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1835438 phase: Ready for Promote to Proposed phase-changed: Friday, 05. July 2019 14:14 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835040] Re: Touchpd not working properly on Linux
Ran `apport-collect`. Please use this dmesg log for debugging. https://launchpadlibrarian.net/431451139/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835040 Title: Touchpd not working properly on Linux Status in linux package in Ubuntu: Confirmed Bug description: Installed Ubuntu 19.04 on a laptop, the touch pad is behaving abnormally. It's detected, but nothing seems to work, however working very normal with Windows 10. Laptop model - iBall CompBook M500 It's somewhat similar to this bug, probably using the same touchpad hardware too. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825718 Attached some logs, with `i2c-hid.debug=1 hid.debug=1` the boot time kernel parameters added. Thanks. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: arnab 931 F pulseaudio CurrentDesktop: LXQt DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-06-22 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: iBall iBall CompBook M500 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=88dcdd79-12d6-4052-8314-eb0074bbca8c ro quiet ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: CC-14.1-BI-Y116AR400-AA54G-051-C dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio CRB dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 31 dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrCC-14.1-BI-Y116AR400-AA54G-051-C:bd07/25/2018:svniBall:pniBallCompBookM500:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnAptioCRB:rvrTobefilledbyO.E.M.:cvn:ct31:cvrTobefilledbyO.E.M.: dmi.product.family: Notebook dmi.product.name: iBall CompBook M500 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: iBall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15
Tested bionic-proposed with both original VM that exhibited the problem
on upgrade and a separate VM used to test the work-around (uncommenting
WaylandEnable=false in /etc/gdm3/custom.conf).
Both VMs upgraded and ran successfully using
https://wiki.ubuntu.com/Testing/EnableProposed.
-
# First test w/older VM that first exhibited the problem...
# [ No network card present ]
# Booted from old, saved VM where update first screwed up:
$ uname -a
Linux linuxTest 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
# Added bionic-proposed repository in update / developer options
# [ Enabled network card for VM ]
# Updated to current; restarted
# Booted & logged in normally
$ uname -a
Linux linuxTest 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
# Yea!
-
# Second test with VM used for later testing of the problem...
# [ No network card present ]
# Re-tested with more recent problem VM...
# Removed fix in /etc/gdm3/custom.conf (re-commented WaylandEnable=false)
# Booted to watch login hang
# {Shift} boot w/Grub in recovery mode to recovery mode menu; resumed startup.
# Logged in (desktop @800x600); re-set desktop width
$ uname -a
Linux Linux linuxTest 4.15.0-52-generic #56-Ubuntu SMP Tue Jun 4 22:49:08
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
# Added bionic-proposed repository in update / developer options
# [ Enabled network card for VM ]
# Updated to current; restarted
# Booted & logged in normally
$ uname -a
Linux linuxTest 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
# Yea!
-
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx using bionic kernel 4.15
Status in linux package in Ubuntu:
Invalid
Status in linux-hwe package in Ubuntu:
Invalid
Status in mutter package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Committed
Status in linux-hwe source package in Bionic:
Fix Released
Status in mutter source package in Bionic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-hwe source package in Disco:
Invalid
Status in mutter source package in Disco:
Invalid
Status in linux source package in Eoan:
Invalid
Status in linux-hwe source package in Eoan:
Invalid
Status in mutter source package in Eoan:
Invalid
Bug description:
[Impact]
With most recent version of mutter installed.
If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver)
and if the login screen uses wayland, then the login prompt doesn't appears.
All we see is the purple background with ubuntu in white at the bottom, nothing
else.
The vmwgfx driver in kernels prior to 4.17 reported bogus timestamps using
the wrong clock. This would lead us to wait forever (or at least 49 years)
before rendering the next frame. There's no decisive way to know this kernel
bug is going to happen before it does so just detect timestamps which are
obviously going to cause freezes and ignore them.
[Test case]
1) Use Virtualbox or VMware ESxi (if you have the infra)
1.1) [virtualbox] Make sure in the VM setting that the display uses 'VMSVGA'
which will force the OS to pick 'vmwgfx' video kernel driver. You can confirm
with 'lspci -nnvv' command.
2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15)
4) apt-get dist-upgrade
5) Reboot
with 4.15 it will fails
with hwe kernel 4.18 it will work as expected. # workaround
[Potential regression]
Low, it should fix vmwgfx and stop using the wrong clock.
A test kernel (pre-sru) has been made available to impact users for
them to test and conclude it works. It does work as expected, and no
regression has been found during the pre-sru testing phase.
As per commit description:
"
This should be transparent to to user space, as long as it doesn't
compare the time against the result of gettimeofday().
"
[Other informations]
upstream fix:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5&id=37efe80ce85f
[Original description]
I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018
Macbook Pro.
I've been running this Ubuntu 18.04.2 VM without problem for many months
without problem.
Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the
system hangs immediately after displaying the splash screen. I never see a
login screen. And I can't use Ctrl+Alt+F2 to navigate to a
[Kernel-packages] [Bug 1400463] Re: [Medion Akoya P2214T] Touchpad not properly recognized
Hey, I have an Akoya P2214T with the same ITE Tech. Inc. ITE Device(8910) Touchpad. Is the fix still available somewhere or another solution. The link above doesnt work anymore. Did ELAN Microelectronics Corp. get anything done? Thanks! Daniel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1400463 Title: [Medion Akoya P2214T] Touchpad not properly recognized Status in linux package in Ubuntu: Confirmed Bug description: The ELAN (not Elantech) touchpad in my Medion Akoya P2214T (MD 99430) laptop/tablet hybrid is not properly recognized. Both the touchscreen and the touchpad function as a regular mouse, but the touchpad shows up as an ITE Tech. Inc. ITE Device(8910) pointer in xinput (see attachment). Multitouch and scrolling however, do not function, nor do options for this show up in the Mouse & Touchpad options in Ubuntu 14.10 64-bit. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xserver-xorg-input-synaptics 1.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Dec 8 20:02:14 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu InstallationDate: Installed on 2014-11-12 (26 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Medion Akoya P2214T ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=06056019-c592-4d2d-9738-54e729126d7d ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 205 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Akoya P2214T dmi.board.vendor: Medion dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 8 dmi.chassis.vendor: Medion dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr205:bd08/26/2014:svnMedion:pnAkoyaP2214T:pvr1.0:rvnMedion:rnAkoyaP2214T:rvr1.0:cvnMedion:ct8:cvrToBeFilledByO.E.M.: dmi.product.name: Akoya P2214T dmi.product.version: 1.0 dmi.sys.vendor: Medion version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 8 18:30:57 2014 xserver.configfile: default xserver.errors: Error loading keymap /var/lib/xkb/server-992DCD2811F9928D990F91F3229E52A1EC62B72A.xkm Error loading keymap /var/lib/xkb/server-992DCD2811F9928D990F91F3229E52A1EC62B72A.xkm Error loading keymap /var/lib/xkb/server-992DCD2811F9928D990F91F3229E52A1EC62B72A.xkm xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12637 vendor AUO xserver.version: 2:1.16.0-1ubuntu1 --- ApportVersion: 2.14.1-0ubuntu3.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mizuti 2439 F pulseaudio CRDA: country EU: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS CurrentDesktop: X-Cinnamon DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=325a292a-ad2c-493d-b148-aff85b17b41e InstallationDate: Installed on 2015-10-15 (616 days ago) InstallationMedia: Linux Mint 17.2 "Rafaela" - Release amd64 20150627 MachineType: Medion Akoya P2214T Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=727a143b-7e46-4f81-8cc9-c37b396d582e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 RelatedPackageVersions: linux-restricted-modules-3.16.0-24-generic N/A linux-backports-modules-3.16.0-24-generic N/A linux-firmware 1.127.23 Tags: rafaela Uname: Linux 3.16.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: Tru
[Kernel-packages] [Bug 1835583] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1835583 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835583 Title: Text not rendering correctly after resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: Since 19.04, I've been experiencing frequent difficulties resuming from suspend, causing text not to be displayed at all, or wrong characters to be displayed. Please see the attached screenshots. I don't know what part of the system this lies in. It seems to affect all gtk apps at least. Firefox and Chromium renders just fine when this happens, other than the titlebar. Description: Pop!_OS 19.04 Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835583] [NEW] Text not rendering correctly after resume from suspend
Public bug reported: Since 19.04, I've been experiencing frequent difficulties resuming from suspend, causing text not to be displayed at all, or wrong characters to be displayed. Please see the attached screenshots. I don't know what part of the system this lies in. It seems to affect all gtk apps at least. Firefox and Chromium renders just fine when this happens, other than the titlebar. Description:Pop!_OS 19.04 Release:19.04 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "bug.zip" https://bugs.launchpad.net/bugs/1835583/+attachment/5275319/+files/bug.zip -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835583 Title: Text not rendering correctly after resume from suspend Status in linux package in Ubuntu: New Bug description: Since 19.04, I've been experiencing frequent difficulties resuming from suspend, causing text not to be displayed at all, or wrong characters to be displayed. Please see the attached screenshots. I don't know what part of the system this lies in. It seems to affect all gtk apps at least. Firefox and Chromium renders just fine when this happens, other than the titlebar. Description: Pop!_OS 19.04 Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835270] Re: linux: 3.2.0-142.189 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 19:03 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa lbm:failed,main:building + promote-to-proposed: Pending -- builds not complete in ppa lbm:failed variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835270 Title: linux: 3.2.0-142.189 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 19:03 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa lbm:failed variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834948] Re: linux-azure: 4.15.0-1051.56~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-trusty ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1834950 - phase: Holding before Promote to Proposed - phase-changed: Friday, 05. July 2019 08:43 UTC + phase: Ready for Promote to Proposed + phase-changed: Friday, 05. July 2019 22:13 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa signed:building + promote-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1834948 Title: linux-azure: 4.15.0-1051.56~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834950 phase: Ready for Promote to Proposed phase-changed: Friday, 05. July 2019 22:13 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834706] Re: linux-azure: 5.0.0-1011.11 -proposed tracker
This bug was fixed in the package linux-azure - 5.0.0-1011.11
---
linux-azure (5.0.0-1011.11) disco; urgency=medium
* linux-azure: 5.0.0-1011.11 -proposed tracker (LP: #1834706)
* linux-azure: mlx4, mlx5, ibverbs, ib_umad are not being loaded by default
(LP: #1834696)
- Revert "UBUNTU: [Config] linux-azure: CONFIG_MLX{4,5}_INFINIBAND=m"
-- Marcelo Henrique Cerri Fri, 28 Jun
2019 22:13:08 -0300
** Changed in: linux-azure (Ubuntu)
Status: Invalid => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1834706
Title:
linux-azure: 5.0.0-1011.11 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Fix Released
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow 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:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
Fix Released
Status in Kernel SRU Workflow verification-testing series:
Invalid
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testing-requested: true
kernel-stable-master-bug: 1833934
phase: Security
phase-changed: Wednesday, 03. July 2019 18:33 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834706/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821625] Re: systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-seccomp)
I agree with the analysis in comment #13 about stress-ng.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1821625
Title:
systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-
seccomp)
Status in libseccomp package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Invalid
Status in libseccomp source package in Bionic:
Invalid
Status in linux source package in Bionic:
Fix Committed
Status in systemd source package in Bionic:
Invalid
Bug description:
Starting with systemd 237-3ubuntu10.14, the testcase test-seccomp is
failing on Bionic on ppc64el with the error messages:
Operating on architecture: ppc
Failed to add n/a() rule for architecture ppc, skipping: Bad address
Operating on architecture: ppc64
Failed to add n/a() rule for architecture ppc64, skipping: Bad address
Operating on architecture: ppc64-le
Failed to add n/a() rule for architecture ppc64-le, skipping: Numerical
argument out of domain
Assertion 'p == MAP_FAILED' failed at ../src/test/test-seccomp.c:413,
function test_memory_deny_write_execute_mmap(). Aborting.
memoryseccomp-mmap terminated by signal ABRT.
Assertion 'wait_for_terminate_and_check("memoryseccomp-mmap", pid, WAIT_LOG)
== EXIT_SUCCESS' failed at ../src/test/test-seccomp.c:427, function
test_memory_deny_write_execute_mmap(). Aborting.
Aborted (core dumped)
FAIL: test-seccomp (code: 134)
Full logs at:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190302_025135_d0e38@/log.gz
The testcase passed with systemd version 237-3ubuntu10.13 running on the same
4.15.0-45 kernel on ppc64el:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190228_154406_6b12f@/log.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1821625/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835580] [NEW] Disco update: 5.0.16 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 5.0.16 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Disco) Importance: Medium Assignee: Connor Kuehl (connork) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Connor Kuehl (connork) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835580 Title: Disco update: 5.0.16 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 5.0.16 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835580/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834948] Re: linux-azure: 4.15.0-1051.56~14.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1834950 phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 08:43 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa signed:retry-needed + promote-to-proposed: Ongoing -- builds not complete in ppa signed:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1834948 Title: linux-azure: 4.15.0-1051.56~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1834950 phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 08:43 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa signed:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835270] Re: linux: 3.2.0-142.189 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 19:03 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,lbm:building + promote-to-proposed: Pending -- builds not complete in ppa lbm:failed,main:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835270 Title: linux: 3.2.0-142.189 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 19:03 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa lbm:failed,main:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824690] Re: proc_thermal flooding dmesg
** Description changed:
+ == SRU Justification Bionic/Disco ==
+
+ proc_thermal messages are spamming the kernel log when used in
+ conjunction with thermal. This is because the message is not set at the
+ correct kernel log level.
+
+ == Fix ==
+
+ Upstream fix 44c0c23725a16c8803b8809b87651405e8741e4d ("drivers:
+ thermal: processor_thermal: Downgrade error message"). This is in 5.2 so
+ not applicable for Eoan.
+
+ This fix needs a minor backport wiggle for Bionic because the driver is
+ located in a different place.
+
+ == Test case ==
+
+ Without the fix the kernel log is being spammed periodically with
+ messages in the form:
+
+ [ 11.520358] proc_thermal :00:00.1: Unsupported event [0x91]
+ [ 16.532358] proc_thermal :00:00.1: Unsupported event [0x91]
+ [ 21.572719] proc_thermal :00:00.1: Unsupported event [0x91]
+ [ 26.580855] proc_thermal :00:00.1: Unsupported event [0x91]
+
+ With the fix these messages are no longer appearing.
+
+ == Regression Potential ==
+
+ This changes the log level, so regression potential is very limited,
+ unless some program is relying on this message for some particular
+ reason.
+
+
+ ---
+
[ 11.520358] proc_thermal :00:00.1: Unsupported event [0x91]
[ 16.532358] proc_thermal :00:00.1: Unsupported event [0x91]
[ 21.572719] proc_thermal :00:00.1: Unsupported event [0x91]
[ 26.580855] proc_thermal :00:00.1: Unsupported event [0x91]
[ 31.588851] proc_thermal :00:00.1: Unsupported event [0x91]
[ 36.592827] proc_thermal :00:00.1: Unsupported event [0x91]
[ 41.572682] random: crng init done
[ 41.572690] random: 7 urandom warning(s) missed due to ratelimiting
Kernel 4.18.0-18-generic
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic
- ---
+ ---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC0: juno 1175 F pulseaudio
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: juno 1175 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-04-15 (0 days ago)
InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
Lsusb:
- Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
- Bus 001 Device 004: ID 8087:0025 Intel Corp.
- Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd
- Bus 001 Device 002: ID 1ea7:0064
- Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+ Bus 001 Device 004: ID 8087:0025 Intel Corp.
+ Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd
+ Bus 001 Device 002: ID 1ea7:0064
+ Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Notebook N24_25GU
Package: thermald 1.7.0-5ubuntu2
PackageArchitecture: amd64
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic
root=UUID=a23ca3ac-6284-45ce-9aa8-6670879910e7 ro quiet splash acpi_osi=
acpi_os_name=Linux vt.handoff=1
ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
RelatedPackageVersions:
- linux-restricted-modules-4.18.0-18-generic N/A
- linux-backports-modules-4.18.0-18-generic N/A
- linux-firmware 1.173.5
+ linux-restricted-modules-4.18.0-18-generic N/A
+ linux-backports-modules-4.18.0-18-generic N/A
+ linux-firmware 1.173.5
Tags: bionic
Uname: Linux 4.18.0-18-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/18/2018
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.06
dmi.board.asset.tag: Tag 12345
dmi.board.name: N24_25GU
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.06:bd05/18/2018:svnNotebook:pnN24_25GU:pvrNotApplicable:rvnNotebook:rnN24_25GU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: N24_25GU
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1824690
Title:
proc_thermal flooding dmesg
Status in linux package in Ubuntu:
In Progress
Status in thermald package in Ubuntu:
Incomplete
Bug description:
== SRU Justification Bionic/Disco ==
proc_therma
[Kernel-packages] [Bug 1830538] Re: Can't get HIDP connection info
See https://bugzilla.redhat.com/show_bug.cgi?id=1671135 https://forums.fedoraforum.org/showthread.php?320530-Kernel-4-19-15-300-fc29 -broke-bluetooth-HIDP ** Bug watch added: Red Hat Bugzilla #1671135 https://bugzilla.redhat.com/show_bug.cgi?id=1671135 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830538 Title: Can't get HIDP connection info Status in linux package in Ubuntu: Confirmed Bug description: Hi, I'm trying to use a Teemi TMSL-50 bluetooth barcode scanner (in keyboard emulation mode) with a USB bluetooth dongle in an 18.04 machine, which used to work some months ago. Now I can still pair them, the ubuntu machine sees the devices and lists as paired, but can't connect with human interface device service (HID). /var/log/syslog says May 26 14:44:49 machine1 bluetoothd[1272]: Can't get HIDP connection info May 26 14:44:51 machine1 bluetoothd[1272]: connect error: Invalid exchange (52) Since the scanner and the usb dongle are unchanged, it must be a problem of the ubuntu machine. regards ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Sun May 26 14:48:12 2019 InstallationDate: Installed on 2018-06-09 (350 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Medion G24 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-50-generic root=UUID=a3f06afa-8405-4064-8044-0a9e1b4c19c8 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: H61TIW08.111 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61H2-TI2 dmi.board.vendor: Medion dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Medion dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: G24 dmi.product.version: 1.0 dmi.sys.vendor: Medion hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:3400 acl:0 sco:0 events:192 errors:0 TX bytes:5012 acl:0 sco:0 commands:142 errors:0 mtime.conffile..etc.dbus-1.system.d.bluetooth.conf: 2019-05-26T14:29:51.468868 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830538/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1239459]
https://www.techjockey.com/category/jewellery-software -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1239459 Title: 1814:3290 [Asus X200CA] wifi doesn't connect or disconnects after few seconds Status in Linux: Won't Fix Status in linux package in Ubuntu: Fix Released Bug description: With the new 3.11.0-12-generic kernel, wifi has problems to connect with many errors like these: Oct 13 23:50:03 ubuntotto kernel: [ 1186.580726] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:03 ubuntotto kernel: [ 1186.740659] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1186.900544] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1187.060571] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1187.096576] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0 Oct 13 23:50:05 ubuntotto kernel: [ 1188.280106] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:05 ubuntotto kernel: [ 1188.440128] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:51:06 ubuntotto kernel: [ 1249.560697] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:51:06 ubuntotto kernel: [ 1249.720644] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:51:07 ubuntotto kernel: [ 1249.880590] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:51:07 ubuntotto kernel: [ 1250.040543] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrea 1791 F pulseaudio Date: Sun Oct 13 23:45:04 2013 HibernationDevice: RESUME=UUID=297ef090-5420-41f6-8439-f1254f3e9e15 InstallationDate: Installed on 2013-10-12 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. X200CA MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=088f2a7d-b78f-4bdd-a184-754b70a3184a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-10-13 (0 days ago) dmi.bios.date: 09/18/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X200CA.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X200CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX200CA.208:bd09/18/2013:svnASUSTeKCOMPUTERINC.:pnX200CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X200CA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1239459/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834930] Re: linux-aws: 4.15.0-1044.46 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834929 (xenial/linux-aws-hwe) derivatives: bug 1834927 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 - phase: Testing - phase-changed: Friday, 05. July 2019 12:09 UTC + phase: Signoff + phase-changed: Friday, 05. July 2019 20:09 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1834930 Title: linux-aws: 4.15.0-1044.46 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834929 (xenial/linux-aws-hwe) derivatives: bug 1834927 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Signoff phase-changed: Friday, 05. July 2019 20:09 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835190] Re: linux: 3.13.0-172.223 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-trusty ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835189 (precise/linux-lts-trusty) -- swm properties -- - phase: Holding before Promote to Proposed - phase-changed: Friday, 05. July 2019 08:33 UTC + boot-testing-requested: true + phase: Ready for Promote to Proposed + phase-changed: Friday, 05. July 2019 20:03 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building + promote-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835190 Title: linux: 3.13.0-172.223 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835189 (precise/linux-lts-trusty) -- swm properties -- boot-testing-requested: true phase: Ready for Promote to Proposed phase-changed: Friday, 05. July 2019 20:03 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835190/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835270] Re: linux: 3.2.0-142.189 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 19:03 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lbm:building,main:building + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,lbm:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835270 Title: linux: 3.2.0-142.189 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 19:03 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,lbm:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835270] Re: linux: 3.2.0-142.189 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 19:03 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa meta:building,main:building,lbm:building + promote-to-proposed: Ongoing -- builds not complete in ppa lbm:building,main:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835270 Title: linux: 3.2.0-142.189 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 19:03 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa lbm:building,main:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835270] Re: linux: 3.2.0-142.189 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-lbm Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- - phase: Packaging - phase-changed: Friday, 05. July 2019 11:32 UTC + phase: Holding before Promote to Proposed + phase-changed: Friday, 05. July 2019 19:03 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-lbm: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa meta:building,main:building,lbm:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835270 Title: linux: 3.2.0-142.189 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 19:03 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa meta:building,main:building,lbm:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1737428] Re: VRF support to solve routing problems associated with multi-homing
Sandor, Not on the VRF usage side but there is a feature in MAAS 2.6 to have a better way to work in multi-homed environments (for bionic+ machines): https://docs.maas.io/2.6/en/intro-new "Networking - Multiple default gateways" It relies on "routing policy database" (RPDB) functionality https://paste.ubuntu.com/p/xg6vFm8Hx7/ (netplan config, routing-policy sections are defined only for subnets that have a gateway configured in MAAS) At the target machine you will see something like this: # ip rule 0: from all lookup local 0: from 10.232.24.0/21 to 10.232.24.0/21 lookup main 0: from 10.232.40.0/21 to 10.232.40.0/21 lookup main 100:from 10.232.24.0/21 lookup 2 100:from 10.232.40.0/21 lookup 1 32766: from all lookup main 32767: from all lookup default # ip route show table 1 default via 10.232.40.1 dev b-enp4s0f0-2730 proto static # ip route show table 2 default via 10.232.24.1 dev b-enp4s0f0-2731 proto static This works well for TCP when responding to traffic (even when software listens on 0.0.0.0). For UDP a frequent server use-case is DNS servers and bind9 binds its UDP sockets to interface addresses directly as opposed to using 0.0.0.0 (some other DNS servers do the same, e.g. PowerDNS - they even have a post about it https://blog.powerdns.com/2012/10/08/on-binding-datagram-udp-sockets-to- the-any-addresses/). For sending, the policy rules will also kick in provided that a client socket (TCP or UDP) is bound to a specific address (so that the source IP is not automatically selected). This requires that the target software supports binding client sockets to specific addresses unfortunately. So far using static routes to summarized prefixes has been a solution for east-west traffic (because we control nodes managed by MAAS) and using the approach above for client responses to arbitrary networks (via https://jaas.ai/u/canonical-bootstack/policy-routing). After juju starts supporting this new MAAS feature https://bugs.launchpad.net/juju/+bug/1829150 we can stop using charm- policy-routing. I hope that helps while VRF functionality is not implemented. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1737428 Title: VRF support to solve routing problems associated with multi-homing Status in juju: Incomplete Status in MAAS: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Problem description: * a host is multi-homed if it has multiple network interfaces with L3 addresses configured (physical or virtual interfaces, natural to OpenStack regardless of IPv4/IPv6 and IPv6 in general); (see 3.3.4 Local Multihoming https://tools.ietf.org/html/rfc1122#page-60 and 3.3.4.2 Multihoming Requirements) * if all hosts that need to participate in L3 communication are located on the same L2 network there is no need for a routing device to be present. ARP/NDP and auto-created directly connected routes are enough; * multi-homing with hosts located on different L2 networks requires more intelligent routing: - "directly connected" routes are no longer enough to talk to all relevant hosts in the same network space; - a default gateway in the main routing table may not be the correct routing device that knows where to forward traffic (management network traffic goes to a management switch and router, other traffic goes to L3 ToR switch but may go via different bonds); - even if a default gateway knows where to forward traffic, it may not be the intended physical path (storage replication traffic must go through a specific outgoing interface, not the same interface as storage access traffic although both interfaces are connected to the same ToR); - there is no longer a single "default gateway" as applications need either per-logical-direction routers or to become routers themselves (if destination == X, forward to next-hop Y). Leaf-spine architecture is a good example of how multiple L2 networks force you to use spaces that have VLANs in different switch fabrics => one or more hops between hosts with interfaces associated with the same network space; - while network spaces implicitly require L3 reachability between each host that has a NIC associated with a network space, the current definition does not mention routing infrastructure required for that. For a single L2 this problem is hidden by directly connected routes, for multi-L2, no solution is provided or discussed; * existing solutions to multi-homing require routing table management on a given host: complex static routing rules, dynamic routing (e.g. running an OSPF or BGP daemon on a host); * using static routes is rigid and requires network planning (i.e. working with network engineers which may have varying degrees of experience, doing VLSM planning etc.); * using dynamic routing requires a broader integr
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
I don't see this: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16 Which is in the previous log. To build a kernel, I use `fakeroot debian/rules clean binary-headers binary-generic`. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep requested (sleeping: no en Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5333] device (40:4E:36:47:ED:D1): state change: disconn Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5358] manager: NetworkManager state is now ASLEEP Apr 02 13:39:54 taplop whoopsie[1779]: [13:39:54] offline Apr 02 13:39:55 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:56 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Apr 02 13:39:56 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Apr 02 13:39:56 taplop kernel: [drm] VCE initialized successfully. Apr 02 13:39:57 taplop systemd[1]: Starting TLP suspend/resume... Apr 02 13:39:57 taplop systemd[1]: Started TLP suspend/resume. Apr 02 13:39:57 taplop systemd[1]: Reached target Sleep. Apr 02 13:39:57 taplop systemd[1]: Starting Suspend... Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9078] caught SIGTERM, shutting down normally. Apr 02 13:39:57 taplop systemd[1]: Stopping Network Manager... Apr 02 13:39:57 taplop gnome-shell[5521]: Removing a network device that was not added Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9485] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP c Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] dhcp4 (wlp2s0): state changed bound -> done Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9486] device (wlp2s0): DHCPv4: 480 seconds grace period Apr 02 13:39:57 taplop NetworkManager[4083]: [1554237597.9570] exiting (success) Apr 02 13:39:57 taplop gnome-shell[5521]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1187]: reference Apr 02 13:39:57 taplop systemd[1]: NetworkManager.service: Succeeded. Apr 02 13:39:57 taplop systemd[1]: Stopped Network Manager. Apr 02 13:39:57 taplop gnome-shell[5521]: Object NM.ActiveConnection (0x55d340e8f5a0), has been already deallocated — im Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: == Stack trace for context 0x55d34160e1e0 == Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #0 55d345364700 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #1 55d345364680 i resource:///org/gnome/shell/ui/status/networ Apr 02 13:39:57 taplop org.gnome.Shell.desktop[5521]: #2 7ffe97451d00 b self-hosted:979 (7fc3d4350a60 @ 440) Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop kernel: wlp2s0: deauthenticating from f0:9f:c2:6e:e1:aa by local choice (Reason: 3=DEAUTH_LEAVING Apr 02 13:39:58 taplop wpa_supplicant[1069]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:6e:e1:aa reason=3 locally_ge Apr 02 13:39:58 taplop gnome-shell[5521]: Failed to flip onscreen: Tried to flip inactive CRTC Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::1c45 Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop whoopsie[1779]: [13:39:58] Cannot reach: https://daisy.ubuntu.com Apr 02 13:39:58 taplop avahi-daemon[1068]: Interface wlp2s0.IPv4 no longer relevant for mDNS. Apr 02 13:39:58 taplop avahi-daemon[1068]: Leaving mDNS multicast group on interface wlp2s0.IPv4 with address 10.30.2.26 Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for fe80::1c45:b634:dc94:8f5f on wlp2s0. Apr 02 13:39:58 taplop avahi-daemon[1068]: Withdrawing address record for 10.30.2.26 on wlp2s0. Apr 02 13:39:58 taplop wpa_supplicant[1069]: nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0 Apr 02 13:39:58 taplop wpa_supplicant[1069]: Could not read interface p2p-dev-wlp2s0 flags: No such device Apr 02 13:39:58 taplop systemd-sleep[9790]: Suspending system... Apr 02 13:39:58 taplop
[Kernel-packages] [Bug 1737428] Re: VRF support to solve routing problems associated with multi-homing
Any news or progress on these issues now that we are a year and a half into this bug? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1737428 Title: VRF support to solve routing problems associated with multi-homing Status in juju: Incomplete Status in MAAS: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Problem description: * a host is multi-homed if it has multiple network interfaces with L3 addresses configured (physical or virtual interfaces, natural to OpenStack regardless of IPv4/IPv6 and IPv6 in general); (see 3.3.4 Local Multihoming https://tools.ietf.org/html/rfc1122#page-60 and 3.3.4.2 Multihoming Requirements) * if all hosts that need to participate in L3 communication are located on the same L2 network there is no need for a routing device to be present. ARP/NDP and auto-created directly connected routes are enough; * multi-homing with hosts located on different L2 networks requires more intelligent routing: - "directly connected" routes are no longer enough to talk to all relevant hosts in the same network space; - a default gateway in the main routing table may not be the correct routing device that knows where to forward traffic (management network traffic goes to a management switch and router, other traffic goes to L3 ToR switch but may go via different bonds); - even if a default gateway knows where to forward traffic, it may not be the intended physical path (storage replication traffic must go through a specific outgoing interface, not the same interface as storage access traffic although both interfaces are connected to the same ToR); - there is no longer a single "default gateway" as applications need either per-logical-direction routers or to become routers themselves (if destination == X, forward to next-hop Y). Leaf-spine architecture is a good example of how multiple L2 networks force you to use spaces that have VLANs in different switch fabrics => one or more hops between hosts with interfaces associated with the same network space; - while network spaces implicitly require L3 reachability between each host that has a NIC associated with a network space, the current definition does not mention routing infrastructure required for that. For a single L2 this problem is hidden by directly connected routes, for multi-L2, no solution is provided or discussed; * existing solutions to multi-homing require routing table management on a given host: complex static routing rules, dynamic routing (e.g. running an OSPF or BGP daemon on a host); * using static routes is rigid and requires network planning (i.e. working with network engineers which may have varying degrees of experience, doing VLSM planning etc.); * using dynamic routing requires a broader integration into an organization's L3 network infrastructure. Routing can be implemented differently across different organizations and it is a security and operational burden to integrate with a company's routing infrastructure. Summary: a mechanism is needed to associate an interface with a forwarding table (FIB) which has its own default gateway and make an application with a listen(2)ing socket(2) return connected sockets associated with different FIBs. In other words, applications need to implicitly get source/destination-based routing capabilities without the need to use static routing schemes or dynamic routing and with minimum or no modifications to the applications themselves. Goals: * avoid turning individual hosts into routers; * avoid complex static rules; * better support multi-fabric deployments with minimum effort (Juju, charms, MAAS, applications, network infrastructure); * reduce operational complexity (custom L3 infrastructure integration for each deployment); * reduce delivery risks (L3 infrastructure, L3 department responsiveness varies); * avoid any form of L2 stretching at the infrastructure level - this is inefficient for various reasons. NOTE: https://cumulusnetworks.com/blog/vrf-for-linux/ - I recommend to read this post to understand suggestions below. How to solve it? What does it mean for Juju to support VRF devices? * enslave certain devices on provisioning based on network space information (physical NICs, VLAN devices, bonds AND bridges created for containers must be considered) - VRF devices logically enslave devices similar to bridges but work differently (on L3, not L2); * the above is per network namespace so it will work equally well in a LXD container; Conceptually: # echo 'net.ipv4.tcp_l3mdev_accept = 1' >> /etc/sysctl.conf # echo 'net.ipv4.udp_l3mdev_accept = 1' >> /etc/sysctl.conf # sysctl -p # # create additional routing tables # cat >> /etc/iproute2/rt_tables.d/vrf.conf
[Kernel-packages] [Bug 1823029] Re: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead
fwiw, i tried to build 5.0.0.20.21 with v2 applied, and was able to reproduce the bug (I may have built it incorrectly though? I git applied the two patches from a clone of git://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/disco and then did `fakeroot debian/rules clean` ; `AUTOBUILD=1 fakeroot debian/rules binary-debs` and installed the resulting packages) tail of journalctl during reproduction: Jul 04 21:48:54 taplop systemd-sleep[11530]: Suspending system... Jul 04 21:48:54 taplop kernel: PM: suspend entry (deep) Jul 04 21:48:58 taplop kernel: PM: Syncing filesystems ... done. Jul 04 21:48:58 taplop kernel: Freezing user space processes ... (elapsed 0.003 seconds) done. Jul 04 21:48:58 taplop kernel: OOM killer disabled. Jul 04 21:48:58 taplop kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Jul 04 21:48:58 taplop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Jul 04 21:48:58 taplop kernel: usb usb2: usb auto-resume Jul 04 21:48:58 taplop kernel: hub 2-0:1.0: hub_resume Jul 04 21:48:58 taplop kernel: usb usb1: usb auto-resume Jul 04 21:48:58 taplop kernel: hub 1-0:1.0: hub_resume Jul 04 21:48:58 taplop kernel: usb usb1-port1: status 0507 change Jul 04 21:48:58 taplop kernel: usb usb1-port6: status 0107 change Jul 04 21:48:58 taplop kernel: usb usb1-port10: status 0107 change Jul 04 21:48:58 taplop kernel: hub 1-0:1.0: hub_suspend Jul 04 21:48:58 taplop kernel: usb usb1: bus suspend, wakeup 0 Jul 04 21:48:58 taplop kernel: hub 2-0:1.0: hub_suspend Jul 04 21:48:58 taplop kernel: usb usb2: bus suspend, wakeup 0 Jul 04 21:48:58 taplop kernel: PM: Some devices failed to suspend, or early wake event detected Jul 04 21:48:58 taplop kernel: usb usb1: usb resume Jul 04 21:48:58 taplop kernel: hub 1-0:1.0: hub_resume Jul 04 21:48:58 taplop kernel: usb usb1-port1: status 0507 change Jul 04 21:48:58 taplop kernel: usb usb1-port6: status 0107 change Jul 04 21:48:58 taplop kernel: usb usb1-port10: status 0107 change Jul 04 21:48:58 taplop kernel: usb usb2: usb resume Jul 04 21:48:58 taplop kernel: hub 2-0:1.0: hub_resume Jul 04 21:48:58 taplop kernel: ACPI: button: The lid device is not compliant to SW_LID. Jul 04 21:48:58 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Jul 04 21:48:58 taplop kernel: usb 1-1: usb resume Jul 04 21:48:58 taplop kernel: usb 1-10: usb resume Jul 04 21:48:58 taplop kernel: usb 1-6: usb resume Jul 04 21:48:58 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Jul 04 21:48:58 taplop kernel: usb 1-10: Waited 0ms for CONNECT Jul 04 21:48:58 taplop kernel: usb 1-10: finish resume Jul 04 21:48:58 taplop kernel: usb 1-6: Waited 0ms for CONNECT Jul 04 21:48:58 taplop kernel: usb 1-6: finish resume Jul 04 21:48:58 taplop kernel: usb 1-1: Waited 0ms for CONNECT Jul 04 21:48:58 taplop kernel: usb 1-1: finish resume Jul 04 21:48:58 taplop kernel: [drm] VCE initialized successfully. Jul 04 21:48:58 taplop kernel: nvme nvme0: 8/0/0 default/read/poll queues Jul 04 21:48:58 taplop kernel: amdgpu :01:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test f Jul 04 21:48:58 taplop kernel: amdgpu :01:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test f Jul 04 21:48:58 taplop kernel: amdgpu :01:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test f Jul 04 21:48:58 taplop kernel: [drm:amdgpu_device_ip_late_init_func_handler [amdgpu]] *ERROR* ib ring tes Jul 04 21:48:58 taplop kernel: OOM killer enabled. Jul 04 21:48:58 taplop kernel: Restarting tasks ... Jul 04 21:48:58 taplop kernel: hub 2-0:1.0: state 7 ports 8 chg evt Jul 04 21:48:58 taplop kernel: done. Jul 04 21:48:58 taplop kernel: hub 2-0:1.0: hub_suspend Jul 04 21:48:58 taplop kernel: usb usb2: bus auto-suspend, wakeup 1 Jul 04 21:48:58 taplop kernel: hub 1-0:1.0: state 7 ports 16 chg evt 0442 Jul 04 21:48:58 taplop kernel: usb 1-10: usb auto-suspend, wakeup 0 Jul 04 21:48:58 taplop kernel: usb 1-6: usb auto-suspend, wakeup 1 Jul 04 21:48:58 taplop kernel: usb 1-1: usb auto-suspend, wakeup 0 Jul 04 21:48:58 taplop kernel: hub 1-0:1.0: hub_suspend Jul 04 21:48:58 taplop kernel: usb usb1: bus auto-suspend, wakeup 1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823029 Title: [Dell XPS 15 9575] Occasionally fails to suspend and locks up instead Status in linux package in Ubuntu: Confirmed Bug description: Sometimes when suspending, the suspend process fails, and the machine becomes unresponsive to any input, has nothing but a black/off display, and fans kick in and run high (which is actually 'good' for detecting the issue has happened). journalctl output from an unsuccessful suspend: Apr 02 13:39:54 taplop systemd-logind[1067]: Suspending... Apr 02 13:39:54 taplop NetworkManager[4083]: [1554237594.5332] manager: sleep: sleep re
[Kernel-packages] [Bug 1828035] Re: StrongSwan with GCM and large packet sizes produces unstable behavior
According to LP 1832623 (especially https://bugs.launchpad.net/ubuntu-z-systems/+bug/1832623/comments/6) the latest kernel available in bionic-proposed (4.15.0-55) includes the 'gcm-aes-s390' patch and is ready for test. See also bionic kernel changelog: https://launchpad.net/ubuntu/+source/linux/+changelog and search for 'gcm-aes-s390' or 1832623) ** Changed in: ubuntu-z-systems 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/1828035 Title: StrongSwan with GCM and large packet sizes produces unstable behavior Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: Confirmed Status in strongswan package in Ubuntu: Incomplete Bug description: StrongSwan with GCM and large packet sizes produces unstable behavior when used in Linux native environment. ---uname output--- Linux ubu01 4.15.0-42-generic #45-Ubuntu SMP Thu Nov 15 19:29:11 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = 3906 / M04 (z14), LPAR (dedicated) ---Debugger--- A debugger is not configured ---Steps to Reproduce--- On two separate machines (Linux native), install StrongSwan and on both machines, configure the encryption with aes128gcm8 for IPsec. Then run the following command from one of the machine: ``` $# ping -s 1024 ``` Small packet sizes are working as expected. However, anything large (around 1024 bytes or more) are sometimes returning wrong values, or the packets are getting lost. This problem does not occur for ciphers not involving GCM. Userspace tool common name: StrongSwan The userspace tool has the following bit modes: both Userspace package: StrongSwan Userspace tool obtained from project website: na -Attach ltrace and strace of userspace application. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1828035/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829257] Re: package linux-image-3.13.0-79-generic 3.13.0-79.123 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829257 Title: package linux-image-3.13.0-79-generic 3.13.0-79.123 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 Status in linux package in Ubuntu: Confirmed Bug description: was upgrading from version 12.04 to version 14.04 when problem occurred. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-79-generic 3.13.0-79.123 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: james 3054 F pulseaudio Date: Wed May 15 06:42:06 2019 DuplicateSignature: package:linux-image-3.13.0-79-generic:3.13.0-79.123:subprocess installed post-installation script returned error exit status 17 ErrorMessage: subprocess installed post-installation script returned error exit status 17 HibernationDevice: RESUME=UUID=a46e9566-b234-42c1-8190-cf2faf38ac18 InstallationDate: Installed on 2014-04-08 (1863 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Dell Inc. Latitude D610 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-170-generic root=UUID=0af89630-e623-4dfc-82a4-e14418a93f26 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.17 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-3.13.0-79-generic 3.13.0-79.123 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17 UpgradeStatus: Upgraded to trusty on 2019-05-15 (0 days ago) dmi.bios.date: 10/02/2005 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0U8082 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd10/02/2005:svnDellInc.:pnLatitudeD610:pvr:rvnDellInc.:rn0U8082:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D610 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829257/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835040] Re: Touchpd not working properly on Linux
** Description changed: Installed Ubuntu 19.04 on a laptop, the touch pad is behaving abnormally. It's detected, but nothing seems to work, however working very normal with Windows 10. Laptop model - iBall CompBook M500 It's somewhat similar to this bug, probably using the same touchpad hardware too. - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757435 + https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825718 Attached some logs, with `i2c-hid.debug=1 hid.debug=1` the boot time kernel parameters added. Thanks. - --- + --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: arnab 931 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: arnab 931 F pulseaudio CurrentDesktop: LXQt DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-06-22 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: iBall iBall CompBook M500 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=88dcdd79-12d6-4052-8314-eb0074bbca8c ro quiet ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: - linux-restricted-modules-5.0.0-13-generic N/A - linux-backports-modules-5.0.0-13-generic N/A - linux-firmware1.178 + linux-restricted-modules-5.0.0-13-generic N/A + linux-backports-modules-5.0.0-13-generic N/A + linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: CC-14.1-BI-Y116AR400-AA54G-051-C dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio CRB dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 31 dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrCC-14.1-BI-Y116AR400-AA54G-051-C:bd07/25/2018:svniBall:pniBallCompBookM500:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnAptioCRB:rvrTobefilledbyO.E.M.:cvn:ct31:cvrTobefilledbyO.E.M.: dmi.product.family: Notebook dmi.product.name: iBall CompBook M500 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: iBall -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835040 Title: Touchpd not working properly on Linux Status in linux package in Ubuntu: Confirmed Bug description: Installed Ubuntu 19.04 on a laptop, the touch pad is behaving abnormally. It's detected, but nothing seems to work, however working very normal with Windows 10. Laptop model - iBall CompBook M500 It's somewhat similar to this bug, probably using the same touchpad hardware too. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825718 Attached some logs, with `i2c-hid.debug=1 hid.debug=1` the boot time kernel parameters added. Thanks. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: arnab 931 F pulseaudio CurrentDesktop: LXQt DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-06-22 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: iBall iBall CompBook M500 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=88dcdd79-12d6-4052-8314-eb0074bbca8c ro quiet ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: CC-14.1-BI-Y116AR400-AA54G-051-C dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio CRB dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 31 dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrCC-14.1-BI-Y116AR400-AA54G-051-C:bd07/25/2018:svniBall:pniBallCompBookM500:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnAptioCRB:rvrTobef
[Kernel-packages] [Bug 1835040] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1835040/+attachment/5275279/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835040 Title: Touchpd not working properly on Linux Status in linux package in Ubuntu: Confirmed Bug description: Installed Ubuntu 19.04 on a laptop, the touch pad is behaving abnormally. It's detected, but nothing seems to work, however working very normal with Windows 10. Laptop model - iBall CompBook M500 It's somewhat similar to this bug, probably using the same touchpad hardware too. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825718 Attached some logs, with `i2c-hid.debug=1 hid.debug=1` the boot time kernel parameters added. Thanks. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: arnab 931 F pulseaudio CurrentDesktop: LXQt DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-06-22 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: iBall iBall CompBook M500 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=88dcdd79-12d6-4052-8314-eb0074bbca8c ro quiet ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: CC-14.1-BI-Y116AR400-AA54G-051-C dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio CRB dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 31 dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrCC-14.1-BI-Y116AR400-AA54G-051-C:bd07/25/2018:svniBall:pniBallCompBookM500:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnAptioCRB:rvrTobefilledbyO.E.M.:cvn:ct31:cvrTobefilledbyO.E.M.: dmi.product.family: Notebook dmi.product.name: iBall CompBook M500 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: iBall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835040] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1835040/+attachment/5275278/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835040 Title: Touchpd not working properly on Linux Status in linux package in Ubuntu: Confirmed Bug description: Installed Ubuntu 19.04 on a laptop, the touch pad is behaving abnormally. It's detected, but nothing seems to work, however working very normal with Windows 10. Laptop model - iBall CompBook M500 It's somewhat similar to this bug, probably using the same touchpad hardware too. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825718 Attached some logs, with `i2c-hid.debug=1 hid.debug=1` the boot time kernel parameters added. Thanks. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: arnab 931 F pulseaudio CurrentDesktop: LXQt DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-06-22 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: iBall iBall CompBook M500 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=88dcdd79-12d6-4052-8314-eb0074bbca8c ro quiet ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: CC-14.1-BI-Y116AR400-AA54G-051-C dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio CRB dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 31 dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrCC-14.1-BI-Y116AR400-AA54G-051-C:bd07/25/2018:svniBall:pniBallCompBookM500:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnAptioCRB:rvrTobefilledbyO.E.M.:cvn:ct31:cvrTobefilledbyO.E.M.: dmi.product.family: Notebook dmi.product.name: iBall CompBook M500 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: iBall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835040] Re: Touchpd not working properly on Linux
apport information ** Tags added: apport-collected ** Description changed: Installed Ubuntu 19.04 on a laptop, the touch pad is behaving abnormally. It's detected, but nothing seems to work, however working very normal with Windows 10. Laptop model - iBall CompBook M500 It's somewhat similar to this bug, probably using the same touchpad hardware too. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757435 Attached some logs, with `i2c-hid.debug=1 hid.debug=1` the boot time kernel parameters added. Thanks. + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu27 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: arnab 931 F pulseaudio + CurrentDesktop: LXQt + DistroRelease: Ubuntu 19.04 + InstallationDate: Installed on 2019-06-22 (13 days ago) + InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) + MachineType: iBall iBall CompBook M500 + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=88dcdd79-12d6-4052-8314-eb0074bbca8c ro quiet + ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 + RelatedPackageVersions: + linux-restricted-modules-5.0.0-13-generic N/A + linux-backports-modules-5.0.0-13-generic N/A + linux-firmware1.178 + Tags: disco + Uname: Linux 5.0.0-13-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 07/25/2018 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: CC-14.1-BI-Y116AR400-AA54G-051-C + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: Aptio CRB + dmi.board.vendor: AMI Corporation + dmi.board.version: To be filled by O.E.M. + dmi.chassis.asset.tag: To be filled by O.E.M. + dmi.chassis.type: 31 + dmi.chassis.version: To be filled by O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrCC-14.1-BI-Y116AR400-AA54G-051-C:bd07/25/2018:svniBall:pniBallCompBookM500:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnAptioCRB:rvrTobefilledbyO.E.M.:cvn:ct31:cvrTobefilledbyO.E.M.: + dmi.product.family: Notebook + dmi.product.name: iBall CompBook M500 + dmi.product.sku: To be filled by O.E.M. + dmi.product.version: To be filled by O.E.M. + dmi.sys.vendor: iBall ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1835040/+attachment/5275277/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835040 Title: Touchpd not working properly on Linux Status in linux package in Ubuntu: Confirmed Bug description: Installed Ubuntu 19.04 on a laptop, the touch pad is behaving abnormally. It's detected, but nothing seems to work, however working very normal with Windows 10. Laptop model - iBall CompBook M500 It's somewhat similar to this bug, probably using the same touchpad hardware too. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825718 Attached some logs, with `i2c-hid.debug=1 hid.debug=1` the boot time kernel parameters added. Thanks. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: arnab 931 F pulseaudio CurrentDesktop: LXQt DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-06-22 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: iBall iBall CompBook M500 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=88dcdd79-12d6-4052-8314-eb0074bbca8c ro quiet ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: CC-14.1-BI-Y116AR400-AA54G-051-C dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Aptio CRB dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 31 dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrCC-14.1-BI-Y116AR400-AA54G-051-C:bd07/25/2018:svniBall:pniBallCompBookM500:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnAptioCRB:rvrTobefilledbyO.E.M.:cvn:ct31:cvrTobefilledbyO.E.M.: dmi.product.family: Notebook dmi.product.name: iBall CompBook M500 dmi.product.sku:
[Kernel-packages] [Bug 1835190] Re: linux: 3.13.0-172.223 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835189 (precise/linux-lts-trusty) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 08:33 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:building + promote-to-proposed: Ongoing -- builds not complete in ppa main:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835190 Title: linux: 3.13.0-172.223 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835189 (precise/linux-lts-trusty) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 08:33 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835190/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821625] Re: systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-seccomp)
$ reverse-depends -l -r bionic -b libseccomp-dev |& xargs
apt chrony docker.io flatpak gnome-desktop3
golang-github-seccomp-libseccomp-golang kscreenlocker lxc man-db ocserv
qemu snapd stenographer systemd tor tracker-miners usbguard
none of those packages reference pkey_mprotect except systemd, qemu, and snapd;
systemd and qemu are discussed above. The snapd package simply lists
pkey_mprotect in a list of syscalls and doesn't appear to compile-in the
syscall number, and so should not be affected:
ddstreet@thorin:~/bugs/lp1821625/sym-check/snapd/snapd-2.39.2+18.04$ grep -r
pkey_mprotect
cmd/snap-seccomp/syscalls/syscalls.go: "pkey_mprotect",
additionally, snapd is updated quite often, so even if it is affected
there should be no need for a no-change rebuild.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1821625
Title:
systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-
seccomp)
Status in libseccomp package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Invalid
Status in libseccomp source package in Bionic:
Invalid
Status in linux source package in Bionic:
Fix Committed
Status in systemd source package in Bionic:
Invalid
Bug description:
Starting with systemd 237-3ubuntu10.14, the testcase test-seccomp is
failing on Bionic on ppc64el with the error messages:
Operating on architecture: ppc
Failed to add n/a() rule for architecture ppc, skipping: Bad address
Operating on architecture: ppc64
Failed to add n/a() rule for architecture ppc64, skipping: Bad address
Operating on architecture: ppc64-le
Failed to add n/a() rule for architecture ppc64-le, skipping: Numerical
argument out of domain
Assertion 'p == MAP_FAILED' failed at ../src/test/test-seccomp.c:413,
function test_memory_deny_write_execute_mmap(). Aborting.
memoryseccomp-mmap terminated by signal ABRT.
Assertion 'wait_for_terminate_and_check("memoryseccomp-mmap", pid, WAIT_LOG)
== EXIT_SUCCESS' failed at ../src/test/test-seccomp.c:427, function
test_memory_deny_write_execute_mmap(). Aborting.
Aborted (core dumped)
FAIL: test-seccomp (code: 134)
Full logs at:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190302_025135_d0e38@/log.gz
The testcase passed with systemd version 237-3ubuntu10.13 running on the same
4.15.0-45 kernel on ppc64el:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190228_154406_6b12f@/log.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1821625/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Landed to upstream as commit 807588ac92018, sru-ed to Bionic as 459448830a9b0 and Cosmic as commit 35e4595ea550f in bug 1801931. Disco or newer has it automatically. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Confirmed Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Fix Released Bug description: ===SRU Justification=== Hantick touchpad stops working after reboot. [Fix] Disable runtime power management for the touchpad. [Test] User confirmed it fixed the issue. Some users reported it doesn't work for them, I'll ask them to file new bugs for different touchpads. [Regression Potential] Low. Disable runtime power management doesn't affect devivce's funtionality. In general desktop usage the graphical session opens the touchpad HID device so the touchpad never get runtime suspended, so it won't hurt power in this case. ===Original Bug Report=== On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821625] Re: systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-seccomp)
> Per [1] this symbol is present in: firejail, elogind, valgrind, glibc, musl, > linux, > systemd, strace, stress-ng, libseccomp, qemu tl;dr: it looks like glibc and stress-ng are the only packages from that list that might need a rebuild, but as with systemd, neither seem important enough to warrant a special no-change rebuild. They will pick up the new syscall value whenever they are next uploaded for any other bugfix (after the current bionic -proposed kernel is promoted to -updates). details: elogind: not included in bionic firejail: it does use SYS_pkey_mprotect (which is defined as __NR_pkey_mprotect): ddstreet@thorin:~/bugs/lp1821625/sym-check/firejail/firejail-0.9.52$ grep -r pkey_mprotect src/man/firejail.txt:the arguments of mmap, mmap2, mprotect, pkey_mprotect and shmat system src/fseccomp/seccomp.c: // same for pkey_mprotect(,,PROT_EXEC), where available src/fseccomp/seccomp.c:#ifdef SYS_pkey_mprotect src/fseccomp/seccomp.c: BPF_JUMP(BPF_JMP+BPF_JEQ+BPF_K, SYS_pkey_mprotect, 0, 5), however, the latest build available: https://launchpad.net/ubuntu/+source/firejail/0.9.52-2 for ppc64el: https://launchpad.net/ubuntu/+source/firejail/0.9.52-2/+build/13948498 was built with libseccomp2, not libseccomp-dev (which provides the problematic public header file): Get:57 http://ftpmaster.internal/ubuntu bionic/main ppc64el libseccomp2 ppc64el 2.3.1-2.1ubuntu3 [47.2 kB] additionally, it was built with libseccomp2 version 2.3.1-2.1ubuntu3, which was earlier than when the problematic patch was added (per this bug comment 1). So no need to recompile. musl: appears to only define __NR_pkey_mprotect in its embedded headers, and doesn't include ppc; no need to require recompile: ddstreet@thorin:~/bugs/lp1821625/sym-check/musl/musl-1.1.19$ grep -r pkey_mprotect arch/mipsn32/bits/syscall.h.in:#define __NR_pkey_mprotect 6327 arch/mips64/bits/syscall.h.in:#define __NR_pkey_mprotect5323 arch/arm/bits/syscall.h.in:#define __NR_pkey_mprotect 394 arch/aarch64/bits/syscall.h.in:#define __NR_pkey_mprotect 288 arch/or1k/bits/syscall.h.in:#define __NR_pkey_mprotect 288 arch/x32/bits/syscall.h.in:#define __NR_pkey_mprotect (0x4000 + 329) arch/i386/bits/syscall.h.in:#define __NR_pkey_mprotect 380 arch/x86_64/bits/syscall.h.in:#define __NR_pkey_mprotect 329 arch/mips/bits/syscall.h.in:#define __NR_pkey_mprotect 4363 arch/microblaze/bits/syscall.h.in:#define __NR_pkey_mprotect 395 qemu: as @cpaelzer said, just in its embedded headers; no need to recompile. strace: does appear to use pkey_mprotect, but the latest ppc64el build: https://launchpad.net/ubuntu/+source/strace/4.21-1ubuntu1/+build/14750033 did not build with libseccomp-dev (or libseccomp2) at all. Additionally, it was built 2018-04-11, while the problematic patch was added to libseccomp 2019-02-12. No need to rebuild. stress-ng: it does include the number in its skip_syscalls list, of syscalls to skip while running the 'enosys' stressor: ddstreet@thorin:~/bugs/lp1821625/sym-check/stress-ng/stress-ng-0.09.25$ grep -r pkey_mprotect stress-enosys.c:#if defined(SYS_pkey_mprotect) stress-enosys.c:SYS_pkey_mprotect, stress-enosys.c:#if defined(__NR_pkey_mprotect) stress-enosys.c:__NR_pkey_mprotect, This stressor appears to call all syscall numbers that it thinks are not supported/implemented. In this case, whether __NR_pkey_mprotect is a negative number (if built with libseccomp-dev header), or not defined, the end result is the same: stress-ng will not skip the *real* pkey_mprotect syscall number. However, running 'sudo stress-ng --enosys 1' on a test ppc64el instance, at kernel 4.15.0-54 or -55, does not appear to have any negative effect. So I don't think stress-ng needs to be no-change rebuilt with the new kernel headers; it should be ok to just let it pick up the correct value whenever it is next uploaded for other reasons. valgrind: referenced only in a commented-out table in arm64-specific file; no rebuild needed. ddstreet@thorin:~/bugs/lp1821625/sym-check/valgrind/valgrind-3.13.0$ grep -r pkey_mprotect coregrind/m_syswrap/syswrap-arm64-linux.c: // (__NR_pkey_mprotect, sys_ni_syscall),// 288 glibc: it does reference pkey_mprotect. However, the latest build for bionic was on 2018-04-16, before the problematic patch was added to libseccomp. It appears that glibc's pkey_mprotect will simply return ENOSYS for the current version: int pkey_mprotect (void *addr, size_t len, int prot, int pkey)
[Kernel-packages] [Bug 1835040] Re: Touchpd not working properly on Linux
Please run `apport-collect`. ** This bug is no longer a duplicate of bug 1776155 Touchpad detected as SYNA3602, does not work at all. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835040 Title: Touchpd not working properly on Linux Status in linux package in Ubuntu: Confirmed Bug description: Installed Ubuntu 19.04 on a laptop, the touch pad is behaving abnormally. It's detected, but nothing seems to work, however working very normal with Windows 10. Laptop model - iBall CompBook M500 It's somewhat similar to this bug, probably using the same touchpad hardware too. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757435 Attached some logs, with `i2c-hid.debug=1 hid.debug=1` the boot time kernel parameters added. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835438] Re: linux-azure: 4.18.0-1025.27 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-cosmic ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835436 (bionic/linux-azure) -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1834904 - phase: Packaging - phase-changed: Thursday, 04. July 2019 19:05 UTC + phase: Ready for Promote to Proposed + phase-changed: Friday, 05. July 2019 14:06 UTC reason: - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1835438 Title: linux-azure: 4.18.0-1025.27 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Cosmic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835436 (bionic/linux-azure) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834904 phase: Ready for Promote to Proposed phase-changed: Friday, 05. July 2019 14:06 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835438/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835436] Re: linux-azure: 4.18.0-1025.27~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834885 (azure-kernel), bug 1834887 (linux-azure-edge), bug 1835435 (azure-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1835438 - phase: Holding before Promote to Proposed - phase-changed: Thursday, 04. July 2019 21:13 UTC + phase: Ready for Promote to Proposed + phase-changed: Friday, 05. July 2019 14:14 UTC reason: - promote-to-proposed: Holding -- master bug not ready for proposed + promote-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1835436 Title: linux-azure: 4.18.0-1025.27~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834885 (azure-kernel), bug 1834887 (linux-azure- edge), bug 1835435 (azure-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1835438 phase: Ready for Promote to Proposed phase-changed: Friday, 05. July 2019 14:14 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835190] Re: linux: 3.13.0-172.223 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835189 (precise/linux-lts-trusty) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 08:33 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa signed:building,main:building + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835190 Title: linux: 3.13.0-172.223 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835189 (precise/linux-lts-trusty) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 08:33 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835190/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835540] [NEW] Confusing "modinfo: ERROR: missing module or filename." during normal operation
Public bug reported: I just installed a new kernel, and when I did so my Nvidia kernel modules were handled through DKMS, as you would expect. However, during what I believe is normal operation, I saw the following stanza (repeated for several nvidia .ko files): nvidia.ko: Running module version sanity check. modinfo: ERROR: missing module or filename. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.0.0-20-generic/updates/dkms/ The "ERROR" in here gave me pause, but I _believe_ that's an expected message for a new kernel. It would make for a less troubling user experience if we didn't print out "ERROR" in all caps when there is no error at all. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: dkms 2.7.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: i3 Date: Fri Jul 5 09:52:41 2019 InstallationDate: Installed on 2019-05-07 (58 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: dkms UpgradeStatus: Upgraded to eoan on 2019-05-08 (57 days ago) ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1835540 Title: Confusing "modinfo: ERROR: missing module or filename." during normal operation Status in dkms package in Ubuntu: New Bug description: I just installed a new kernel, and when I did so my Nvidia kernel modules were handled through DKMS, as you would expect. However, during what I believe is normal operation, I saw the following stanza (repeated for several nvidia .ko files): nvidia.ko: Running module version sanity check. modinfo: ERROR: missing module or filename. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.0.0-20-generic/updates/dkms/ The "ERROR" in here gave me pause, but I _believe_ that's an expected message for a new kernel. It would make for a less troubling user experience if we didn't print out "ERROR" in all caps when there is no error at all. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: dkms 2.7.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: i3 Date: Fri Jul 5 09:52:41 2019 InstallationDate: Installed on 2019-05-07 (58 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: dkms UpgradeStatus: Upgraded to eoan on 2019-05-08 (57 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1835540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783961] Re: CONFIG_KVM is disabled for linux-raspi2 (aarch64)
just as a followup ... better ignore my comment above ... KVM is indeed not KMS ... sorry for causing confusion here -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1783961 Title: CONFIG_KVM is disabled for linux-raspi2 (aarch64) Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: In contrast to the Linux kernel for x86_64, the CONFIG_KVM option is disabled for the "linux-raspi2" kernel (version 4.15.0-1016-raspi2 aarch64) on Ubuntu 18.04. This prevents running QEMU with the -enable-kvm option to use hardware virtualization capabilities of the CPU. I have recompiled the kernel with CONFIG_KVM set and could successfully run QEMU with -enable-kvm on my Raspberry Pi 3 B+ afterwards. In my opinion, there is no reason for not activating CONFIG_KVM in the official raspi2 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1783961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835040] Re: Touchpd not working properly on Linux
*** This bug is a duplicate of bug 1776155 *** https://bugs.launchpad.net/bugs/1776155 ** This bug has been marked a duplicate of bug 1776155 Touchpad detected as SYNA3602, does not work at all. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835040 Title: Touchpd not working properly on Linux Status in linux package in Ubuntu: Confirmed Bug description: Installed Ubuntu 19.04 on a laptop, the touch pad is behaving abnormally. It's detected, but nothing seems to work, however working very normal with Windows 10. Laptop model - iBall CompBook M500 It's somewhat similar to this bug, probably using the same touchpad hardware too. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757435 Attached some logs, with `i2c-hid.debug=1 hid.debug=1` the boot time kernel parameters added. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69
It seems it's the Gnome extension GSConnect (https://extensions.gnome.org/extension/1319/gsconnect/) in my case. Removed that and had no freezes since. Will examine further. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1785964 Title: Unable to unlock the desktop session: systemd-logind: got pause for 13:69 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Confirmed Bug description: When this issue happens, you won't be able to unlock your desktop session (VT works fine). This happened twice today for me, one is after a suspend, one is just a screen lock. Not sure what is the trigger yet. Syndrome: On the login screen after typing the correct password, you will see a small circle keep spinning and that's it. I need to restart my computer to get it back to normal. In the syslog this error message looks fishy: Aug 8 10:44:57 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' failed This is part of the syslog fetching from a VT after a GUI unlock attempt (session 24 is the desktop login attempt): Aug 8 10:44:42 Leggiero systemd[1]: Started Session 24 of user sam. Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 226:0 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) AIGLX: Resuming AIGLX clients after VT switch Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): EDID vendor "AUO", prod id 4204 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Printing DDC gathered Modelines: Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Modeline "1366x768"x0.0 76.20 1366 1404 1426 1590 768 771 777 798 +hsync -vsync (47.9 kHz eP) Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Modeline "1366x768"x0.0 76.20 1366 1404 1426 1988 768 771 777 798 +hsync -vsync (38.3 kHz e) Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:78 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - Dell WMI hotkeys: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - Dell WMI hotkeys: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:66 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2 - Sleep Button: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2 - Sleep Button: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:79 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - Integrated_Webcam_HD: Integrate: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - Integrated_Webcam_HD: Integrate: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:68 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4 - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4 - AT Translated Set 2 keyboard: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:67 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3 - Power Button: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3 - Power Button: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:71 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7 - AlpsPS/2 ALPS GlidePoint: is tagged by udev as: Touchpad Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7 - AlpsPS/2 ALPS GlidePoint: device is a touchpad Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:72 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8 - DELL Wireless hotkeys: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8 - DELL Wireless hotkeys: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) libinput: PixArt Microsoft USB Optical Mouse: SetProperty on 286 called but device is disabled. Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: This driver cannot change properties on a disabled device Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:65 Aug 8 10:44:55 Le
[Kernel-packages] [Bug 1835190] Re: linux: 3.13.0-172.223 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835189 (precise/linux-lts-trusty) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 08:33 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:building + promote-to-proposed: Ongoing -- builds not complete in ppa signed:building,main:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835190 Title: linux: 3.13.0-172.223 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835189 (precise/linux-lts-trusty) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 08:33 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa signed:building,main:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835190/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834935] Re: linux-gcp: 4.15.0-1037.39~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834932 (gcp-kernel), bug 1834934 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834936 - phase: Testing - phase-changed: Friday, 05. July 2019 11:43 UTC + phase: Signoff + phase-changed: Friday, 05. July 2019 13:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1834935 Title: linux-gcp: 4.15.0-1037.39~16.04.1 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834932 (gcp-kernel), bug 1834934 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834936 phase: Signoff phase-changed: Friday, 05. July 2019 13:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821625] Re: systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-seccomp)
Marking this bug as Invalid for libseccomp; I still disagree with their
upstream decision re: their header file, but it doesn't appear any
rebuild or SRU code change is needed for it for this bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1821625
Title:
systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-
seccomp)
Status in libseccomp package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Invalid
Status in libseccomp source package in Bionic:
Invalid
Status in linux source package in Bionic:
Fix Committed
Status in systemd source package in Bionic:
Invalid
Bug description:
Starting with systemd 237-3ubuntu10.14, the testcase test-seccomp is
failing on Bionic on ppc64el with the error messages:
Operating on architecture: ppc
Failed to add n/a() rule for architecture ppc, skipping: Bad address
Operating on architecture: ppc64
Failed to add n/a() rule for architecture ppc64, skipping: Bad address
Operating on architecture: ppc64-le
Failed to add n/a() rule for architecture ppc64-le, skipping: Numerical
argument out of domain
Assertion 'p == MAP_FAILED' failed at ../src/test/test-seccomp.c:413,
function test_memory_deny_write_execute_mmap(). Aborting.
memoryseccomp-mmap terminated by signal ABRT.
Assertion 'wait_for_terminate_and_check("memoryseccomp-mmap", pid, WAIT_LOG)
== EXIT_SUCCESS' failed at ../src/test/test-seccomp.c:427, function
test_memory_deny_write_execute_mmap(). Aborting.
Aborted (core dumped)
FAIL: test-seccomp (code: 134)
Full logs at:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190302_025135_d0e38@/log.gz
The testcase passed with systemd version 237-3ubuntu10.13 running on the same
4.15.0-45 kernel on ppc64el:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190228_154406_6b12f@/log.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1821625/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821625] Re: systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-seccomp)
> @Dan did that already contain the fix you expect or would considering
a seccomp be useful?
For libseccomp, it looks like it doesn't need a rebuild; it appears to
only reference the symbol in its header (which is what causes this
problem for other packages that pull in that header); in its code, the
only reference is where its syscall number is defined is inside its
ppc64_syscall_table (and ppc_syscall_table), where it is defined
correctly.
ddstreet@thorin:~/bugs/lp1821625/sym-check/libseccomp/libseccomp-2.4.1$ grep -r
pkey_mprotect
include/seccomp.h.in:#define __PNR_pkey_mprotect-10201
include/seccomp.h.in:#ifndef __NR_pkey_mprotect
include/seccomp.h.in:#define __NR_pkey_mprotect __PNR_pkey_mprotect
include/seccomp.h.in:#endif /* __NR_pkey_mprotect */
include/seccomp.h:#define __PNR_pkey_mprotect -10201
include/seccomp.h:#ifndef __NR_pkey_mprotect
include/seccomp.h:#define __NR_pkey_mprotect__PNR_pkey_mprotect
include/seccomp.h:#endif /* __NR_pkey_mprotect */
src/arch-ppc-syscalls.c:{ "pkey_mprotect", 386 },
src/arch-x32-syscalls.c:{ "pkey_mprotect", (X32_SYSCALL_BIT + 329) },
src/arch-mips-syscalls.c: { "pkey_mprotect", (__SCMP_NR_BASE + 363) },
src/arch-x86-syscalls.c:{ "pkey_mprotect", 380 },
src/arch-s390-syscalls.c: { "pkey_mprotect", __PNR_pkey_mprotect },
src/arch-parisc-syscalls.c: { "pkey_mprotect", __PNR_pkey_mprotect },
src/arch-s390x-syscalls.c: { "pkey_mprotect", __PNR_pkey_mprotect },
src/arch-ppc64-syscalls.c: { "pkey_mprotect", 386 },
src/arch-aarch64-syscalls.c:{ "pkey_mprotect", 288 },
src/arch-arm-syscalls.c:{ "pkey_mprotect", (__SCMP_NR_BASE + 394) },
src/arch-mips64-syscalls.c: { "pkey_mprotect", (__SCMP_NR_BASE + 323) },
src/arch-x86_64-syscalls.c: { "pkey_mprotect", 329 },
src/arch-mips64n32-syscalls.c: { "pkey_mprotect", (__SCMP_NR_BASE + 327) },
I still don't understand why libseccomp ever decided to define
__NR_pkey_mprotect to a negative number (if the kernel header doesn't define
it) in its public header file. IMHO that should be done in its code, or at
least in a private header file.
** Changed in: libseccomp (Ubuntu Bionic)
Status: Incomplete => Invalid
** Changed in: libseccomp (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1821625
Title:
systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-
seccomp)
Status in libseccomp package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Invalid
Status in libseccomp source package in Bionic:
Invalid
Status in linux source package in Bionic:
Fix Committed
Status in systemd source package in Bionic:
Invalid
Bug description:
Starting with systemd 237-3ubuntu10.14, the testcase test-seccomp is
failing on Bionic on ppc64el with the error messages:
Operating on architecture: ppc
Failed to add n/a() rule for architecture ppc, skipping: Bad address
Operating on architecture: ppc64
Failed to add n/a() rule for architecture ppc64, skipping: Bad address
Operating on architecture: ppc64-le
Failed to add n/a() rule for architecture ppc64-le, skipping: Numerical
argument out of domain
Assertion 'p == MAP_FAILED' failed at ../src/test/test-seccomp.c:413,
function test_memory_deny_write_execute_mmap(). Aborting.
memoryseccomp-mmap terminated by signal ABRT.
Assertion 'wait_for_terminate_and_check("memoryseccomp-mmap", pid, WAIT_LOG)
== EXIT_SUCCESS' failed at ../src/test/test-seccomp.c:427, function
test_memory_deny_write_execute_mmap(). Aborting.
Aborted (core dumped)
FAIL: test-seccomp (code: 134)
Full logs at:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190302_025135_d0e38@/log.gz
The testcase passed with systemd version 237-3ubuntu10.13 running on the same
4.15.0-45 kernel on ppc64el:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190228_154406_6b12f@/log.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1821625/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834899] Re: linux-gcp: 4.18.0-1016.17 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834896 (bionic/linux-gcp-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834904 phase: Testing phase-changed: Friday, 05. July 2019 11:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1834899 Title: linux-gcp: 4.18.0-1016.17 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834896 (bionic/linux-gcp-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834904 phase: Testing phase-changed: Friday, 05. July 2019 11:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834899/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835190] Re: linux: 3.13.0-172.223 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835189 (precise/linux-lts-trusty) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 08:33 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa signed:building,main:building + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835190 Title: linux: 3.13.0-172.223 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835189 (precise/linux-lts-trusty) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 08:33 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835190/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1443924]
https://www.techjockey.com/category/jewellery-software -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1443924 Title: 1814:0201 ieee80211 phy0: rt2x00queue_flush_queue:Warning - Queue 0 failed to flush Status in Linux: Won't Fix Status in linux package in Ubuntu: Triaged Bug description: Philips i386 PC with rt2x00 pci is suffering loss of WiFi connectivity after installing 15.04 Beta. The system did work correctly with older Ubuntu versions (like 12.04) and had this problem show up after upgrading to Trusty (as I already reported in bug #1318837). Using Trusty the problem went away when switching from the stock 3.13.0-XX-generic kernel to builds of newer kernels (like 3.14.1-031401). Now the same problem shows up again after installing Vivid Beta. It seems to be the same problem reported for other Ubuntu releases (see bugs #1318837 and #1383555) and also the same problem of this upstream kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=61621 Someone on kernel's bug mentions turning off MSI interrupts and I can confirm it did change the situation: - normally the system looses WiFi connectivity mere seconds after boot (eg. can't ping anything after boot) - if I boot with "pci=nomsi" the system will remain connected to the WiFi for a much longer period (eg. I am able to apt-get install something after boot) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-extra-3.19.0-13-generic 3.19.0-13.13 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic i686 ApportVersion: 2.17-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luca 1997 F pulseaudio CurrentDesktop: LXDE Date: Tue Apr 14 14:19:19 2015 HibernationDevice: RESUME=UUID=cbd1e136-ffc4-48b9-b2aa-c15264b9b132 MachineType: Freeline Freeline Series ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-13-generic root=UUID=6110f881-b32b-426d-910a-c63b355c179c ro quiet splash vt.handoff=7 pci=nomsi RelatedPackageVersions: linux-restricted-modules-3.19.0-13-generic N/A linux-backports-modules-3.19.0-13-generic N/A linux-firmware 1.143 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2004 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: Freeline Series dmi.board.vendor: Freeline dmi.board.version: Ver1.0 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd10/29/2004:svnFreeline:pnFreelineSeries:pvrVer1.0:rvnFreeline:rnFreelineSeries:rvrVer1.0:cvn:ct3:cvr: dmi.product.name: Freeline Series dmi.product.version: Ver1.0 dmi.sys.vendor: Freeline To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1443924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834930] Re: linux-aws: 4.15.0-1044.46 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834929 (xenial/linux-aws-hwe) derivatives: bug 1834927 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 - phase: Promote to Proposed - phase-changed: Friday, 05. July 2019 11:39 UTC + phase: Testing + phase-changed: Friday, 05. July 2019 12:09 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1834930 Title: linux-aws: 4.15.0-1044.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834929 (xenial/linux-aws-hwe) derivatives: bug 1834927 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Testing phase-changed: Friday, 05. July 2019 12:09 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834883] Re: linux-aws: 4.18.0-1021.25 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834882 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834904 phase: Testing phase-changed: Thursday, 04. July 2019 13:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED + automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1834883 Title: linux-aws: 4.18.0-1021.25 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834882 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834904 phase: Testing phase-changed: Thursday, 04. July 2019 13:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834948] Re: linux-azure: 4.15.0-1051.56~14.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1834950 phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 08:43 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa signed:building + promote-to-proposed: Pending -- builds not complete in ppa signed:retry-needed variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1834948 Title: linux-azure: 4.15.0-1051.56~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1834950 phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 08:43 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa signed:retry-needed variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834886] Re: linux-aws: 5.0.0-1011.12 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Testing phase-changed: Wednesday, 03. July 2019 12:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED + automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1834886 Title: linux-aws: 5.0.0-1011.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Testing phase-changed: Wednesday, 03. July 2019 12:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834886/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828166] Comment bridged from LTC Bugzilla
--- Comment From tmri...@de.ibm.com 2019-07-05 07:48 EDT---
I have tried to last 2 days to find a patch series to apply the required patch
which failed above.
The difference between upstream linux kernel 5.2.0rc7 and the ubuntu
18.04 kernel I downloaded from
url = git://kernel.ubuntu.com/ubuntu/ubuntu-bionic
branch master-next
in regards to the function machine__create_kernel_maps() in file
tools/perf/util/machine.c
is very big.
Command
git log --oneline '-L: machine__create_kernel_maps:tools/perf/util/machine.c'
identifies the difference of applied patches. The following patches
are missing in ubuntu version:
Commit-ID Description
ed9adb2035b5 perf machine: Read also the end of the kernel
977c7a6d1e26 perf machine: Update kernel map address and re-order properly
1c5aae7710bbperf machine: Create maps for x86 PTI entry trampolines
3183f8ca304f perf symbols: Unify symbol maps
ee05d21791db perf machine: Set main kernel end address properly
1fb87b8e9599perf machine: Don't search for active kernel start in
__machine__create_kernel_maps
Already the first patch missing:
Commit-ID Description
1fb87b8e9599perf machine: Don't search for active kernel start in
__machine__create_kernel_maps
does not apply because in this patch a function named machine__set_kernel_mmap()
is moved in file perf/tools/util/machine.c but this function is missing
in the ubuntu 18.04 master-next tree.
It turned out that this tree also misses patch:
Commit-ID Description
05db6ff73d80 perf machine: Generalize machine__set_kernel_mmap()
Having found the starting patch, I can applied the following patch sequence:
root@s8360046:~/ubuntu-bionic# patch -p1 <
../patches/0001-perf-machine-Generalize- machine__set_kernel_mmap.patch
patching file tools/perf/util/machine.c
Hunk #1 succeeded at 1255 (offset -7 lines).
Hunk #2 succeeded at 1370 (offset -5 lines).
root@s8360046:~/ubuntu-bionic# patch -p1 <
../patches/0001-perf-machine-Don-t-search-for-active-kernel-start-in.patch
patching file tools/perf/util/machine.c
Hunk #1 succeeded at 849 (offset -7 lines).
Hunk #2 succeeded at 861 (offset -7 lines).
Hunk #3 succeeded at 1212 (offset -7 lines).
Hunk #4 succeeded at 1254 (offset -7 lines).
patching file tools/perf/util/machine.h
Hunk #1 succeeded at 239 (offset 1 line).
root@s8360046:~/ubuntu-bionic# patch -p1 <
../patches/0001-perf-machine-Set-main-kernel-end-address-properly.patch
patching file tools/perf/util/machine.c
Hunk #1 succeeded at 1020 (offset 1 line).
Hunk #2 succeeded at 1227 (offset 1 line).
Hunk #3 succeeded at 1254 (offset 1 line).
root@s8360046:~/ubuntu-bionic# patch -p1 <
../patches/0001-perf-machine-Update-kernel-map-address-and-re-order-.patch
patching file tools/perf/util/machine.c
Hunk #1 succeeded at 1223 with fuzz 1 (offset -198 lines).
Hunk #2 succeeded at 1269 with fuzz 1 (offset -198 lines).
Hunk #3 succeeded at 1381 (offset -226 lines).
root@s8360046:~/ubuntu-bionic# patch -p1 <
../patches/0001-perf-machine-Read-also-the-end-of-the-kernel.patch
patching file tools/perf/util/machine.c
Hunk #1 succeeded at 821 (offset -103 lines).
Hunk #2 succeeded at 847 (offset -103 lines).
Hunk #3 succeeded at 1248 (offset -199 lines).
Hunk #4 FAILED at 1466.
Hunk #5 FAILED at 1478.
2 out of 5 hunks FAILED -- saving rejects to file tools/perf/util/machine.c.rej
root@s8360046:~/ubuntu-bionic#
The last patch is the one we need and it fails.
Refering to above patch list, I do not want to apply these two patches:
Commit-ID Description
1c5aae7710bb perf machine: Create maps for x86 PTI entry trampolines
3183f8ca304fperf symbols: Unify symbol maps
Both patches require tremendous change in the symbol table code of perf and
introduce trampoline functionality to handle security fixes in the kernel for
x86.
If you want to apply these two patch, better upgrade the perf tool completely.
Appling the last patch, the last 2 hunks fail because of missing context.
The changes itself are trivial, but I can not do the changes as the code of the
last patch is not from IBM.
Here is the difference from the file tools/perf/util/machine.c.rej:
-- tools/perf/util/machine.c
+++ tools/perf/util/machine.c
@@ -1466,9 +1472,9 @@ int machine__create_kernel_maps(struct machine *machine)
"continuing anyway...\n", machine->pid);
}
- if (!machine__get_running_kernel_start(machine, &name, &addr)) {
+ if (!machine__get_running_kernel_start(machine, &name, &start, &end)) {
if (name &&
- map__set_kallsyms_ref_reloc_sym(machine->vmlinux_map, name,
addr)) {
+ map__set_kallsyms_ref_reloc_sym(machine->vmlinux_map, name,
start)) {
machine__destroy_kernel_maps(machine);
ret = -1;
goto out_put;
@@ -1478,16 +1484,19 @@ int machine__create_kernel_maps(struct machine *machine)
* we have a real start address now, so re-order the kmaps
* assume it's the last in the kmaps
*/
- machine__update_kernel_mmap(machine, addr, ~0ULL);
+
[Kernel-packages] [Bug 1835167] Re: Everything is faster if you place image with wide image ratio in fullscreen, zoom in and skip to next window for example with Alt-TAB
** No longer affects: linux (Ubuntu) ** Also affects: xfwm4 Importance: Undecided Status: New ** No longer affects: linux (Fedora) ** Bug watch added: Red Hat Bugzilla #1726250 https://bugzilla.redhat.com/show_bug.cgi?id=1726250 ** Also affects: fedora via https://bugzilla.redhat.com/show_bug.cgi?id=1726250 Importance: Unknown Status: Unknown ** Summary changed: - Everything is faster if you place image with wide image ratio in fullscreen, zoom in and skip to next window for example with Alt-TAB + Alt-TAB is faster if you place horizontally maximized window that exceeds a bit screen width underneath -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835167 Title: Alt-TAB is faster if you place horizontally maximized window that exceeds a bit screen width underneath Status in Xfwm4: New Status in Fedora: Unknown Bug description: Place wide ratio image in fullscreen, zoom in. Skip to next window. This seems like serious performance bug maybe exposing mistake in windows geometry logic somewhere. To manage notifications about this bug go to: https://bugs.launchpad.net/xfwm4/+bug/1835167/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834899] Re: linux-gcp: 4.18.0-1016.17 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834896 (bionic/linux-gcp-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834904 - phase: Promote to Proposed - phase-changed: Friday, 05. July 2019 08:05 UTC + phase: Testing + phase-changed: Friday, 05. July 2019 11:36 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Pending -- packages copied to Proposed signed:queued + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1834899 Title: linux-gcp: 4.18.0-1016.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834896 (bionic/linux-gcp-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834904 phase: Testing phase-changed: Friday, 05. July 2019 11:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834899/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834908] Re: linux-aws: 4.4.0-1088.99 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834907 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834918 - phase: Promote to Proposed - phase-changed: Friday, 05. July 2019 08:36 UTC + phase: Signoff + phase-changed: Friday, 05. July 2019 11:36 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- review in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1834908 Title: linux-aws: 4.4.0-1088.99 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834907 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834918 phase: Signoff phase-changed: Friday, 05. July 2019 11:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834908/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834935] Re: linux-gcp: 4.15.0-1037.39~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834932 (gcp-kernel), bug 1834934 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834936 - phase: Promote to Proposed - phase-changed: Friday, 05. July 2019 08:42 UTC + phase: Testing + phase-changed: Friday, 05. July 2019 11:43 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- review in progress + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1834935 Title: linux-gcp: 4.15.0-1037.39~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834932 (gcp-kernel), bug 1834934 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834936 phase: Testing phase-changed: Friday, 05. July 2019 11:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834930] Re: linux-aws: 4.15.0-1044.46 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834929 (xenial/linux-aws-hwe) derivatives: bug 1834927 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 - phase: Ready for Promote to Proposed - phase-changed: Thursday, 04. July 2019 19:08 UTC + phase: Promote to Proposed + phase-changed: Friday, 05. July 2019 11:39 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1834930 Title: linux-aws: 4.15.0-1044.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834929 (xenial/linux-aws-hwe) derivatives: bug 1834927 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Promote to Proposed phase-changed: Friday, 05. July 2019 11:39 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834948] Re: linux-azure: 4.15.0-1051.56~14.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1834950 phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 08:43 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa meta:building,signed:building,main:building + promote-to-proposed: Ongoing -- builds not complete in ppa signed:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1834948 Title: linux-azure: 4.15.0-1051.56~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1834950 phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 08:43 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa signed:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835270] Re: linux: 3.2.0-142.189 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: New => Invalid ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- - phase: Ready for Packaging - phase-changed: Wednesday, 03. July 2019 16:14 UTC + phase: Packaging + phase-changed: Friday, 05. July 2019 11:32 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-lbm: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835270 Title: linux: 3.2.0-142.189 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lbm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Packaging phase-changed: Friday, 05. July 2019 11:32 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lbm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834883] Re: linux-aws: 4.18.0-1021.25 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834882 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834904 phase: Testing phase-changed: Thursday, 04. July 2019 13:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1834883 Title: linux-aws: 4.18.0-1021.25 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834882 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834904 phase: Testing phase-changed: Thursday, 04. July 2019 13:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834886] Re: linux-aws: 5.0.0-1011.12 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Testing phase-changed: Wednesday, 03. July 2019 12:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1834886 Title: linux-aws: 5.0.0-1011.12 -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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Testing phase-changed: Wednesday, 03. July 2019 12:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834886/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835190] Re: linux: 3.13.0-172.223 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835189 (precise/linux-lts-trusty) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 08:33 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa meta:building,signed:building,main:building + promote-to-proposed: Ongoing -- builds not complete in ppa signed:building,main:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835190 Title: linux: 3.13.0-172.223 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835189 (precise/linux-lts-trusty) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Friday, 05. July 2019 08:33 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa signed:building,main:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835190/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835270] Re: linux: 3.2.0-142.189 -proposed tracker
** Summary changed: - linux: -proposed tracker + linux: 3.2.0-142.189 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger (juergh) ** Changed in: kernel-sru-workflow/prepare-package-lbm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lbm Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger (juergh) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger (juergh) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835270 Title: linux: 3.2.0-142.189 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lbm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Packaging phase-changed: Friday, 05. July 2019 11:32 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lbm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1549613] Re: Enable Sunix Serial/Parallel cards [1FD4:1999]
*** This bug is a duplicate of bug 1826716 *** https://bugs.launchpad.net/bugs/1826716 ** This bug has been marked a duplicate of bug 1826716 Include Sunix serial/parallel driver -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1549613 Title: Enable Sunix Serial/Parallel cards [1FD4:1999] Status in HWE Next: New Status in linux package in Ubuntu: Triaged Bug description: This card often shows up in our projects. We got the attached driver from vendor for inclusion into Ubuntu. This bug is for tracking purpose, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1549613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811335] Re: ELAN900C:00 04F3:2844 touchscreen doesn't work
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: hwe-next
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1811335
Title:
ELAN900C:00 04F3:2844 touchscreen doesn't work
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Bug description:
[Impact]
[ELAN900C:00 04F3:2844] doesn't work
[Fix]
It works under kernel v4.19, so after bisect the kernel and got the first bad
commit
e50d95e2ad12 pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H
variant
[Test]
Verified on the DELL machine, the touchscreen works well.
[Regression Potential]
Low, the 2 commits are all
Fixes: a663ccf0fea1 ("pinctrl: intel: Add Intel Cannon Lake PCH-H pin
controller support")
Should be safe to be included.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1811335/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826716] Re: Include Sunix serial/parallel driver
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-oem (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1826716 Title: Include Sunix serial/parallel driver Status in HWE Next: New Status in linux-oem package in Ubuntu: Confirmed Status in linux-oem source package in Bionic: Confirmed Bug description: [Impact] We shipped several platform with sunix device, which is enabled by sunix DKMS driver. We should use in-tree driver instead. [Fix] Include not-yet-merged sunix driver: https://lore.kernel.org/lkml/20190319120723.3691-1-sau...@gmail.com/ [Test] Use command `inputattach` to test serial mouse connected to the Sunix board. The mouse works correctly. [Regression Potential] Low. It's a new driver so the regression potential is minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1826716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826716] Re: Include Sunix serial/parallel driver
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-oem (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1826716 Title: Include Sunix serial/parallel driver Status in HWE Next: New Status in linux-oem package in Ubuntu: Confirmed Status in linux-oem source package in Bionic: Confirmed Bug description: [Impact] We shipped several platform with sunix device, which is enabled by sunix DKMS driver. We should use in-tree driver instead. [Fix] Include not-yet-merged sunix driver: https://lore.kernel.org/lkml/20190319120723.3691-1-sau...@gmail.com/ [Test] Use command `inputattach` to test serial mouse connected to the Sunix board. The mouse works correctly. [Regression Potential] Low. It's a new driver so the regression potential is minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1826716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833934] Re: linux: 5.0.0-20.21 -proposed tracker
This bug was fixed in the package linux - 5.0.0-20.21 --- linux (5.0.0-20.21) disco; urgency=medium * linux: 5.0.0-20.21 -proposed tracker (LP: #1833934) * CVE-2019-11479 - SAUCE: tcp: add tcp_min_snd_mss sysctl - SAUCE: tcp: enforce tcp_min_snd_mss in tcp_mtu_probing() * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) // CVE-2019-11478 - tcp: refine memory limit test in tcp_fragment() -- Stefan Bader Mon, 24 Jun 2019 10:09:02 +0200 ** Changed in: linux (Ubuntu) Status: Invalid => 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/1833934 Title: linux: 5.0.0-20.21 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: Fix Released Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1833930 (bionic/linux-hwe-edge), bug 1833932 (bionic/linux-oem-osp1) derivatives: bug 1833921 (linux-raspi2), bug 1833922 (linux-aws), bug 1833924 (linux-azure), bug 1833927 (linux-gcp), bug 1833928 (linux-kvm), bug 1833929 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Complete phase-changed: Friday, 28. June 2019 17:01 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1833934/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in sddm package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-prime source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in sddm source package in Bionic: Confirmed Status in ubuntu-drivers-common source package in Bionic: Fix Released Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390 /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia- ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808768] Re: Initrd of pc-kernel snap contains out-of-date packages
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808768 Title: Initrd of pc-kernel snap contains out-of-date packages Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: The build script does not install package updates during generate the pc-kernel snap. I met this bug #1783810 when I was verify my Ubuntu Core 18 image on KVM. The system stuck at resizing the writable partition. the resize script of initrd called sgdisk to achieve the resizing. Inside sgdisk, it use libuuid1 to get random bytes and generate UUIDs. After I extracted the kernel snap, I found it is still using libuuid1 2.31.1-0.4ubuntu3 which is not the latest version. At this moment, Bionic has 2.31.1-0.4ubuntu3.2. Then I added commands to make the build script installing package updates. After that, the system can boot correctly without any problem. I am wondering if there is any concern to pull updates before building? The attachment is my patch to pull updates. Snippet of console output, before patch [2.491404] usbcore: registered new interface driver usb-storage [2.503788] sdhci: Secure Digital Host Controller Interface driver [2.505627] sdhci: Copyright(c) Pierre Ossman [2.548485] initrd: found more than 10% free space on disk, resizing /dev/sda3 [2.550345] initrd: partition to full disk size, see /dev/kmsg for details [2.912472] clocksource: tsc: mask: 0x max_cycles: 0x255b2dea34c, max_idle_ns: 440795243480 ns ## several keystrokes here, or the boot process won't continue [ 351.361426] random: crng init done [ 351.423462] fixing backup GPT [ 352.435735] systemd-udevd[240]: passed device to netlink monitor 0x55e45653e330 [ 352.443221] sda: sda1 sda2 sda3 [ 352.445486] The operation has completed successfully. Snippet of console output, after patch [2.548203] usbcore: registered new interface driver usb-storage [2.561439] sdhci: Secure Digital Host Controller Interface driver [2.562878] sdhci: Copyright(c) Pierre Ossman [2.602093] initrd: found more than 10% free space on disk, resizing /dev/sda3 [2.603900] initrd: partition to full disk size, see /dev/kmsg for details ## block a few seconds, until timeout. [2.912418] clocksource: tsc: mask: 0x max_cycles: 0x255b2dea34c, max_idle_ns: 440795243480 ns [9.174552] random: fast init done [9.179127] random: parted: uninitialized urandom read (16 bytes read) [9.183726] random: parted: uninitialized urandom read (16 bytes read) [9.190606] random: parted: uninitialized urandom read (16 bytes read) [9.230419] fixing backup GPT [9.236989] random: crng init done [9.238102] random: 5 urandom warning(s) missed due to ratelimiting [ 10.245047] systemd-udevd[259]: passed device to netlink monitor 0x56376c45b150 [ 10.253093] sda: sda1 sda2 sda3 [ 10.256202] The operation has completed successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1808768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811929] Re: Fix not working Goodix touchpad
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811929 Title: Fix not working Goodix touchpad Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: [Impact] Goodix I2C PTP touchpad doesn't work. [Fix] Disable runtime PM can fix it. [Test] I verified the touchpad starts working with the fix. [Regression Potential] Low. The fix limits to a specific device which doesn't work without it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1811929/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783906] Re: Linux 4.15 and onwards fails to initialize some hard drives
I'm not familiar with kernel mailing list so I don't know why my patch
was ignored. Maybe format of email was not proper, or I send wrong
recipients.
I also updated the patch, so I attach the latest version.
** Patch added:
"0001-Fix-for-initialize-drives-not-capable-to-handle-maxi.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783906/+attachment/5275252/+files/0001-Fix-for-initialize-drives-not-capable-to-handle-maxi.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1783906
Title:
Linux 4.15 and onwards fails to initialize some hard drives
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Status in linux source package in Cosmic:
Confirmed
Bug description:
I have two hard drives, the main hard drive is a TOSHIBA DT01ACA200
the second backup hard drive is a Western Digital WD5003AZEX. I
installed lubuntu 18.04.1 on the Toshiba HDD and it boots just fine,
the issue is with the second hard drive, when installing the WD HDD
wouldn't even come as an option to install, and after boot the WD HDD
still wouldn't come up, this is the dmesg with the stock kernel (4.15)
https://paste.ubuntu.com/p/kpxh94v2SK/
ata6 is the WD HDD that refuses to work. The messages:
[ 302.107650] ata6: SError: { CommWake 10B8B Dispar DevExch }
[ 302.107658] ata6: hard resetting link
[ 307.860291] ata6: link is slow to respond, please be patient (ready=0)
[ 312.120898] ata6: COMRESET failed (errno=-16)
[ 363.445120] INFO: task kworker/u8:5:201 blocked for more than 120 seconds.
[ 363.445131] Not tainted 4.15.0-29-generic #31-Ubuntu
[ 363.445135] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[ 363.445140] kworker/u8:5D0 201 2 0x8000
[ 363.445155] Workqueue: events_unbound async_run_entry_fn
[ 363.445157] Call Trace:
[ 363.445171] __schedule+0x291/0x8a0
[ 363.445177] schedule+0x2c/0x80
[ 363.445182] ata_port_wait_eh+0x7c/0xf0
[ 363.445186] ? wait_woken+0x80/0x80
[ 363.445189] ata_port_probe+0x28/0x40
[ 363.445192] async_port_probe+0x2e/0x52
[ 363.445196] async_run_entry_fn+0x3c/0x150
[ 363.445199] process_one_work+0x1de/0x410
[ 363.445203] worker_thread+0x32/0x410
[ 363.445207] kthread+0x121/0x140
[ 363.445210] ? process_one_work+0x410/0x410
[ 363.445214] ? kthread_create_worker_on_cpu+0x70/0x70
[ 363.445218] ret_from_fork+0x22/0x40
Repeat constantly. Also when I try to turn off the computer, the
computer seem to freeze, the lights of the keyboard and mouse turn off
and the computer just stay on.
I tried Tiny Core 9.0 which has linux 4.14.10, and i didn't had this
issue, i also installed linux 4.14 on this lubuntu 18.04 using Ukuu
Kernel Update Utility. And with this kernel version, or any previous
version the WD HDD does work again. Here's a dmesg of lubuntu 18.04
with linux 4.14 and the WD HDD finally coming up at the end:
https://paste.ubuntu.com/p/Gd3cGFbjTJ/
Also tried with with linux 4.17 but the WD HDD would also refuse to
work on this version. Here's another dmesg with this version:
https://paste.ubuntu.com/p/PmNn96vZZv/
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-29-generic 4.15.0-29.31
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-29-generic.
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: testtest756 F pulseaudio
/dev/snd/controlC1: testtest756 F pulseaudio
Card0.Amixer.info:
Card hw:0 'NVidia_1'/'HDA NVidia at 0xfe02 irq 22'
Mixer name : 'Realtek ALC1200'
Components : 'HDA:10ec0888,10ec,00100101
HDA:10de0002,10de0101,0010'
Controls : 56
Simple ctrls : 21
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xfcffc000 irq 16'
Mixer name : 'Nvidia GPU 42 HDMI/DP'
Components : 'HDA:10de0042,38422651,00100100'
Controls : 21
Simple ctrls : 3
CurrentDesktop: LXDE
Date: Thu Jul 26 17:10:58 2018
HibernationDevice: RESUME=UUID=17e70869-516d-4b63-b900-e92e3c4b73b6
InstallationDate: Installed on 2018-07-26 (0 days ago)
InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
MachineType: 113 1
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic
root=UUID=71cf0a32-7827-49be-a2c0-cd50a72c26a1 ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.15.0-29-generic N/A
linux-backports-modules-4.15.0-29-generic N/A
linux-firmware 1.173.1
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
H
[Kernel-packages] [Bug 1811777] Re: Fix non-working pinctrl-intel
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811777 Title: Fix non-working pinctrl-intel Status in HWE Next: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: [Impact] Intel pinctrl doesn't work. There's a WWAN card needs to use pinctrl to reset itself after firmware update. Currently we can't use pinctrl to reset it. [Fix] Translate GPIO to pinctrl pins correctly. [Test] The WWAN reset function works once the fix is applied. [Regression Potential] Low. Limits to pinctrl-intel and it's in mainline for a while. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1811777/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802813] Re: Fix "incomplete report" noise after S3
** Changed in: hwe-next Status: New => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1802813 Title: Fix "incomplete report" noise after S3 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Bug description: [Impact] I2C HID devices may keep spewing out error "i2c_hid_get_input: incomplete report (30/2)" after system S3. [Fix] It a regression caused by commit ac75a041048b, backport commmit ef6eaf27274c to fix it. Input report length 2 is a valid length. [Test] With the fix the issue can no longer be observed on Alps touchpads. [Regression Potential] None. Input report lenght 2 is valid per spec. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1802813/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812812] Re: Fix non-working QCA Rome Bluetooth after S3
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812812 Title: Fix non-working QCA Rome Bluetooth after S3 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Bug description: [Impact] Sometimes QCA Rome Bluetooth USB host doesn't work after S3: [ 165.110742] Bluetooth: hci0: using NVM file: qca/nvm_usb_0302.bin [ 168.432065] Bluetooth: hci0: Failed to send body at 4 of 1953 (-110) This is due to USB core enables LPM two times after S3. [Fix] Only enable LPM once. [Test] The Bluetooth USB works all the time after applying the fix. [Regression Potential] Low. Enabling a hardware feature twice in a row isn't right, I'd be surprise if any hardware relies on this driver behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1812812/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821271] Re: New Intel Wireless-AC 9260 [8086:2526] card not correctly probed in Ubuntu system
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821271 Title: New Intel Wireless-AC 9260 [8086:2526] card not correctly probed in Ubuntu system Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Bug description: [Impact] New Intel Wireless-AC 9260 [8086:2526] card with subsystem id 4018 is not correctly probed without the corresponding id entry in kernel. [Fix] Upstream commit 3941310cf665 "iwlwifi: add new card for 9260 series". [Test Case] Verified on Intel 9260D2WL. [Regression Risk] Low. This patch effectively adds new id match for a unsupported (yet) device only. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1821271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817518] Re: Bluetooth not working (Intel CyclonePeak)
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1817518 Title: Bluetooth not working (Intel CyclonePeak) Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Status in linux-firmware source package in Xenial: Won't Fix Status in linux source package in Bionic: Fix Released Status in linux-firmware source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-firmware source package in Cosmic: Fix Released Status in linux-firmware source package in Disco: Fix Released Bug description: [Impact] New Intel bluetooth device 8087:0029 takes a new ID to be enabled, or the device will not work. [Fix] 2da711bcebe81 Bluetooth: btusb: Add support for Intel bluetooth device 8087:0029 This change requires new firmware blob as well, which is to be upstreamed & backported from linux-firmware. [Test Case] Verified on AX200NGW & 22560NGW chips. Use hciconfig to list probed hci device. [Regression Risk] Low. This patch effectively adds new id match for a unsupported (yet) device. The most lines of the patches actually introduces an helper function that generates firmware blob name. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1817518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813733] Re: Ignore "incomplete report" from Elan touchpanels
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813733 Title: Ignore "incomplete report" from Elan touchpanels Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Bug description: [Impact] When using Elan touchpanels, this message keeps getting spurted out: [ 136.138487] i2c_hid i2c-DELL08D6:00: i2c_hid_get_input: incomplete report (14/65535) This is an error message, so systemd-journald flushes to disk as soon as the message shows. This prevents the storage enters power saving state, hurting battery time. Other than the annoying message, the touchpad itself works fine. [Fix] Just warn once to avoid the annoying message. [Test] The annoying message stops once the fix applied. [Regression Potential] None. The user still gets the warning from dmesg without all the flooding. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1813733/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820930] Re: some codecs stop working after S3
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1820930 Title: some codecs stop working after S3 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Bug description: To fix this bug, B/OEM-B/C needs only 1 patch, while v5.0-rc1 introduced a new patch which affect this issue, so the DISCO needs 2 patches. [Impact] After S3, some codecs (alc236, alc255, alc891 and some HDMI codec) stop working, they can't detect jack plugging/unplugging or the audio device can't show up in the gnome-sound-setting [Fix] After S3, if it runs runtime_resume(), the codec works again. We change the driver to let system_resume() trigger runtime_resume() [Test Case] This issue is reported from OEM project, some codecs can't detect jack pluggin/unplugging, some codecs can't show up in the UI, after applying this patch, all related bugs are fixed. [Regression Potential] Low. have tested on many machines (with this issue or without this issue), all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1820930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820990] Re: [SRU][B/B-OEM/C/D] Fix AMD IOMMU NULL dereference
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1820990 Title: [SRU][B/B-OEM/C/D] Fix AMD IOMMU NULL dereference Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-oem source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Released Bug description: [Impact] When no acpi hid match the device, there will be a NULL dereference in amd iommu. It will make system hang. [Fix] Check NULL pointer before using it. [Test] Tested on several AMD platforms, bugs are fixed with this patch. [Regression Potential] Low, upstream fix, Verified on several platforms. It should be safe. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1820990/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817676] Re: r8169 doesn't get woken up by ethernet cable plugging, no PME generated
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1817676 Title: r8169 doesn't get woken up by ethernet cable plugging, no PME generated Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Released Bug description: [Impact] Once r8169 (Realtek ethernet) and its root port enter to D3, plugging network cable doesn't wake r8169 up. [Fix] Revert "PCI/PME: Implement runtime PM callbacks". Quote the original commit message: " The commit tried to prevent root port waking up from D3cold immediately but looks like disabing root port PME interrupt is not the right way to fix that issue so revert it now. The patch following proposes an alternative solution to that issue. " [Test] After applying the fix, plugging the ethernet cable can generate PME IRQ correctly, hence waking up r8169. [Regression Potential] Medium. The commits are relative new, rely on some PCI detail that I am not familiar with (PCI spec isn't publicly available). Fortunately we only need this fix for Unstable/OEM-B, so it won't hit most users if any regression happens. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1817676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825487] Re: The Realtek card reader does not enter PCIe 1.1/1.2
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1825487 Title: The Realtek card reader does not enter PCIe 1.1/1.2 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-oem source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Released Bug description: [Impact] The Realtek card reader does not enter PCIe 1.1/1.2. This keeps Intel SoC staying at PC3, which consumes lots of power. [Fix] Set correct ASPM parameter on rtsx_pci. [Test] With the patch applied, Intel SoC can enter PC10, which saves lots of power. [Regression Potential] Low. The card reader in question still works as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1825487/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828798] Re: Electrical noise occurred when external headset enter powersaving mode on a DEll machine
** Summary changed: - Eletrical noise occurred when external headset enter powersaving mode on a DEll machine + Electrical noise occurred when external headset enter powersaving mode on a DEll machine ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1828798 Title: Electrical noise occurred when external headset enter powersaving mode on a DEll machine Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: Fix Released Bug description: [Impact] Eletrical noise occurred when external headset enter powersaving mode (around 7 seconds) [Fix] Don't clear pinctl when runtime suspend. [Test Case] Plug headset and wait for the codec to enter runtime suspend, there is no any noise from headphone. [Regression Risk] Low. the 1st patch is specific to a Dell machine and the 2nd patch is specific to the machine with the codec alc298 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1828798/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818490] Re: Intel I210 Ethernet card not working after hotplug [8086:1533]
** Changed in: hwe-next Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818490 Title: Intel I210 Ethernet card not working after hotplug [8086:1533] Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Bug description: Summary: Intel I210 Ethernet card not working after hotplug Steps to reproduce: 1. Power on system with ethernet cable on Intel I210 2. Check ethernet is workable 3. Unplug then plug the ethernet cable Expected result: Intel I210 Ethernet card is working, e.g. IP address acquired automatically if configured as DHCP. Actual result: Intel I210 Ethernet card not working after hotplug. dmesg has following error messages instead: [ 16.464321] [ cut here ] [ 16.464326] PCI PM: State of device not saved by igb_runtime_suspend+0x0/0x90 [igb] [ 16.464334] WARNING: CPU: 2 PID: 49 at /build/linux-oem-ta19Pv/linux-oem-4.15.0/drivers/pci/pci-driver.c:1282 pci_pm_runtime_suspend+0x175/0x180 [ 16.464334] Modules linked in: joydev input_leds nls_iso8859_1 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_hda_intel irqbypass snd_hda_codec crct10dif_pclmul snd_hda_core crc32_pclmul snd_hwdep ghash_clmulni_intel pcbc snd_pcm dell_smm_hwmon aesni_intel aes_x86_64 snd_seq_midi crypto_simd snd_seq_midi_event glue_helper cryptd snd_rawmidi intel_cstate snd_seq intel_rapl_perf dell_wmi snd_seq_device dell_smbios dcdbas snd_timer dell_wmi_aio dell_wmi_descriptor intel_wmi_thunderbolt snd sparse_keymap wmi_bmof soundcore idma64 virt_dma mei_me intel_lpss_pci intel_pch_thermal mei intel_lpss mac_hid acpi_pad sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 [ 16.464354] async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log hid_generic usbhid hid i915 igb drm_kms_helper syscopyarea dca sysfillrect i2c_algo_bit e1000e sysimgblt ptp fb_sys_fops pps_core ahci libahci drm wmi video [ 16.464366] CPU: 2 PID: 49 Comm: kworker/2:1 Not tainted 4.15.0-1032-oem #37-Ubuntu [ 16.464367] Hardware name: Dell Inc. Precision 3630 Tower/, BIOS 99.2.2 01/14/2019 [ 16.464369] Workqueue: pm pm_runtime_work [ 16.464370] RIP: 0010:pci_pm_runtime_suspend+0x175/0x180 [ 16.464371] RSP: 0018:a968c3363d48 EFLAGS: 00010282 [ 16.464372] RAX: RBX: 8a2557aee0a0 RCX: 0006 [ 16.464372] RDX: 0007 RSI: 0096 RDI: 8a257c496490 [ 16.464373] RBP: a968c3363d70 R08: 0001 R09: 0373 [ 16.464373] R10: R11: R12: [ 16.464373] R13: c0481540 R14: 8a2557aee000 R15: [ 16.464374] FS: () GS:8a257c48() knlGS: [ 16.464375] CS: 0010 DS: ES: CR0: 80050033 [ 16.464375] CR2: 7f30b3e93170 CR3: 000842c0a004 CR4: 003606e0 [ 16.464376] DR0: DR1: DR2: [ 16.464376] DR3: DR6: fffe0ff0 DR7: 0400 [ 16.464376] Call Trace: [ 16.464379] ? pci_pm_runtime_resume+0xb0/0xb0 [ 16.464380] __rpm_callback+0xca/0x210 [ 16.464381] ? __switch_to_asm+0x40/0x70 [ 16.464382] ? __switch_to_asm+0x34/0x70 [ 16.464382] rpm_callback+0x59/0x80 [ 16.464383] ? pci_pm_runtime_resume+0xb0/0xb0 [ 16.464384] rpm_suspend+0x137/0x640 [ 16.464385] ? __switch_to_asm+0x40/0x70 [ 16.464386] pm_runtime_work+0x81/0xa0 [ 16.464388] process_one_work+0x1de/0x410 [ 16.464389] worker_thread+0x32/0x410 [ 16.464390] kthread+0x121/0x140 [ 16.464391] ? process_one_work+0x410/0x410 [ 16.464392] ? kthread_create_worker_on_cpu+0x70/0x70 [ 16.464392] ret_from_fork+0x35/0x40 [ 16.464393] Code: 2b ff ff ff 80 3d 21 c6 11 01 00 0f 85 1e ff ff ff 49 8b b5 a0 00 00 00 48 c7 c7 a0 56 b2 ad c6 05 06 c6 11 01 01 e8 0b 74 b9 ff <0f> 0b e9 fd fe ff ff 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 53 [ 16.464408] ---[ end trace 97e5f2cf651b62e6 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1818490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : http
[Kernel-packages] [Bug 1830822] Re: Killer 1650X Wifi/BT(2723:1654) fails to load correct firmware
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1830822 Title: Killer 1650X Wifi/BT(2723:1654) fails to load correct firmware Status in HWE Next: Fix Released Status in linux-oem package in Ubuntu: Fix Released Bug description: Killer series loadded IWL_22000_HR_B_FW_PRE prefixed firmware instead IWL_CC_A_FW_PRE prefixed firmware, and firmware named iwlwifi-QuQnj-b0-hr-b0-XX.ucode doesn't exist. [ 4.252701] iwlwifi :03:00.0: enabling device ( -> 0002) [ 4.263301] iwlwifi :03:00.0: Direct firmware load for iwlwifi-QuQnj-b0-hr-b0-46.ucode failed with error -2 [ 4.263372] iwlwifi :03:00.0: Direct firmware load for iwlwifi-QuQnj-b0-hr-b0-45.ucode failed with error -2 [ 4.263517] iwlwifi :03:00.0: Direct firmware load for iwlwifi-QuQnj-b0-hr-b0-44.ucode failed with error -2 [ 4.263589] iwlwifi :03:00.0: Direct firmware load for iwlwifi-QuQnj-b0-hr-b0-43.ucode failed with error -2 [ 4.263658] iwlwifi :03:00.0: Direct firmware load for iwlwifi-QuQnj-b0-hr-b0-42.ucode failed with error -2 [ 4.263663] iwlwifi :03:00.0: Direct firmware load for iwlwifi-QuQnj-b0-hr-b0-41.ucode failed with error -2 [ 4.263668] iwlwifi :03:00.0: Direct firmware load for iwlwifi-QuQnj-b0-hr-b0-40.ucode failed with error -2 [ 4.263673] iwlwifi :03:00.0: Direct firmware load for iwlwifi-QuQnj-b0-hr-b0-39.ucode failed with error -2 [ 4.263675] iwlwifi :03:00.0: no suitable firmware found! [ 4.263676] iwlwifi :03:00.0: minimum version required: iwlwifi-QuQnj-b0-hr-b0-39 [ 4.263677] iwlwifi :03:00.0: maximum version supported: iwlwifi-QuQnj-b0-hr-b0-46 [ 4.263678] iwlwifi :03:00.0: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1830822/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835509] [NEW] False warning "The kernel version is not supported." on xenial with -hwe kernels
Public bug reported: [Impact] The message appears as when running -hwe kernels (4.15) on Xenial. This happens because makedumpfile defines a LATEST_VERSION kernel that "officially" supports. Currently, makedumpfile package for xenial has this version set to 4.14.8 and this is why it shows this message with 4.15 kernels. [Test Case] TBD [Regression Potential] TBD [Other] ** Affects: makedumpfile (Ubuntu) Importance: Undecided Assignee: Ioanna Alifieraki (joalif) Status: New ** Affects: makedumpfile (Ubuntu Xenial) Importance: Undecided Assignee: Ioanna Alifieraki (joalif) Status: New ** Changed in: makedumpfile (Ubuntu) Assignee: (unassigned) => Ioanna Alifieraki (joalif) ** Also affects: makedumpfile (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: makedumpfile (Ubuntu Xenial) Assignee: (unassigned) => Ioanna Alifieraki (joalif) -- 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/1835509 Title: False warning "The kernel version is not supported." on xenial with -hwe kernels Status in makedumpfile package in Ubuntu: New Status in makedumpfile source package in Xenial: New Bug description: [Impact] The message appears as when running -hwe kernels (4.15) on Xenial. This happens because makedumpfile defines a LATEST_VERSION kernel that "officially" supports. Currently, makedumpfile package for xenial has this version set to 4.14.8 and this is why it shows this message with 4.15 kernels. [Test Case] TBD [Regression Potential] TBD [Other] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1835509/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834930] Re: linux-aws: 4.15.0-1044.46 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1834930 Title: linux-aws: 4.15.0-1044.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834929 (xenial/linux-aws-hwe) derivatives: bug 1834927 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Ready for Promote to Proposed phase-changed: Thursday, 04. July 2019 19:08 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834930] Re: linux-aws: 4.15.0-1044.46 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1834930 Title: linux-aws: 4.15.0-1044.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834929 (xenial/linux-aws-hwe) derivatives: bug 1834927 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Ready for Promote to Proposed phase-changed: Thursday, 04. July 2019 19:08 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834908] Re: linux-aws: 4.4.0-1088.99 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1834908 Title: linux-aws: 4.4.0-1088.99 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834907 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834918 phase: Promote to Proposed phase-changed: Friday, 05. July 2019 08:36 UTC reason: promote-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834908/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801540]
I submitted this bug over 2 years ago. It's pretty obvious at this point that it'll never get fixed. It's a shame all the board makers are using these realtek chips. I'd expect with their popularity some developer somewhere would have wanted it fixed. Do we have to take a collection for a bug bounty for someone to be interested in this? It might end up being cheaper than us all going out and buying USB DACs. Oh, wait, I already bought one. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801540]
I'm also experiencing this issue on an MSI B450 Carbon Pro Gaming AC mobo with the ALC1220 codec. I can get the output crackling to stop somewhat using tsched=0, but my mic still experiences the issue. Works fine in Windows. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs
*** This bug is a duplicate of bug 1796292 *** https://bugs.launchpad.net/bugs/1796292 ** This bug has been marked a duplicate of bug 1796292 Tight timeout for bcache removal causes spurious failures -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784665 Title: mkfs.ext4 over /dev/bcache0 hangs Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: $ cat /proc/version_signature Ubuntu 4.15.0-29.31-generic 4.15.18 $ lsb_release -rd Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 $ apt-cache policy linux-image-`uname -r` linux-image-4.15.0-29-generic: Installed: 4.15.0-29.31 Candidate: 4.15.0-29.31 Version table: *** 4.15.0-29.31 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 3) mkfs.ext4 /dev/bcache0 returns successful creating an ext4 filesystem on top of a bcache device 4) mkfs.ext4 doesn't return and kernel prints hung process info [ 58.018099] cloud-init[920]: Running command ['mkfs.ext4', '-F', '-L', 'root-fs', '-U', 'f01aec97-9457-11e8-b8d6-525400123401', '/dev/bcache0'] with allowed return codes [0] (capture=True) [ 242.652018] INFO: task kworker/u4:0:5 blocked for more than 120 seconds. [ 242.653767] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.655391] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.657397] INFO: task kworker/0:2:410 blocked for more than 120 seconds. [ 242.659126] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.660980] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.663000] INFO: task bcache_allocato:2326 blocked for more than 120 seconds. [ 242.664807] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.666516] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.668503] INFO: task bcache_writebac:2345 blocked for more than 120 seconds. [ 242.670301] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.671936] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.673909] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds. [ 242.675414] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.677038] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.483998] INFO: task kworker/u4:0:5 blocked for more than 120 seconds. [ 363.488441] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.489598] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.491043] INFO: task kworker/0:2:410 blocked for more than 120 seconds. [ 363.492252] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.494085] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.495659] INFO: task bcache_allocato:2326 blocked for more than 120 seconds. [ 363.496957] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.498454] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.499866] INFO: task bcache_writebac:2345 blocked for more than 120 seconds. [ 363.501156] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.502597] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.504048] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds. [ 363.505505] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.506677] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. System has two virtio block devices. bcache was created like so: make-bcache -C /dev/vdb make-bcache -B /dev/vda2 resulting in /dev/bcache0 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: User Name 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 31 15:52 seq crw-rw 1 root audio 116, 33 Jul 31 15:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Tue Jul 31 15:53:56 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440
[Kernel-packages] [Bug 1796292] Re: Tight timeout for bcache removal causes spurious failures
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Cosmic)
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/1796292
Title:
Tight timeout for bcache removal causes spurious failures
Status in curtin:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Status in linux source package in Cosmic:
Confirmed
Status in linux source package in Disco:
Confirmed
Status in linux source package in Eoan:
Confirmed
Bug description:
I've had a number of deployment faults where curtin would report
Timeout exceeded for removal of /sys/fs/bcache/xxx when doing a mass-
deployment of 30+ nodes. Upon retrying the node would usually deploy
fine. Experimentally I've set the timeout ridiculously high, and it
seems I'm getting no faults with this. I'm wondering if the timeout
for removal is set too tight, or might need to be made configurable.
--- curtin/util.py~ 2018-05-18 18:40:48.0 +
+++ curtin/util.py 2018-10-05 09:40:06.807390367 +
@@ -263,7 +263,7 @@
return _subp(*args, **kwargs)
-def wait_for_removal(path, retries=[1, 3, 5, 7]):
+def wait_for_removal(path, retries=[1, 3, 5, 7, 1200, 1200]):
if not path:
raise ValueError('wait_for_removal: missing path parameter')
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1796292/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796292] Re: Tight timeout for bcache removal causes spurious failures
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Disco)
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/1796292
Title:
Tight timeout for bcache removal causes spurious failures
Status in curtin:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Status in linux source package in Cosmic:
Confirmed
Status in linux source package in Disco:
Confirmed
Status in linux source package in Eoan:
Confirmed
Bug description:
I've had a number of deployment faults where curtin would report
Timeout exceeded for removal of /sys/fs/bcache/xxx when doing a mass-
deployment of 30+ nodes. Upon retrying the node would usually deploy
fine. Experimentally I've set the timeout ridiculously high, and it
seems I'm getting no faults with this. I'm wondering if the timeout
for removal is set too tight, or might need to be made configurable.
--- curtin/util.py~ 2018-05-18 18:40:48.0 +
+++ curtin/util.py 2018-10-05 09:40:06.807390367 +
@@ -263,7 +263,7 @@
return _subp(*args, **kwargs)
-def wait_for_removal(path, retries=[1, 3, 5, 7]):
+def wait_for_removal(path, retries=[1, 3, 5, 7, 1200, 1200]):
if not path:
raise ValueError('wait_for_removal: missing path parameter')
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1796292/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796292] Re: Tight timeout for bcache removal causes spurious failures
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Bionic)
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/1796292
Title:
Tight timeout for bcache removal causes spurious failures
Status in curtin:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Status in linux source package in Cosmic:
Confirmed
Status in linux source package in Disco:
Confirmed
Status in linux source package in Eoan:
Confirmed
Bug description:
I've had a number of deployment faults where curtin would report
Timeout exceeded for removal of /sys/fs/bcache/xxx when doing a mass-
deployment of 30+ nodes. Upon retrying the node would usually deploy
fine. Experimentally I've set the timeout ridiculously high, and it
seems I'm getting no faults with this. I'm wondering if the timeout
for removal is set too tight, or might need to be made configurable.
--- curtin/util.py~ 2018-05-18 18:40:48.0 +
+++ curtin/util.py 2018-10-05 09:40:06.807390367 +
@@ -263,7 +263,7 @@
return _subp(*args, **kwargs)
-def wait_for_removal(path, retries=[1, 3, 5, 7]):
+def wait_for_removal(path, retries=[1, 3, 5, 7, 1200, 1200]):
if not path:
raise ValueError('wait_for_removal: missing path parameter')
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1796292/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834935] Re: linux-gcp: 4.15.0-1037.39~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1834935 Title: linux-gcp: 4.15.0-1037.39~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834932 (gcp-kernel), bug 1834934 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834936 phase: Promote to Proposed phase-changed: Friday, 05. July 2019 08:42 UTC reason: promote-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
