[Kernel-packages] [Bug 1800995] Re: [ICL] GPIO support
The commit is already in Disco kernel. ** Changed in: intel Status: New => Fix Released ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux 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/1800995 Title: [ICL] GPIO support Status in intel: Fix Released Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Description: GPIO support for ICL should be basically the same as in CNL. Reduction in minimum selectable GPIO block configuration. Allows for more flexibility in selecting 1.8 or 3.3V GPIOs Commit ID: e6800d2601fafb51f5feb3c216c884c2efb4c77d Target Kernel: 4.19 Target Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1800995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819881] Re: [CONFIG] please enable highdpi font FONT_TER16x32
** Description changed: + == Justification == + The console font size on a high resolution screen is only suitable for + eagles, although we can choose a bigger font by running: + sudo dpkg-reconfigure console-setup + + But that is not enough, the font size before video driver kicks in is + still small. If we need to debug some early stage issues that will be a + problem. + + + == Fix == + ac8b6f14 (Fonts: New Terminus large console font) + Config for this TER16x32 and the compiled-in fonts support needs to be + enabled to keep engineers away from ophthalmologists. + + * Disco + It's already there. Just need to enable the configs. + * Cosmic / Bionic + Patch can be cherry-picked. + * Xenial + It needs an extra patch to make it a clean cherry-pick: + * 7bcae826 (lib/fonts/Kconfig: keep non-Sparc fonts listed together + * Trusty + It needs two extra patches to make it a clean cherry-pick: + * fonts: Add 6x10 font (33ac9dba) + * lib/fonts/Kconfig: keep non-Sparc fonts listed together (7bcae826). + And a config entry for the 6x10 font. + + Commit "fonts: Add 6x10 font" is just adding a new font. + Commit "lib/fonts/Kconfig: keep non-Sparc fonts listed together" is + just a patch for context rearrangement. + + I think these two are safe to be pulled-in. + + + == Test == + Test kernels: http://people.canonical.com/~phlin/kernel/lp-1819881-font/ + + Add "fbcon=font:TER16x32" to the GRUB_CMDLINE_LINUX in + /etc/default/grub, and follow these steps. + + * Disco + sudo update-grub; sudo reboot + * Cosmic / Bionic + Add "GRUB_GFXPAYLOAD_LINUX=3840x2160" to /etc/default/grub + sudo update-grub; sudo reboot + * Xenial + sudo update-grub; sudo reboot + * Trusty + sudo update-grub; sudo reboot (I need the proprietary nvidia driver + to boot for my SUT - Dell Precision M3800) + + The font before the video driver kicks in will get bigger. + + == Regression potential == + Minimal, changes are limited to adding console fonts, turn on fonts + related kernel configs. + + + [CONFIG] please enable highdpi font FONT_TER16x32 This is now available in v5.0 config/config.common.ubuntu:# CONFIG_FONT_TER16x32 is not set https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/lib/fonts/Kconfig?id=ac8b6f148fc97e9e10b48bd337ef571b1d1136aa ** Tags added: bionic cosmic disco trusty xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819881 Title: [CONFIG] please enable highdpi font FONT_TER16x32 Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: == Justification == The console font size on a high resolution screen is only suitable for eagles, although we can choose a bigger font by running: sudo dpkg-reconfigure console-setup But that is not enough, the font size before video driver kicks in is still small. If we need to debug some early stage issues that will be a problem. == Fix == ac8b6f14 (Fonts: New Terminus large console font) Config for this TER16x32 and the compiled-in fonts support needs to be enabled to keep engineers away from ophthalmologists. * Disco It's already there. Just need to enable the configs. * Cosmic / Bionic Patch can be cherry-picked. * Xenial It needs an extra patch to make it a clean cherry-pick: * 7bcae826 (lib/fonts/Kconfig: keep non-Sparc fonts listed together * Trusty It needs two extra patches to make it a clean cherry-pick: * fonts: Add 6x10 font (33ac9dba) * lib/fonts/Kconfig: keep non-Sparc fonts listed together (7bcae826). And a config entry for the 6x10 font. Commit "fonts: Add 6x10 font" is just adding a new font. Commit "lib/fonts/Kconfig: keep non-Sparc fonts listed together" is just a patch for context rearrangement. I think these two are safe to be pulled-in. == Test == Test kernels: http://people.canonical.com/~phlin/kernel/lp-1819881-font/ Add "fbcon=font:TER16x32" to the GRUB_CMDLINE_LINUX in /etc/default/grub, and follow these steps. * Disco sudo update-grub; sudo reboot * Cosmic / Bionic Add "GRUB_GFXPAYLOAD_LINUX=3840x2160" to /etc/default/grub sudo update-grub; sudo reboot * Xenial sudo update-grub; sudo reboot * Trusty sudo update-grub; sudo reboot (I need the proprietary nvidia driver to boot for my SUT - Dell Precision M3800) The font before the video driver kicks in will get bigger. == Regression potential == Minimal, changes are limited to adding console fonts, turn on fonts related kernel configs. [CONFIG] please enable highdpi font FONT_TER16x32 This is now available in v5.0 config/config.common.ubuntu:# CON
[Kernel-packages] [Bug 1820794] Re: [Dell Inspiron 3558] PCI/internal sound card not detected
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820794 Title: [Dell Inspiron 3558] PCI/internal sound card not detected Status in linux package in Ubuntu: Confirmed Bug description: SOUND ONLY PLAY VIA BLUETOOTH AND NOT IN EARPHONE OR LAPTOP ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-168.218-generic 3.13.11-ckt39 Uname: Linux 3.13.0-168-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Tue Mar 19 10:08:35 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-10-29 (1236 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0XCR91 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd04/22/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0XCR91:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820794] Re: PCI/internal sound card not detected
According to the attached AlsaInfo.txt the kernel doesn't have a driver compatible with your internal sound card: !!Soundcards recognised by ALSA !!- --- no soundcards --- So this is a kernel bug. Please try a newer version of Ubuntu like 18.04: http://releases.ubuntu.com/18.04 ** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) ** Summary changed: - PCI/internal sound card not detected + [Dell Inspiron 3558] PCI/internal sound card not detected -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820794 Title: [Dell Inspiron 3558] PCI/internal sound card not detected Status in linux package in Ubuntu: Confirmed Bug description: SOUND ONLY PLAY VIA BLUETOOTH AND NOT IN EARPHONE OR LAPTOP ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-168.218-generic 3.13.11-ckt39 Uname: Linux 3.13.0-168-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Tue Mar 19 10:08:35 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-10-29 (1236 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0XCR91 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd04/22/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0XCR91:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820794] [NEW] PCI/internal sound card not detected
You have been subscribed to a public bug: SOUND ONLY PLAY VIA BLUETOOTH AND NOT IN EARPHONE OR LAPTOP ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-168.218-generic 3.13.11-ckt39 Uname: Linux 3.13.0-168-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Tue Mar 19 10:08:35 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-10-29 (1236 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0XCR91 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd04/22/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0XCR91:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- PCI/internal sound card not detected https://bugs.launchpad.net/bugs/1820794 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
I finally updated to 1.13 bios. I also have the a315-41, not the 41g. Can confirm that it only loads 11 acpi tables. Still playing with the 4.19 fedora kernel (need to try newer distro, not much time tho). It boots with secure boot, touchpad works, seems about the same as before; not completely reliable, bit works. Still using the ivrs work-arounds. Will experiment more. Had to play with swapping drives for win 10. -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820796] Re: natacpi bug in 4.18.0-16-generic, fixed upstream 5.0.2
already fixed (see https://lists.ubuntu.com/archives/cosmic- changes/2019-March/012430.html) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820796 Title: natacpi bug in 4.18.0-16-generic, fixed upstream 5.0.2 Status in linux package in Ubuntu: Fix Committed Bug description: low-impact bug, easy workaround. Thinkpad T480 4.18.0-16-generic Bug: # cd /sys/class/power_supply/BAT1 # # echo 95 > charge_start_threshold bash: echo: write error: No such device but it works for BAT0 It means tlp, latest version installed via PPA, by default can't set battery charge thresholds for the second battery in ubuntu 18.04 because tlp now defaults to using natacpi. This can be reverted to the old way of working via a simple change in the tlp conf file. This bug is fixed in 5.0.2 installed from ubuntu mainline ppa. I did not try earlier. - root@moncrief:/sys/class/power_supply/BAT1# cat /proc/version_signature Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1820796] Re: natacpi bug in 4.18.0-16-generic, fixed upstream 5.0.2
Yep. I didn't find that, I filed a new Ubuntu kernel bug which I will now close. On Tue, 19 Mar. 2019, 16:05 Kai-Heng Feng, wrote: > LP: #1812099? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1820796 > > Title: > natacpi bug in 4.18.0-16-generic, fixed upstream 5.0.2 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820796/+subscriptions > ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820796 Title: natacpi bug in 4.18.0-16-generic, fixed upstream 5.0.2 Status in linux package in Ubuntu: Fix Committed Bug description: low-impact bug, easy workaround. Thinkpad T480 4.18.0-16-generic Bug: # cd /sys/class/power_supply/BAT1 # # echo 95 > charge_start_threshold bash: echo: write error: No such device but it works for BAT0 It means tlp, latest version installed via PPA, by default can't set battery charge thresholds for the second battery in ubuntu 18.04 because tlp now defaults to using natacpi. This can be reverted to the old way of working via a simple change in the tlp conf file. This bug is fixed in 5.0.2 installed from ubuntu mainline ppa. I did not try earlier. - root@moncrief:/sys/class/power_supply/BAT1# cat /proc/version_signature Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819915] Re: s2disk freezes at saving image to disk (hibernation)
Linux kernel and DKMS. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819915 Title: s2disk freezes at saving image to disk (hibernation) Status in linux package in Ubuntu: Confirmed Bug description: This started happening after I upgrade to ubuntu 18.04.2. In 18.04.1 hibernation was working flawlessly on my machine. (with kernel 4.15-46! not a kernel issue then?) Another thing that got updated recently was nvidia drivers which were known to cause hibernation issues, but those were on restoring the snapshot. http://imgur.com/gallery/jOyHEcL --> I get stuck on this screen after running hibernate or pm-hibernate. (sys-req REISUB combination works there and is the only good way to restart I found) SPECS Laptop Dell Inspiron 7567 A30P Intel Core i7-7700HQ 1x 16 GB DDR4 1 TB HDD + 256 GB SSD Nvidia GeForce GTX 1050 Ti FHD display Intel Dual Band Wireless AC 3165 1x1 Motherboard: Intel HM175 Graphics adapter: NVIDIA GeForce GTX 1050 Ti (Laptop) - 4096 MB, Core: 1620 MHz, Memory: 1752 MHz, GDDR5, 21.21.13.7320 (ForceWare 373.20), Nvidia Optimus nvidia driver: 415.27 INFO # uname -a Linux matheus-Inspiron-15-7000-Gaming 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux # free -m totalusedfree shared buff/cache available Mem: 1590629258742 1614238 12485 Swap: 16333 0 16333 # cat /etc/fstab | grep swap # swap was on /dev/sda8 during installation UUID=70d967e6-ad52-4c21-baf0-01a813ccc6ac noneswapsw 0 0 n root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep hibernate root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep hiber root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep s2disk root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep hibernation I could find nothing scrolling up on syslog about the hibernation process or with grep An interesting Note is that if I run hibernate just after I boot, it works and resumes perfectly! But after some system usage it randomly has that problem if I try. The percentage it freezes at is also random, sometimes 0, 1 even 30 once. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: matheus 25949 F...m pulseaudio /dev/snd/pcmC0D0p: matheus 25949 F...m pulseaudio /dev/snd/controlC0: matheus 25949 F pulseaudio /dev/snd/seq:matheus4986 f qsynth CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=bfc6f294-b737-4999-a444-01e1f410de06 InstallationDate: Installed on 2018-05-10 (308 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 15 7000 Gaming NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=659db14c-2a6c-4f9c-93bf-d31c4a84abb6 ro nouveau.blacklist=1 debug no_console_suspend systemd.log_level=info nvidia-drm.modeset=0 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip kvm lpadmin netdev plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/15/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0P84C9 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd08/15/2018:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn0P84C9:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819915/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752072] Re: [Packaging] Allow overlay of config annotations
** Changed in: linux-gcp (Ubuntu Bionic) Status: Fix Released => 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/1752072 Title: [Packaging] Allow overlay of config annotations Status in linux package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux-gcp source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux-gcp source package in Cosmic: New Bug description: Currently for custom kernels, it's necessary to keep a separate annotations file that often gets out of sync with the corresponding file in debian.master/. The "debian/scripts/config-check" script can be changed to allow additional annotations files to act as overlays over the original annotations file, allowing custom kernels to override the policies just for the relevant configs. As an initial proposal, any file matching the pattern "$DEBIAN/config/*.annotations" could be considered as an overlay file and policies could be overridden on a config basis. That means that any mention to a config in the overlay file would discard all the policies for that config in the original file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820687] Re: Sound issue, or rather, lack of sound
Does a cold boot help? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820687 Title: Sound issue, or rather, lack of sound Status in linux package in Ubuntu: Incomplete Bug description: Linux Mint 18.3 update Kernel 4.4.0-143-generic up-heaved my Alsa mixer/pulse-audio or something to disable sound, made the mixer and configurations useless and grayed out/inoperable. I have gone through this some time ago and forgotten how to remedy but the next thing, besides what I have tried futilely, will be to rollback the new kernel to its predecessor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820687/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1820687] Re: Sound issue, or rather, lack of sound
I tried launching an earlier kernel, which has worked in the past. It did not this time and so I downloaded Linux Mint 19.1 to run side by side and transfer from its predecessor 18.3 to the newest one and when done will eliminate the elder partition. I have done that before, as well. This one was stubborn. The problem occurred once before in Ubuntu and I updated by clean install that time as well. I find it a bit tedious to state the many terminal commands suggested that I tried. I am still not so technically savvy. I do have a hands on like most around me don't but I am not there yet as far as a guru or wizard. On Monday, March 18, 2019, 10:00:46 PM PDT, Kai-Heng Feng wrote: Does the sound come back by booting an older kernel? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1820687 Title: Sound issue, or rather, lack of sound Status in linux package in Ubuntu: Incomplete Bug description: Linux Mint 18.3 update Kernel 4.4.0-143-generic up-heaved my Alsa mixer/pulse-audio or something to disable sound, made the mixer and configurations useless and grayed out/inoperable. I have gone through this some time ago and forgotten how to remedy but the next thing, besides what I have tried futilely, will be to rollback the new kernel to its predecessor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820687/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820687 Title: Sound issue, or rather, lack of sound Status in linux package in Ubuntu: Incomplete Bug description: Linux Mint 18.3 update Kernel 4.4.0-143-generic up-heaved my Alsa mixer/pulse-audio or something to disable sound, made the mixer and configurations useless and grayed out/inoperable. I have gone through this some time ago and forgotten how to remedy but the next thing, besides what I have tried futilely, will be to rollback the new kernel to its predecessor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820687/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819915] Re: s2disk freezes at saving image to disk (hibernation)
What packages you recommend me downgrade there? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819915 Title: s2disk freezes at saving image to disk (hibernation) Status in linux package in Ubuntu: Confirmed Bug description: This started happening after I upgrade to ubuntu 18.04.2. In 18.04.1 hibernation was working flawlessly on my machine. (with kernel 4.15-46! not a kernel issue then?) Another thing that got updated recently was nvidia drivers which were known to cause hibernation issues, but those were on restoring the snapshot. http://imgur.com/gallery/jOyHEcL --> I get stuck on this screen after running hibernate or pm-hibernate. (sys-req REISUB combination works there and is the only good way to restart I found) SPECS Laptop Dell Inspiron 7567 A30P Intel Core i7-7700HQ 1x 16 GB DDR4 1 TB HDD + 256 GB SSD Nvidia GeForce GTX 1050 Ti FHD display Intel Dual Band Wireless AC 3165 1x1 Motherboard: Intel HM175 Graphics adapter: NVIDIA GeForce GTX 1050 Ti (Laptop) - 4096 MB, Core: 1620 MHz, Memory: 1752 MHz, GDDR5, 21.21.13.7320 (ForceWare 373.20), Nvidia Optimus nvidia driver: 415.27 INFO # uname -a Linux matheus-Inspiron-15-7000-Gaming 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux # free -m totalusedfree shared buff/cache available Mem: 1590629258742 1614238 12485 Swap: 16333 0 16333 # cat /etc/fstab | grep swap # swap was on /dev/sda8 during installation UUID=70d967e6-ad52-4c21-baf0-01a813ccc6ac noneswapsw 0 0 n root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep hibernate root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep hiber root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep s2disk root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep hibernation I could find nothing scrolling up on syslog about the hibernation process or with grep An interesting Note is that if I run hibernate just after I boot, it works and resumes perfectly! But after some system usage it randomly has that problem if I try. The percentage it freezes at is also random, sometimes 0, 1 even 30 once. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: matheus 25949 F...m pulseaudio /dev/snd/pcmC0D0p: matheus 25949 F...m pulseaudio /dev/snd/controlC0: matheus 25949 F pulseaudio /dev/snd/seq:matheus4986 f qsynth CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=bfc6f294-b737-4999-a444-01e1f410de06 InstallationDate: Installed on 2018-05-10 (308 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 15 7000 Gaming NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=659db14c-2a6c-4f9c-93bf-d31c4a84abb6 ro nouveau.blacklist=1 debug no_console_suspend systemd.log_level=info nvidia-drm.modeset=0 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip kvm lpadmin netdev plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/15/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0P84C9 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd08/15/2018:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn0P84C9:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819915/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819915] Re: s2disk freezes at saving image to disk (hibernation)
Yes please. Most likely it's cause by kernel and drivers update. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819915 Title: s2disk freezes at saving image to disk (hibernation) Status in linux package in Ubuntu: Confirmed Bug description: This started happening after I upgrade to ubuntu 18.04.2. In 18.04.1 hibernation was working flawlessly on my machine. (with kernel 4.15-46! not a kernel issue then?) Another thing that got updated recently was nvidia drivers which were known to cause hibernation issues, but those were on restoring the snapshot. http://imgur.com/gallery/jOyHEcL --> I get stuck on this screen after running hibernate or pm-hibernate. (sys-req REISUB combination works there and is the only good way to restart I found) SPECS Laptop Dell Inspiron 7567 A30P Intel Core i7-7700HQ 1x 16 GB DDR4 1 TB HDD + 256 GB SSD Nvidia GeForce GTX 1050 Ti FHD display Intel Dual Band Wireless AC 3165 1x1 Motherboard: Intel HM175 Graphics adapter: NVIDIA GeForce GTX 1050 Ti (Laptop) - 4096 MB, Core: 1620 MHz, Memory: 1752 MHz, GDDR5, 21.21.13.7320 (ForceWare 373.20), Nvidia Optimus nvidia driver: 415.27 INFO # uname -a Linux matheus-Inspiron-15-7000-Gaming 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux # free -m totalusedfree shared buff/cache available Mem: 1590629258742 1614238 12485 Swap: 16333 0 16333 # cat /etc/fstab | grep swap # swap was on /dev/sda8 during installation UUID=70d967e6-ad52-4c21-baf0-01a813ccc6ac noneswapsw 0 0 n root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep hibernate root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep hiber root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep s2disk root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | grep hibernation I could find nothing scrolling up on syslog about the hibernation process or with grep An interesting Note is that if I run hibernate just after I boot, it works and resumes perfectly! But after some system usage it randomly has that problem if I try. The percentage it freezes at is also random, sometimes 0, 1 even 30 once. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: matheus 25949 F...m pulseaudio /dev/snd/pcmC0D0p: matheus 25949 F...m pulseaudio /dev/snd/controlC0: matheus 25949 F pulseaudio /dev/snd/seq:matheus4986 f qsynth CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=bfc6f294-b737-4999-a444-01e1f410de06 InstallationDate: Installed on 2018-05-10 (308 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 15 7000 Gaming NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=659db14c-2a6c-4f9c-93bf-d31c4a84abb6 ro nouveau.blacklist=1 debug no_console_suspend systemd.log_level=info nvidia-drm.modeset=0 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip kvm lpadmin netdev plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/15/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0P84C9 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd08/15/2018:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn0P84C9:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819915/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820287] Re: kernel panic during pxe boot on DL360 gen9
If it's bare metal, the only way I know of is to use serial port. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820287 Title: kernel panic during pxe boot on DL360 gen9 Status in linux package in Ubuntu: Confirmed Bug description: A machine in our test lab kernel panic'd during PXE boot from MAAS. It was running 4.15.0-46-generic #49-Ubuntu I've attached a screenshot of the call trace. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813783] Re: Unable to toggle Touchpad by keyboard shortcut
So this shows when FN gets pressed, before F5? [ 248.412826] atkbd serio0: Unknown key pressed (translated set 2, code 0xf8 on isa0060/serio0). [ 248.412833] atkbd serio0: Use 'setkeycodes e078 ' to make it known. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813783 Title: Unable to toggle Touchpad by keyboard shortcut Status in linux package in Ubuntu: Confirmed Bug description: Pressing Fn+F5 button should toggle the onboard touchpad. This seems not to work and might be related to the following bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/717931 After pressing Fn+F5 shows the following: $ dmesg ... [ 248.412826] atkbd serio0: Unknown key pressed (translated set 2, code 0xf8 on isa0060/serio0). [ 248.412833] atkbd serio0: Use 'setkeycodes e078 ' to make it known. [ 250.261108] atkbd serio0: Unknown key released (translated set 2, code 0xf8 on isa0060/serio0). [ 250.261110] atkbd serio0: Use 'setkeycodes e078 ' to make it known. I've added the mentioned kernel parameters as described in https://wiki.ubuntu.com/DebuggingACPI (adding acpi=off) and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/717931/comments/21 (i8042.nomux=1) but the problem still exists. Touchpad also has a little dot in the upper left side which I assume also is for toggling on/off the touchpad. This is also unresponsive. How reproducible: Always Steps to Reproduce: Press Fn+F5 Actual results: Touchpad is not working Expected results: Touchpad should toggle on/off, making it able to use the touchpad. Extra info: Bios is up to date. $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ inxi -F System:Host: CarogaLaptopLinux Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3 Distro: Ubuntu 18.04.1 LTS Machine: Device: laptop System: Standard product: Standard v: Standard serial: N/A Mobo: Standard model: Standard v: Standard serial: N/A UEFI: American Megatrends v: N.0.05 date: 04/14/2018 BatteryBAT0: charge: 42.2 Wh 90.2% condition: 46.7/46.7 Wh (100%) CPU: 6 core Intel Core i7-8750H (-MT-MCP-) cache: 9216 KB clock speeds: max: 4100 MHz 1: 1541 MHz 2: 2043 MHz 3: 2069 MHz 4: 2345 MHz 5: 2241 MHz 6: 2111 MHz 7: 2080 MHz 8: 2047 MHz 9: 2035 MHz 10: 2388 MHz 11: 1879 MHz 12: 2175 MHz Graphics: Card-1: Intel Device 3e9b Card-2: NVIDIA GP106M [GeForce GTX 1060 Mobile] Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting,nvidia (unloaded: fbdev,vesa,nouveau) Resolution: 1920x1080@144.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics (Coffeelake 3x8 GT2) version: 4.5 Mesa 18.0.5 Audio: Card Intel Device a348 driver: snd_hda_intel Sound: ALSA v: k4.15.0-43-generic Network: Card-1: Intel Device a370 driver: iwlwifi IF: wlo1 state: up speed: N/A duplex: N/A mac: 94:b8:6d:fc:16:24 Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169 IF: enp4s0 state: down mac: b0:25:aa:29:17:57 Drives:HDD Total Size: 500.1GB (25.6% used) ID-1: /dev/nvme0n1 model: WDS500G2X0C size: 500.1GB ID-2: /dev/nvme1n1 model: WDS500G2X0C size: 500.1GB Partition: ID-1: / size: 398G used: 61G (17%) fs: ext4 dev: /dev/nvme0n1p2 ID-2: swap-1 size: 65.53GB used: 0.00GB (0%) fs: swap dev: /dev/nvme0n1p1 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 55.0C mobo: 54.0C Fan Speeds (in rpm): cpu: N/A Info: Processes: 387 Uptime: 16 min Memory: 3855.5/32027.2MB Client: Shell (zsh) inxi: 2.3.56 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caroga 3523 F...m pulseaudio /dev/snd/controlC0: caroga 3523 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 16:04:41 2019 HibernationDevice: RESUME=UUID=8cafe715-f523-4099-8dd8-7f80c5de58d4 InstallationDate: Installed on 2018-08-17 (164 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Standard Standard ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=e177b84e-a10b-4a4e-8d1c-8eeafbb021ba ro quiet splash i8042.nomux=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.1
[Kernel-packages] [Bug 1817200] Re: Trackpad is not recognized.
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1817200 Title: Trackpad is not recognized. Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: === SRU Justification === [Impact] Touchpad on Walmart Overpowered laptop doesn't work. [Fix] Quote the commit message: "The gpio base for GPP-E was set incorrectly to 258 instead of 256" [Test] User confirm the commit makes the touchpad work. [Regression Potential] Low. This commit is in upstream stable for a while. === Original Bug Report === Trackpad is not recognized in linux for Overpowered laptop model OP-LP1 (sold by Walmart) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-45-generic 4.15.0-45.48 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: d 2135 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Feb 21 14:01:39 2019 InstallationDate: Installed on 2019-02-21 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: OVERPOWERED OP-LP1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=abb2aee4-3166-41d9-8ac4-14a5a3fccc92 ro acpi_osi=! "acpi_osi=Windows 2009" blacklist=nouveau elevator=deadline drmdebug=0xe quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N.1.02 dmi.board.asset.tag: Standard dmi.board.name: GK5CN4Z dmi.board.vendor: OVERPOWERED dmi.board.version: Standard dmi.chassis.asset.tag: Standard dmi.chassis.type: 10 dmi.chassis.vendor: Standard dmi.chassis.version: Standard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN.1.02:bd09/26/2018:svnOVERPOWERED:pnOP-LP1:pvrStandard:rvnOVERPOWERED:rnGK5CN4Z:rvrStandard:cvnStandard:ct10:cvrStandard: dmi.product.family: OP-LP dmi.product.name: OP-LP1 dmi.product.version: Standard dmi.sys.vendor: OVERPOWERED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817200/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820796] Re: natacpi bug in 4.18.0-16-generic, fixed upstream 5.0.2
LP: #1812099? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820796 Title: natacpi bug in 4.18.0-16-generic, fixed upstream 5.0.2 Status in linux package in Ubuntu: Incomplete Bug description: low-impact bug, easy workaround. Thinkpad T480 4.18.0-16-generic Bug: # cd /sys/class/power_supply/BAT1 # # echo 95 > charge_start_threshold bash: echo: write error: No such device but it works for BAT0 It means tlp, latest version installed via PPA, by default can't set battery charge thresholds for the second battery in ubuntu 18.04 because tlp now defaults to using natacpi. This can be reverted to the old way of working via a simple change in the tlp conf file. This bug is fixed in 5.0.2 installed from ubuntu mainline ppa. I did not try earlier. - root@moncrief:/sys/class/power_supply/BAT1# cat /proc/version_signature Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820796] 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 1820796 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820796 Title: natacpi bug in 4.18.0-16-generic, fixed upstream 5.0.2 Status in linux package in Ubuntu: Incomplete Bug description: low-impact bug, easy workaround. Thinkpad T480 4.18.0-16-generic Bug: # cd /sys/class/power_supply/BAT1 # # echo 95 > charge_start_threshold bash: echo: write error: No such device but it works for BAT0 It means tlp, latest version installed via PPA, by default can't set battery charge thresholds for the second battery in ubuntu 18.04 because tlp now defaults to using natacpi. This can be reverted to the old way of working via a simple change in the tlp conf file. This bug is fixed in 5.0.2 installed from ubuntu mainline ppa. I did not try earlier. - root@moncrief:/sys/class/power_supply/BAT1# cat /proc/version_signature Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798708] Re: It will load nvidia driver when swith to Intel mode
The external monitor problem is probably a well-known gdm3 bug: gdm3 with nvidia modeset=1 stops the nvidia driver from detecting external monitors (possibly it invokes some wayland features when it shouldn't). It is not a problem with nvidia-prime or with the kernel. You can fix it by using lightdm instead of gdm3. This bug affects fedora as well. ubuntu 19.04 has reverted to nvidia modeset = 0 be default to avoid this bug (at the cost of unfixable screen tearing for Optimus users in nvidia mode). nvidia-prime does always include the nvidia modules in the initramfs kernel, this was a change in 18.10 backported to 18.04. Previous nvidia- prime pacakges used to rebuild initramfs to add or remove the module, but this is not required any longer. Choosing prime-select intel means the nvidia module is unloaded when the machine is starting. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798708 Title: It will load nvidia driver when swith to Intel mode Status in linux package in Ubuntu: Confirmed Bug description: We found the nvidia-prime will not run update-initramfs as before. After switch to intel, then reboot I found the nvidia modules was loaded. If I did S3 or close the lid, and resume back, the nvidia modules was removed, so the gnome session will be reloaded, you need to login again, all the opend applications in this session was gone. nvidia-prime 0.8.8.1 linux 4.15.0-1021-oem nvidia-driver-390 380.87-0ubuntu0~gpu18.04.1. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u 2218 F pulseaudio /dev/snd/controlC0: u 2218 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-bionic-amd64-20181018-40+sutton-mccarthy-bionic-amd64+iso DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=2b45d917-3587-410f-9b94-f52eb082b7dc InstallationDate: Installed on 2018-10-19 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20181018-09:17 MachineType: LENOVO 20MEZ480US NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1021-oem root=UUID=e68fa8d5-22f5-464b-9775-753b4ae159eb ro noprompt quiet splash acpi_osi=! acpi_osi=Linux-Lenovo-NV-HDMI-Audio vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1021.24-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1021-oem N/A linux-backports-modules-4.15.0-1021-oem N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-1021-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/04/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET30W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MEZ480US dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET30W(1.12):bd10/04/2018:svnLENOVO:pn20MEZ480US:pvrThinkPadP1:rvnLENOVO:rn20MEZ480US:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 dmi.product.name: 20MEZ480US dmi.product.version: ThinkPad P1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798708/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820687] Re: Sound issue, or rather, lack of sound
Does the sound come back by booting an older kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820687 Title: Sound issue, or rather, lack of sound Status in linux package in Ubuntu: Incomplete Bug description: Linux Mint 18.3 update Kernel 4.4.0-143-generic up-heaved my Alsa mixer/pulse-audio or something to disable sound, made the mixer and configurations useless and grayed out/inoperable. I have gone through this some time ago and forgotten how to remedy but the next thing, besides what I have tried futilely, will be to rollback the new kernel to its predecessor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820687/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820796] Re: natacpi bug in 4.18.0-16-generic, fixed upstream 5.0.2
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820796/+attachment/5247477/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820796 Title: natacpi bug in 4.18.0-16-generic, fixed upstream 5.0.2 Status in linux package in Ubuntu: New Bug description: low-impact bug, easy workaround. Thinkpad T480 4.18.0-16-generic Bug: # cd /sys/class/power_supply/BAT1 # # echo 95 > charge_start_threshold bash: echo: write error: No such device but it works for BAT0 It means tlp, latest version installed via PPA, by default can't set battery charge thresholds for the second battery in ubuntu 18.04 because tlp now defaults to using natacpi. This can be reverted to the old way of working via a simple change in the tlp conf file. This bug is fixed in 5.0.2 installed from ubuntu mainline ppa. I did not try earlier. - root@moncrief:/sys/class/power_supply/BAT1# cat /proc/version_signature Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820796] [NEW] natacpi bug in 4.18.0-16-generic, fixed upstream 5.0.2
Public bug reported: low-impact bug, easy workaround. Thinkpad T480 4.18.0-16-generic Bug: # cd /sys/class/power_supply/BAT1 # # echo 95 > charge_start_threshold bash: echo: write error: No such device but it works for BAT0 It means tlp, latest version installed via PPA, by default can't set battery charge thresholds for the second battery in ubuntu 18.04 because tlp now defaults to using natacpi. This can be reverted to the old way of working via a simple change in the tlp conf file. This bug is fixed in 5.0.2 installed from ubuntu mainline ppa. I did not try earlier. - root@moncrief:/sys/class/power_supply/BAT1# cat /proc/version_signature Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820796 Title: natacpi bug in 4.18.0-16-generic, fixed upstream 5.0.2 Status in linux package in Ubuntu: New Bug description: low-impact bug, easy workaround. Thinkpad T480 4.18.0-16-generic Bug: # cd /sys/class/power_supply/BAT1 # # echo 95 > charge_start_threshold bash: echo: write error: No such device but it works for BAT0 It means tlp, latest version installed via PPA, by default can't set battery charge thresholds for the second battery in ubuntu 18.04 because tlp now defaults to using natacpi. This can be reverted to the old way of working via a simple change in the tlp conf file. This bug is fixed in 5.0.2 installed from ubuntu mainline ppa. I did not try earlier. - root@moncrief:/sys/class/power_supply/BAT1# cat /proc/version_signature Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820755] Re: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found
I have a same problem too. It seems to be problem of linux-base package version. linux-image-4.4.0-143-generic require linux-base 4.5ubuntu1 but netboot installer use a linux-base 4.0ubuntu1 which does not contain below tools. /usr/bin/linux-update-symlinks /usr/bin/linux-version /usr/bin/linux-check-removal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1820755 Title: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found Status in linux-base package in Ubuntu: Confirmed Bug description: Using a netboot install of Ubuntu 16.04 LTS server, the install fails when configuring the kernel. The failure will not let you move on. This seems to have happened after the release of https://lists.ubuntu.com/archives/ubuntu-security-announce/2019-March/004803.html The error logs Mar 18 17:09:50 in-target: Setting up linux-modules-4.4.0-143-generic (4.4.0-143.169) ... Mar 18 17:09:50 in-target: ^M Mar 18 17:09:51 in-target: Setting up linux-image-4.4.0-143-generic (4.4.0-143.169) ... Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: Mar 18 17:09:51 in-target: linux-update-symlinks: not found Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: dpkg: error processing package linux-image-4.4.0-143-generic (--configure): Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: subprocess installed post-installation script returned error exit status 127 Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: dpkg: dependency problems prevent configuration of linux-modules-extra-4.4.0-143-generic: Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: linux-modules-extra-4.4.0-143-generic depends on linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however: Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: Package linux-image-4.4.0-143-generic is not configured yet. Mar 18 17:09:51 in-target: ^M Mar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1820755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811999] Re: [USB-Audio - Audioengine D3, playback] fails after a while (a second)
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811999 Title: [USB-Audio - Audioengine D3, playback] fails after a while (a second) Status in linux package in Ubuntu: Expired Bug description: USB DAC stops playing sound after a second. I had problem with kernel 4.15. So, I tried upgrading to 4.19 but still issue persists. I think, we might need to add it to sound/usb/quirks.c I see following in dmesg [ 155.552404] usb 1-1.4.1: new full-speed USB device number 10 using xhci_hcd [ 155.941031] usb 1-1.4.1: New USB device found, idVendor=2912, idProduct=120b, bcdDevice= 1.0c [ 155.941035] usb 1-1.4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 155.941037] usb 1-1.4.1: Product: Audioengine D3 [ 155.941038] usb 1-1.4.1: Manufacturer: Audioengine [ 155.941040] usb 1-1.4.1: SerialNumber: Audioengine [ 156.503248] usb 1-1.4.1: 1:1: cannot get freq at ep 0x1 [ 156.526074] usbcore: registered new interface driver snd-usb-audio [ 156.575999] usb 1-1.4.1: 1:1: cannot get freq at ep 0x1 [ 156.605461] usb 1-1.4.1: 1:1: cannot get freq at ep 0x1 And lsusb -v has following entry for the device. Bus 001 Device 017: ID 2912:120b Couldn't open device, some information will be missing Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x2912 idProduct 0x120b bcdDevice1.0c iManufacturer 1 iProduct2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 131 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 200mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 0 bInterfaceClass 1 Audio bInterfaceSubClass 1 Control Device bInterfaceProtocol 0 iInterface 0 AudioControl Interface Descriptor: bLength 9 bDescriptorType36 bDescriptorSubtype 1 (HEADER) bcdADC 1.00 wTotalLength 43 bInCollection 1 baInterfaceNr( 0) 1 AudioControl Interface Descriptor: bLength12 bDescriptorType36 bDescriptorSubtype 2 (INPUT_TERMINAL) bTerminalID 5 wTerminalType 0x0101 USB Streaming bAssocTerminal 0 bNrChannels 2 wChannelConfig 0x0003 Left Front (L) Right Front (R) iChannelNames 0 iTerminal 0 AudioControl Interface Descriptor: bLength13 bDescriptorType36 bDescriptorSubtype 6 (FEATURE_UNIT) bUnitID 7 bSourceID 5 bControlSize2 bmaControls( 0) 0x01 bmaControls( 0) 0x00 Mute Control bmaControls( 1) 0x02 bmaControls( 1) 0x00 Volume Control bmaControls( 2) 0x02 bmaControls( 2) 0x00 Volume Control iFeature0 AudioControl Interface Descriptor: bLength 9 bDescriptorType36 bDescriptorSubtype 3 (OUTPUT_TERMINAL) bTerminalID 8 wTerminalType 0x0301 Speaker bAssocTerminal 0 bSourceID 7 iTerminal 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 0 bInterfaceClass 1 Audio bInterfaceSubClass 2 Streaming bInterfaceProtocol 0 iInterface 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 1 bNumEndpoints 2 bInterfaceClass 1 Audio
[Kernel-packages] [Bug 1820695] Re: 5.0.0 kernels (5.0.0-7 and 5.0.0-8) don't boot
Would it be possible for you to do a kernel bisection? First, find the last good kernel (4.19 in this case) and the first bad -rc kernel (5.0-rc*) from http://kernel.ubuntu.com/~kernel-ppa/mainline/ Then, $ sudo apt build-dep linux $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git $ cd linux $ git bisect start $ git bisect good $(the good version you found) $ git bisect bad $(the bad version found) $ make localmodconfig $ make -j`nproc` deb-pkg Install the newly built kernel, then reboot with it. If the issue still happens, $ git bisect bad Otherwise, $ git bisect good Repeat to "make -j`nproc` deb-pkg" until you find the commit that causes the regression. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820695 Title: 5.0.0 kernels (5.0.0-7 and 5.0.0-8) don't boot Status in linux package in Ubuntu: Confirmed Bug description: System runs fine with previous kernel 4.19.0-13-generic. On kernels 5.0.0-7 and 5.0.0-8, system freezes after GRUB screen on the background picture. Note: The attached logs are done with kernel 4.19.0-13-generic, since the kernels in question don't even boot and give no chance to catch a log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820695/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1652101] Re: Can't create nested AppArmor namespaces
It is fixed to the degree it can be fixed until upstream agrees on
changes in the LSM layer.
The apparmor devs certainly can do the work of proposing new hooks, etc
that are necessary but it hasn't been the highest priority item. I will
note that this is a high priority item, just that others have been
ranked higher.
There is hope that someone can return to this soon.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1652101
Title:
Can't create nested AppArmor namespaces
Status in AppArmor:
Confirmed
Status in apparmor package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
A user with CAP_MAC_ADMIN in the init namespace can create an AppArmor
policy namespace and load a profile belonging to that AppArmor
namespace. Once that's done, the user can confine a process with that
namespaced AppArmor profile and enter into a user namespace. That
process can then load additional AppArmor profiles inside of the
AppArmor and user namespace. Here's an example:
We need to set up the namespace, n1, and load the profile, p1.
$ export rules="file, signal, unix, dbus, ptrace, mount, pivot_root,
capability,"
$ sudo mkdir /sys/kernel/security/apparmor/policy/namespaces/n1
$ echo "profile p1 { $rules }" | sudo apparmor_parser -qrn n1
Now we enter into confinement using the AppArmor namespace and profile and
then enter into an unprivileged user namespace
$ aa-exec -n n1 -p p1 -- unshare -Ur
We can now load profiles as the privileged user inside of the unprivileged
user namespace
# echo "profile test {}" | apparmor_parser -qr
The reason for this bug report is that we cannot create a nested
AppArmor policy namespace inside of the unprivileged user namespace
# mkdir /sys/kernel/security/apparmor/policy/namespaces/n1/namespaces/p1
mkdir: cannot create directory
‘/sys/kernel/security/apparmor/policy/namespaces/n1/namespaces/p1’: Permission
denied
If that worked, we could adjust LXD to read
/sys/kernel/security/apparmor/.ns_name to get the current AppArmor
namespace, then create a new namespace under the current namespace,
and leverage the nested namespace for its nested containers.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1652101/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820685] Re: Wrong resolution during boot
Can you please try some slightly older kernels and tell us if using those avoids the bug? https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820685 Title: Wrong resolution during boot Status in linux package in Ubuntu: Incomplete Bug description: When booting the startup screen is in low resolution while before it was in high resolution. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 18 18:04:57 2019 DistUpgraded: 2018-09-26 21:31:06,974 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-46-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 530] [10de:0de5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 530] [1043:839b] InstallationDate: Installed on 2018-01-04 (437 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: ASUSTeK COMPUTER INC. CM6870 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic root=UUID=4aa7afed-ca87-4f94-9a08-c806fccfbd1d ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-09-26 (172 days ago) dmi.bios.date: 12/25/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0708 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: CM6870 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0708:bd12/25/2012:svnASUSTeKCOMPUTERINC.:pnCM6870:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCM6870:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: Desktop dmi.product.name: CM6870 dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Sep 26 20:09:04 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820685] Re: Wrong resolution during boot
Actually it looks like just vesafb starting in low resolution: [0.532845] vesafb: mode is 1280x1024x32, linelength=5120, pages=0 [0.532846] vesafb: scrolling: redraw [0.532847] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0 [0.532854] vesafb: framebuffer at 0xf100, mapped to 0x(ptrval), using 5120k, total 5120k which is then later corrected by nouveaufb: [ 15.346865] fb: switching to nouveaufb from VESA VGA ... [ 16.853149] nouveau :01:00.0: DRM: allocated 1920x1080 fb: 0x6, bo 4d979e0c so it sounds like the main issue is that vesafb is used at all during boot. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Tags removed: nvidia -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820685 Title: Wrong resolution during boot Status in linux package in Ubuntu: Incomplete Bug description: When booting the startup screen is in low resolution while before it was in high resolution. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 18 18:04:57 2019 DistUpgraded: 2018-09-26 21:31:06,974 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-46-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 530] [10de:0de5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 530] [1043:839b] InstallationDate: Installed on 2018-01-04 (437 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: ASUSTeK COMPUTER INC. CM6870 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic root=UUID=4aa7afed-ca87-4f94-9a08-c806fccfbd1d ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-09-26 (172 days ago) dmi.bios.date: 12/25/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0708 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: CM6870 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0708:bd12/25/2012:svnASUSTeKCOMPUTERINC.:pnCM6870:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCM6870:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: Desktop dmi.product.name: CM6870 dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Sep 26 20:09:04 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while
No problem. If the issue doesn't return after 60 days and there are no further comments then this bug will automatically close. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818802 Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Audio dies after few seconds, returns after few minutes and dies again filip@ux433:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.20.14-042014-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 8566 F pulseaudio /dev/snd/pcmC0D0p: filip 8566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 10:11:01 2019 InstallationDate: Installed on 2019-01-05 (59 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 comm="/usr/bin/pulseaudio --daemonize=no ") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN 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.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818802/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820685] [NEW] Wrong resolution during boot
You have been subscribed to a public bug: When booting the startup screen is in low resolution while before it was in high resolution. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 18 18:04:57 2019 DistUpgraded: 2018-09-26 21:31:06,974 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-46-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 530] [10de:0de5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 530] [1043:839b] InstallationDate: Installed on 2018-01-04 (437 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: ASUSTeK COMPUTER INC. CM6870 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic root=UUID=4aa7afed-ca87-4f94-9a08-c806fccfbd1d ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-09-26 (172 days ago) dmi.bios.date: 12/25/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0708 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: CM6870 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0708:bd12/25/2012:svnASUSTeKCOMPUTERINC.:pnCM6870:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCM6870:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: Desktop dmi.product.name: CM6870 dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Sep 26 20:09:04 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: nouveau ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic nouveau nvidia resolution ubuntu -- Wrong resolution during boot https://bugs.launchpad.net/bugs/1820685 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1652101] Re: Can't create nested AppArmor namespaces
how does this get assigned to someone so it might get fixed?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1652101
Title:
Can't create nested AppArmor namespaces
Status in AppArmor:
Confirmed
Status in apparmor package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
A user with CAP_MAC_ADMIN in the init namespace can create an AppArmor
policy namespace and load a profile belonging to that AppArmor
namespace. Once that's done, the user can confine a process with that
namespaced AppArmor profile and enter into a user namespace. That
process can then load additional AppArmor profiles inside of the
AppArmor and user namespace. Here's an example:
We need to set up the namespace, n1, and load the profile, p1.
$ export rules="file, signal, unix, dbus, ptrace, mount, pivot_root,
capability,"
$ sudo mkdir /sys/kernel/security/apparmor/policy/namespaces/n1
$ echo "profile p1 { $rules }" | sudo apparmor_parser -qrn n1
Now we enter into confinement using the AppArmor namespace and profile and
then enter into an unprivileged user namespace
$ aa-exec -n n1 -p p1 -- unshare -Ur
We can now load profiles as the privileged user inside of the unprivileged
user namespace
# echo "profile test {}" | apparmor_parser -qr
The reason for this bug report is that we cannot create a nested
AppArmor policy namespace inside of the unprivileged user namespace
# mkdir /sys/kernel/security/apparmor/policy/namespaces/n1/namespaces/p1
mkdir: cannot create directory
‘/sys/kernel/security/apparmor/policy/namespaces/n1/namespaces/p1’: Permission
denied
If that worked, we could adjust LXD to read
/sys/kernel/security/apparmor/.ns_name to get the current AppArmor
namespace, then create a new namespace under the current namespace,
and leverage the nested namespace for its nested containers.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1652101/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817969] Re: hns3 nic speed may not match optical port speed
** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1817969 Title: hns3 nic speed may not match optical port speed Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Released Bug description: [Impact] The onboard optical NICs on HiSilicon D06 systems do not adjust to match the actual optical module speed. [Test Case] Verify that linked speed of interface matches the optical port speed. [Fix] 5d497936756fa net: hns3: Config NIC port speed same as that of optical module [Regression Risk] Fix is restricted to a driver that is only used for the Hi1620 SoC. Note: for pre-GA hardware, this does require a firmware fix as well. Without it, users will see messages like this on the console: [ 769.833818] hns3 :bd:00.0: get sfp speed failed -5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817969/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816425] Re: Use memblock quirk instead of delayed allocation for GICv3 LPI tables
Verified - I was able to successfully crash dump a cosmic system. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1816425 Title: Use memblock quirk instead of delayed allocation for GICv3 LPI tables Status in linux package in Ubuntu: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] The fix for LP: #1806766 has the issue that the persistent memory reservations for the GICv3 LPI tables may have been allocated an overwritten by the time we get to reserving them. This can continue to break kdump in certain conditions. [Test Case] sudo apt install linux-crashdump echo 'GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=512M"' | \ sudo tee /etc/default/grub.d/kdump-tools.cfg sudo update-grub sudo reboot echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger [Fix] 582a32e708823 efi/arm: Revert "Defer persistent reservations until after paging_init()" 8a5b403d71aff arm64, mm, efi: Account for GICv3 LPI tables in static memblock reserve table [Regression Risk] The change in reserved regions only impacts arm64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816425/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820755] Re: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found
I can confirm I'm seeing this as well with a fresh install from the latest 16.04 netboot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1820755 Title: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found Status in linux-base package in Ubuntu: Confirmed Bug description: Using a netboot install of Ubuntu 16.04 LTS server, the install fails when configuring the kernel. The failure will not let you move on. This seems to have happened after the release of https://lists.ubuntu.com/archives/ubuntu-security-announce/2019-March/004803.html The error logs Mar 18 17:09:50 in-target: Setting up linux-modules-4.4.0-143-generic (4.4.0-143.169) ... Mar 18 17:09:50 in-target: ^M Mar 18 17:09:51 in-target: Setting up linux-image-4.4.0-143-generic (4.4.0-143.169) ... Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: Mar 18 17:09:51 in-target: linux-update-symlinks: not found Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: dpkg: error processing package linux-image-4.4.0-143-generic (--configure): Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: subprocess installed post-installation script returned error exit status 127 Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: dpkg: dependency problems prevent configuration of linux-modules-extra-4.4.0-143-generic: Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: linux-modules-extra-4.4.0-143-generic depends on linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however: Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: Package linux-image-4.4.0-143-generic is not configured yet. Mar 18 17:09:51 in-target: ^M Mar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1820755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820755] Re: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-base (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1820755 Title: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found Status in linux-base package in Ubuntu: Confirmed Bug description: Using a netboot install of Ubuntu 16.04 LTS server, the install fails when configuring the kernel. The failure will not let you move on. This seems to have happened after the release of https://lists.ubuntu.com/archives/ubuntu-security-announce/2019-March/004803.html The error logs Mar 18 17:09:50 in-target: Setting up linux-modules-4.4.0-143-generic (4.4.0-143.169) ... Mar 18 17:09:50 in-target: ^M Mar 18 17:09:51 in-target: Setting up linux-image-4.4.0-143-generic (4.4.0-143.169) ... Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: Mar 18 17:09:51 in-target: linux-update-symlinks: not found Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: dpkg: error processing package linux-image-4.4.0-143-generic (--configure): Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: subprocess installed post-installation script returned error exit status 127 Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: dpkg: dependency problems prevent configuration of linux-modules-extra-4.4.0-143-generic: Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: linux-modules-extra-4.4.0-143-generic depends on linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however: Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: Package linux-image-4.4.0-143-generic is not configured yet. Mar 18 17:09:51 in-target: ^M Mar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1820755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809841] Re: Touchpad showing as PS/2 Generic Mouse
Unfortunately that did not resolve this but I am fine with leaving this closed Thank you for following up! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809841 Title: Touchpad showing as PS/2 Generic Mouse Status in linux package in Ubuntu: Expired Bug description: The touchpad on my HP 1011 Elite X2 G1 is showing as a PS/2 mouse after installation in xinput. Multitouch gestures do not work and installing xserver-xorg-input-synaptics did not resolve the issue. The touch pad uses the Synaptics driver in Windows 10. Other functionalities of the keyboard do work such as enabling/disabling wireless and volume up/down. The touchpad should be able to use multitouch for two-finger scrolling and two-finger tap for right click but instead only single touch inputs are accepted for left and right click. No multitouch gestures are recognized. Current version is Ubuntu 4.15.0-43.46-generic 4.15.18 on Ubuntu 18.04.1 LTS. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: johnny 1379 F...m pulseaudio /dev/snd/controlC0: johnny 1379 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 26 19:31:50 2018 InstallationDate: Installed on 2018-12-21 (5 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP Elite x2 1011 G1 Tablet ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=0d10c1f2-6c44-4717-a4df-73b592d11fe3 ro i8042.reset quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M72 Ver. 01.25 dmi.board.name: 2009 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 79.61 dmi.chassis.asset.tag: 5CG5465MYV dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM72Ver.01.25:bd10/30/2018:svnHewlett-Packard:pnHPElitex21011G1Tablet:pvrA3009FD10303:rvnHewlett-Packard:rn2009:rvrKBCVersion79.61:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP Elite x2 1011 G1 Tablet dmi.product.version: A3009FD10303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809841/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
siyia, I don't think they created it. Firmwares are often manufactured by third party companies however it would be nice to see a studious community work. -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
I think acer should join the Linux Foundation or sth, this is embarassing, they cant even create proper iASL compliant bios. -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
@Darksurf i looked at that laptop model and there was an 1.12 bios for it but the changes wasn't that exciting. Bios 1.12 "1.Add SCCM solution. 2.Change touch pad mode from basic to advance for linux sku." I do know that A315-41 got the touchpad changes as well with 1.13 -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
Created attachment 281891 attachment-3076-0.html So it looks like my changes in 1.12 got merged into everyone's 1.13? it's an obvious attempt at some form of Linux support. BIOS tweaks don't have to be exciting or glorious to show they're trying vs ignoring us. It's baby steps in the right direction. They also don't breakdown the exact changes making the changes seem vague and unexciting. Not much in the way of details. On Mon, Mar 18, 2019, 08:45 wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=200087 > > --- Comment #111 from Erik (erikjohans...@flashbox.5july.org) --- > @Darksurf i looked at that laptop model and there was an 1.12 bios for it > but > the changes wasn't that exciting. > Bios 1.12 > "1.Add SCCM solution. > 2.Change touch pad mode from basic to advance for linux sku." > I do know that A315-41 got the touchpad changes as well with 1.13 > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1690085]
So if you got message with "typical current idle" option: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0) it means probe of this C-state failed and it must be avoided by kernel. Is there any difference between C-state list in OS with and without this option? I have only laptop with very limited BIOS and can't check. And there only C0-1-2. What about C6? What says zenstates.py about that? Frankly, I have not tried this script - do not want disable power-saving features for laptop. Also some overclocking may solve this problem (see comment 103). Turn on "performance bias" or similar option in BIOS for testing. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "
[Kernel-packages] [Bug 1776563]
touchpad gets stuck sometimes during boot or after hibernation, but it is easy to fix with a script containing: modprobe -r i2c_hid modprobe i2c_hid -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
Created attachment 281887 attachment-32209-0.html That update was for the AN515-42 Acer Nitro5. They're are legitimately making an attempt, so color me impressed. On Mon, Mar 18, 2019, 08:17 wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=200087 > > --- Comment #109 from siyia (eutychio...@gmail.com) --- > there is no bios update 1.12 where did you get this? > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
Created attachment 281883 Manjaro kernel config in use with bios 1.13 this is the standard running kernel config of manjaro nothing exotic. -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
there is no bios update 1.12 where did you get this? -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
Created attachment 281885 attachment-28119-0.html They called out in BIOS update 1.12 that it was an attempt at fixing "Linux SKU". On Mon, Mar 18, 2019, 06:10 wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=200087 > > --- Comment #107 from siyia (eutychio...@gmail.com) --- > Created attachment 281883 > --> https://bugzilla.kernel.org/attachment.cgi?id=281883&action=edit > Manjaro kernel config in use with bios 1.13 > > this is the standard running kernel config of manjaro nothing exotic. > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
Whoa, looks like ACER really trying fix this! Sadly, current solution is not working for all. And touchpad behaviors somewhat strange. It forced to advanced mode in 1.03 bios too, but does not cause suspend issues - sleep by Fn+F1 works fine. -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
anyways if acer uploads a new bios, i wont update again, i think it was pure luck they fixed it. -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
(In reply to siyia from comment #96) > on kernel 5.01 with bios v 1.13 everything works out of the box even > touchpad and suspend!!! it is time to close this nusty bug once and for > all!!! Could you please attach the kernel config used for that 5.0 kernel. -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
0: 41 0 0 337718 IR-IO-APIC2-edge timer 1: 0 0 0435 IR-IO-APIC1-edge i8042 6: 0 0900 0 IR-IO-APIC6-edge AMDI0010:01 7: 0 0 0 337784 IR-IO-APIC7-fasteoi pinctrl_amd 8: 0 1 0 0 IR-IO-APIC8-edge rtc0 9: 0 2 0 0 IR-IO-APIC9-fasteoi acpi 25: 0 0 0 0 PCI-MSI 4096-edge AMD-Vi 26: 0 0 0 0 IR-PCI-MSI 18432-edge PCIe PME, aerdrv, pciehp 27: 0 0 0 0 IR-PCI-MSI 28672-edge PCIe PME, aerdrv 28: 0 0 0 0 IR-PCI-MSI 30720-edge PCIe PME, aerdrv 29: 0 0 0 0 IR-PCI-MSI 133120-edge PCIe PME 30: 0 0 0 0 IR-PCI-MSI 135168-edge PCIe PME 32: 0 0 14 0 IR-PCI-MSI 1048576-edge rtsx_pci 34: 5021 0222 0 IR-PCI-MSI 2103296-edge xhci_hcd 35: 0 0 0 0 IR-PCI-MSI 2103297-edge xhci_hcd 36: 0 0 0 0 IR-PCI-MSI 2103298-edge xhci_hcd 37: 0 0 0 0 IR-PCI-MSI 2103299-edge xhci_hcd 38: 0 0 0 0 IR-PCI-MSI 2103300-edge xhci_hcd 40: 0 43 0 0 IR-PCI-MSI 2105344-edge xhci_hcd 41: 0 0 0 0 IR-PCI-MSI 2105345-edge xhci_hcd 42: 0 0 0 0 IR-PCI-MSI 2105346-edge xhci_hcd 43: 0 0 0 0 IR-PCI-MSI 2105347-edge xhci_hcd 44: 0 0 0 0 IR-PCI-MSI 2105348-edge xhci_hcd 46: 0 0 4560 4458 IR-PCI-MSI 2621440-edge ahci[:05:00.0] 48: 0 0 0 0 IR-PCI-MSI 1050624-edge enp2s0f1 51: 0 9953 0 0 IR-PCI-MSI 1572864-edge ath10k_pci 52: 0 0 65 0 IR-PCI-MSI 524288-edge amdgpu 54: 0 0 0154 IR-PCI-MSI 2099200-edge snd_hda_intel:card0 55:743 0 0 0 IR-PCI-MSI 2109440-edge snd_hda_intel:card1 56: 0 2933 52252 0 IR-PCI-MSI 2097152-edge amdgpu 57: 0 0 0 2 amd_gpio 90 SYNA7DB5:01 NMI: 0 0 0 0 Non-maskable interrupts LOC: 33374 41942 40050 31907 Local timer interrupts SPU: 0 0 0 0 Spurious interrupts PMI: 0 0 0 0 Performance monitoring interrupts IWI: 0 0 0 0 IRQ work interrupts RTR: 0 0 0 0 APIC ICR read retries RES: 70523 61960 62555 69313 Rescheduling interrupts CAL: 11464 7087 9805 9037 Function call interrupts TLB: 32793 26519 27310 23387 TLB shootdowns TRM: 0 0 0 0 Thermal event interrupts THR: 0 0 0 0 Threshold APIC interrupts DFR: 0 0 0 0 Deferred Error APIC interrupts MCE: 0 0 0 0 Machine check exceptions MCP: 2 2 2 2 Machine check polls HYP: 0 0 0 0 Hypervisor callback interrupts HRE: 0 0 0 0 Hyper-V reenlightenment interrupts HVS: 0 0 0 0 Hyper-V stimer0 interrupts ERR: 0 MIS: 0 PIN: 0 0 0 0 Posted-interrupt notification event NPI: 0 0 0 0 Nested posted-interrupt event PIW: 0 0 0 0 Posted-interrupt wakeup event -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Confirmed Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new noteb
[Kernel-packages] [Bug 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while
** Attachment added: "dmesgafter.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818802/+attachment/5247408/+files/dmesgafter.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/1818802 Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Audio dies after few seconds, returns after few minutes and dies again filip@ux433:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.20.14-042014-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 8566 F pulseaudio /dev/snd/pcmC0D0p: filip 8566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 10:11:01 2019 InstallationDate: Installed on 2019-01-05 (59 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 comm="/usr/bin/pulseaudio --daemonize=no ") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN 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.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818802/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while
** Attachment added: "journalafter.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818802/+attachment/5247407/+files/journalafter.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/1818802 Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Audio dies after few seconds, returns after few minutes and dies again filip@ux433:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.20.14-042014-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 8566 F pulseaudio /dev/snd/pcmC0D0p: filip 8566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 10:11:01 2019 InstallationDate: Installed on 2019-01-05 (59 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 comm="/usr/bin/pulseaudio --daemonize=no ") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN 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.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818802/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769927] Comment bridged from LTC Bugzilla
*** This bug is a duplicate of bug 1751328 *** https://bugs.launchpad.net/bugs/1751328 --- Comment From s...@us.ibm.com 2019-03-18 17:02 EDT--- No response from submitter in a long time. Rejecting. -- 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/1769927 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3g4:ubuntu1604:'kdump-config show' shows Not ready to kdump even after doing kdump setup. Status in The Ubuntu-power-systems project: Incomplete Status in makedumpfile package in Ubuntu: Incomplete Bug description: Problem Description: === 'kdump-config show' shows Not ready to kdump even after doing kdump setup on ubuntu160404 guest. Steps to re-create: == 1. boslcp3 is up with BMC:1.20 & PNOR: 20180420 levels 2. Installed p8 compat guest with ubutnu160404 root@boslcp3g4:~# uname -a Linux boslcp3g4 4.4.0-122-generic #146-Ubuntu SMP Mon Apr 23 15:33:25 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3g4:~# uname -r 4.4.0-122-generic 3. Installed linux-crashdump crash dump utility. 4. root@boslcp3g4:~# cat /etc/default/grub.d/kexec-tools.cfg GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4096M" root@boslcp3g4:~# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinux-4.4.0-116-generic root=UUID=8be749b1-a5a8-4ab8-986c-ee4fcc61165e ro root@boslcp3g4:~# 5. rebooted guest and checked kdump status. root@boslcp3g4:~# /etc/init.d/kdump-tools status ? kdump-tools.service - Kernel crash dump capture service Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor preset: enabled) Active: active (exited) since Sun 2018-05-06 04:18:37 EDT; 7min ago Process: 2317 ExecStart=/etc/init.d/kdump-tools start (code=exited, status=0/SUCCESS) Main PID: 2317 (code=exited, status=0/SUCCESS) Tasks: 0 Memory: 0B CPU: 0 CGroup: /system.slice/kdump-tools.service May 06 04:18:37 boslcp3g4 systemd[1]: Starting Kernel crash dump capture service... May 06 04:18:37 boslcp3g4 kdump-tools[2317]: Starting kdump-tools: * no crashkernel= parameter in the kernel cmdline May 06 04:18:37 boslcp3g4 systemd[1]: Started Kernel crash dump capture service. root@boslcp3g4:~# sed -i 's/USE_KDUMP=0/USE_KDUMP=1/g' /etc/default/kdump-tools 4. kdump state root@boslcp3g4:~# kdump-config show * no crashkernel= parameter in the kernel cmdline DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz kdump initrd: /var/lib/kdump/initrd.img current state:Not ready to kdump kexec command: no kexec command recorded --> It still says 'Not ready to kdump' --> Becuase of this state not able take dump when guest hangs/crashes > Tried again changing crashkernel parameter on ubuntu160404 guest- p8 compat ,but still facing same issue root@boslcp3g4:/kte/tools/setup.d# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinux-4.4.0-122-generic root=UUID=8be749b1-a5a8-4ab8-986c-ee4fcc61165e ro ro splash quiet xmon=on crashkernel=512M crashkernel=4096M root@boslcp3g4:/kte/tools/setup.d# root@boslcp3g4:/kte/tools/setup.d# /etc/init.d/kdump-tools status ? kdump-tools.service - Kernel crash dump capture service Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor preset: enabled) Active: active (exited) since Sun 2018-05-06 04:59:51 EDT; 14min ago Main PID: 2330 (code=exited, status=0/SUCCESS) Tasks: 0 Memory: 0B CPU: 0 CGroup: /system.slice/kdump-tools.service May 06 04:59:50 boslcp3g4 systemd[1]: Starting Kernel crash dump capture se. May 06 04:59:51 boslcp3g4 kdump-tools[2330]: Starting kdump-tools: * Invali...g May 06 04:59:51 boslcp3g4 kdump-tools[2330]: * Creating symlink /var/lib/kd...g May 06 04:59:51 boslcp3g4 kdump-tools[2330]: * Invalid symlink : /var/lib/k...z May 06 04:59:51 boslcp3g4 kdump-tools[2330]: * Creating symlink /var/lib/kd...z May 06 04:59:51 boslcp3g4 kdump-tools[2330]: * /etc/default/kdump-tools: KD...g May 06 04:59:51 boslcp3g4 systemd[1]: Started Kernel crash dump capture service. Hint: Some lines were ellipsized, use -l to show in full. root@boslcp3g4:/kte/tools/setup.d# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.4.0-122-generic kdump initrd: /var/lib/kdump/initrd.img: broken symbolic link to /var/lib/kdump/initrd.img-4.4.0-122-generic current state:Not ready to kdump kexec command: no kexec command recorded --> Still kdump state shows 'Not ready to kdump' Regards, Indira > > > Thanks Breno! You point out
[Kernel-packages] [Bug 1819620] Re: linux-gcp: 4.18.0-1008.9 -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 1819619 (bionic/linux-gcp-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819624 phase: Promote to Proposed phase-changed: Monday, 18. March 2019 18:35 UTC reason: - promote-to-proposed: Ongoing -- packages copied but not yet published to -proposed + promote-to-proposed: Ongoing -- packages copies requested -- 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/1819620 Title: linux-gcp: 4.18.0-1008.9 -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 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 1819619 (bionic/linux-gcp-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819624 phase: Promote to Proposed phase-changed: Monday, 18. March 2019 18:35 UTC reason: promote-to-proposed: Ongoing -- packages copies requested To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819694] Re: linux-aws: 4.15.0-1035.37 -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 backports: bug 1819693 (xenial/linux-aws-hwe) -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1819716 - phase: Holding before Promote to Proposed - phase-changed: Monday, 18. March 2019 19:00 UTC + phase: Ready for Promote to Proposed + phase-changed: Monday, 18. March 2019 21:05 UTC reason: - promote-to-proposed: Ongoing -- builds not complete + promote-to-proposed: Pending -- ready for review -- 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/1819694 Title: linux-aws: 4.15.0-1035.37 -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: 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid 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 1819693 (xenial/linux-aws-hwe) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819716 phase: Ready for Promote to Proposed phase-changed: Monday, 18. March 2019 21:05 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819694/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820755] [NEW] Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found
Public bug reported: Using a netboot install of Ubuntu 16.04 LTS server, the install fails when configuring the kernel. The failure will not let you move on. This seems to have happened after the release of https://lists.ubuntu.com/archives/ubuntu-security-announce/2019-March/004803.html The error logs Mar 18 17:09:50 in-target: Setting up linux-modules-4.4.0-143-generic (4.4.0-143.169) ... Mar 18 17:09:50 in-target: ^M Mar 18 17:09:51 in-target: Setting up linux-image-4.4.0-143-generic (4.4.0-143.169) ... Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: Mar 18 17:09:51 in-target: linux-update-symlinks: not found Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: dpkg: error processing package linux-image-4.4.0-143-generic (--configure): Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: subprocess installed post-installation script returned error exit status 127 Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: dpkg: dependency problems prevent configuration of linux-modules-extra-4.4.0-143-generic: Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: linux-modules-extra-4.4.0-143-generic depends on linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however: Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: Package linux-image-4.4.0-143-generic is not configured yet. Mar 18 17:09:51 in-target: ^M Mar ** Affects: linux-base (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1820755 Title: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found Status in linux-base package in Ubuntu: New Bug description: Using a netboot install of Ubuntu 16.04 LTS server, the install fails when configuring the kernel. The failure will not let you move on. This seems to have happened after the release of https://lists.ubuntu.com/archives/ubuntu-security-announce/2019-March/004803.html The error logs Mar 18 17:09:50 in-target: Setting up linux-modules-4.4.0-143-generic (4.4.0-143.169) ... Mar 18 17:09:50 in-target: ^M Mar 18 17:09:51 in-target: Setting up linux-image-4.4.0-143-generic (4.4.0-143.169) ... Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: Mar 18 17:09:51 in-target: linux-update-symlinks: not found Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: dpkg: error processing package linux-image-4.4.0-143-generic (--configure): Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: subprocess installed post-installation script returned error exit status 127 Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: dpkg: dependency problems prevent configuration of linux-modules-extra-4.4.0-143-generic: Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: linux-modules-extra-4.4.0-143-generic depends on linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however: Mar 18 17:09:51 in-target: ^M Mar 18 17:09:51 in-target: Package linux-image-4.4.0-143-generic is not configured yet. Mar 18 17:09:51 in-target: ^M Mar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1820755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820754] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820754 Title: bcache null pointer exception , recursive fault Status in linux package in Ubuntu: Confirmed Bug description: 1) # cat /proc/version_signature Ubuntu 3.13.0-166.216-generic 3.13.11-ckt39 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-generic 3.13.0.167.178 ProcVersionSignature: Ubuntu 3.13.0-166.216-generic 3.13.11-ckt39 Uname: Linux 3.13.0-166-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 18 20:14 seq crw-rw 1 root audio 116, 33 Mar 18 20:14 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Mar 18 20:23:48 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=/dev/disk/by-id/virtio-boot-disk ds=nocloud-net;seedfrom=http://10.245.168.20:40373/ console=ttyS0 overlayroot=tmpfs ro systemd.mask=snapd.seeded.service systemd.mask=snapd.service iscsi_auto ip=:BOOTIF:dhcp BOOTIF=01-52-54-00-12-34-01 RelatedPackageVersions: linux-restricted-modules-3.13.0-166-generic N/A linux-backports-modules-3.13.0-166-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-disco dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-disco:cvnQEMU:ct1:cvrpc-i440fx-disco: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-disco dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820754] [NEW] bcache null pointer exception , recursive fault
Public bug reported: 1) # cat /proc/version_signature Ubuntu 3.13.0-166.216-generic 3.13.11-ckt39 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-generic 3.13.0.167.178 ProcVersionSignature: Ubuntu 3.13.0-166.216-generic 3.13.11-ckt39 Uname: Linux 3.13.0-166-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 18 20:14 seq crw-rw 1 root audio 116, 33 Mar 18 20:14 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Mar 18 20:23:48 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=/dev/disk/by-id/virtio-boot-disk ds=nocloud-net;seedfrom=http://10.245.168.20:40373/ console=ttyS0 overlayroot=tmpfs ro systemd.mask=snapd.seeded.service systemd.mask=snapd.service iscsi_auto ip=:BOOTIF:dhcp BOOTIF=01-52-54-00-12-34-01 RelatedPackageVersions: linux-restricted-modules-3.13.0-166-generic N/A linux-backports-modules-3.13.0-166-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-disco dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-disco:cvnQEMU:ct1:cvrpc-i440fx-disco: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-disco dmi.sys.vendor: QEMU ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug curtin trusty uec-images -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820754 Title: bcache null pointer exception , recursive fault Status in linux package in Ubuntu: New Bug description: 1) # cat /proc/version_signature Ubuntu 3.13.0-166.216-generic 3.13.11-ckt39 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-generic 3.13.0.167.178 ProcVersionSignature: Ubuntu 3.13.0-166.216-generic 3.13.11-ckt39 Uname: Linux 3.13.0-166-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 18 20:14 seq crw-rw 1 root audio 116, 33 Mar 18 20:14 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Mar 18 20:23:48 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=/dev/disk/by-id/virtio-boot-disk ds=nocloud-net;seedfrom=http://10.245.168.20:40373/ console=ttyS0 overlayroot=tmpfs ro systemd.mask=snapd.seeded.service systemd.mask=snapd.service iscsi_auto ip=:BOOTIF:dhcp BOOTIF=01-52-54-00-12-34-01 RelatedPackageVersions: linux-restricted-modules-3.13.0-166-generic N/A linux-backports-modules-3.13.0-166-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-disco dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-disco:cvnQEMU:ct1:cvrpc-i440fx-disco: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-disco dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819711] Re: linux-azure: 4.15.0-1041.45~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: 1819713 - phase: Holding before Promote to Proposed - phase-changed: Monday, 18. March 2019 16:05 UTC + phase: Ready for Promote to Proposed + phase-changed: Monday, 18. March 2019 20:33 UTC reason: - promote-to-proposed: Ongoing -- builds not complete + promote-to-proposed: Pending -- ready for review -- 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/1819711 Title: linux-azure: 4.15.0-1041.45~14.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 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: 1819713 phase: Ready for Promote to Proposed phase-changed: Monday, 18. March 2019 20:33 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819711/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820754] Re: bcache null pointer exception , recursive fault
Kernel oops when attempting to stop an online bcache device. ** Attachment added: "trusty-bcache-null.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820754/+attachment/5247406/+files/trusty-bcache-null.txt ** Tags added: curtin -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820754 Title: bcache null pointer exception , recursive fault Status in linux package in Ubuntu: New Bug description: 1) # cat /proc/version_signature Ubuntu 3.13.0-166.216-generic 3.13.11-ckt39 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-generic 3.13.0.167.178 ProcVersionSignature: Ubuntu 3.13.0-166.216-generic 3.13.11-ckt39 Uname: Linux 3.13.0-166-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 18 20:14 seq crw-rw 1 root audio 116, 33 Mar 18 20:14 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Mar 18 20:23:48 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=/dev/disk/by-id/virtio-boot-disk ds=nocloud-net;seedfrom=http://10.245.168.20:40373/ console=ttyS0 overlayroot=tmpfs ro systemd.mask=snapd.seeded.service systemd.mask=snapd.service iscsi_auto ip=:BOOTIF:dhcp BOOTIF=01-52-54-00-12-34-01 RelatedPackageVersions: linux-restricted-modules-3.13.0-166-generic N/A linux-backports-modules-3.13.0-166-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-disco dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-disco:cvnQEMU:ct1:cvrpc-i440fx-disco: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-disco dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802021] Re: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()
Thanks Mauricio! @mfo Will begin deploying this and let you guys know as soon as possible. -- 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/1802021 Title: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start() Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Fix Released Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-azure source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-azure source package in Cosmic: Fix Released Bug description: We had a customer seeing traces like the following: tack trace from kern.log: 2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. 2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 4.15.0-1023-azure #24~16.04.1-Ubuntu 2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 0x8000 2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound fsnotify_mark_destroy_workfn 2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace: 2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0 2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kernel: ? check_preempt_wakeup+0xfb/0x240 2018-10-10T04:43:08.547431+00:00 hbp2ann-2 kernel: ? sched_clock_local+0x17/0x90 2018-10-10T04:43:08.547440+00:00 hbp2ann-2 kernel: schedule+0x36/0x80 2018-10-10T04:43:08.547448+00:00 hbp2ann-2 kernel: schedule_timeout+0x1db/0x370 2018-10-10T04:43:08.547458+00:00 hbp2ann-2 kernel: ? __enqueue_entity+0x5c/0x60 2018-10-10T04:43:08.547467+00:00 hbp2ann-2 kernel: ? enqueue_entity+0x112/0x670 2018-10-10T04:43:08.547477+00:00 hbp2ann-2 kernel: wait_for_completion+0xb4/0x140 2018-10-10T04:43:08.547486+00:00 hbp2ann-2 kernel: ? wake_up_q+0x70/0x70 2018-10-10T04:43:08.547510+00:00 hbp2ann-2 kernel: __synchronize_srcu.part.13+0x85/0xb0 2018-10-10T04:43:08.547535+00:00 hbp2ann-2 kernel: ? trace_raw_output_rcu_utilization+0x50/0x50 2018-10-10T04:43:08.547560+00:00 hbp2ann-2 kernel: synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547594+00:00 hbp2ann-2 kernel: ? synchronize_srcu+0xd3/0xe0 2018-10-10T04:43:08.547604+00:00 hbp2ann-2 kernel: fsnotify_mark_destroy_workfn+0x7c/0xe0 2018-10-10T04:43:08.547612+00:00 hbp2ann-2 kernel: process_one_work+0x14d/0x410 2018-10-10T04:43:08.547620+00:00 hbp2ann-2 kernel: worker_thread+0x4b/0x460 2018-10-10T04:43:08.547628+00:00 hbp2ann-2 kernel: kthread+0x105/0x140 2018-10-10T04:43:08.547637+00:00 hbp2ann-2 kernel: ? process_one_work+0x410/0x410 2018-10-10T04:43:08.547645+00:00 hbp2ann-2 kernel: ? kthread_destroy_worker+0x50/0x50 2018-10-10T04:43:08.547654+00:00 hbp2ann-2 kernel: ? do_syscall_64+0x73/0x130 2018-10-10T04:43:08.547677+00:00 hbp2ann-2 kernel: ? SyS_exit_group+0x14/0x20 2018-10-10T04:43:08.547685+00:00 hbp2ann-2 kernel: ret_from_fork+0x35/0x40 Error Code: INFO: task kworker/u16:0:16678 blocked for more than 120 seconds. We are seeing more issue with fsnotify related callbacks. These are not a soft/hard lockup but seem to significantly degrade the responsiveness of systemd (and from there everything else). The following upstream commit may fix this issue, but it is in Paul's RCU tree and not in linux-next or upstream yet: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux- rcu.git/commit/?h=dev&id=1a05c0cd2fee234a10362cc8f66057557cbb291f srcu: Lock srcu_data structure in srcu_gp_start() The srcu_gp_start() function is called with the srcu_struct structure's ->lock held, but not with the srcu_data structure's ->lock. This is problematic because this function accesses and updates the srcu_data structure's ->srcu_cblist, which is protected by that lock. Failing to hold this lock can result in corruption of the SRCU callback lists, which in turn can result in arbitrarily bad results. This commit therefore makes srcu_gp_start() acquire the srcu_data structure's ->lock across the calls to rcu_segcblist_advance() and rcu_segcblist_accelerate(), thus preventing this corruption. Please investigate this issue and evaluate the proposed fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802021/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818645] Comment bridged from LTC Bugzilla
--- Comment From lagar...@br.ibm.com 2019-03-18 16:15 EDT--- Removing the genesis keyword. The fix for this issue is already contained in the Ubuntu 18.04.1 for Genesis kernel (request was made through SalesForce). But I think it is still a valid Ubuntu 18.04.1 LTS issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818645 Title: Ubuntu18.04.01: [Power9] power8 Compat guest(RHEL7.6) crashes during guest boot with > 256G of memory (kernel/kvm) Status in The Ubuntu-power-systems project: Invalid Status in linux package in Ubuntu: Invalid Bug description: == Comment: #0 - Satheesh Rajendran - 2019-02-28 04:38:22 == ---Problem Description--- Power8 Compat guest(RHEL 7.6) crashes during guest boot with > 256G of memory (kernel/kvm) Contact Information = sathe...@in.ibm.com ---uname output--- Host Kernel: 4.15.0-1016-ibm-gt ii qemu-system-ppc1:2.11+dfsg- 1ubuntu7.8-1ibm3 ppc64el QEMU full system emulation binaries (ppc) ii libvirt-bin4.0.0-1ubuntu8.6 ppc64el programs for the libvirt library Guest kernel: 3.10.0-957.5.1.el7.ppc64le (rhel7.6 zstream) Machine Type = power9 ppc64le ---Steps to Reproduce--- 1. Boot a power8 compat guest with memory >256G virsh define avocado-vt-vm1;virsh start --console avocado-vt-vm1 (guest xml sosreport attached) Guest crashes while booting 2019-02-28 10:36:44.752+: starting up libvirt version: 4.0.0, package: 1ubuntu8.6 (Christian Ehrhardt Fri, 09 Nov 2018 07:42:01 +0100), qemu version: 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.8-1ibm3), hostname: cs-host-f37-ac922-3.pok.ibm.com LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/qemu-system-ppc64 -name guest=avocado-vt-vm1,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-15-avocado-vt-vm1/master-key.aes -machine pseries-2.11,accel=kvm,usb=off,dump-guest-core=off -m 264192 -realtime mlock=off -smp 256,sockets=256,cores=1,threads=1 -uuid f4e14f88-bf1b-4cc3-b6d6-958d514d6c18 -display none -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-15-avocado-vt-vm1/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -device qemu-xhci,id=usb,bus=pci.0,addr=0x3 -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive file=/home/sath/avocado-fvt-wrapper/data/avocado-vt/images/rhel76-ppc64le.qcow2,format=qcow2,if=none,id=drive-scsi0-0-0-0 -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=28,id=hostnet0,vhost=on,vhostfd=30 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:fc:fd:fe,bus=pci.0,addr=0x1 -chardev pty,id=charserial0 -device spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-15-avocado-vt-vm1/org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on 2019-02-28 10:36:44.759+: 19598: info : libvirt version: 4.0.0, package: 1ubuntu8.6 (Christian Ehrhardt Fri, 09 Nov 2018 07:42:01 +0100) 2019-02-28 10:36:44.759+: 19598: info : hostname: cs-host-f37-ac922-3 2019-02-28 10:36:44.759+: 19598: info : virObjectUnref:350 : OBJECT_UNREF: obj=0x76d594111710 2019-02-28T10:36:44.781703Z qemu-system-ppc64: -chardev pty,id=charserial0: char device redirected to /dev/pts/3 (label charserial0) 2019-02-28T10:36:44.781945Z qemu-system-ppc64: warning: Number of SMP cpus requested (256) exceeds the recommended cpus supported by KVM (128) 2019-02-28T10:36:44.781953Z qemu-system-ppc64: warning: Number of hotpluggable cpus requested (256) exceeds the recommended cpus supported by KVM (128) 2019-02-28 10:37:18.060+: shutting down, reason=crashed 2019-02-28T10:37:18.071969Z qemu-system-ppc64: terminating on signal 15 from pid 14056 (/usr/sbin/libvirtd) *Additional Instructions for sathe...@in.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. == Comment: #3 - Satheesh Rajendran - 2019-02-28 04:51:45 == Possible Upstream fix: https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next&id=46dec40fb741f00f1864580130779aeeaf24fb3d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1818645/+subscriptions -- Mailing list: https://launchpad.net/~kernel-pa
[Kernel-packages] [Bug 1819617] Re: linux-azure: 4.18.0-1014.14~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 1819616 (linux-azure-edge) -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1819618 - phase: Holding before Promote to Proposed - phase-changed: Monday, 18. March 2019 16:30 UTC + phase: Ready for Promote to Proposed + phase-changed: Monday, 18. March 2019 20:06 UTC reason: - promote-to-proposed: Ongoing -- builds not complete + promote-to-proposed: Pending -- ready for review -- 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/1819617 Title: linux-azure: 4.18.0-1014.14~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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid 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: 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 1819616 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819618 phase: Ready for Promote to Proposed phase-changed: Monday, 18. March 2019 20:06 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819617/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761379] Re: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu
I sincerely apologise for the delay. I'll do my utmost to get you a response as soon as possible. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1761379 Title: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: In Progress Bug description: ---Problem Description--- File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods ---uname output--- inux-image-4.13.0-36-generic Machine Type = not relevant ---Debugger--- A debugger is not configured ---Steps to Reproduce--- File libperf-jvmti.so is missing in linux-tools-common deb provided for Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also checked if the file is available on launchpad (https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) at it's also absent there: gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm I do see the file in tools/perf/jvmti dir in the source .tar.gz, but apparently it's no being packaged in any .deb file? Thanks. Userspace tool common name: perf The userspace tool has the following bit modes: 64-bit Userspace tool obtained from project website: na To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1761379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818474] Re: Unable to install the proposed Trusty LTS kernel on Precise
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-lts-trusty (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1818474 Title: Unable to install the proposed Trusty LTS kernel on Precise Status in linux-lts-trusty package in Ubuntu: Confirmed Bug description: With ESM ppa added, -proposed enabled on a Precise testing node, I can't install the 3.13.0.166.156 kernel, it will complain about some dependency issues: $ sudo apt-get install linux-image-generic-lts-trusty The following packages have unmet dependencies: linux-image-generic-lts-trusty : Depends: linux-image-3.13.0-166-generic but it is not going to be installed or linux-unsigned-image-3.13.0-166-generic but it is not installable E: Unable to correct problems, you have held broken packages. And if you try: $ sudo apt-get install linux-image-3.13.0-166-generic It will show that the problem lies within linux-base The following packages have unmet dependencies: linux-image-3.13.0-166-generic : Depends: linux-base (>= 4.5ubuntu1~12.04.1) but it is not going to be installed E: Unable to correct problems, you have held broken packages. Version 4.5ubuntu1~12.04.1 for linux-base seems not exist in Precise. $ apt-cache show linux-base | grep Version Version: 3.4ubuntu3 Version: 3.4 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.13.0-117-generic 3.13.0-117.164~precise1 ProcVersionSignature: User Name 3.13.0-117.164~precise1-generic 3.13.11-ckt39 Uname: Linux 3.13.0-117-generic x86_64 AlsaDevices: total 0 crw-rw---T 1 root audio 116, 1 Mar 4 05:10 seq crw-rw---T 1 root audio 116, 33 Mar 4 05:10 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.0.1-0ubuntu17.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: [ 77.824525] random: nonblocking pool is initialized Date: Mon Mar 4 05:13:24 2019 IwConfig: ens6 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) MarkForUpload: True PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-117-generic root=UUID=71302c0e-ac2e-4c65-b368-143d7606b585 ro console=ttyS0,1152008n1 RelatedPackageVersions: linux-restricted-modules-3.13.0-117-generic N/A linux-backports-modules-3.13.0-117-generic N/A linux-firmware 1.79.18 RfKill: Error: [Errno 2] No such file or directory SourcePackage: linux-lts-trusty UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1818474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819694] Re: linux-aws: 4.15.0-1035.37 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package 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 backports: bug 1819693 (xenial/linux-aws-hwe) -- swm properties -- kernel-stable-master-bug: 1819716 - phase: Packaging - phase-changed: Monday, 18. March 2019 06:01 UTC + phase: Holding before Promote to Proposed + phase-changed: Monday, 18. March 2019 19:00 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete -- 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/1819694 Title: linux-aws: 4.15.0-1035.37 -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: 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid 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 1819693 (xenial/linux-aws-hwe) -- swm properties -- kernel-stable-master-bug: 1819716 phase: Holding before Promote to Proposed phase-changed: Monday, 18. March 2019 19:00 UTC reason: promote-to-proposed: Ongoing -- builds not complete To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819694/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820695] Re: 5.0.0 kernels (5.0.0-7 and 5.0.0-8) don't boot
The kernel 5.1.0-050100rc1-generic does boot for a short moment but freezes before the login screen appears. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820695 Title: 5.0.0 kernels (5.0.0-7 and 5.0.0-8) don't boot Status in linux package in Ubuntu: Confirmed Bug description: System runs fine with previous kernel 4.19.0-13-generic. On kernels 5.0.0-7 and 5.0.0-8, system freezes after GRUB screen on the background picture. Note: The attached logs are done with kernel 4.19.0-13-generic, since the kernels in question don't even boot and give no chance to catch a log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820695/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820366] Re: network install of xenial 16.04 fails with linux-generic package error
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820366 Title: network install of xenial 16.04 fails with linux-generic package error Status in linux package in Ubuntu: Confirmed Bug description: network installing xenial ubuntu is failing for myself and other people (as seen on the #ubuntu irc channel). I had this issue both with and without preseed. I am using the latest netboot kernel and initrd files from http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/installer- amd64/current/images/netboot/ ( I re-downloaded and checked the file digest). The latest version available from the above URL is 4.4.0-142 and the installer fails while installing 4.4.0-143. The following error messages seen during installation: Mar 16 01:20:12 in-target: Setting up linux-image-4.4.0-143-generic (4.4.0-143.169) ... Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: Mar 16 01:20:12 in-target: linux-update-symlinks: not found Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: error processing package linux-image-4.4.0-143-generic (--configure): Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: subprocess installed post-installation script returned error exit status 127 Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: dependency problems prevent configuration of linux-modules-extra-4.4.0-143-generic: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: linux-modules-extra-4.4.0-143-generic depends on linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-image-4.4.0-143-generic is not configured yet. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-image-unsigned-4.4.0-143-generic is not installed. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: error processing package linux-modules-extra-4.4.0-143-generic (--configure): Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dependency problems - leaving unconfigured Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Setting up intel-microcode (3.20180807a.0ubuntu0.16.04.1) ... Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: update-initramfs: deferring update (trigger activated) Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: intel-microcode: microcode will be updated at next boot Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Setting up amd64-microcode (3.20180524.1~ubuntu0.16.04.2) ...^M Mar 16 01:20:12 in-target: update-initramfs: deferring update (trigger activated) Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: amd64-microcode: microcode will be updated at next boot Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: dependency problems prevent configuration of linux-image-generic: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: linux-image-generic depends on linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-image-4.4.0-143-generic is not configured yet. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-image-unsigned-4.4.0-143-generic is not installed. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: linux-image-generic depends on linux-modules-extra-4.4.0-143-generic; however: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-modules-extra-4.4.0-143-generic is not configured yet. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: error processing package linux-image-generic (--configure): Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dependency problems - leaving unconfigured Mar 16 01:20:12 in-target: ^M After having these issue with a preseed file, I started a PXE install without any preseed ( therefore answering the standard installer questions manually) but I still had the same error. I was told in the #ubuntu irc channel to set : d-i base-installer/kernel/image string linux-image-4.4.0-142-generic in my preseed file. This worked and the installer completed correctly without any failures. Previously my preseed file container: d-i base-installer/kernel/image string linux-generic but as I said above, even without a preseed file the error occured. One thought - shouldn't a 4.4.0-143 netboot kernel / initrd be on http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/installer- amd64/current/images/netboot ? Maybe the issu
[Kernel-packages] [Bug 1820366] [NEW] network install of xenial 16.04 fails with linux-generic package error
You have been subscribed to a public bug: network installing xenial ubuntu is failing for myself and other people (as seen on the #ubuntu irc channel). I had this issue both with and without preseed. I am using the latest netboot kernel and initrd files from http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/installer- amd64/current/images/netboot/ ( I re-downloaded and checked the file digest). The latest version available from the above URL is 4.4.0-142 and the installer fails while installing 4.4.0-143. The following error messages seen during installation: Mar 16 01:20:12 in-target: Setting up linux-image-4.4.0-143-generic (4.4.0-143.169) ... Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: /var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: Mar 16 01:20:12 in-target: linux-update-symlinks: not found Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: error processing package linux-image-4.4.0-143-generic (--configure): Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: subprocess installed post-installation script returned error exit status 127 Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: dependency problems prevent configuration of linux-modules-extra-4.4.0-143-generic: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: linux-modules-extra-4.4.0-143-generic depends on linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-image-4.4.0-143-generic is not configured yet. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-image-unsigned-4.4.0-143-generic is not installed. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: error processing package linux-modules-extra-4.4.0-143-generic (--configure): Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dependency problems - leaving unconfigured Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Setting up intel-microcode (3.20180807a.0ubuntu0.16.04.1) ... Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: update-initramfs: deferring update (trigger activated) Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: intel-microcode: microcode will be updated at next boot Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Setting up amd64-microcode (3.20180524.1~ubuntu0.16.04.2) ...^M Mar 16 01:20:12 in-target: update-initramfs: deferring update (trigger activated) Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: amd64-microcode: microcode will be updated at next boot Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: dependency problems prevent configuration of linux-image-generic: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: linux-image-generic depends on linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-image-4.4.0-143-generic is not configured yet. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-image-unsigned-4.4.0-143-generic is not installed. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: linux-image-generic depends on linux-modules-extra-4.4.0-143-generic; however: Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: Package linux-modules-extra-4.4.0-143-generic is not configured yet. Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dpkg: error processing package linux-image-generic (--configure): Mar 16 01:20:12 in-target: ^M Mar 16 01:20:12 in-target: dependency problems - leaving unconfigured Mar 16 01:20:12 in-target: ^M After having these issue with a preseed file, I started a PXE install without any preseed ( therefore answering the standard installer questions manually) but I still had the same error. I was told in the #ubuntu irc channel to set : d-i base-installer/kernel/image string linux-image-4.4.0-142-generic in my preseed file. This worked and the installer completed correctly without any failures. Previously my preseed file container: d-i base-installer/kernel/image string linux-generic but as I said above, even without a preseed file the error occured. One thought - shouldn't a 4.4.0-143 netboot kernel / initrd be on http://archive.ubuntu.com/ubuntu/dists/xenial-updates/main/installer- amd64/current/images/netboot ? Maybe the issue would go away if those files were available for us to place on our PXE servers. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: bot-comment -- network install of xenial 16.04 fails with linux-generic package error https://bugs.launchpad.net/bugs/1820366 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launc
[Kernel-packages] [Bug 1766851] Re: Missing `linux-update-symlinks` causes Linux package installation to fail
I am still having this issue with a fresh install of 16.04. Can anyone give an update to this bug -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1766851 Title: Missing `linux-update-symlinks` causes Linux package installation to fail Status in linux-base package in Ubuntu: Confirmed Bug description: On Ubuntu 16.04.3 LTS, the installation of Linux 4.17-rc2 from [1] fails because `linux-update-symlinks` is not available. [1]: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc2/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1766851/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819620] Re: linux-gcp: 4.18.0-1008.9 -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 1819619 (bionic/linux-gcp-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819624 - phase: Ready for Promote to Proposed - phase-changed: Friday, 15. March 2019 14:01 UTC + phase: Promote to Proposed + phase-changed: Monday, 18. March 2019 18:35 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- packages copied but not yet published to -proposed -- 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/1819620 Title: linux-gcp: 4.18.0-1008.9 -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 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 1819619 (bionic/linux-gcp-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819624 phase: Promote to Proposed phase-changed: Monday, 18. March 2019 18:35 UTC reason: promote-to-proposed: Ongoing -- packages copied but not yet published to -proposed To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819618] Re: linux-azure: 4.18.0-1014.14 -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-azure in Ubuntu. https://bugs.launchpad.net/bugs/1819618 Title: linux-azure: 4.18.0-1014.14 -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 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: 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 1819617 (bionic/linux-azure) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819624 phase: Promote to Proposed phase-changed: Monday, 18. March 2019 18:33 UTC reason: promote-to-proposed: Ongoing -- packages copies requested To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1761379] Comment bridged from LTC Bugzilla
--- Comment From grom...@br.ibm.com 2019-03-18 14:24 EDT--- Frankly, it's quite upsetting not hearing from Canonical after so much time. I do understand that kernel team might frown upon adding a Java stuff as a dep for building the kernel packages and that any other similar conundrum might exist. But it seems Canonical is not paying much attention at all to that issue which, besides PPC64, also applies to other architectures. I could even try to help working that upstream on perf side but without even knowing what's the Canonical plan for that bug it's moot because who knows exactly what's the hindrance here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1761379 Title: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: In Progress Bug description: ---Problem Description--- File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods ---uname output--- inux-image-4.13.0-36-generic Machine Type = not relevant ---Debugger--- A debugger is not configured ---Steps to Reproduce--- File libperf-jvmti.so is missing in linux-tools-common deb provided for Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also checked if the file is available on launchpad (https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) at it's also absent there: gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm I do see the file in tools/perf/jvmti dir in the source .tar.gz, but apparently it's no being packaged in any .deb file? Thanks. Userspace tool common name: perf The userspace tool has the following bit modes: 64-bit Userspace tool obtained from project website: na To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1761379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819618] Re: linux-azure: 4.18.0-1014.14 -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 1819617 (bionic/linux-azure) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819624 - phase: Ready for Promote to Proposed - phase-changed: Friday, 15. March 2019 16:31 UTC + phase: Promote to Proposed + phase-changed: Monday, 18. March 2019 18:33 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- packages copies requested -- 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/1819618 Title: linux-azure: 4.18.0-1014.14 -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 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: 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 1819617 (bionic/linux-azure) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819624 phase: Promote to Proposed phase-changed: Monday, 18. March 2019 18:33 UTC reason: promote-to-proposed: Ongoing -- packages copies requested To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820695] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820695 Title: 5.0.0 kernels (5.0.0-7 and 5.0.0-8) don't boot Status in linux package in Ubuntu: Confirmed Bug description: System runs fine with previous kernel 4.19.0-13-generic. On kernels 5.0.0-7 and 5.0.0-8, system freezes after GRUB screen on the background picture. Note: The attached logs are done with kernel 4.19.0-13-generic, since the kernels in question don't even boot and give no chance to catch a log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820695/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817786] Re: tcm_loop.ko: move from modules-extra into main modules package
** No longer affects: linux-gcp (Ubuntu Disco) -- 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/1817786 Title: tcm_loop.ko: move from modules-extra into main modules package Status in linux package in Ubuntu: In Progress Status in linux-gcp package in Ubuntu: In Progress Status in linux-gcp source package in Xenial: Fix Committed Status in linux source package in Bionic: In Progress Status in linux-gcp source package in Bionic: Fix Committed Status in linux source package in Cosmic: In Progress Status in linux-gcp source package in Cosmic: Fix Committed Status in linux source package in Disco: In Progress Bug description: Please move the tcm_loop.ko module from the linux-modules-extra-* to main linux-modules-* package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817786/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820695] [NEW] 5.0.0 kernels (5.0.0-7 and 5.0.0-8) don't boot
Public bug reported: System runs fine with previous kernel 4.19.0-13-generic. On kernels 5.0.0-7 and 5.0.0-8, system freezes after GRUB screen on the background picture. Note: The attached logs are done with kernel 4.19.0-13-generic, since the kernels in question don't even boot and give no chance to catch a log. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "version.log" https://bugs.launchpad.net/bugs/1820695/+attachment/5247352/+files/version.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820695 Title: 5.0.0 kernels (5.0.0-7 and 5.0.0-8) don't boot Status in linux package in Ubuntu: New Bug description: System runs fine with previous kernel 4.19.0-13-generic. On kernels 5.0.0-7 and 5.0.0-8, system freezes after GRUB screen on the background picture. Note: The attached logs are done with kernel 4.19.0-13-generic, since the kernels in question don't even boot and give no chance to catch a log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820695/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820695] Re: 5.0.0 kernels (5.0.0-7 and 5.0.0-8) don't boot
** Attachment added: "uname-a.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820695/+attachment/5247353/+files/uname-a.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/1820695 Title: 5.0.0 kernels (5.0.0-7 and 5.0.0-8) don't boot Status in linux package in Ubuntu: New Bug description: System runs fine with previous kernel 4.19.0-13-generic. On kernels 5.0.0-7 and 5.0.0-8, system freezes after GRUB screen on the background picture. Note: The attached logs are done with kernel 4.19.0-13-generic, since the kernels in question don't even boot and give no chance to catch a log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820695/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820695] Re: 5.0.0 kernels (5.0.0-7 and 5.0.0-8) don't boot
** Attachment added: "lspci-vvnn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820695/+attachment/5247354/+files/lspci-vvnn.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/1820695 Title: 5.0.0 kernels (5.0.0-7 and 5.0.0-8) don't boot Status in linux package in Ubuntu: New Bug description: System runs fine with previous kernel 4.19.0-13-generic. On kernels 5.0.0-7 and 5.0.0-8, system freezes after GRUB screen on the background picture. Note: The attached logs are done with kernel 4.19.0-13-generic, since the kernels in question don't even boot and give no chance to catch a log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820695/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820695] Re: 5.0.0 kernels (5.0.0-7 and 5.0.0-8) don't boot
** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820695/+attachment/5247355/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820695 Title: 5.0.0 kernels (5.0.0-7 and 5.0.0-8) don't boot Status in linux package in Ubuntu: New Bug description: System runs fine with previous kernel 4.19.0-13-generic. On kernels 5.0.0-7 and 5.0.0-8, system freezes after GRUB screen on the background picture. Note: The attached logs are done with kernel 4.19.0-13-generic, since the kernels in question don't even boot and give no chance to catch a log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820695/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)
I can confirm kernel 4.18.10 there is no flickering. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813701 Title: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12) Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: The screen always flickers at a frequency of 75 GHz on the AMD RX 580 gpu. At 60 and 50 GHz, if you switch to any other than 75, the flickering will disappear until the display turns off. After switching on, flicker returns. At the core of 4.18.0-10, just like on the AMD Radeon HD7970 gpu, the problem is not visible. More in the video https://www.youtube.com/watch?v=d_LXHqWKTbk ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 13:13:19 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1043:0519] InstallationDate: Installed on 2019-01-22 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: MSI MS-7693 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=ad22bc6d-c4e8-4393-a30b-6c247159b9dd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G43 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd01/08/2016:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~c version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901280730.d1d2bb~oibaf~c version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819618] Re: linux-azure: 4.18.0-1014.14 -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-azure in Ubuntu. https://bugs.launchpad.net/bugs/1819618 Title: linux-azure: 4.18.0-1014.14 -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: 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 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: 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 1819617 (bionic/linux-azure) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819624 phase: Ready for Promote to Proposed phase-changed: Friday, 15. March 2019 16:31 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819620] Re: linux-gcp: 4.18.0-1008.9 -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/1819620 Title: linux-gcp: 4.18.0-1008.9 -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 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 1819619 (bionic/linux-gcp-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819624 phase: Ready for Promote to Proposed phase-changed: Friday, 15. March 2019 14:01 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819362] Re: HUAWEI E3531 HSPA+ USB Stick "please report the device ID to the Linux USB developers"
Correction: The mode that Huawei calls "HiLink" is No.1, not No.2. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1819362 Title: HUAWEI E3531 HSPA+ USB Stick "please report the device ID to the Linux USB developers" Status in linux package in Ubuntu: Triaged Status in usb-modeswitch package in Ubuntu: New Bug description: I have a HUAWEI E3531 HSPA+ USB Stick When I plug it in, journalctl shows me Mär 10 19:21:20 pshp usb_modeswitch[3556]: usb_modeswitch: switched to 12d1:14dc on 1/9 Mär 10 19:21:20 pshp kernel: scsi 1:0:0:0: Direct-Access HUAWEI TF CARD Storage 2.31 PQ: 0 ANSI: 2 Mär 10 19:21:20 pshp kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0 Mär 10 19:21:20 pshp kernel: sd 1:0:0:0: [sda] Attached SCSI removable disk Mär 10 19:21:21 pshp usb_modeswitch_dispatcher[3556]: Unable to open bind list file: No such file or directory Mär 10 19:21:21 pshp usb_modeswitch[3556]: usb_modeswitch: add device ID 12d1:14dc to driver option Mär 10 19:21:21 pshp usb_modeswitch[3556]: usb_modeswitch: please report the device ID to the Linux USB developers! Mär 10 19:21:22 pshp ModemManager[860]: Couldn't check support for device at '/sys/devices/pci:00/:00:14.0/usb1/1-1': not supported by any plugin And the modem does not work (no ttyUSBX appears) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-15-generic 4.18.0-15.16~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 10 19:17:23 2019 EcryptfsInUse: Yes SourcePackage: linux-signed-hwe UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ps 1825 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=f51203fe-7748-4c6c-b60e-becfac3f8f93 MachineType: HP HP EliteBook 820 G4 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=ef37c096-b516-41e7-89ce-be7432f1677e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic wayland-session Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago) UserGroups: adm cdrom dip gsmsms lpadmin plugdev sambashare scanner sudo _MarkForUpload: True dmi.bios.date: 10/17/2017 dmi.bios.vendor: HP dmi.bios.version: P78 Ver. 01.08 dmi.board.name: 8292 dmi.board.vendor: HP dmi.board.version: KBC Version 45.3C dmi.chassis.asset.tag: 5CG7453N9P dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP78Ver.01.08:bd10/17/2017:svnHP:pnHPEliteBook820G4:pvr:rvnHP:rn8292:rvrKBCVersion45.3C:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 820 G4 dmi.product.sku: X3T22AV dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ps 1825 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=f51203fe-7748-4c6c-b60e-becfac3f8f93 MachineType: HP HP EliteBook 820 G4 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=ef37c096-b516-41e7-89ce-be7432f1677e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic wayland-session Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-01 (252 days ago) UserGroups: adm cdrom dip gsmsms lpadmin plugdev sambashare scanner sudo _MarkForUpload: True dmi.bios.date: 10/17/2017 dmi.bios.vendor: HP dmi.bios.version: P78 Ver. 01.08 dmi.board.name: 8292 dmi.board.vendor: HP dmi.board.version: KBC Version 45.3C dmi.chassis.asset.tag: 5CG7453N9P dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP78Ver.01.08:bd10/17/2017:svnHP:pnHPEliteBook820G4:pvr:rvnHP:rn8292:rvrKBCVersion45.3C:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 820 G4
[Kernel-packages] [Bug 1820687] 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 1820687 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: xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820687 Title: Sound issue, or rather, lack of sound Status in linux package in Ubuntu: Incomplete Bug description: Linux Mint 18.3 update Kernel 4.4.0-143-generic up-heaved my Alsa mixer/pulse-audio or something to disable sound, made the mixer and configurations useless and grayed out/inoperable. I have gone through this some time ago and forgotten how to remedy but the next thing, besides what I have tried futilely, will be to rollback the new kernel to its predecessor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820687/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820687] [NEW] Sound issue, or rather, lack of sound
Public bug reported: Linux Mint 18.3 update Kernel 4.4.0-143-generic up-heaved my Alsa mixer /pulse-audio or something to disable sound, made the mixer and configurations useless and grayed out/inoperable. I have gone through this some time ago and forgotten how to remedy but the next thing, besides what I have tried futilely, will be to rollback the new kernel to its predecessor. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820687 Title: Sound issue, or rather, lack of sound Status in linux package in Ubuntu: Incomplete Bug description: Linux Mint 18.3 update Kernel 4.4.0-143-generic up-heaved my Alsa mixer/pulse-audio or something to disable sound, made the mixer and configurations useless and grayed out/inoperable. I have gone through this some time ago and forgotten how to remedy but the next thing, besides what I have tried futilely, will be to rollback the new kernel to its predecessor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820687/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819620] Re: linux-gcp: 4.18.0-1008.9 -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-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1819620 Title: linux-gcp: 4.18.0-1008.9 -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: 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-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 1819619 (bionic/linux-gcp-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819624 phase: Ready for Promote to Proposed phase-changed: Friday, 15. March 2019 14:01 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10
I confirmed that 3rpako's settings work for my env too. My env is Dell XPS13 (9343) + Xubuntu 18.10. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798961 Title: Random unrecoverable freezes on Ubuntu 18.10 Status in Linux: New Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Status in linux source package in Disco: Triaged Bug description: First thing I notice is that the mouse cursor freezes as I'm using it, then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then I try the "REISUB" command, but it doesn't do anything either. Only a hard reset works, pressing down the power button for a few seconds. How to reproduce? I couldn't figure out a consistent method. It is still random to me. Version: Ubuntu 4.18.0-10.11-generic 4.18.12 System information attached. Also happens under Arch Linux and Fedora. I've talked to another user on IRC who seems to be having the same freezes. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsilva 1213 F pulseaudio /dev/snd/controlC0: dsilva 1213 F pulseaudio CurrentDesktop: XFCE Date: Sat Oct 20 09:54:50 2018 InstallationDate: Installed on 2018-10-20 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Dell Inc. Inspiron 5458 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 09WGNT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817321] Re: installer does not support iSCSI iBFT
bionic-proposed verification done; iscsi_ibft.ko is present in udeb and loads correctly. --- $ uname -rv 4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:44:52 UTC 2019 $ apt-get download scsi-modules-4.15.0-47-generic-di $ dpkg-deb -c scsi-modules-4.15.0-47-generic-di_4.15.0-47.50_amd64.udeb | grep ibft -rw-r--r-- root/root 17086 2019-03-13 04:37 ./lib/modules/4.15.0-47-generic/kernel/drivers/firmware/iscsi_ibft.ko $ dpkg-deb -x scsi-modules-4.15.0-47-generic-di_4.15.0-47.50_amd64.udeb udeb $ sudo insmod udeb/lib/modules/4.15.0-47-generic/kernel/drivers/scsi/iscsi_boot_sysfs.ko $ sudo insmod udeb/lib/modules/4.15.0-47-generic/kernel/drivers/firmware/iscsi_ibft.ko $ dmesg | grep -i ibft [ 297.999505] No iBFT detected. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1817321 Title: installer does not support iSCSI iBFT Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Released Bug description: [Impact] * It's not possible to access iBFT (iSCSI Boot Firmware Table) information (settings for network interface, initiator, and target) in the installer because the 'iscsi_ibft' module is not present in udeb packages. * Even if it was, the installer does not handle iBFT information at all, thus any settings are ignored, and iSCSI-related configuration has to be done manually or with workarounds. * This impacts user-experience and automatic installation on systems and deployments which actually do provide the iBFT feature and information, but cannot use it practically. * With proper iBFT support in the installer (kernel module in udeb package and automatic iSCSI-related configuration) users will be able to rely on iBFT to install/deploy Ubuntu on their servers and datacenters. * These fixes add the 'iscsi_ibft' kernel module in the scsi-modules udeb, and configure network/iSCSI according to iBFT information in disk-detect. This is done in disk-detect so that the iSCSI LUNs are detected as disks (useful in case of no other disks in the system so the installer doesn't complain nor wait too long) and that any partman-related preseed options are not required and may be still available for the user. [Test Case] * linux package / kernel module in udeb: $ dpkg-deb -c scsi-modules_*.udeb | grep iscsi_ibft.ko Check the module loads in the installer environment. See comment with example for disco. * d-i/hw-detect package: (to be done) [Regression Potential] * linux package: low, the kernel module is not loaded by default, and only checks whether iBFT information is present in firmware, then exposes that in sysfs in read-only mode. * d-i/hw-detect: (to be done) [Other Info] * This has been verified both by the developer with a simple iSCSI iBFT environment (2 VMs: iSCSI target & initiator with UEFI+iPXE) and by an user with system/firmware that supports iBFT for iSCSI. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815831] Re: [ALSA] [PATCH] System76 darp5 and oryp5 fixups
Kernel in cosmic proposed also works and fixes this issue. Tags updated. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1815831 Title: [ALSA] [PATCH] System76 darp5 and oryp5 fixups Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: SRU Justification Impact: The System76 darp5 and oryp5 platforms need audio driverquirks to fix up the pin configuration. Fix: One backport from upstream, and one cherry pick from the upstream sound tree. Test Case: Backports have been tested on the affected hardware. Regression Potential: These are quirks for specific PCI device ids and thus are not expected to introduce regressions for any other hardware. --- Two fixups are needed to support the headset microphone on the System76 darp5 and oryp5. The darp5 patch is attached here, the oryp5 patch will be attached on the next comment. On the System76 Darter Pro (darp5), there is a headset microphone input attached to 0x1a that does not have a jack detect. In order to get it working, the pin configuration needs to be set correctly, and the ALC269_FIXUP_HEADSET_MODE_NO_HP_MIC fixup needs to be applied. This is similar to the MIC_NO_PRESENCE fixups for some Dell laptops, except we have a separate microphone jack that is already configured correctly. On the System76 Oryx Pro (oryp5), there is a headset microphone input attached to 0x19 that does not have a jack detect. In order to get it working, the pin configuration needs to be set correctly, and the ALC269_FIXUP_HEADSET_MODE_NO_HP_MIC fixup needs to be applied. This is similar to the MIC_NO_PRESENCE fixups for some Dell laptops, except we have a separate microphone jack that is already configured correctly. Since the ALC1220 does not have a fixup similar to ALC269_FIXUP_HEADSET_MODE_NO_HP_MIC, I have exposed the fixup from the ALC269 in a way that it can be accessed from the alc1220_fixup_system76_oryp5 function. In addition, the alc1220_fixup_clevo_p950 needs to be applied to gain speaker output. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815831/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817321] Re: installer does not support iSCSI iBFT
cosmic-proposed verification done; iscsi_ibft.ko is present in udeb and loads correctly. --- $ uname -rv 4.18.0-17-generic #18-Ubuntu SMP Wed Mar 13 14:34:40 UTC 2019 $ apt-get download scsi-modules-4.18.0-17-generic-di $ dpkg-deb -c scsi-modules-4.18.0-17-generic-di_4.18.0-17.18_amd64.udeb | grep ibft -rw-r--r-- root/root 17257 2019-03-13 11:52 ./lib/modules/4.18.0-17-generic/kernel/drivers/firmware/iscsi_ibft.ko $ dpkg-deb -x scsi-modules-4.18.0-17-generic-di_4.18.0-17.18_amd64.udeb udeb $ sudo insmod udeb/lib/modules/4.18.0-17-generic/kernel/drivers/scsi/iscsi_boot_sysfs.ko $ sudo insmod udeb/lib/modules/4.18.0-17-generic/kernel/drivers/firmware/iscsi_ibft.ko $ dmesg | grep -i ibft [ 117.143116] No iBFT detected. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1817321 Title: installer does not support iSCSI iBFT Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Released Bug description: [Impact] * It's not possible to access iBFT (iSCSI Boot Firmware Table) information (settings for network interface, initiator, and target) in the installer because the 'iscsi_ibft' module is not present in udeb packages. * Even if it was, the installer does not handle iBFT information at all, thus any settings are ignored, and iSCSI-related configuration has to be done manually or with workarounds. * This impacts user-experience and automatic installation on systems and deployments which actually do provide the iBFT feature and information, but cannot use it practically. * With proper iBFT support in the installer (kernel module in udeb package and automatic iSCSI-related configuration) users will be able to rely on iBFT to install/deploy Ubuntu on their servers and datacenters. * These fixes add the 'iscsi_ibft' kernel module in the scsi-modules udeb, and configure network/iSCSI according to iBFT information in disk-detect. This is done in disk-detect so that the iSCSI LUNs are detected as disks (useful in case of no other disks in the system so the installer doesn't complain nor wait too long) and that any partman-related preseed options are not required and may be still available for the user. [Test Case] * linux package / kernel module in udeb: $ dpkg-deb -c scsi-modules_*.udeb | grep iscsi_ibft.ko Check the module loads in the installer environment. See comment with example for disco. * d-i/hw-detect package: (to be done) [Regression Potential] * linux package: low, the kernel module is not loaded by default, and only checks whether iBFT information is present in firmware, then exposes that in sysfs in read-only mode. * d-i/hw-detect: (to be done) [Other Info] * This has been verified both by the developer with a simple iSCSI iBFT environment (2 VMs: iSCSI target & initiator with UEFI+iPXE) and by an user with system/firmware that supports iBFT for iSCSI. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819703] Re: linux-oracle: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** 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: 1819704 - phase: Holding before Packaging - phase-changed: Tuesday, 12. March 2019 18:10 UTC + phase: Ready for Packaging + phase-changed: Monday, 18. March 2019 16:33 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1819703 Title: linux-oracle: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed 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-oracle package in Ubuntu: Invalid Status in linux-oracle 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 -- swm properties -- kernel-stable-master-bug: 1819704 phase: Ready for Packaging phase-changed: Monday, 18. March 2019 16:33 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819703/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819617] Re: linux-azure: 4.18.0-1014.14~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Khaled El Mously (kmously) => (unassigned) ** Changed in: kernel-sru-workflow/prepare-package-signed 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 1819616 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1819618 - phase: Packaging - phase-changed: Monday, 18. March 2019 03:01 UTC + phase: Holding before Promote to Proposed + phase-changed: Monday, 18. March 2019 16:30 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete -- 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/1819617 Title: linux-azure: 4.18.0-1014.14~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: 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid 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: 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 1819616 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1819618 phase: Holding before Promote to Proposed phase-changed: Monday, 18. March 2019 16:30 UTC reason: promote-to-proposed: Ongoing -- builds not complete To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819617/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819704] Re: linux-oracle: 4.15.0-1010.12 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package 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 backports: bug 1819703 (xenial/linux-oracle) -- swm properties -- kernel-stable-master-bug: 1819716 phase: Packaging phase-changed: Monday, 18. March 2019 06:34 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1819704 Title: linux-oracle: 4.15.0-1010.12 -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: In Progress 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-oracle package in Ubuntu: Invalid Status in linux-oracle 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 1819703 (xenial/linux-oracle) -- swm properties -- kernel-stable-master-bug: 1819716 phase: Packaging phase-changed: Monday, 18. March 2019 06:34 UTC reason: prepare-package-signed: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820557] Re: Chelsio T5/T6 kernel modules missing in 4.18.0-1013
While the linux-azure package has the necessary modules for running a virtual machine under Hyper-V, especially in Azure, it does not include every possible driver for PCIe. The other drivers should be available by installing the "linux-modules-extra-azure" metapackage. I have not checked on this particular driver. Was this an item that was in 4.15 but not 4.18? -- 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/1820557 Title: Chelsio T5/T6 kernel modules missing in 4.18.0-1013 Status in linux-azure package in Ubuntu: New Bug description: Installed the linux-azure package, and the VF Chelsio T520-CR device became unclaimed. When into the path '/lib/modules/4.18.0-1013-azure/kernel/drivers/net/ethernet/' and was a little surprised to not see a Chelsio folder. Has Chelsio been removed from Ubuntu support in the linux-azure package? Test platform: Hyper-V 2019 Server Role with Ubuntu Server 18.04.2(HVE) guest. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1820557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819504] Re: tcmu user space crash results in kernel module hang.
Note: The Disco 5.0 kernel already carries the required patches, via mainline. ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Cosmic) Status: New => In Progress ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => High ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux-gcp (Ubuntu Cosmic) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu Cosmic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux-gcp (Ubuntu Cosmic) Importance: Undecided => High -- 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/1819504 Title: tcmu user space crash results in kernel module hang. Status in linux package in Ubuntu: Incomplete Status in linux-gcp package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux-gcp source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux-gcp source package in Cosmic: In Progress Bug description: With the 4.15.0 kernel version used in bionic GCP/GKE, if the tcmu user space code crashes while handling a netlink message from the kernel, the kernel module will be stuck waiting for the response. This situation can only be resolved with a server reboot. === SRU Justification === [Impact] With this particular user-space crash in the current Ubuntu image it results in a hang hobbles the entire physical server. [Fix] The request is for Canonical to backport the patch https://patchwork.kernel.org/patch/10319623/ to the bionic 4.15.0 kernel [** CORRECTION: See comment #2 ***] There were a number of mainline upstream commits to apply as part of the backport [Test] unavailable [Regression Potential] Low. it's all mainline commits, and affects only that driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817786] Re: tcm_loop.ko: move from modules-extra into main modules-gcp package
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Xenial) ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Cosmic) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Summary changed: - tcm_loop.ko: move from modules-extra into main modules-gcp package + tcm_loop.ko: move from modules-extra into main modules package ** Description changed: - Please move the tcm_loop.ko module from the linux-modules-extra-*-gcp to - main linux-modules-*-gcp package. + Please move the tcm_loop.ko module from the linux-modules-extra-* to + main linux-modules-* package. ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High -- 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/1817786 Title: tcm_loop.ko: move from modules-extra into main modules package Status in linux package in Ubuntu: In Progress Status in linux-gcp package in Ubuntu: In Progress Status in linux-gcp source package in Xenial: Fix Committed Status in linux source package in Bionic: In Progress Status in linux-gcp source package in Bionic: Fix Committed Status in linux source package in Cosmic: In Progress Status in linux-gcp source package in Cosmic: Fix Committed Status in linux source package in Disco: In Progress Status in linux-gcp source package in Disco: In Progress Bug description: Please move the tcm_loop.ko module from the linux-modules-extra-* to main linux-modules-* package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817786/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819711] Re: linux-azure: 4.15.0-1041.45~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed 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 -- kernel-stable-master-bug: 1819713 - phase: Packaging - phase-changed: Monday, 18. March 2019 02:00 UTC + phase: Holding before Promote to Proposed + phase-changed: Monday, 18. March 2019 16:05 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete -- 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/1819711 Title: linux-azure: 4.15.0-1041.45~14.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: 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: 1819713 phase: Holding before Promote to Proposed phase-changed: Monday, 18. March 2019 16:05 UTC reason: promote-to-proposed: Ongoing -- builds not complete To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819711/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818253] Re: 18.10 when lid closed and opened again no keyboard
The previously posted log was from this nightmare: This is a major bug in this regard, my system was totally unusable for an hour. Had a phone call had to attend to and some items related top that, system turned off screen when I finally got back to my system, could not use the keyboard, touch screen was unresponsive, on screen keyboard would not activate, on board touch pad was unresponsive, Bluetooth mouse moved but clicks were unresponsive, even power button was unresponsive, again after an hour of messing with things was lucky enough to get an occasional touch screen keyboard and was finally able to a terminal and after 15 trying to get a touch screen keyboard was able to reboot. This is a very serious regression, this worked absolutely great in 18.04. Sorry it appear I haven't provided a log before this, but I did, didn't realize that for some reason the log and my detailed explanation of events actually wasn't posted. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818253 Title: 18.10 when lid closed and opened again no keyboard Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: Using Dell Inspiron 7000 w/Intel corei7. With 18.04 power settings had options for what to do when lid was closed. Now available with Gnome-tweak in 18.10. However does not work correctly. Did Google search happening to others as well especially with detach keyboards which is not my case. With 18.10 and tweak setting to suspend when lid closed, the system does suspend, however when lid is closed it appears that the on board keyboard gets totally dropped when lid is opened back up. Have to use touch screen to switch user, then touch screen again at login to get a screen keyboard, sometimes I get the on board keyboard back, usually have to reboot to get on on board keyboard back. If I power off or restart keyboard works fine. Definite regression this has worked for several older versions of Ubuntu, at least on this system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818253/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
