[Kernel-packages] [Bug 1836857] Re: [18.04 FEAT] Enhanced hardware support
** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836857 Title: [18.04 FEAT] Enhanced hardware support Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: SRU Justification: == [Impact] * Enhanced hardware support for upcoming machine and make sure it can report new CPU capabilities [Fix] * a8fd61688dfad6fdce95fa64cacd8a66595697b8 a8fd616 "s390: report new CPU capabilities" * 142c52d7bce45d335f48d53fdbf428bb15cf3924 142c52d "s390: add alignment hints to vector load and store" [Test Case] * check /proc/cpuinfo in bionic running on upcoming machine - currently only IBM can do that [Regression Potential] * The regression potential can be considered as very low since these changes are limited to arch/s390 * and mainly adds code for the capability to report new features in cpuinfo - in case of running on new hardware [Other Info] * a8fd616 got upstream accepted with 5.2; 142c52d with 5.1 - hence both are already in eoan __ Feature request to apply this to Ubuntu 18.04 in support of new machine. Summary: kernel: report new CPU capabilities Description: Add hardware capability bits and features tags to /proc/cpuinfo for 4 new CPU features: the "Vector-Enhancements Facility 2", the "Vector-Packed-Decimal-Enhancement Facility", the "Enhanced-Sort Facility" and the "Deflate-Conversion Facility" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1836857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835001] Re: System does not auto detect disconnection of external monitor
** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1835001 Title: System does not auto detect disconnection of external monitor Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: In Progress Status in linux-oem source package in Bionic: In Progress Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Cosmic: Won't Fix Status in linux-oem source package in Cosmic: Won't Fix Status in linux-oem-osp1 source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: Won't Fix Status in linux-oem-osp1 source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem source package in Eoan: Won't Fix Status in linux-oem-osp1 source package in Eoan: Won't Fix Bug description: [Impact] System does not auto detect disconnection of external monitor Steps to reproduce: 1. install dell-bto-bionic-beaver-lancel-X84-20190507-42.iso and boot into OS 2. open "system settings > display settings" 3. connect laptop to an external HDMI monitor via HDMI port & cable 4. unplug the HDMI cable 5. check if "display settings" automatically detects the removal of the external monitor Expected result: display settings should automatically detect the removal of external monitor when unplugging the HDMI cable Actual result: System does not automatically detect the removal of the external monitor when HDMI cable is removed. Sound setting also list HDMI audio in output tab after removal external monitor. Failure rate: 2/10 to 1/10 [Fix] two commits from upstream drm-intel-next-queued branch [Test case] see "steps to reproduce" [Regression potential] still possible, but for the distro only Eoan will get it. OEM kernels will get tested on systems that get it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838886] Re: New ID in ums-realtek module breaks cardreader
I am currently sorting this out with Realtek. I'll let you know when there's any progress. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838886 Title: New ID in ums-realtek module breaks cardreader Status in linux package in Ubuntu: Confirmed Bug description: When installing the latest HWE stack (Linux 5.0) to Ubuntu 18.04, the Realtek cardreader in my ZOTAC ZBOX-CI323NANO stops working correctly. Previously it accepted SD cards all the time. Now it looks like you have to insert the card on booting or shortly after booting to access it. If you wait longer, it no longer detects the card. The reason for this can be found in the kernel log (dmes). On boot it seems to detect a card in the reader, although there is none. After a while it says "Read capacity failed" and "scsi 2:0:0:0: rejecting I/O to dead device" and then resets the device. It tries this 3 times and then gives up completely. After that any real device plugged is no longer detected. The device is: idVendor=0bda, idProduct=0153, bcdDevice=57.13 Support for this was added in mainline kernel: https://github.com/torvalds/linux/commit/1a6dd3fea131276a4fc44ae77b0f471b0b473577 And this seems to be backported to 5.0 kernel in Ubuntu 18.04 HWE stack. Full log on boot (no card inserted): [3.689559] usb 1-5.1: new high-speed USB device number 4 using xhci_hcd [3.898312] usb 1-5.1: New USB device found, idVendor=0bda, idProduct=0153, bcdDevice=57.13 [3.898316] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [3.898319] usb 1-5.1: Product: USB2.0-CRW [3.898322] usb 1-5.1: Manufacturer: Generic [3.898324] usb 1-5.1: SerialNumber: 2012092657120 [3.911571] usbcore: registered new interface driver usb-storage [3.914796] usbcore: registered new interface driver uas [3.917676] ums-realtek 1-5.1:1.0: USB Mass Storage device detected [3.924478] scsi host2: usb-storage 1-5.1:1.0 [3.924649] usbcore: registered new interface driver ums-realtek [...] [ 13.477360] ums-realtek 1-5.1:1.0: USB Mass Storage device detected [ 13.509592] scsi host2: usb-storage 1-5.1:1.0 [ 14.544213] scsi 2:0:0:0: Direct-Access Generic- SD/MMC/MS PRO1.00 PQ: 0 ANSI: 4 [ 14.545237] sd 2:0:0:0: Attached scsi generic sg1 type 0 [ 14.549430] sd 2:0:0:0: [sdb] Attached SCSI removable disk [ 170.961728] scsi 2:0:0:0: rejecting I/O to dead device [ 170.962069] scsi 2:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_ERROR [ 170.962073] scsi 2:0:0:0: [sdb] Sense not available. [ 171.985846] usb 1-5.1: new high-speed USB device number 8 using xhci_hcd [ 172.194299] usb 1-5.1: New USB device found, idVendor=0bda, idProduct=0153, bcdDevice=57.13 [ 172.194317] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 172.194327] usb 1-5.1: Product: USB2.0-CRW [ 172.194338] usb 1-5.1: Manufacturer: Generic [ 172.194346] usb 1-5.1: SerialNumber: 2012092657120 [ 172.200625] ums-realtek 1-5.1:1.0: USB Mass Storage device detected [ 172.212503] scsi host2: usb-storage 1-5.1:1.0 [ 173.233036] scsi 2:0:0:0: Direct-Access Generic- SD/MMC/MS PRO1.00 PQ: 0 ANSI: 4 [ 173.233796] sd 2:0:0:0: Attached scsi generic sg1 type 0 [ 173.239620] sd 2:0:0:0: [sdb] Attached SCSI removable disk [ 329.654468] usb 1-5.1: USB disconnect, device number 8 [ 329.665905] scsi 2:0:0:0: rejecting I/O to dead device [ 329.665970] scsi 2:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_ERROR [ 329.665976] scsi 2:0:0:0: [sdb] Sense not available. [ 330.701685] usb 1-5.1: new high-speed USB device number 9 using xhci_hcd [ 330.910415] usb 1-5.1: New USB device found, idVendor=0bda, idProduct=0153, bcdDevice=57.13 [ 330.910433] usb 1-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 330.910444] usb 1-5.1: Product: USB2.0-CRW [ 330.910455] usb 1-5.1: Manufacturer: Generic [ 330.910463] usb 1-5.1: SerialNumber: 2012092657120 [ 330.917013] ums-realtek 1-5.1:1.0: USB Mass Storage device detected [ 330.932295] scsi host2: usb-storage 1-5.1:1.0 [ 331.952829] scsi 2:0:0:0: Direct-Access Generic- SD/MMC/MS PRO1.00 PQ: 0 ANSI: 4 [ 331.953686] sd 2:0:0:0: Attached scsi generic sg1 type 0 [ 331.960126] sd 2:0:0:0: [sdb] Attached SCSI removable disk [ 488.343981] usb 1-5.1: USB disconnect, device number 9 [ 488.354292] scsi 2:0:0:0: rejecting I/O to dead device [ 488.356453] scsi 2:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_ERROR [ 488.356458] scsi 2:0:0:0: [sdb] Sense not available. After time 488, any SD card inserted is no longer detected, because driver gave up. Please revert adding the device with
[Kernel-packages] [Bug 1836860] Re: [18.04 FEAT] Enhanced CPU-MF hardware counters - kernel part
** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836860 Title: [18.04 FEAT] Enhanced CPU-MF hardware counters - kernel part Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: SRU Justification: == [Impact] * Enhanced CPU-MF hardware counters - fix lack of support of new hardware [Fix] * 46a984ffb86c8542fa510656fa8cb33befe8ee8f 46a984ff "s390/cpum_cf: Add support for CPU-MF SVN 6" * 820bace734722715c643dcb5f74b502cb912d4eb 820bace "s390/cpumf: Add extended counter set definitions for model 8561 and 8562" [Test Case] * try CPU-Measurement Facility counter on z14 and next generation hardware - only IBM can do that now [Regression Potential] * The regression potential can be considered as low since these changes are limited to arch/s390 * do only touch perf_* code * and mainly add code (rather than modify or remove) [Other Info] * first commit is taken from 5.2, second from 5.3-rc1 __ Enhance the CPU-MF hardware counters for improved HW support . Kernel 5.2 commits and kernel 5.3 patch on top Already requested for Ubuntu 19.10 kernel 5.2 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834201 kernel 5.3 fix https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836739 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1836860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837117] Re: EeePC 1005px laptop backlight is off after system boot up
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Disco)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1837117
Title:
EeePC 1005px laptop backlight is off after system boot up
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Disco:
Fix Committed
Status in linux source package in Eoan:
Fix Released
Bug description:
== SRU Justification ==
Commit 78f3ac76d9e5 ("platform/x86: asus-wmi: Tell the EC the OS will
handle the display off hotkey") causes the backlight to be permanently off
on various EeePC laptop models using the eeepc-wmi driver (Asus EeePC
1015BX, Asus EeePC 1025C).
== Fix ==
* 1dd93f87 (platform/x86: asus-wmi: Only Tell EC the OS will handle
display hotkeys from asus_nb_wmi)
This patch addes a .wmi_backlight_set_devstate quirk for specific
models to make asus_wmi_set_devstate(ASUS_WMI_DEVID_BACKLIGHT, 2, NULL)
conditional.
Only X/D contain the commit that introduce this issue (78f3ac76), this
patch can be cherry-picked into D.
For X, it needs some content adjustment to add quirks only to those
models that exist in Xenial tree.
== Test ==
Test kernels could be found here:
https://people.canonical.com/~phlin/kernel/lp-1837117-eeepc/
Bug reporter has verified that this fix works as expected on X.
== Regression Potential ==
Low, quirks limited to specific ASUS laptops and by far there is no
further change to this in upstream kernel.
== Original Bug Report ==
After kernel update the backlight on my Asus eeepc 1005px becomes off during
boot up. I can see the login screen if I point light to the screen. The
backlight is not reacting on brightness adjustment keys. The backlight starts
working only if I close and open the laptop lid.
I have tried to:
* echo 10 > /sys/class/backlight/acpi_video0/brightness
* echo 125 > /sys/class/backlight/intel_backlight/brightness
* vbetool dpms on
* pass "acpi_backlight=vendor" kernel parameter
* install gdm instead of lightdm
* create /usr/share/X11/xorg.conf.d/80-backlight.conf with content
recommended in Kernel/Debugging/Backlight Wiki article
with no luck.
The backlight works fine if I pass "acpi_osi=" kernel parameter, the
brightness is adjusted by keys, but the applet does not react to
adjustments.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-145-generic 4.4.0-145.171
ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
Uname: Linux 4.4.0-145-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Jul 18 22:30:44 2019
InstallationDate: Installed on 2019-02-17 (151 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
SourcePackage: linux-signed
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837117/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836910] Re: br_netfilter: namespace sysctl operations
** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836910 Title: br_netfilter: namespace sysctl operations Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Disco: Fix Committed Bug description: SRU Justification Impact: Currently, the /proc/sys/net/bridge folder is only created in the initial network namespace. This blocks use-cases where users would like to e.g. not do bridge filtering for bridges in a specific network namespace while doing so for bridges located in another network namespace. Fix: The patches linked below ensure that the /proc/sys/net/bridge folder is available in each network namespace if the module is loaded and disappears from all network namespaces when the module is unloaded. In doing so the patch makes the sysctls: bridge-nf-call-arptables bridge-nf-call-ip6tables bridge-nf-call-iptables bridge-nf-filter-pppoe-tagged bridge-nf-filter-vlan-tagged bridge-nf-pass-vlan-input-dev apply per network namespace. Regression Potential: Low since it is limited to the br_netfilter module. I tested the patchset extensively by compiling a kernel with the patches applied. I loaded and unloaded the module and verified that it works correctly for the container usecase and does not crash. The Google ChromeOS team has also backported this patchset to their kernel and has not seen any issues so far: https://bugs.chromium.org/p/chromium/issues/detail?id=878034 Security considerations around netfilter rules are also low. The netfilter rules are already per network namespace so it should be safe for users to specify whether bridge devices inside a network namespace are supposed to go through iptables et al. or not. Also, this can already be done per-bridge by setting an option for each individual bridge via Netlink. It should also be possible to do this for all bridges in a network namespace via sysctls. Test Case: Tested with LXD on a kernel with the patches applied and per-network namespace iptables. Target Kernels: All LTS kernels starting from 4.15. Kernel 5.3 has the patchset upstream. Patches: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ff6d090d0db41425aef0cfe5dc58bb3cc12514a2 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=22567590b2e634247931b3d2351384ba45720ebe https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7e6daf50e1f4ea0ecd56406beb64ffc66e1e94db To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837136] Re: ideapad_laptop disables WiFi/BT radios on Lenovo Y540
** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837136 Title: ideapad_laptop disables WiFi/BT radios on Lenovo Y540 Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Released Bug description: === SRU Justification === [Impact] WiFi on Ideapads are rfkill HW blocked by default. [Fix] Remove no_hw_rfkill_list as most Ideapads don't have hardware rfkill button. [Test] User reported the fix works. [Regression Potential] Low. If there's any actual device that has HW rfkill button, we can simply add it to whitelist. === Original Bug Report === I have a brand new LeNovo legion Y540 and the ideapad_laptop module results in a rfkill. If the module is removed/blacklisted, then wifi works, but some ACPI functionality is lost (the fans don't spin correctly and the laptop doesn't cool properly). I will try to compile ideapad_laptop adding the laptop info to no_hw_rfkill_list[]. I only tried in ubuntu 19.10 (although this is a kernel issue) rfkill output: sudo rfkill ID TYPE DEVICE SOFT HARD 2 bluetooth hci0blocked unblocked 3 wlan phy0 unblocked unblocked 4 wlan ideapad_wlan unblocked blocked 5 bluetooth ideapad_bluetooth blocked blocked 1) Ubuntu 5.0.0-20.21-generic 5.0.8 (rest of info in attachment) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jmamede2484 F pulseaudio /dev/snd/controlC0: jmamede2484 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-07-18 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81SX NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=/dev/mapper/lvmmamede-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-20-generic N/A linux-backports-modules-5.0.0-20-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN28WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y540-15IRH dmi.modalias: dmi:bvnLENOVO:bvrBHCN28WW:bd05/28/2019:svnLENOVO:pn81SX:pvrLegionY540-15IRH:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY540-15IRH: dmi.product.family: Legion Y540-15IRH dmi.product.name: 81SX dmi.product.sku: LENOVO_MT_81SX_BU_idea_FM_Legion Y540-15IRH dmi.product.version: Legion Y540-15IRH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826447] Re: Azure: Backport vIOMMU driver (increase vCPU limits)
** Changed in: linux-azure (Ubuntu Disco) 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/1826447 Title: Azure: Backport vIOMMU driver (increase vCPU limits) Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure source package in Disco: Fix Committed Bug description: Description: To support VM instances with >255 vCPUS, we need the patch set below backported to the Azure 4.18 kernel. These patches include - - New Hyper-V IOMMU driver. This driver will be Hyper-V specific. - Minor update to the Hyper-V specific virtual PCI code. Need to expand the size of an array to allow for a larger number of vCPUs. There are very large VM instance sizes coming to Azure in 2019, and Ubuntu will require the following patches in order to function properly: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=29217a4746835fef35279abbd12c1a1efe83bfca https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=84fdfafab849036b5aefa52824b5cb42e887ef0e https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=c8ccf7599ddac5fa48e06104c44b24709e21eed5 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/controller /pci-hyperv.c?id=9bc1174280ddf7693e8c29a8f1743809e987ac37 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1826447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839891] Re: suspend by power button doesn't work when screen is locked
Thank you for taking the time to report this bug and helping to make Ubuntu better. I have no special knowledge here, but your settings are saved for your user account, but with the machine unattended and therefore lock taking effect, 'rights' to suspend and do other functions are disabled until users have proven who they are. It could be anyone trying to suspend the system, so I think it's correct for the system to ignore the 'suspend' until the person-wishing-to- suspend has proven they have the rights to suspend the machine. Also please your system if fully-updated, should report itself as 18.04.3 (which was officially released last Thursday 8 August (http://fridge.ubuntu.com/?p=8730) though most people saw it a day or so before then). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839891 Title: suspend by power button doesn't work when screen is locked Status in linux package in Ubuntu: Incomplete Bug description: I have In Privacy Settings, Screen Lock : On In Power Settings, When the Power Button is pressed : Suspend However suspending only works when the desktop session is unlocked. When I leave the computer unattended so it locks the screen after 10 minutes, as soon as the screen is locked I can hit the Power Button as many times as I want and the computer won't suspend. This is on uptodate Ubuntu 18.04.2 LTS, using the flashback gnome session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839891/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838677] Re: shiftfs: allow overlayfs
** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838677 Title: shiftfs: allow overlayfs Status in linux package in Ubuntu: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: SRU Justification Impact: Currently it is not possible to use overlayfs on top of shiftfs. This means Docker inside of LXD cannot make user of the overlay2 graph driver which is blocking users such as Travis from making use of it efficiently. Regression Potential: Limited to shiftfs and overlayfs on top of shiftfs. Overlayfs does prevent "remote" filesystems such as ceph, nfs, etc. from being used as the underlay. With this patch shiftfs however can be used as an underlay and we special case it as a suitable filesystem to be used under overlayfs. I verified that the patch does not lead to regression on overlayfs workloads that do not make use of shiftfs as underlay. Additionally, I tested Docker with the overlay2 graphdriver on top of shiftfs. This also has not lead to any regressions. Test case: Building a kernel with the patch: sudo snap install lxd sudo lxd init sudo lxc launch images:ubuntu/bionic b1 sudo lxc config set b1 security.nesting true sudo lxc restart --force b1 sudo lxc shell b1 sudo apt-get install \ apt-transport-https \ ca-certificates \ curl \ gnupg-agent \ software-properties-common curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add - curl -fsSL get.docker.com | CHANNEL=test sh sudo add-apt-repository \ "deb [arch=amd64] https://download.docker.com/linux/ubuntu \ $(lsb_release -cs) \ stable" sudo apt-get update sudo apt-get install docker-ce docker-ce-cli containerd.io sudo systemctl stop docker cat
[Kernel-packages] [Bug 1447664] Re: 14e4:1687 broadcom tg3 network driver disconnects under high load
Chi-Thanh Christopher Nguyen, please note:
1) The kernel 5.2.7 is not supported here on Launchapd. Hence, please
re-direct your inquiry to the relevant maintainer(s) upstream.
2) If you can reproduce the issue with a supported kernel then please file a
new report to provide debugging logs via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
** Package changed: linux (Debian) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
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/1447664
Title:
14e4:1687 broadcom tg3 network driver disconnects under high load
Status in linux package in Ubuntu:
Fix Released
Bug description:
The tg3 broadcom network driver that binds with chipset 5762 goes offline and
unable to recover (even with tg3 watchdog timeout) when network transmit is
under high load. Call trace:
https://launchpadlibrarian.net/204185480/dmesg
When this happens, only a reboot would be able to fix it. Sometimes,
however, bringing the interface offline and online (via ifconfig)
would recover networking. I've also tested with the latest tg3 driver
(dec 2014 version) and networking is still problematic. I have also
disabled TSO, GSO etc... with ethtool and the bug still surfaces.
This bug may be related to the integrated Firmware.
Here is the procedure to replicate the issue because it is hard to
replicate it under moderate network load.
1. Bootup a machine with a broadcom 5762 NIC (ie. HP DeskElite 705) using a
Ubuntu/Kubunu Live CD 14.04-15.04.
2. from another machine: start 5 sessions, repetitively copy (scp with public
key authentication) a 70 meg file back and forth to the tg3 machine in each
session. (not sure if this is necessary)
3. create a 1GB file on the tg3 machine, with something like dd
if=/dev/urandom of=/my/test/file bs=1024 count=$((1024*1000))
4. from another machine: repetitively scp copy that 1GB file from the tg3
machine. This can be done with something like:
while [ 0 ]; do
scp -i /my/scp/private.key u...@ip.of.tg3:/my/test/file /tmp
done;
Networking will mostly goes offline in about 10-30 minutes.
WORKAROUND: Add udev rule to make the changes permanent in
/etc/udev/rules.d/80-tg3-fix.rules :
ACTION=="add", SUBSYSTEM=="net", ATTRS{vendor}=="0x14e4",
ATTRS{device}=="0x1687", RUN+="/sbin/ethtool -K %k highdma off"
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-15-generic 3.19.0-15.15
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: kubuntu3748 F pulseaudio
/dev/snd/controlC0: kubuntu3748 F pulseaudio
CasperVersion: 1.360
Date: Thu Apr 23 11:16:24 2015
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
LiveMediaBuild: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Hewlett-Packard HP EliteDesk 705 G1 MT
ProcEnviron:
LANGUAGE=
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi
file=/cdrom/preseed/hostname.seed boot=casper maybe-ubiquity quiet splash ---
PulseList:
Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not
accessible: Permission denied
No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-3.19.0-15-generic N/A
linux-backports-modules-3.19.0-15-generic N/A
linux-firmware 1.143
RfKill:
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/22/2014
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L06 v02.15
dmi.board.asset.tag: 2UA5041TG4
dmi.board.name: 2215
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: 2UA5041TG4
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias:
dmi:bvnHewlett-Packard:bvrL06v02.15:bd10/22/2014:svnHewlett-Packard:pnHPEliteDesk705G1MT:pvr:rvnHewlett-Packard:rn2215:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.product.name: HP EliteDesk 705 G1 MT
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1447664/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1447664] Re: 14e4:1687 broadcom tg3 network driver disconnects under high load
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/1447664
Title:
14e4:1687 broadcom tg3 network driver disconnects under high load
Status in linux package in Ubuntu:
Fix Released
Bug description:
The tg3 broadcom network driver that binds with chipset 5762 goes offline and
unable to recover (even with tg3 watchdog timeout) when network transmit is
under high load. Call trace:
https://launchpadlibrarian.net/204185480/dmesg
When this happens, only a reboot would be able to fix it. Sometimes,
however, bringing the interface offline and online (via ifconfig)
would recover networking. I've also tested with the latest tg3 driver
(dec 2014 version) and networking is still problematic. I have also
disabled TSO, GSO etc... with ethtool and the bug still surfaces.
This bug may be related to the integrated Firmware.
Here is the procedure to replicate the issue because it is hard to
replicate it under moderate network load.
1. Bootup a machine with a broadcom 5762 NIC (ie. HP DeskElite 705) using a
Ubuntu/Kubunu Live CD 14.04-15.04.
2. from another machine: start 5 sessions, repetitively copy (scp with public
key authentication) a 70 meg file back and forth to the tg3 machine in each
session. (not sure if this is necessary)
3. create a 1GB file on the tg3 machine, with something like dd
if=/dev/urandom of=/my/test/file bs=1024 count=$((1024*1000))
4. from another machine: repetitively scp copy that 1GB file from the tg3
machine. This can be done with something like:
while [ 0 ]; do
scp -i /my/scp/private.key u...@ip.of.tg3:/my/test/file /tmp
done;
Networking will mostly goes offline in about 10-30 minutes.
WORKAROUND: Add udev rule to make the changes permanent in
/etc/udev/rules.d/80-tg3-fix.rules :
ACTION=="add", SUBSYSTEM=="net", ATTRS{vendor}=="0x14e4",
ATTRS{device}=="0x1687", RUN+="/sbin/ethtool -K %k highdma off"
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-15-generic 3.19.0-15.15
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: kubuntu3748 F pulseaudio
/dev/snd/controlC0: kubuntu3748 F pulseaudio
CasperVersion: 1.360
Date: Thu Apr 23 11:16:24 2015
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
LiveMediaBuild: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Hewlett-Packard HP EliteDesk 705 G1 MT
ProcEnviron:
LANGUAGE=
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi
file=/cdrom/preseed/hostname.seed boot=casper maybe-ubiquity quiet splash ---
PulseList:
Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not
accessible: Permission denied
No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-3.19.0-15-generic N/A
linux-backports-modules-3.19.0-15-generic N/A
linux-firmware 1.143
RfKill:
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/22/2014
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L06 v02.15
dmi.board.asset.tag: 2UA5041TG4
dmi.board.name: 2215
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: 2UA5041TG4
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias:
dmi:bvnHewlett-Packard:bvrL06v02.15:bd10/22/2014:svnHewlett-Packard:pnHPEliteDesk705G1MT:pvr:rvnHewlett-Packard:rn2215:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.product.name: HP EliteDesk 705 G1 MT
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1447664/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1447664] Re: 14e4:1687 broadcom tg3 network driver disconnects under high load
** No longer affects: 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/1447664
Title:
14e4:1687 broadcom tg3 network driver disconnects under high load
Status in linux package in Ubuntu:
Fix Released
Bug description:
The tg3 broadcom network driver that binds with chipset 5762 goes offline and
unable to recover (even with tg3 watchdog timeout) when network transmit is
under high load. Call trace:
https://launchpadlibrarian.net/204185480/dmesg
When this happens, only a reboot would be able to fix it. Sometimes,
however, bringing the interface offline and online (via ifconfig)
would recover networking. I've also tested with the latest tg3 driver
(dec 2014 version) and networking is still problematic. I have also
disabled TSO, GSO etc... with ethtool and the bug still surfaces.
This bug may be related to the integrated Firmware.
Here is the procedure to replicate the issue because it is hard to
replicate it under moderate network load.
1. Bootup a machine with a broadcom 5762 NIC (ie. HP DeskElite 705) using a
Ubuntu/Kubunu Live CD 14.04-15.04.
2. from another machine: start 5 sessions, repetitively copy (scp with public
key authentication) a 70 meg file back and forth to the tg3 machine in each
session. (not sure if this is necessary)
3. create a 1GB file on the tg3 machine, with something like dd
if=/dev/urandom of=/my/test/file bs=1024 count=$((1024*1000))
4. from another machine: repetitively scp copy that 1GB file from the tg3
machine. This can be done with something like:
while [ 0 ]; do
scp -i /my/scp/private.key u...@ip.of.tg3:/my/test/file /tmp
done;
Networking will mostly goes offline in about 10-30 minutes.
WORKAROUND: Add udev rule to make the changes permanent in
/etc/udev/rules.d/80-tg3-fix.rules :
ACTION=="add", SUBSYSTEM=="net", ATTRS{vendor}=="0x14e4",
ATTRS{device}=="0x1687", RUN+="/sbin/ethtool -K %k highdma off"
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-15-generic 3.19.0-15.15
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: kubuntu3748 F pulseaudio
/dev/snd/controlC0: kubuntu3748 F pulseaudio
CasperVersion: 1.360
Date: Thu Apr 23 11:16:24 2015
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
LiveMediaBuild: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Hewlett-Packard HP EliteDesk 705 G1 MT
ProcEnviron:
LANGUAGE=
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi
file=/cdrom/preseed/hostname.seed boot=casper maybe-ubiquity quiet splash ---
PulseList:
Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not
accessible: Permission denied
No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-3.19.0-15-generic N/A
linux-backports-modules-3.19.0-15-generic N/A
linux-firmware 1.143
RfKill:
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/22/2014
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L06 v02.15
dmi.board.asset.tag: 2UA5041TG4
dmi.board.name: 2215
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: 2UA5041TG4
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias:
dmi:bvnHewlett-Packard:bvrL06v02.15:bd10/22/2014:svnHewlett-Packard:pnHPEliteDesk705G1MT:pvr:rvnHewlett-Packard:rn2215:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.product.name: HP EliteDesk 705 G1 MT
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1447664/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1447664] [NEW] 14e4:1687 broadcom tg3 network driver disconnects under high load
You have been subscribed to a public bug:
The tg3 broadcom network driver that binds with chipset 5762 goes offline and
unable to recover (even with tg3 watchdog timeout) when network transmit is
under high load. Call trace:
https://launchpadlibrarian.net/204185480/dmesg
When this happens, only a reboot would be able to fix it. Sometimes,
however, bringing the interface offline and online (via ifconfig) would
recover networking. I've also tested with the latest tg3 driver (dec
2014 version) and networking is still problematic. I have also disabled
TSO, GSO etc... with ethtool and the bug still surfaces. This bug may
be related to the integrated Firmware.
Here is the procedure to replicate the issue because it is hard to
replicate it under moderate network load.
1. Bootup a machine with a broadcom 5762 NIC (ie. HP DeskElite 705) using a
Ubuntu/Kubunu Live CD 14.04-15.04.
2. from another machine: start 5 sessions, repetitively copy (scp with public
key authentication) a 70 meg file back and forth to the tg3 machine in each
session. (not sure if this is necessary)
3. create a 1GB file on the tg3 machine, with something like dd if=/dev/urandom
of=/my/test/file bs=1024 count=$((1024*1000))
4. from another machine: repetitively scp copy that 1GB file from the tg3
machine. This can be done with something like:
while [ 0 ]; do
scp -i /my/scp/private.key u...@ip.of.tg3:/my/test/file /tmp
done;
Networking will mostly goes offline in about 10-30 minutes.
WORKAROUND: Add udev rule to make the changes permanent in
/etc/udev/rules.d/80-tg3-fix.rules :
ACTION=="add", SUBSYSTEM=="net", ATTRS{vendor}=="0x14e4",
ATTRS{device}=="0x1687", RUN+="/sbin/ethtool -K %k highdma off"
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-15-generic 3.19.0-15.15
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: kubuntu3748 F pulseaudio
/dev/snd/controlC0: kubuntu3748 F pulseaudio
CasperVersion: 1.360
Date: Thu Apr 23 11:16:24 2015
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
LiveMediaBuild: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Hewlett-Packard HP EliteDesk 705 G1 MT
ProcEnviron:
LANGUAGE=
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi
file=/cdrom/preseed/hostname.seed boot=casper maybe-ubiquity quiet splash ---
PulseList:
Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not
accessible: Permission denied
No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-3.19.0-15-generic N/A
linux-backports-modules-3.19.0-15-generic N/A
linux-firmware 1.143
RfKill:
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/22/2014
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L06 v02.15
dmi.board.asset.tag: 2UA5041TG4
dmi.board.name: 2215
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: 2UA5041TG4
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias:
dmi:bvnHewlett-Packard:bvrL06v02.15:bd10/22/2014:svnHewlett-Packard:pnHPEliteDesk705G1MT:pvr:rvnHewlett-Packard:rn2215:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.product.name: HP EliteDesk 705 G1 MT
dmi.sys.vendor: Hewlett-Packard
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bios-outdated-2.28 cscc kernel-bug-exists-upstream
kernel-bug-exists-upstream-4.11 lucid trusty vivid xenial
--
14e4:1687 broadcom tg3 network driver disconnects under high load
https://bugs.launchpad.net/bugs/1447664
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 1795292] Re: ELAN469D touch pad not working
Sorry because I mistakenly used "ivrs_ioapic[4]=00:14.0" in my patch. I've updated it as "ivrs_ioapic[32]=00:14.0" in my patch sent to upstream: https://lkml.org/lkml/2019/8/8/286 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1795292 Title: ELAN469D touch pad not working Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I installed Bionic Beaver and now upgraded to Cosmic Cuttlefish on this Lenovo Ideapad 330S-15ARR laptop. The touch pad doesn't work in either. Some possibly relevant info from dmesg: i2c_hid i2c-ELAN469D:00: i2c-ELAN469D:00 supply vdd not found, using dummy regulator i2c_designware AMDI0010:01: controller timed out ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-7-generic 4.18.0-7.8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xorbit 2086 F pulseaudio /dev/snd/pcmC1D0p: xorbit 2086 F...m pulseaudio /dev/snd/controlC0: xorbit 2086 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 30 23:14:26 2018 InstallationDate: Installed on 2018-09-20 (10 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81FB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic processor.max_cstate=1 rcu_nocbs=0-7 pcie_aspm=off pci=noaer quiet splash vt.handoff=1 elan_i2c.dyndbg=+p RelatedPackageVersions: linux-restricted-modules-4.18.0-7-generic N/A linux-backports-modules-4.18.0-7-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-09-30 (0 days ago) dmi.bios.date: 06/08/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7WCN22WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7WCN22WW:bd06/08/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR: dmi.product.family: ideapad 330S-15ARR dmi.product.name: 81FB dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR dmi.product.version: Lenovo ideapad 330S-15ARR dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-20 (13 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: cosmic Uname: Linux 4.19.0-041900rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to cosmic on 2018-09-30 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1795292/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838627] Re: AppArmor onexec transition causes WARN kernel stack trace
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838627 Title: AppArmor onexec transition causes WARN kernel stack trace Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Fix Committed Bug description: microk8s has reported on issue with the Xenial kernel where apparmor causes the following kernel stack trace due to an apparmor AA_BUG condition being triggered. [ 225.236085] [ cut here ] [ 225.236104] WARNING: CPU: 1 PID: 13726 at /build/linux-aUWTNP/linux-4.4.0/security/apparmor/file.c:136 aa_audit_file+0x16e/0x180() [ 225.236109] AppArmor WARN aa_audit_file: ((!()->apparmor_audit_data->request)): [ 225.236113] Modules linked in: [ 225.236118] btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs veth xt_nat xt_mark xt_comment ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs libcrc32c ctr ccm ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat_ipv4 br_netfilter bridge stp llc pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep aufs overlay binfmt_misc drbg ansi_cprng dm_crypt snd_hda_codec_hdmi arc4 eeepc_wmi asus_wmi sparse_keymap nvidia_uvm(POE) mxm_wmi joydev input_leds btusb btrtl btbcm btintel bluetooth snd_usb_audio snd_usbmidi_lib snd_hda_intel snd_hda_codec intel_rapl x86_pkg_temp_thermal snd_hda_core intel_powerclamp snd_hwdep coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_ens1371 snd_ac97_codec gameport ac97_bus [ 225.236305] snd_seq_midi aesni_intel snd_pcm snd_seq_midi_event aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_rawmidi snd_seq iwlmvm snd_seq_device serio_raw snd_timer mac80211 snd soundcore iwlwifi cfg80211 mei_me mei shpchp 8250_fintek wmi acpi_pad mac_hid ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_recent xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack parport_pc iptable_filter ip_tables ppdev x_tables lp parport autofs4 hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) i915_bpo psmouse e1000e intel_ips ptp i2c_algo_bit [ 225.236420] pps_core drm_kms_helper nvme syscopyarea sysfillrect sysimgblt fb_sys_fops ahci drm libahci video fjes [ 225.236446] CPU: 1 PID: 13726 Comm: runc:[2:INIT] Tainted: PW OE 4.4.0-154-generic #181-Ubuntu [ 225.236451] Hardware name: System manufacturer System Product Name/PRIME H270-PRO, BIOS 0323 01/04/2017 [ 225.236456] 0286 fa217f3573a84520 88033ade39d0 8140b481 [ 225.236464] 88033ade3a18 81d03018 88033ade3a08 81085432 [ 225.236477] 88035cb2f000 88033ade3b6c 88033bcb8b88 88033ade3d88 [ 225.236484] Call Trace: [ 225.236498] [] dump_stack+0x63/0x82 [ 225.236509] [] warn_slowpath_common+0x82/0xc0 [ 225.236518] [] warn_slowpath_fmt+0x5c/0x80 [ 225.236527] [] ? label_match.constprop.9+0x3dc/0x6c0 [ 225.236536] [] aa_audit_file+0x16e/0x180 [ 225.236544] [] profile_onexec+0x13d/0x3d0 [ 225.236554] [] handle_onexec+0x10e/0x10d0 [ 225.236562] [] ? vfs_getxattr_alloc+0x67/0x100 [ 225.236571] [] ? cap_inode_getsecurity+0x95/0x220 [ 225.236581] [] ? security_inode_getsecurity+0x5d/0x70 [ 225.236589] [] apparmor_bprm_set_creds+0x117/0xa60 [ 225.236596] [] ? vfs_getxattr+0x9e/0xb0 [ 225.236608] [] ? ovl_getxattr+0x52/0xb0 [overlay] [ 225.236617] [] ? get_vfs_caps_from_disk+0x7d/0x180 [ 225.236624] [] ? cap_bprm_set_creds+0xa3/0x5f0 [ 225.236633] [] security_bprm_set_creds+0x39/0x50 [ 225.236642] [] prepare_binprm+0x85/0x190 [ 225.236651] [] do_execveat_common.isra.31+0x4b4/0x770 [ 225.236661] [] SyS_execve+0x3a/0x50 [ 225.236671] [] stub_execve+0x5/0x5 [ 225.236678] [] ? entry_SYSCALL_64_fastpath+0x22/0xcb [ 225.236684] ---[ end trace 6b2beaa85ae31c29 ]--- This is caused when the change_onexec api is used and permitted by the profile but the task has the NO_NEW_PRIVS flag set causing the domain transition specified in the change_onexec request to fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838627/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832383] Re: failed command: WRITE FPDMA QUEUED on ata6 port of Marvell 88EE9230 controller
[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/1832383
Title:
failed command: WRITE FPDMA QUEUED on ata6 port of Marvell 88EE9230
controller
Status in linux package in Ubuntu:
Expired
Bug description:
After updating the Marvell 88EE9230 SATA controller firmware to 2.3.xxx from:
https://www.station-drivers.com/index.php?option=com_remository=352=select=347=en
approximately every 2-3 weeks the ata6 port populated with a SAMSUNG MZ7TN512
throws errors:
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: failed command: WRITE FPDMA
QUEUED
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: status: { DRDY }
Jun 02 03:49:29 doomsdaydevice kernel: ata6.00: cmd
61/08:80:a8:08:10/00:00:00:00:00/40 tag 16 ncq dma 4096 out
The other ports don't throw errors.
However, when the Marvell controller was initially using firmware 1.x.xxx,
the siutation was even worse. Frequently, links were rested, raid corruption
happened, and kernel panics occurred. Example from May/2018 (hostname changed,
same machine):
May 31 18:25:43 amd-server kernel: [ 3339.410446] ata5.00: failed command:
WRITE FPDMA QUEUED
May 31 18:25:43 amd-server kernel: [ 3339.412748] ata5.00: cmd
61/40:f0:28:f1:b6/05:00:ac:00:00/40 tag 30 ncq dma 688128 out
May 31 18:25:43 amd-server kernel: [ 3339.412748] res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May 31 18:25:43 amd-server kernel: [ 3339.417375] ata5.00: status: { DRDY }
May 31 18:25:43 amd-server kernel: [ 3339.419665] ata5: hard resetting link
May 31 18:25:44 amd-server kernel: [ 3339.733599] ata5: SATA link up 6.0 Gbps
(SStatus 133 SControl 300)
May 31 18:25:44 amd-server kernel: [ 3339.734865] ata5.00: configured for
UDMA/133
May 31 18:25:44 amd-server kernel: [ 3339.734935] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734945] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734956] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734966] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734976] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.734986] ata5.00: device reported
invalid CHS sector 0
May 31 18:25:44 amd-server kernel: [ 3339.735066] ata5: EH complete
Which also caused errors within the drives (smartctl -a /dev/sdd):
Error 2 occurred at disk power-on lifetime: 2069 hours (86 days + 5 hours)
When the command that caused the error occurred, the device was active or
idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 71 8f 66 c9 0f Error: ICRC, ABRT 113 sectors at LBA = 0x0fc9668f =
264857231
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- --
25 00 00 00 60 c9 e0 00 03:34:02.078 READ DMA EXT
25 00 00 00 5c c9 e0 00 03:34:02.060 READ DMA EXT
25 00 00 00 58 c9 e0 00 03:34:02.042 READ DMA EXT
25 00 00 00 54 c9 e0 00 03:34:02.026 READ DMA EXT
25 00 00 00 4c c9 e0 00 03:34:02.024 READ DMA EXT
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Jun 11 01:17 seq
crw-rw 1 root audio 116, 33 Jun 11 01:17 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 18.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=339ce141-0884-4f2f-8f05-47a488cc3dd2
InstallationDate: Installed on 2018-03-29 (438 days ago)
InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
IwConfig:
enp3s0 no wireless extensions.
lo no wireless extensions.
enp5s0 no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
Package: linux (not installed)
PciMultimedia:
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic
root=UUID=c77001fd-6968-4606-9baa-a60439b1e173 ro
ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
PulseList:
Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio
daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-4.18.0-21-generic N/A
[Kernel-packages] [Bug 1658219] Re: flock not mediated by 'k'
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1658219
Title:
flock not mediated by 'k'
Status in AppArmor:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Yakkety:
Won't Fix
Bug description:
$ cat ./apparmor.profile
#include
profile test {
#include
/bin/bash ixr,
/dev/pts/* rw,
/usr/bin/flock ixr,
# Not blocked:
# aa-exec -p test -- flock -w 1 /tmp/test.lock -c true
/tmp/test.lock rw,
}
$ sudo apparmor_parser -r ./apparmor.profile
$ aa-exec -p test -- flock -w 1 /tmp/test.lock -c true && echo yes
yes
$ ls -l /tmp/test.lock
-rw-rw-r-- 1 jamie jamie 0 Jan 20 15:57 /tmp/test.lock
The flock command uses flock(LOCK_EX) and I expected it to be blocked
due to the lack of 'k'.
apparmor userspace 2.10.95-0ubuntu2.5 (xenial) and 4.9.0-12.13-generic
kernel on amd64.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1658219/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839037] Re: Stacked onexec transitions fail when under NO NEW PRIVS restrictions
** Changed in: linux (Ubuntu Xenial) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839037 Title: Stacked onexec transitions fail when under NO NEW PRIVS restrictions Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: running the apparmor nnp regression tests results in the following failure Error: transition failed. Test 'NNP (stack onexec - NNP)' was expected to 'pass'. Reason for failure 'FAIL - execv: Operation not permitted' with a log message of [ 1169.863302] audit: type=1400 audit(1565046042.144:280686): apparmor="DENIED" operation="exec" info="no new privs" error=-1 profile="/home/jj/apparmor.git/tests/regression/apparmor/transition" name="/home/jj/apparmor.git/tests/regression/apparmor/open" pid=1888 comm="transition" requested_mask="x" denied_mask="x" fsuid=0 ouid=1000 target="/home/jj/apparmor.git/tests/regression/apparmor/open" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839912] 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/1839912 Title: test_map in ubuntu_bpf failed with "Allowed update sockmap '0:3' not in ESTABLISHED" Status in linux package in Ubuntu: Confirmed Bug description: This is at lease a test case regression with the proposed kernel: selftests: test_maps Allowed update sockmap '0:3' not in ESTABLISHED not ok 1..3 selftests: test_maps [FAIL] But with older kernel: selftests: test_maps test_maps: OK ok 1..3 selftests: test_maps [PASS] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 13 03:42 seq crw-rw 1 root audio 116, 33 Aug 13 03:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Aug 13 03:52:52 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839912] [NEW] test_map in ubuntu_bpf failed with "Allowed update sockmap '0:3' not in ESTABLISHED"
Public bug reported: This is at lease a test case regression with the proposed kernel: selftests: test_maps Allowed update sockmap '0:3' not in ESTABLISHED not ok 1..3 selftests: test_maps [FAIL] But with older kernel: selftests: test_maps test_maps: OK ok 1..3 selftests: test_maps [PASS] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 13 03:42 seq crw-rw 1 root audio 116, 33 Aug 13 03:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Aug 13 03:52:52 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic package-from-proposed 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/1839912 Title: test_map in ubuntu_bpf failed with "Allowed update sockmap '0:3' not in ESTABLISHED" Status in linux package in Ubuntu: Confirmed Bug description: This is at lease a test case regression with the proposed kernel: selftests: test_maps Allowed update sockmap '0:3' not in ESTABLISHED not ok 1..3 selftests: test_maps [FAIL] But with older kernel: selftests: test_maps test_maps: OK ok 1..3 selftests: test_maps [PASS] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 13 03:42 seq crw-rw 1 root audio 116, 33 Aug 13 03:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Aug 13 03:52:52 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version:
[Kernel-packages] [Bug 1839037] Re: Stacked onexec transitions fail when under NO NEW PRIVS restrictions
** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839037 Title: Stacked onexec transitions fail when under NO NEW PRIVS restrictions Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: running the apparmor nnp regression tests results in the following failure Error: transition failed. Test 'NNP (stack onexec - NNP)' was expected to 'pass'. Reason for failure 'FAIL - execv: Operation not permitted' with a log message of [ 1169.863302] audit: type=1400 audit(1565046042.144:280686): apparmor="DENIED" operation="exec" info="no new privs" error=-1 profile="/home/jj/apparmor.git/tests/regression/apparmor/transition" name="/home/jj/apparmor.git/tests/regression/apparmor/open" pid=1888 comm="transition" requested_mask="x" denied_mask="x" fsuid=0 ouid=1000 target="/home/jj/apparmor.git/tests/regression/apparmor/open" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784665] Re: bcache: bch_allocator_thread(): hung task timeout
** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Xenial) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784665 Title: bcache: bch_allocator_thread(): hung task timeout Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: [Impact] bcache_allocator() can call the following: bch_allocator_thread() -> bch_prio_write() -> bch_bucket_alloc() -> wait on >set->bucket_wait But the wake up event on bucket_wait is supposed to come from bch_allocator_thread() itself causing a deadlock. [Test Case] This is a simple script that can easily trigger the deadlock condition: https://launchpadlibrarian.net/381282009/bcache-basic-repro.sh A better test case has been also provided in bug 1796292 (duplicate of this bug): https://bugs.launchpad.net/curtin/+bug/1796292/+attachment/5280353/+files/curtin-nvme.sh [Fix] Fix by making the call to bch_prio_write() non-blocking, so that bch_allocator_thread() never waits on itself. Moreover, make sure to wake up the garbage collector thread when bch_prio_write() is failing to allocate buckets to increase the chance of freeing up more buckets. In addition to that it would be safe to also import other upstream bcache fixes (all clean cherry picks): 7e865eba00a3df2dc8c4746173a8ca1c1c7f042e bcache: fix potential deadlock in cached_def_free() 80265d8dfd77792e133793cef44a21323aac2908 bcache: acquire bch_register_lock later in cached_dev_free() ce4c3e19e5201424357a0c82176633b32a98d2ec bcache: Replace bch_read_string_list() by __sysfs_match_string() ecb37ce9baac653cc09e2b631393dde3df82979f bcache: Move couple of functions to sysfs.c 04cbc21137bfa4d7b8771a5b14f3d6c9b2aee671 bcache: Move couple of string arrays to sysfs.c 5f2b18ec8e1643410a2369f06888951cdedea0bf bcache: Fix a compiler warning in bcache_device_init() 20d3a518713e394efa5a899c84574b4b79ec5098 bcache: Reduce the number of sparse complaints about lock imbalances 42361469ae84c851e40cb1f94c8c9a14cdd94039 bcache: Suppress more warnings about set-but-not-used variables f0d3814090ac77de94c42b7124c37ece23629197 bcache: Remove an unused variable 47344e330eabc1515cbe6061eb337100a3ab6d37 bcache: Fix kernel-doc warnings 9dfbdec7b7fea1ff1b7b5d5d12980dbc7dca46c7 bcache: Annotate switch fall-through 4a4e443835a43a79113cc237c472c0d268eb1e1c bcache: Add __printf annotation to __bch_check_keys() fd01991d5c20098c5c1ffc4dca6c821cc60a2f74 bcache: Fix indentation ca71df31661a0518ed58a1a59cf1993962153ebb bcache: fix using of loop variable in memory shrink f3641c3abd1da978ee969b0203b71b86ec1bfa93 bcache: fix error return value in memory shrink 688892b3bc05e25da94866e32210e5f503f16f69 bcache: fix incorrect sysfs output value of strip size 09a44ca2114737e0932257619c16a2b50c7807f1 bcache: use pr_info() to inform duplicated CACHE_SET_IO_DISABLE set c4dc2497d50d9c6fb16aa0d07b6a14f3b2adb1e0 bcache: fix high CPU occupancy during journal a728eacbbdd229d1d903e46261c57d5206f87a4a bcache: add journal statistic 616486ab52ab7f9739b066d958bdd20e65aefd74 bcache: fix writeback target calc on large devices 1f0ffa67349c56ea54c03ccfd1e073c990e7411e bcache: only set BCACHE_DEV_WB_RUNNING when cached device attached eb8cbb6df38f6e5124a3d5f1f8a3dbf519537c60 bcache: improve bcache_reboot() 9951379b0ca88c95876ad9778b9099e19a95d566 bcache: never writeback a discard operation [Regression Potential] The upstream fixes are all clean cherry picks from stable (most of them are small cleanups), so regression potential is minimal. The only special patch is "UBUNTU: SAUCE: bcache: fix deadlock in bcache_allocator()" that is addressing the main deadlock bug (that seems to be a mainline bug - not fixed yet). We should spend more time trying to reproduce this deadlock with a mainline kernel and post the patch to the LKML for review / feedback. However, considering that this patch seems to fix/prevent the specific deadlock problem reported in this bug (tested on the affected platform) it can be considered safe to apply it. [Original Bug Report] $ cat /proc/version_signature Ubuntu 4.15.0-29.31-generic 4.15.18 $ lsb_release -rd Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 $ apt-cache policy linux-image-`uname -r` linux-image-4.15.0-29-generic: Installed: 4.15.0-29.31 Candidate: 4.15.0-29.31 Version table: *** 4.15.0-29.31 500
[Kernel-packages] [Bug 1829725] Re: af_alg06 test from crypto test suite in LTP failed with kernel oops on B/C
** Changed in: linux (Ubuntu Cosmic) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829725 Title: af_alg06 test from crypto test suite in LTP failed with kernel oops on B/C Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Won't Fix Bug description: == Justification == From the commit message: Keys for "authenc" AEADs are formatted as an rtattr containing a 4-byte 'enckeylen', followed by an authentication key and an encryption key. crypto_authenc_extractkeys() parses the key to find the inner keys. However, it fails to consider the case where the rtattr's payload is longer than 4 bytes but not 4-byte aligned, and where the key ends before the next 4-byte aligned boundary. In this case, 'keylen -= RTA_ALIGN(rta->rta_len);' underflows to a value near UINT_MAX. This causes a buffer overread and crash during crypto_ahash_setkey(). This error can be easily reproduced with the af_alg06 test in LTP test suite. (Basically it's the reproducer in the commit message) == Fix == 8f9c4693 (crypto: authenc - fix parsing key with misaligned rta_len) This patch can be cherry-picked into B/C, and it's already in X/D/E. == Test == Test kernels could be found here: https://people.canonical.com/~phlin/kernel/lp-1829725-afalg06/ Both verified on a KVM node, this issue will no longer exist. == Regression potential == Low, this patch just improves the checking for rtattr payload size to make sure it's the expected size. Also It has been upstream since 2018 Dec. and applied in some of our kernels. No subsequent bug report was filed against it. == Original bug report == LTP: starting af_alg06 BUG: unable to handle kernel paging request at 9cbe IP: sha256_transform+0x28/0x1b20 PGD 4d341067 P4D 4d341067 PUD 4d345067 PMD 4d346067 PTE 0 Oops: [#1] SMP PTI Modules linked in: authenc algif_aead xfrm_user xfrm_algo sha3_generic algif_hash salsa20_generic algif_skcipher af_alg kvm_intel kvm irqbypass joydev input_leds serio_raw mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear cirrus ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops virtio_net psmouse virtio_blk drm i2c_piix4 pata_acpi floppy CPU: 0 PID: 24368 Comm: af_alg06 Not tainted 4.15.0-50-generic #54-Ubuntu Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 RIP: 0010:sha256_transform+0x28/0x1b20 RSP: 0018:b58e8344baa0 EFLAGS: 00010283 RAX: 0034 RBX: 9cbe000c RCX: RDX: RSI: 9cbdffcc RDI: b58e8344bca8 RBP: b58e8344bbd0 R08: 1b6c96f6 R09: b58e8344baa0 R10: 7a9a01a1 R11: 1ecb7428 R12: 9cc0f332c00c R13: b58e8344bca8 R14: 9cbff4d8d048 R15: 9cbff332c00c FS: 7f9f2a44d580() GS:9cbfffc0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 9cbe CR3: 7c1da000 CR4: 06f0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 Call Trace: sha256_generic_block_fn+0x36/0x50 crypto_sha256_finup+0xef/0x170 crypto_shash_finup+0x25/0x30 shash_digest_unaligned+0x47/0x60 crypto_shash_digest+0x2e/0x40 hmac_setkey+0x15a/0x210 ? tty_insert_flip_string_fixed_flag+0x86/0xe0 crypto_shash_setkey+0x35/0xc0 ? pty_write+0x71/0x90 shash_async_setkey+0x15/0x20 crypto_ahash_setkey+0x38/0xb0 crypto_authenc_setkey+0x68/0x100 [authenc] crypto_aead_setkey+0x35/0xc0 aead_setkey+0x15/0x20 [algif_aead] alg_setsockopt+0x112/0x140 [af_alg] SyS_setsockopt+0x86/0xf0 do_syscall_64+0x73/0x130 entry_SYSCALL_64_after_hwframe+0x3d/0xa2 RIP: 0033:0x7f9f29f61e6a RSP: 002b:7ffdd050ba38 EFLAGS: 0207 ORIG_RAX: 0036 RAX: ffda RBX: 7f9f2a44d500 RCX: 7f9f29f61e6a RDX: 0001 RSI: 0117 RDI: 0006 RBP: 0006 R08: 0009 R09: 7ffdd050b960 R10: 7ffdd050ba4f R11: 0207 R12: 0001 R13: R14: R15: 56456d64d908 Code: 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 81 ec 08 01 00 00 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 <8b> 14 06 0f ca 89 94 05 d0 fe ff ff 48 83 c0 04 48 83
[Kernel-packages] [Bug 1839818] Re: System won't enter suspend after idle over 20 minutes (TSC unstable)
** Changed in: oem-priority Assignee: (unassigned) => Cyrus Lien (cyruslien) ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Status: New => Confirmed ** Description changed: Summary: System won't enter suspend after idle over 20 minutes Steps to reproduce: 1. install manifest and boot into OS 2. idle system for 20 mins Expected result: System could enter suspend after idle over 20 minutes Actual result: System won't enter suspend after idle over 20 minutes Failure rate: 3/3 Dmesg: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123341] clocksource: timekeeping watchdog on CPU3: Marking clocksource 'tsc' as unstable because the skew is too large: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123365] clocksource: 'hpet' wd_now: e336cfbb wd_last: e2e9b5c5 mask: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123370] clocksource: 'tsc' cs_now: 6299ac5acc cs_last: 6250285866 mask: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123377] tsc: Marking TSC unstable due to clocksource watchdog Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123486] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123491] sched_clock: Marking unstable (158972862012, 149405080)<-(159105581047, 17903053) Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.122862] clocksource: Switched to clocksource hpet + + + Upstream bug: + https://bugzilla.kernel.org/show_bug.cgi?id=203183 ** Description changed: Summary: System won't enter suspend after idle over 20 minutes Steps to reproduce: 1. install manifest and boot into OS 2. idle system for 20 mins Expected result: System could enter suspend after idle over 20 minutes Actual result: System won't enter suspend after idle over 20 minutes Failure rate: 3/3 Dmesg: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123341] clocksource: timekeeping watchdog on CPU3: Marking clocksource 'tsc' as unstable because the skew is too large: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123365] clocksource: 'hpet' wd_now: e336cfbb wd_last: e2e9b5c5 mask: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123370] clocksource: 'tsc' cs_now: 6299ac5acc cs_last: 6250285866 mask: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123377] tsc: Marking TSC unstable due to clocksource watchdog Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123486] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123491] sched_clock: Marking unstable (158972862012, 149405080)<-(159105581047, 17903053) Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.122862] clocksource: Switched to clocksource hpet - Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=203183 + lkml patch: + https://lkml.org/lkml/2019/4/10/167 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1839818 Title: System won't enter suspend after idle over 20 minutes (TSC unstable) Status in OEM Priority Project: Confirmed Status in linux-oem package in Ubuntu: New Bug description: Summary: System won't enter suspend after idle over 20 minutes Steps to reproduce: 1. install manifest and boot into OS 2. idle system for 20 mins Expected result: System could enter suspend after idle over 20 minutes Actual result: System won't enter suspend after idle over 20 minutes Failure rate: 3/3 Dmesg: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123341] clocksource: timekeeping watchdog on CPU3: Marking clocksource 'tsc' as unstable because the skew is too large: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123365] clocksource: 'hpet' wd_now: e336cfbb wd_last: e2e9b5c5 mask: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123370] clocksource: 'tsc' cs_now: 6299ac5acc cs_last: 6250285866 mask: Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123377] tsc: Marking TSC unstable due to clocksource watchdog Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123486] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.123491] sched_clock: Marking unstable (158972862012, 149405080)<-(159105581047, 17903053) Jan 30 03:04:47 u-Precision-5540 kernel: [ 159.122862] clocksource: Switched to clocksource hpet Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=203183 lkml patch: https://lkml.org/lkml/2019/4/10/167 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1839818/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1839856] Re: Screen resolution on external monitor won't go above 2560 x 1080
** Also 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/1839856 Title: Screen resolution on external monitor won't go above 2560 x 1080 Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: New Bug description: I have an external monitor capable of 3440 x 1440. I am using a Thinkpad T480s. Up until about 2 weeks ago, I could set the resolution of the monitor to 3440 x 1440 just fine. Now when I try, the screen goes black and I have to revert to a lower resolution. The highest it will go now is 2560 x 1080. Lower resolutions work fine as well. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 12 08:56:25 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 4.18.0-25-generic, x86_64: installed acpi-call, 1.1.0, 5.0.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:2258] InstallationDate: Installed on 2019-02-19 (173 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20L7S01200 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=UUID=471b6634-e334-44c7-b898-080ab93327e0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET53W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L7S01200 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET53W(1.30):bd02/19/2019:svnLENOVO:pn20L7S01200:pvrThinkPadT480s:rvnLENOVO:rn20L7S01200:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L7S01200 dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839856] 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/1839856 Title: Screen resolution on external monitor won't go above 2560 x 1080 Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: New Bug description: I have an external monitor capable of 3440 x 1440. I am using a Thinkpad T480s. Up until about 2 weeks ago, I could set the resolution of the monitor to 3440 x 1440 just fine. Now when I try, the screen goes black and I have to revert to a lower resolution. The highest it will go now is 2560 x 1080. Lower resolutions work fine as well. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 12 08:56:25 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 4.18.0-25-generic, x86_64: installed acpi-call, 1.1.0, 5.0.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:2258] InstallationDate: Installed on 2019-02-19 (173 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20L7S01200 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=UUID=471b6634-e334-44c7-b898-080ab93327e0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET53W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L7S01200 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN22ET53W(1.30):bd02/19/2019:svnLENOVO:pn20L7S01200:pvrThinkPadT480s:rvnLENOVO:rn20L7S01200:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L7S01200 dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
Hello Rafael, Testing results to share, Bit 5 Arch Capability is verified implemented. See below for details, please feel free to let me know if you need more information. Thanks. Regards, Ai B. +++ Tested on Host:- Ubuntu 18.04.1 Kernel 4.15.0-55-generic #virsh version Compiled against library: libvirt 4.0.0 Using library: libvirt 4.0.0 Using API: QEMU 4.0.0 Running hypervisor: QEMU 2.11.1 #lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 80 On-line CPU(s) list: 0-79 Thread(s) per core: 2 Core(s) per socket: 20 Socket(s): 2 NUMA node(s):2 Vendor ID: GenuineIntel CPU family: 6 Model: 85 Model name: Intel(R) Xeon(R) Gold 6230 CPU @ 2.10GHz Stepping:6 CPU MHz: 800.144 CPU max MHz: 2100. CPU min MHz: 800. BogoMIPS:4200.00 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache:1024K L3 cache:28160K NUMA node0 CPU(s): 0-19,40-59 NUMA node1 CPU(s): 20-39,60-79 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cdp_l3 invpcid_single ssbd mba ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm mpx rdt_a avx512f avx512dq rdseed adx smap clflushopt clwb intel_pt avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm arat pln pts pku ospke avx512_vnni md_clear flush_l1d arch_capabilities #rdmsr 0x10a 2b qemu: Installed: (none) Candidate: 1:2.11+dfsg-1ubuntu7.17~ppa1 Version table: 1:2.11+dfsg-1ubuntu7.17~ppa1 500 500 http://ppa.launchpad.net/rafaeldtinoco/lp1828495/ubuntu bionic/main amd64 Packages 1:2.11+dfsg-1ubuntu7.15 500 500 http://cn.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 1:2.11+dfsg-1ubuntu7.14 500 500 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages 1:2.11+dfsg-1ubuntu7 500 500 http://cn.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages +++ Guest OS CentOS 7.6 kernel 3.10.0-957.12.2.el7.x86_64 #lscpu Architecture: x86_64 CPU op-mode(s):32-bit, 64-bit Byte Order:Little Endian CPU(s):8 On-line CPU(s) list: 0-7 Thread(s) per core:1 Core(s) per socket:1 Socket(s): 8 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family:6 Model: 85 Model name:Intel(R) Xeon(R) Gold 6230 CPU @ 2.10GHz Stepping: 6 CPU MHz: 2095.074 BogoMIPS: 4190.14 Virtualization:VT-x Hypervisor vendor: KVM Virtualization type: full L1d cache: 32K L1i cache: 32K L2 cache: 4096K L3 cache: 16384K NUMA node0 CPU(s): 0-7 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon rep_good nopl xtopology eagerfpu pni pclmulqdq vmx ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch ssbd ibrs ibpb ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx avx512f avx512dq rdseed adx smap clflushopt clwb avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 arat pku ospke avx512_vnni md_clear spec_ctrl arch_capabilities #rdmsr 0x10a 2b #./spectre-meltdown-checker.sh Spectre and Meltdown mitigation detection tool v0.42 Checking for vulnerabilities on current system Kernel is Linux 3.10.0-957.12.2.el7.x86_64 #1 SMP Tue May 14 21:24:32 UTC 2019 x86_64 CPU is Intel(R) Xeon(R) Gold 6230 CPU @ 2.10GHz Hardware check * Hardware support (CPU microcode) for mitigation techniques * Indirect Branch Restricted Speculation (IBRS) * SPEC_CTRL MSR is available: YES * CPU indicates IBRS capability: YES (SPEC_CTRL feature bit) * Indirect Branch Prediction Barrier (IBPB) * PRED_CMD MSR is available: YES * CPU indicates IBPB capability: YES (SPEC_CTRL feature bit) * Single Thread Indirect Branch Predictors (STIBP) * SPEC_CTRL MSR is available: YES * CPU
[Kernel-packages] [Bug 1839891] 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 1839891 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/1839891 Title: suspend by power button doesn't work when screen is locked Status in linux package in Ubuntu: Incomplete Bug description: I have In Privacy Settings, Screen Lock : On In Power Settings, When the Power Button is pressed : Suspend However suspending only works when the desktop session is unlocked. When I leave the computer unattended so it locks the screen after 10 minutes, as soon as the screen is locked I can hit the Power Button as many times as I want and the computer won't suspend. This is on uptodate Ubuntu 18.04.2 LTS, using the flashback gnome session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839891/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839891] [NEW] suspend by power button doesn't work when screen is locked
Public bug reported: I have In Privacy Settings, Screen Lock : On In Power Settings, When the Power Button is pressed : Suspend However suspending only works when the desktop session is unlocked. When I leave the computer unattended so it locks the screen after 10 minutes, as soon as the screen is locked I can hit the Power Button as many times as I want and the computer won't suspend. This is on uptodate Ubuntu 18.04.2 LTS, using the flashback gnome session. ** 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/1839891 Title: suspend by power button doesn't work when screen is locked Status in linux package in Ubuntu: New Bug description: I have In Privacy Settings, Screen Lock : On In Power Settings, When the Power Button is pressed : Suspend However suspending only works when the desktop session is unlocked. When I leave the computer unattended so it locks the screen after 10 minutes, as soon as the screen is locked I can hit the Power Button as many times as I want and the computer won't suspend. This is on uptodate Ubuntu 18.04.2 LTS, using the flashback gnome session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839891/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807378] Re: zfs/spl build in conjunction with the kernel from DKMS source
This broke my ability to build the Xenial HWE kernel offline using the default kernel configuration (trying to build binary-lowlatency specifically). Building a package shouldn't require me to have an internet connection. I am also concerned about complying with the CDDL license since the ZFS source code is no longer part of the linux-source package. Is something being done to properly point to the source code of the modules? -- 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/1807378 Title: zfs/spl build in conjunction with the kernel from DKMS source Status in linux package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux-gcp source package in Bionic: Fix Committed Bug description: We currently carry a complete copy of the zfs/spl source in the kernel package. It would be much simpler to maintain if we used the published sources for the dkms package to build these at kernel build time. We are still able to sign those modules into the kernel modules key. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807378/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838090] Re: Ubuntu 16.04: read access incorrectly implies 'm' rule
*** This bug is a duplicate of bug 1658219 ***
https://bugs.launchpad.net/bugs/1658219
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1838090
Title:
Ubuntu 16.04: read access incorrectly implies 'm' rule
Status in AppArmor:
Invalid
Status in linux package in Ubuntu:
New
Status in linux source package in Xenial:
Confirmed
Bug description:
I've already been corresponding with jjohansen privately via email on
this, filing a bug here based on our conversation. To summarize the
email thread:
I was poking around some stuff today, and noticed that it seems like
the 'm' rule doesn't actually do anything. I've tested this on two
separate machines, both running Ubuntu 16.04:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.6 LTS
Release: 16.04
Codename: xenial
PoC:
$ sudo dmesg -c
$ cp /bin/ls /tmp
$ echo "/tmp/ls {
> /** r,
> }" > /tmp/tmp.ls
$ sudo apparmor_parser -C -r /tmp/tmp.ls
$ /tmp/ls
.
$ sudo dmesg
[1746349.392925] audit: type=1400 audit(1562018298.880:81): apparmor="STATUS"
operation="profile_replace" profile="unconfined" name="/tmp/ls" pid=28205
comm="apparmor_parser"
There are no "ALLOWED" messages stating that we're missing the
necessary "mr," rule for mmap'ing shared objects such as libc.
As a follow-up, even with an empty profile running in complain mode, I
do not see any mention of needing the 'm' rule in the requested /
denied mask, it just asks for read access:
[1748198.369441] audit: type=1400 audit(1562020148.006:82): apparmor="STATUS"
operation="profile_replace" profile="unconfined" name="/tmp/ls" pid=28677
comm="apparmor_parser"
[1748203.023838] audit: type=1400 audit(1562020152.662:83):
apparmor="ALLOWED" operation="open" profile="/tmp/ls" name="/etc/ld.so.cache"
pid=28678 comm="ls" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[1748203.023877] audit: type=1400 audit(1562020152.662:84):
apparmor="ALLOWED" operation="open" profile="/tmp/ls"
name="/lib/x86_64-linux-gnu/libselinux.so.1" pid=28678 comm="ls"
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[1748203.023945] audit: type=1400 audit(1562020152.662:85):
apparmor="ALLOWED" operation="open" profile="/tmp/ls"
name="/lib/x86_64-linux-gnu/libc-2.23.so" pid=28678 comm="ls"
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[1748203.023998] audit: type=1400 audit(1562020152.662:86):
apparmor="ALLOWED" operation="open" profile="/tmp/ls"
name="/lib/x86_64-linux-gnu/libpcre.so.3.13.2" pid=28678 comm="ls"
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[1748203.024039] audit: type=1400 audit(1562020152.662:87):
apparmor="ALLOWED" operation="open" profile="/tmp/ls"
name="/lib/x86_64-linux-gnu/libdl-2.23.so" pid=28678 comm="ls"
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[1748203.024076] audit: type=1400 audit(1562020152.662:88):
apparmor="ALLOWED" operation="open" profile="/tmp/ls"
name="/lib/x86_64-linux-gnu/libpthread-2.23.so" pid=28678 comm="ls"
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
I tested this on Ubuntu 12.04, 18.04, and 19.04, and the expected
behavior is indeed there. Seems like a regression in specifically
16.04.
Response from jjohansen:
"This bug was fixed in Ubuntu in the Ubuntu zesty kernel (4.10) but
the fix was for a different issue and never cherry-picked back to
Xenial. We are going to need a bug report to get this fixed in the
Xenial kernel. So please do file a bug report. I can then attach the
patch and send it to the kt for inclusion in the next SRU."
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1838090/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839110] Re: xenial/linux-kvm: 4.4.0-1054.61 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-xenial ** Tags removed: 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 -- kernel-stable-master-bug: 1839119 packages: main: linux-kvm meta: linux-meta-kvm - phase: Ready for Testing - phase-changed: Thursday, 08. August 2019 11:38 UTC + phase: Ready for Release + phase-changed: Monday, 12. August 2019 21:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-updates: Pending -- ready to copy variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1839110 Title: xenial/linux-kvm: 4.4.0-1054.61 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1839119 packages: main: linux-kvm meta: linux-meta-kvm phase: Ready for Release phase-changed: Monday, 12. August 2019 21:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839110] Re: xenial/linux-kvm: 4.4.0-1054.61 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1839110 Title: xenial/linux-kvm: 4.4.0-1054.61 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1839119 packages: main: linux-kvm meta: linux-meta-kvm phase: Ready for Release phase-changed: Monday, 12. August 2019 21:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838590] Re: Update thermald to 1.9 release
This bug was fixed in the package dptfxtract - 1.4.2-0ubuntu1 --- dptfxtract (1.4.2-0ubuntu1) eoan; urgency=medium * New upstream release. (LP: #1838590) -- Anthony Wong Fri, 09 Aug 2019 07:41:05 + ** Changed in: dptfxtract (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1838590 Title: Update thermald to 1.9 release Status in dptfxtract package in Ubuntu: Fix Released Status in thermald package in Ubuntu: Fix Released Bug description: The thermald 1.9 release was just tagged, and has potential to help quite a bit with platform performance on some newer platforms when run with kernel 5.3. It would be nice to update eoan to this new release. > - The major change in this version is the active power limits adjustment. This will be useful to improve performance on some newer platform. But this will will lead to increase in CPU and other temperatures. Hence this is important to run dptfxtract version 1.4.1 tool to get performance sensitive thermal limits (https://github.com/intel/dptfxtract/commits/v1.4.1). If the default configuration picked up by thermald is not optimal, user can select other less aggressive configuration. Refer to the README here https://github.com/intel/dptfxtract/blob/master/README.txt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dptfxtract/+bug/1838590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839887] [NEW] Disco update: upstream stable patchset 2019-08-12
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
upstream stable patchset 2019-08-12
Ported from the following upstream stable releases:
v4.19.48, v5.1.7,
v4.19.49, v5.1.8,
v4.19.50, v5.1.9,
v4.19.51, v5.1.10,
v4.19.52, v5.1.11,
from git://git.kernel.org/
UBUNTU: [Config] updateconfigs for CONFIG_ARM64_ERRATUM_1463225
selftests/tls: test for lowat overshoot with multiple records
selftests/tls: add test for sleeping even though there is data
UBUNTU: upstream stable to v4.19.48, v5.0.21, v5.1.7
sparc64: Fix regression in non-hypervisor TLB flush xcall
include/linux/bitops.h: sanitize rotate primitives
xhci: update bounce buffer with correct sg num
xhci: Use %zu for printing size_t type
xhci: Convert xhci_handshake() to use readl_poll_timeout_atomic()
usb: xhci: avoid null pointer deref when bos field is NULL
usbip: usbip_host: fix BUG: sleeping function called from invalid context
usbip: usbip_host: fix stub_dev lock context imbalance regression
USB: Fix slab-out-of-bounds write in usb_get_bos_descriptor
USB: sisusbvga: fix oops in error path of sisusb_probe
USB: Add LPM quirk for Surface Dock GigE adapter
USB: rio500: refuse more than one device at a time
USB: rio500: fix memory leak in close after disconnect
media: usb: siano: Fix general protection fault in smsusb
media: usb: siano: Fix false-positive "uninitialized variable" warning
media: smsusb: better handle optional alignment
brcmfmac: fix NULL pointer derefence during USB disconnect
scsi: zfcp: fix missing zfcp_port reference put on -EBUSY from port_remove
scsi: zfcp: fix to prevent port_remove with pure auto scan LUNs (only sdevs)
tracing: Avoid memory leak in predicate_parse()
Btrfs: fix wrong ctime and mtime of a directory after log replay
Btrfs: fix race updating log root item during fsync
Btrfs: fix fsync not persisting changed attributes of a directory
Btrfs: incremental send, fix file corruption when no-holes feature is enabled
iio: dac: ds4422/ds4424 fix chip verification
iio: adc: ti-ads8688: fix timestamp is not updated in buffer
s390/crypto: fix possible sleep during spinlock aquired
KVM: PPC: Book3S HV: XIVE: Do not clear IRQ data of passthrough interrupts
powerpc/perf: Fix MMCRA corruption by bhrb_filter
ALSA: line6: Assure canceling delayed work at disconnection
ALSA: hda/realtek - Set default power save node to 0
KVM: s390: Do not report unusabled IDs via KVM_CAP_MAX_VCPU_ID
drm/nouveau/i2c: Disable i2c bus access after ->fini()
i2c: mlxcpld: Fix wrong initialization order in probe
i2c: synquacer: fix synquacer_i2c_doxfer() return value
tty: serial: msm_serial: Fix XON/XOFF
tty: max310x: Fix external crystal register setup
memcg: make it work on sparse non-0-node systems
kernel/signal.c: trace_signal_deliver when signal_group_exit
arm64: Fix the arm64_personality() syscall wrapper redirection
docs: Fix conf.py for Sphinx 2.0
doc: Cope with the deprecation of AutoReporter
doc: Cope with Sphinx logging deprecations
ima: show rules with IMA_INMASK correctly
evm: check hash algorithm passed to init_desc()
vt/fbcon: deinitialize resources in visual_init() after failed memory allocation
serial: sh-sci: disable DMA for uart_console
staging: vc04_services: prevent integer overflow in create_pagelist()
staging: wlan-ng: fix adapter initialization failure
cifs: fix memory leak of pneg_inbuf on -EOPNOTSUPP ioctl case
CIFS: cifs_read_allocate_pages: don't iterate through whole page array on ENOMEM
Revert "lockd: Show pid of lockd for remote locks"
gcc-plugins: Fix build failures under Darwin host
drm/tegra: gem: Fix CPU-cache maintenance for BO's allocated using get_pages()
drm/vmwgfx: Don't send drm sysfs hotplug events on initial master set
drm/sun4i: Fix sun8i HDMI PHY clock initialization
drm/sun4i: Fix sun8i HDMI PHY configuration for > 148.5 MHz
drm/rockchip: shutdown drm subsystem on shutdown
drm/lease: Make sure implicit planes are leased
Revert "x86/build: Move _etext to actual end of .text"
x86/kprobes: Set instruction page as executable
scsi: lpfc: Fix backport of faf5a744f4f8 ("scsi: lpfc: avoid uninitialized
variable warning")
KVM: PPC: Book3S HV: Fix lockdep warning when entering guest on POWER9
KVM: PPC: Book3S HV: Restore SPRG3 in kvmhv_p9_guest_entry()
powerpc/kexec: Fix loading of kernel + initramfs with kexec_file_load()
kasan: initialize tag to 0xff in __kasan_kmalloc
signal/arm64: Use force_sig not force_sig_fault for SIGKILL
x86/ima: Check EFI_RUNTIME_SERVICES
[Kernel-packages] [Bug 1839258] Re: bionic/linux-raspi2: 4.15.0-1043.46 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-bionic ** Tags removed: 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 1839257 (pi-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-raspi2 meta: linux-meta-raspi2 - phase: Holding before Release - phase-changed: Monday, 12. August 2019 10:56 UTC + phase: Ready for Release + phase-changed: Monday, 12. August 2019 21:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- master bug not ready for release + promote-to-updates: Pending -- ready to copy trackers: bionic/linux-raspi2/pi-kernel: bug 1839257 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1839258 Title: bionic/linux-raspi2: 4.15.0-1043.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839257 (pi-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Ready for Release phase-changed: Monday, 12. August 2019 21:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy trackers: bionic/linux-raspi2/pi-kernel: bug 1839257 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839261] Re: bionic/linux-oem: 4.15.0-1050.57 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1839261 Title: bionic/linux-oem: 4.15.0-1050.57 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Ready for Testing phase-changed: Monday, 12. August 2019 09:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839261/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839260] Re: bionic/linux-snapdragon: 4.15.0-1060.66 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-bionic ** Tags removed: 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 1839259 (dragonboard-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-snapdragon meta: linux-meta-snapdragon - phase: Holding before Release - phase-changed: Monday, 12. August 2019 12:27 UTC + phase: Ready for Release + phase-changed: Monday, 12. August 2019 21:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- master bug not ready for release + promote-to-updates: Pending -- ready to copy trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1839259 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1839260 Title: bionic/linux-snapdragon: 4.15.0-1060.66 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839259 (dragonboard-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Ready for Release phase-changed: Monday, 12. August 2019 21:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1839259 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839260/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839270] Re: xenial/linux-gcp: 4.15.0-1040.42~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-xenial ** Tags removed: 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 1839268 (gcp-kernel), bug 1839269 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839272 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Holding before Release - phase-changed: Monday, 12. August 2019 16:01 UTC + phase: Ready for Release + phase-changed: Monday, 12. August 2019 21:17 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- master bug not ready for release + promote-to-updates: Pending -- ready to copy trackers: xenial/linux-gcp/gcp-kernel: bug 1839268 xenial/linux-gcp/gke-kernel: bug 1839269 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1839270 Title: xenial/linux-gcp: 4.15.0-1040.42~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839268 (gcp-kernel), bug 1839269 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839272 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Ready for Release phase-changed: Monday, 12. August 2019 21:17 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy trackers: xenial/linux-gcp/gcp-kernel: bug 1839268 xenial/linux-gcp/gke-kernel: bug 1839269 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839261] Re: bionic/linux-oem: 4.15.0-1050.57 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Ready for Testing phase-changed: Monday, 12. August 2019 09:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress - regression-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1839261 Title: bionic/linux-oem: 4.15.0-1050.57 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Ready for Testing phase-changed: Monday, 12. August 2019 09:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839261/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839266] Re: bionic/linux-aws: 4.15.0-1045.47 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-bionic ** Tags removed: 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 1839264 (xenial/linux-aws-hwe) derivatives: bug 1839263 (aws-kernel) -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-aws meta: linux-meta-aws - phase: Holding before Release - phase-changed: Monday, 12. August 2019 11:58 UTC + phase: Ready for Release + phase-changed: Monday, 12. August 2019 21:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- master bug not ready for release + promote-to-updates: Pending -- ready to copy trackers: bionic/linux-aws/aws-kernel: bug 1839263 xenial/linux-aws-hwe: bug 1839264 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1839266 Title: bionic/linux-aws: 4.15.0-1045.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839264 (xenial/linux-aws-hwe) derivatives: bug 1839263 (aws-kernel) -- swm properties -- kernel-stable-master-bug: 1839293 packages: main: linux-aws meta: linux-meta-aws phase: Ready for Release phase-changed: Monday, 12. August 2019 21:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy trackers: bionic/linux-aws/aws-kernel: bug 1839263 xenial/linux-aws-hwe: bug 1839264 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839276] Re: bionic/linux-kvm: 4.15.0-1042.42 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-bionic ** Tags removed: 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: 1839293 packages: main: linux-kvm meta: linux-meta-kvm - phase: Ready for Testing - phase-changed: Friday, 09. August 2019 20:55 UTC + phase: Ready for Release + phase-changed: Monday, 12. August 2019 21:14 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-updates: Pending -- ready to copy variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1839276 Title: bionic/linux-kvm: 4.15.0-1042.42 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-kvm meta: linux-meta-kvm phase: Ready for Release phase-changed: Monday, 12. August 2019 21:14 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839276/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839272] Re: bionic/linux-gcp: 4.15.0-1040.42 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-bionic ** Tags removed: 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 1839270 (xenial/linux-gcp) derivatives: bug 1839267 (gcp-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Holding before Release - phase-changed: Monday, 12. August 2019 12:10 UTC + phase: Ready for Release + phase-changed: Monday, 12. August 2019 21:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- master bug not ready for release + promote-to-updates: Pending -- ready to copy trackers: bionic/linux-gcp/gcp-kernel: bug 1839267 xenial/linux-gcp: bug 1839270 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1839272 Title: bionic/linux-gcp: 4.15.0-1040.42 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839270 (xenial/linux-gcp) derivatives: bug 1839267 (gcp-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Ready for Release phase-changed: Monday, 12. August 2019 21:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy trackers: bionic/linux-gcp/gcp-kernel: bug 1839267 xenial/linux-gcp: bug 1839270 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839272/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839276] Re: bionic/linux-kvm: 4.15.0-1042.42 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1839276 Title: bionic/linux-kvm: 4.15.0-1042.42 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-kvm meta: linux-meta-kvm phase: Ready for Release phase-changed: Monday, 12. August 2019 21:14 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839276/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839278] Re: xenial/linux-oracle: 4.15.0-1021.23~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-xenial ** Tags removed: 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: 1839280 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Holding before Release - phase-changed: Monday, 12. August 2019 16:42 UTC + phase: Ready for Release + phase-changed: Monday, 12. August 2019 21:17 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- master bug not ready for release + promote-to-updates: Pending -- ready to copy variant: debs -- 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/1839278 Title: xenial/linux-oracle: 4.15.0-1021.23~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839280 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Ready for Release phase-changed: Monday, 12. August 2019 21:17 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839278/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839280] Re: bionic/linux-oracle: 4.15.0-1021.23 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-bionic ** Tags removed: 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 1839278 (xenial/linux-oracle) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Holding before Release - phase-changed: Monday, 12. August 2019 14:05 UTC + phase: Ready for Release + phase-changed: Monday, 12. August 2019 21:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- master bug not ready for release + promote-to-updates: Pending -- ready to copy trackers: xenial/linux-oracle: bug 1839278 variant: debs -- 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/1839280 Title: bionic/linux-oracle: 4.15.0-1021.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839278 (xenial/linux-oracle) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Ready for Release phase-changed: Monday, 12. August 2019 21:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy trackers: xenial/linux-oracle: bug 1839278 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839280/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839293] Re: bionic/linux: 4.15.0-58.64 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-bionic ** Tags removed: 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 1839287 (xenial/linux-azure), bug 1839291 (xenial/linux-hwe) derivatives: bug 1839255 (pc-kernel), bug 1839256 (pc-lowlatency-kernel), bug 1839258 (linux-raspi2), bug 1839260 (linux-snapdragon), bug 1839261 (linux-oem), bug 1839266 (linux-aws), bug 1839272 (linux-gcp), bug 1839275 (linux-gke-4.15), bug 1839276 (linux-kvm), bug 1839277 (linux-ibm-gt), bug 1839280 (linux-oracle), bug 1839281 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Ready for Testing - phase-changed: Friday, 09. August 2019 21:00 UTC + phase: Ready for Release + phase-changed: Monday, 12. August 2019 21:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-updates: Pending -- ready to copy trackers: bionic/linux-aws: bug 1839266 bionic/linux-fips: bug 1839281 bionic/linux-gcp: bug 1839272 bionic/linux-gke-4.15: bug 1839275 bionic/linux-ibm-gt: bug 1839277 bionic/linux-kvm: bug 1839276 bionic/linux-oem: bug 1839261 bionic/linux-oracle: bug 1839280 bionic/linux-raspi2: bug 1839258 bionic/linux-snapdragon: bug 1839260 bionic/linux/pc-kernel: bug 1839255 bionic/linux/pc-lowlatency-kernel: bug 1839256 xenial/linux-azure: bug 1839287 xenial/linux-hwe: bug 1839291 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839293 Title: bionic/linux: 4.15.0-58.64 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839287 (xenial/linux-azure), bug 1839291 (xenial/linux-hwe) derivatives: bug 1839255 (pc-kernel), bug 1839256 (pc-lowlatency-kernel), bug 1839258 (linux-raspi2), bug 1839260 (linux-snapdragon), bug 1839261 (linux-oem), bug 1839266 (linux-aws), bug 1839272 (linux-gcp), bug 1839275 (linux-gke-4.15), bug 1839276 (linux-kvm), bug 1839277 (linux-ibm-gt), bug 1839280 (linux-oracle), bug 1839281 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Release phase-changed: Monday, 12. August 2019 21:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy trackers: bionic/linux-aws: bug 1839266 bionic/linux-fips: bug 1839281 bionic/linux-gcp: bug 1839272 bionic/linux-gke-4.15: bug 1839275 bionic/linux-ibm-gt: bug 1839277 bionic/linux-kvm: bug 1839276 bionic/linux-oem: bug 1839261 bionic/linux-oracle: bug 1839280 bionic/linux-raspi2: bug 1839258 bionic/linux-snapdragon: bug 1839260 bionic/linux/pc-kernel: bug 1839255 bionic/linux/pc-lowlatency-kernel: bug 1839256 xenial/linux-azure: bug 1839287 xenial/linux-hwe: bug 1839291 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839293/+subscriptions
[Kernel-packages] [Bug 1839293] Re: bionic/linux: 4.15.0-58.64 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839293 Title: bionic/linux: 4.15.0-58.64 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839287 (xenial/linux-azure), bug 1839291 (xenial/linux-hwe) derivatives: bug 1839255 (pc-kernel), bug 1839256 (pc-lowlatency-kernel), bug 1839258 (linux-raspi2), bug 1839260 (linux-snapdragon), bug 1839261 (linux-oem), bug 1839266 (linux-aws), bug 1839272 (linux-gcp), bug 1839275 (linux-gke-4.15), bug 1839276 (linux-kvm), bug 1839277 (linux-ibm-gt), bug 1839280 (linux-oracle), bug 1839281 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Release phase-changed: Monday, 12. August 2019 21:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy trackers: bionic/linux-aws: bug 1839266 bionic/linux-fips: bug 1839281 bionic/linux-gcp: bug 1839272 bionic/linux-gke-4.15: bug 1839275 bionic/linux-ibm-gt: bug 1839277 bionic/linux-kvm: bug 1839276 bionic/linux-oem: bug 1839261 bionic/linux-oracle: bug 1839280 bionic/linux-raspi2: bug 1839258 bionic/linux-snapdragon: bug 1839260 bionic/linux/pc-kernel: bug 1839255 bionic/linux/pc-lowlatency-kernel: bug 1839256 xenial/linux-azure: bug 1839287 xenial/linux-hwe: bug 1839291 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839293/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817225] Re: 18.04.2 breaks xrdp
Confirmed this works in the Hyper-V 18.04 desktop image. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done 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/1817225 Title: 18.04.2 breaks xrdp Status in linux package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xrdp-hwe-18.04 package in Ubuntu: Fix Committed Bug description: I have observed the following on two different computers: On both computers, running Ubuntu 18.04, I am able to install xrdp and log in remotely using a third computer via Reminna or Windows RDP client without any problems. If I do a fresh install of Ubuntu 18.04.2 and install xrdp OR if I update my working 18.04 installation by running sudo apt-get install --install-recommends linux-generic-hwe-18.04 xserver-xorg-hwe-18.04 then xrdp stops working. That is, when I login using an RDP client, I am presented with the xrdp login screen, but when I select xorg and try to login with my username and password, I see a blue screen for about a minute and then connecting to sesman ip 127.0.0.1 sesman connect ok sending login info to session manager, please wait... login successful for display 10 started connecting connection problem, giving up some problem The only difference between the working configuration and the broken one is Ubuntu 18.04 vs 18.04.2 (OR HWE installed using the above command). Out of the two computers I tried one has nvidia graphics and one has intel on-board graphics. For the nvidia computer, I tried both nvidia and nouveau drivers to no avail. Not sure if this is a problem with xrdp or xorg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rushik 4016 F pulseaudio /dev/snd/controlC1: rushik 4016 F pulseaudio /dev/snd/controlC0: rushik 4016 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=007a0916-b97e-4f06-b096-9694f8b3085c InstallationDate: Installed on 2019-01-11 (41 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=UUID=5c3c3434-9b1d-40dd-8388-8005cf88989e 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 Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0802 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z390-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0802:bd01/04/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839096] Re: disco/linux-kvm: 5.0.0-1013.14 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-disco ** Tags removed: 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 -- kernel-stable-master-bug: 1839106 packages: main: linux-kvm meta: linux-meta-kvm - phase: Ready for Testing - phase-changed: Thursday, 08. August 2019 15:35 UTC + phase: Ready for Release + phase-changed: Monday, 12. August 2019 19:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-updates: Pending -- ready to copy variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1839096 Title: disco/linux-kvm: 5.0.0-1013.14 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1839106 packages: main: linux-kvm meta: linux-meta-kvm phase: Ready for Release phase-changed: Monday, 12. August 2019 19:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839096/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839096] Re: disco/linux-kvm: 5.0.0-1013.14 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1839096 Title: disco/linux-kvm: 5.0.0-1013.14 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1839106 packages: main: linux-kvm meta: linux-meta-kvm phase: Ready for Release phase-changed: Monday, 12. August 2019 19:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839096/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839115] Re: trusty/linux-aws: 4.4.0-1050.54 -proposed tracker
** Tags added: regression-testing-passed -- 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/1839115 Title: trusty/linux-aws: 4.4.0-1050.54 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1839119 packages: main: linux-aws meta: linux-meta-aws phase: Ready for Release phase-changed: Monday, 12. August 2019 18:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839115/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839115] Re: trusty/linux-aws: 4.4.0-1050.54 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-trusty ** Tags removed: 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 -- kernel-stable-master-bug: 1839119 packages: main: linux-aws meta: linux-meta-aws - phase: Ready for Testing - phase-changed: Tuesday, 06. August 2019 19:11 UTC + phase: Ready for Release + phase-changed: Monday, 12. August 2019 18:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-updates: Pending -- ready to copy variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1839115 Title: trusty/linux-aws: 4.4.0-1050.54 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1839119 packages: main: linux-aws meta: linux-meta-aws phase: Ready for Release phase-changed: Monday, 12. August 2019 18:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839115/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839395] Re: Regressions in CMA allocation rework
** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839395 Title: Regressions in CMA allocation rework Status in linux package in Ubuntu: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: Introduced by the fixes for bug 1823753. [Impact] Crashes (as observed on a nigrogen8m device), and a potential memory leak. [Test Case] Regression tested only. [Fix] f46cc0152501e dma-contiguous: page-align the size in dma_free_contiguous() c6622a425acd1 dma-contiguous: do not overwrite align in dma_alloc_contiguous() [Regression Risk] Bugs in CMA code could lead to device driver errors/crashes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824228] Re: ept test fails in kvm_unit_tests
** Tags added: sru-20190722 -- 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/1824228 Title: ept test fails in kvm_unit_tests Status in ubuntu-kernel-tests: New Status in linux-azure package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-azure source package in Disco: New Status in linux-kvm source package in Disco: New Status in linux-oracle source package in Disco: New Bug description: Reproducible: Yes, Series: cosmic Kernel: "linux-azure 4.18.0-1015.15" Steps: 1.) apt-get install -y build-essential cpu-checker qemu-kvm git gcc-multilib 2.) git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 3.) cd kvm-unit-tests; ./configure; make 4.) sudo TESTNAME=ept TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,host-phys-bits,+vmx -m 2560 -append "ept_access*" timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/vmx.flat -smp 1 -cpu host,host-phys-bits,+vmx -m 2560 -append ept_access* # -initrd /tmp/tmp.RcwfbGP5Ou enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: ept_access_test_not_present Test suite: ept_access_test_read_only Test suite: ept_access_test_write_only Test suite: ept_access_test_read_write Test suite: ept_access_test_execute_only Test suite: ept_access_test_read_execute Test suite: ept_access_test_write_execute Test suite: ept_access_test_read_write_execute Test suite: ept_access_test_reserved_bits Test suite: ept_access_test_ignored_bits Test suite: ept_access_test_paddr_not_present_ad_disabled Test suite: ept_access_test_paddr_not_present_ad_enabled Host skipping test: EPT AD bits not supported. Test suite: ept_access_test_paddr_read_only_ad_disabled EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x008b - ''''''''''''''1000'1011 - 139 RHS: 0x008a - ''''''''''''''1000'1010 - 138 STACK: 40f328 40f8fb 40fb0b 40ff49 401577 4039d0 400312 EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x008b - ''''''''''''''1000'1011 - 139 RHS: 0x008a - ''''''''''''''1000'1010 - 138 STACK: 40f328 40f8fb 40fb0b 40ff62 401577 4039d0 400312 EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x008b - ''''''''''''''1000'1011 - 139 RHS: 0x008a - ''''''''''''''1000'1010 - 138 STACK: 40f328 40f8fb 40fb0b 40ff7b 401577 4039d0 400312 EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x008b - ''''''''''''''1000'1011 - 139 RHS: 0x008a - ''''''''''''''1000'1010 - 138 STACK: 40f328 40f8fb 40fb0b 40ffa8 401577 4039d0 400312 Test suite: ept_access_test_paddr_read_only_ad_enabled Host skipping test: EPT AD bits not supported. Test suite: ept_access_test_paddr_read_write Test suite: ept_access_test_paddr_read_write_execute Test suite: ept_access_test_paddr_read_execute_ad_disabled EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x00ab - ''''''''''''''1010'1011 - 171 RHS: 0x00aa - ''''''''''''''1010'1010 - 170 STACK: 40f328 40f8fb 40fb0b 40fde3 401577 4039d0 400312 EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x00ab - ''''''''''''''1010'1011 - 171 RHS: 0x00aa - ''''''''''''''1010'1010 - 170 STACK: 40f328 40f8fb 40fb0b 40fdfc 401577 4039d0 400312 EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x00ab -
[Kernel-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
Just noticed this with my new Bluetooth headset. With the same headset, the microphone and audio quality is a lot better when paired with an Android device than when paired with my desktop (4.15.0-55-generic Ubuntu 18.04.03 LTS). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Triaged Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839521] Re: Xenial: ZFS deadlock in shrinker path with xattrs
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839521 Title: Xenial: ZFS deadlock in shrinker path with xattrs Status in linux package in Ubuntu: Invalid Status in zfs-linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Status in zfs-linux source package in Xenial: In Progress Status in linux source package in Bionic: Invalid Status in zfs-linux source package in Bionic: Invalid Status in linux source package in Disco: Invalid Status in zfs-linux source package in Disco: Invalid Status in linux source package in Eoan: Invalid Status in zfs-linux source package in Eoan: Invalid Bug description: [Impact] * Xenial's ZFS can deadlock in the memory shrinker path after removing files with extended attributes (xattr). * Extended attributes are enabled by default, but are _not_ used by default, which reduces the likelyhood. * It's very difficult/rare to reproduce this problem, due to file/xattr/remove/shrinker/lru order/timing circumstances required. (weeks for a reporter user) but a synthetic test-case has been found for tests. [Test Case] * A synthetic reproducer is available for this LP, with a few steps to touch/setfattr/rm/drop_caches plus a kernel module to massage the disposal list. (comment #8) * In the original ZFS module: the xattr dir inode is not purged immediately on file removal, but possibly purged _two_ shrinker invocations later. This allows for other thread started before file remove to call zfs_zget() on the xattr child inode and iput() it, so it makes to the same disposal list as the xattr dir inode. (comment #3) * In the modified ZFS module: the xattr dir inode is purged immediately on file removal not possibly later on shrinker invocation, so the problem window above doesn't exist anymore. (comment #12) [Regression Potential] * Low. The patches are confined to extended attributes in ZFS, specifically node removal/purge, and another change how an xattr child inode tracks its xattr dir (parent) inode, so that it can be purged immediately on removal. * The ZFS test-suite has been run on original/modified zfs-dkms package/kernel modules, with no regressions. (comment #11) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839521/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812318] Re: ftrace test in ubuntu_kernel_selftests failed on KVM kernels
** Tags added: sru-20190722 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1812318 Title: ftrace test in ubuntu_kernel_selftests failed on KVM kernels Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Bionic: Confirmed Status in linux-kvm source package in Cosmic: Confirmed Bug description: This test failed with: Error: No ftrace directory found In the script: DEBUGFS_DIR=`grep debugfs /proc/mounts | cut -f2 -d' ' | head -1` if [ -z "$DEBUGFS_DIR" ]; then TRACING_DIR=`grep tracefs /proc/mounts | cut -f2 -d' ' | head -1` else TRACING_DIR=$DEBUGFS_DIR/tracing fi The script exit here: # Verify parameters if [ -z "$TRACING_DIR" -o ! -d "$TRACING_DIR" ]; then errexit "No ftrace directory found" fi DEBUGFS_DIR=/sys/kernel/debug TRACING_DIR=/sys/kernel/debug/tracing ls: cannot access '/sys/kernel/debug/tracing': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28 ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18 Uname: Linux 4.15.0-1028-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Jan 18 03:04:17 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812318/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812622] Re: fib related test in net from ubuntu_kernel_selftests failed
** Tags added: sru-20190722 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1812622 Title: fib related test in net from ubuntu_kernel_selftests failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux source package in Cosmic: Incomplete Status in linux-kvm source package in Cosmic: New Status in linux source package in Disco: New Status in linux-aws source package in Disco: New Status in linux-kvm source package in Disco: New Bug description: These tests: * fib_tests.sh * fib-onlink-tests.sh * fib_rule_tests.sh All failed on Cosmic KVM kernel with RTNETLINK answers: Operation not supported: selftests: net: fib_tests.sh Single path route test RTNETLINK answers: Operation not supported not ok 1..11 selftests: net: fib_tests.sh [FAIL] selftests: net: fib-onlink-tests.sh Configuring interfaces RTNETLINK answers: Operation not supported not ok 1..12 selftests: net: fib-onlink-tests.sh [FAIL] selftests: net: fib_rule_tests.sh RTNETLINK answers: Operation not supported not ok 1..16 selftests: net: fib_rule_tests.sh [FAIL] (works on generic Cosmic kernel) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6 ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17 Uname: Linux 4.18.0-1006-kvm x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 Date: Mon Jan 21 08:00:22 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833396] Re: ubuntu_bpf test failed on KVM kernels
** Tags added: disco sru-20190722 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1833396 Title: ubuntu_bpf test failed on KVM kernels Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Bionic: New Status in linux-kvm source package in Disco: New Bug description: This should not considered as a regression, we just switching from the "cloud" test list to the "generic" list. Summary: 775 PASSED, 0 SKIPPED, 123 FAILED #165/u PTR_TO_STACK store/load - out of bounds low FAIL Unexpected error message! EXP: invalid stack off=-79992 size=8 RES: 0: (bf) r1 = r10 1: (07) r1 += -8 invalid stack off=-8 size=1 R1 stack pointer arithmetic goes out of range, prohibited for !root 0: (bf) r1 = r10 1: (07) r1 += -8 invalid stack off=-8 size=1 R1 stack pointer arithmetic goes out of range, prohibited for !root #173/p unpriv: check that printk is disallowed FAIL Failed to load prog 'Invalid argument'! 0: (7a) *(u64 *)(r10 -8) = 0 1: (bf) r1 = r10 2: (07) r1 += -8 3: (b7) r2 = 8 4: (bf) r3 = r1 5: (85) call bpf_trace_printk#6 unknown func bpf_trace_printk#6 #185/p unpriv: spill/fill of different pointers ldx FAIL Unexpected error message! EXP: same insn cannot be used with different pointers RES: #193/u unpriv: adding of fp FAIL Failed to load prog 'Permission denied'! 0: (b7) r0 = 0 1: (b7) r1 = 0 2: (0f) r1 += r10 invalid stack off=0 size=1 R1 stack pointer arithmetic goes out of range, prohibited for !root #287/p constant register |= constant should keep constant type FAIL Failed to load prog 'Invalid argument'! #288/p constant register |= constant should not bypass stack boundary checks FAIL Unexpected error message! EXP: invalid stack type R1 off=-48 access_size=58 RES: #289/p constant register |= constant register should keep constant type FAIL Failed to load prog 'Invalid argument'! #290/p constant register |= constant register should not bypass stack boundary checks FAIL Unexpected error message! EXP: invalid stack type R1 off=-48 access_size=58 RES: #306/p helper access to map: full range FAIL Failed to load prog 'Invalid argument'! #307/p helper access to map: partial range FAIL Failed to load prog 'Invalid argument'! #308/p helper access to map: empty range FAIL Unexpected error message! EXP: invalid access to map value, value_size=48 off=0 size=0 RES: #309/p helper access to map: out-of-bound range FAIL Unexpected error message! EXP: invalid access to map value, value_size=48 off=0 size=56 RES: #310/p helper access to map: negative range FAIL Unexpected error message! EXP: R2 min value is negative RES: #311/p helper access to adjusted map (via const imm): full range FAIL Failed to load prog 'Invalid argument'! #312/p helper access to adjusted map (via const imm): partial range FAIL Failed to load prog 'Invalid argument'! #313/p helper access to adjusted map (via const imm): empty range FAIL Unexpected error message! EXP: invalid access to map value, value_size=48 off=4 size=0 RES: #314/p helper access to adjusted map (via const imm): out-of-bound range FAIL Unexpected error message! EXP: invalid access to map value, value_size=48 off=4 size=52 RES: #315/p helper access to adjusted map (via const imm): negative range (> adjustment) FAIL Unexpected error message! EXP: R2 min value is negative RES: #316/p helper access to adjusted map (via const imm): negative range (< adjustment) FAIL Unexpected error message! EXP: R2 min value is negative RES: #317/p helper access to adjusted map (via const reg): full range FAIL Failed to load prog 'Invalid argument'! #318/p helper access to adjusted map (via const reg): partial range FAIL Failed to load prog 'Invalid argument'! #319/p helper access to adjusted map (via const reg): empty range FAIL Unexpected error message! EXP: R1 min value is outside of the array range RES: #320/p helper access to adjusted map (via const reg): out-of-bound range FAIL Unexpected error message! EXP: invalid access to map value, value_size=48 off=4 size=52 RES: #321/p helper access to adjusted map (via const reg): negative range (> adjustment) FAIL Unexpected error message! EXP: R2 min value is negative RES: #322/p helper access to adjusted map (via const reg): negative range (< adjustment) FAIL Unexpected error message! EXP: R2 min value is negative RES:
[Kernel-packages] [Bug 1775165] Re: fanotify07/fanotify08 in LTP syscall test generates kernel trace with T/X/X-AWS kernel
** Tags added: linux-oracle oracle sru-20190722 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775165 Title: fanotify07/fanotify08 in LTP syscall test generates kernel trace with T/X/X-AWS kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Won't Fix Status in linux source package in Xenial: Won't Fix Bug description: BugLink: https://bugs.launchpad.net/bugs/1775165 [Impact] When userspace tasks which are processing fanotify permission events act incorrectly, the fsnotify_mark_srcu SRCU is held indefinitely which causes the whole notification subsystem to hang. This has been seen in production, and it can also be seen when running the Linux Test Project testsuite, specifically fanotify07. [Fix] Instead of holding the SRCU lock while waiting for userspace to respond, which may never happen, or not in the order we are expecting, we drop the fsnotify_mark_srcu SRCU lock before waiting for userspace response, and then reacquire the lock again when userspace responds. The fixes are from a series of upstream commits: 05f0e38724e8449184acd8fbf0473ee5a07adc6c (cherry-pick) 9385a84d7e1f658bb2d96ab798393e4b16268aaa (backport) abc77577a669f424c5d0c185b9994f2621c52aa4 (backport) The following are upstream commits necessary for the fixes to function: 35e481761cdc688dbee0ef552a13f49af8eba6cc (backport) 0918f1c309b86301605650c836ddd2021d311ae2 (cherry-pick) [Testcase] You can reproduce the problem pretty quickly with the Linux Test Project: Steps (with root): 1. sudo apt-get install git xfsprogs -y 2. git clone --depth=1 https://github.com/linux-test-project/ltp.git 3. cd ltp 4. make autotools 5. ./configure 6. make; make install 7. cd /opt/ltp 8. echo -e "fanotify07 fanotify07 \nfanotify08 fanotify08" > /tmp/jobs 9. ./runltp -f /tmp/jobs On a stock Xenial kernel, the system will hang, and the testcase will look like: <<>> tag=fanotify07 stime=1554326200 cmdline="fanotify07 " contacts="" analysis=exit <<>> tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Cannot kill test processes! Congratulation, likely test hit a kernel bug. Exitting uncleanly... <<>> initiation_status="ok" duration=350 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> Looking at dmesg, we see the following call stack [ 790.772792] LTP: starting fanotify07 (fanotify07 ) [ 960.140455] INFO: task fsnotify_mark:36 blocked for more than 120 seconds. [ 960.140867] Not tainted 4.4.0-142-generic #168-Ubuntu [ 960.141185] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 960.141498] fsnotify_mark D 8800b6703c98 036 2 0x [ 960.141516] 8800b6703c98 88013a558a00 8800b7797000 8800b66f8000 [ 960.141524] 8800b6704000 7fff 8800b6703de0 8800b66f8000 [ 960.141528] 8800b6703cb0 8185cb45 8800b6703de8 [ 960.141532] Call Trace: [ 960.141580] [] schedule+0x35/0x80 [ 960.141588] [] schedule_timeout+0x1b4/0x270 [ 960.141617] [] ? mod_timer+0x10c/0x240 [ 960.141621] [] ? __schedule+0x30d/0x810 [ 960.141625] [] wait_for_completion+0xb2/0x190 [ 960.141636] [] ? wake_up_q+0x70/0x70 [ 960.141641] [] __synchronize_srcu+0x100/0x1a0 [ 960.141645] [] ? trace_raw_output_rcu_utilization+0x60/0x60 [ 960.141664] [] ? fsnotify_put_mark+0x40/0x40 [ 960.141669] [] synchronize_srcu+0x24/0x30 [ 960.141672] [] fsnotify_mark_destroy+0x84/0x130 [ 960.141680] [] ? wake_atomic_t_function+0x60/0x60 [ 960.141691] [] kthread+0xe7/0x100 [ 960.141694] [] ? __schedule+0x301/0x810 [ 960.141699] [] ? kthread_create_on_node+0x1e0/0x1e0 [ 960.141703] [] ret_from_fork+0x55/0x80 [ 960.141706] [] ? kthread_create_on_node+0x1e0/0x1e0 The vanilla 4.4 kernel also shows the same call stack. On a patched kernel, the test will pass successfully, and there will be no messages in dmesg. [Regression Potential] This makes modifications to how locking is performed in fsnotify / fanotify and there may be some cause for regression. Running all fanotify Linux Test Project tests shows that there are no extra failures caused by the patches, and instead fewer failures are seen due to the bugfix. Running the entire
[Kernel-packages] [Bug 1839278] Re: xenial/linux-oracle: 4.15.0-1021.23~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839280 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Ready for Testing - phase-changed: Friday, 09. August 2019 20:56 UTC + phase: Holding before Release + phase-changed: Monday, 12. August 2019 16:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-updates: Holding -- master bug not ready for release variant: debs -- 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/1839278 Title: xenial/linux-oracle: 4.15.0-1021.23~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839280 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Holding before Release phase-changed: Monday, 12. August 2019 16:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- master bug not ready for release variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839278/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839278] Re: xenial/linux-oracle: 4.15.0-1021.23~16.04.1 -proposed tracker
Known Bugs: https://bugs.launchpad.net/ubuntu-kernel- tests/+bugs?field.searchtext==-importance=Search%3Alist=NEW%3Alist=CONFIRMED%3Alist=TRIAGED%3Alist=INPROGRESS%3Alist=FIXCOMMITTED%3Alist=INCOMPLETE_WITH_RESPONSE%3Alist=INCOMPLETE_WITHOUT_RESPONSE_option=any=_reporter=_commenter==_subscriber==sru-20190722+oracle+_combinator=ALL_cve.used=_dupes.used=_dupes=on_me.used=_patch.used=_branches.used=_branches=on_no_branches.used=_no_branches=on_blueprints.used=_blueprints=on_no_blueprints.used=_no_blueprints=on ** Tags added: regression-testing-passed -- 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/1839278 Title: xenial/linux-oracle: 4.15.0-1021.23~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839280 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Holding before Release phase-changed: Monday, 12. August 2019 16:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- master bug not ready for release variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839278/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
@bellengc, you'd need to open up your Terminal to make a more permanent edit to your grub bootfile. Once you have the terminal open, type in: cd /etc/default sudo vi grub This will open up a text editor in your terminal. You're going to be making edits to your bootfile so it's a good idea to copy/paste a back up of this file in another text file. Near the top of the file you should see a line that looks like: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" Go to this line, and after whatever commands are in there, add "dis_ucode_ldr" to the end. If you haven't used vi, you'll need to first hit "i" to go into edit mode, then start moving around and typing. When you're done, you should have a line that looks like: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash dis_ucode_ldr" To save your changes and exit the editor, type ":wq". Now run the command "sudo update-grub". Now, next time you boot up, you should be good to go. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829620 Title: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: Description: - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of booting, after grub) - does not even show the enter cryptsetup passphrase - affected kernels: # apt list --installed |grep linux-signed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 [installed] linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 amd64 [installed] linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 5.0.0.15.71 amd64 [installed] - the setup is not new, has been working perfectly before (about 7 days since my last restart?) System: - HW: ASUS Zenbook 14 UX433FN - Ubuntu 18.04, runing latest HWE, fully updated - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), Suspected/possible cause?: - recent intel-microcode package update - recent kernel package updates Steps taken: - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding nosplash, noplymouth) - completely removed nvidia drivers (apt purge *nvidia*) - completely purged and reinstalled grub (grup-pc) - completely purged and reinstalled all kernels (headers, modules, image, ..) - toggle BIOS "fastboot" (now using OFF) - toggle UEFI SecureBoot (now using ON) - remove plymouth (apt remove *plymouth* , but the workaround is working with plymouth installed) Workaround: - so far, I'm only able to boot with non-Ubuntu kernel! (linux-image-liquorix-amd64) - which needs "splash" option ON - reinstall cryptsetup & update-grub (as suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 ) I am not sure how to get you more debug info, as this setup has been working before, and it's a very eary boot-process bug, so I can't even access dmesg etc. EDIT: Hypothesis: Only affects ASUS with i7-8565U Whiskey Lake Intel CPU Upstream Bug Report: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 WORKAROUND 1: disable intel microcode updates during boot From this bug: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920 1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub 2/ update-grub WORKAROUND 2: downgrade (and hold) intel-microcode to older version from bionic/main apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1 WORKAROUND 3: upgrade BIOS Asus has released updated BIOSes, which probably include the newest microcode. After upgrading workarounds 1,2 are not needed. Please NOTE, unlike workarounds 1,2, BIOS upgrade is permanent and cannot be (easily) reverted. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2337 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge (not installed) Tags: bionic wayland-session Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on
[Kernel-packages] [Bug 1839857] [NEW] apic tests fail to run
Public bug reported:
Originally Affected: linux-oracle
Version: 4.15.0-1021.23~16.04.1
Series: Xenial
Apic tests appear to fail to run , with a series of test failures
itself.
08/09 20:46:23 DEBUG| utils:0153| [stdout] starting broadcast (x2apic)
08/09 20:46:23 DEBUG| utils:0153| [stdout] PASS: APIC physical broadcast
address
08/09 20:46:23 DEBUG| utils:0153| [stdout] PASS: APIC physical broadcast
shorthand
08/09 20:46:23 DEBUG| utils:0153| [stdout] FAIL: PV IPIs testing
08/09 20:46:23 DEBUG| utils:0153| [stdout] PASS: nmi-after-sti
08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: multiple nmi
08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: APIC LVT timer one shot
08/09 20:46:28 DEBUG| utils:0153| [stdout] starting apic change mode
08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMICT value reset
08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMCCT should have a
non-zero value
08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMCCT should have reached 0
08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMCCT should have a
non-zero value
08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMCCT should not be reset
to TMICT value
08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMCCT should be reset to
the initial-count
08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMCCT should not be reset
to init
08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMCCT should have reach
zero
08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMCCT should stay at zero
08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: tsc deadline timer
08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: tsc deadline timer clearing
08/09 20:46:28 DEBUG| utils:0153| [stdout] SUMMARY: 51 tests, 5 unexpected
failures
08/09 20:46:28 DEBUG| utils:0153| [stdout] FAIL apic (51 tests, 5
unexpected failures)
08/09 20:46:28 ERROR| test:0414| Exception escaping from test:
Traceback (most recent call last):
File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 823, in
_call_test_function
return func(*args, **dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 212, in
_call_run_once
self.run_once(*args, **dargs)
File
"/home/ubuntu/autotest/client/tests/ubuntu_kvm_unit_tests/ubuntu_kvm_unit_tests.py",
line 88, in run_once
raise error.TestError("Test failed for {}".format(test_name))
TestError: Test failed for apic
** Affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
** Affects: linux-oracle (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-oracle (Ubuntu Xenial)
Importance: Undecided
Status: New
** Tags: apic linux-oracle oracle sru-20190722
** Attachment added: "ubuntu_kvm_unit_tests.apic.DEBUG"
https://bugs.launchpad.net/bugs/1839857/+attachment/5282224/+files/ubuntu_kvm_unit_tests.apic.DEBUG
** Description changed:
Originally Affected: linux-oracle
Version: 4.15.0-1021.23~16.04.1
Series: Xenial
Apic tests appear to fail to run , with a series of test failures
itself.
+
+ 08/09 20:46:23 DEBUG| utils:0153| [stdout] starting broadcast (x2apic)
+ 08/09 20:46:23 DEBUG| utils:0153| [stdout] PASS: APIC physical broadcast
address
+ 08/09 20:46:23 DEBUG| utils:0153| [stdout] PASS: APIC physical broadcast
shorthand
+ 08/09 20:46:23 DEBUG| utils:0153| [stdout] FAIL: PV IPIs testing
+ 08/09 20:46:23 DEBUG| utils:0153| [stdout] PASS: nmi-after-sti
+ 08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: multiple nmi
+ 08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: APIC LVT timer one shot
+ 08/09 20:46:28 DEBUG| utils:0153| [stdout] starting apic change mode
+ 08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMICT value reset
+ 08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMCCT should have a
non-zero value
+ 08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMCCT should have
reached 0
+ 08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMCCT should have a
non-zero value
+ 08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMCCT should not be
reset to TMICT value
+ 08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMCCT should be reset to
the initial-count
+ 08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMCCT should not be
reset to init
+ 08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMCCT should have reach
zero
+ 08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMCCT should stay at zero
+ 08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: tsc deadline timer
+ 08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: tsc deadline timer
clearing
+ 08/09 20:46:28 DEBUG| utils:0153| [stdout] SUMMARY: 51 tests, 5
unexpected
[Kernel-packages] [Bug 1839758] Re: [amdgpu] System locks up with VMC page fault on Ryzen 2400G and HWE kernel 5.0.
Tried your suggestion, but it didn't help so far. Latest kernel still can't have gnome started, while 5.0 HWE kernel produced result similar to previous ones. I have verified that environment variable was set successfully: $ printenv | grep -i amd_debug AMD_DEBUG=nodcc syslog: steam.desktop[3741]: STEAM_RUNTIME_HEAVY: ./steam-runtime-heavy kernel: gmc_v9_0_process_interrupt: 49 callbacks suppressed kernel: amdgpu :08:00.0: [gfxhub] VMC page fault (src_id:0 ring:158 vmid:2 pasid:32784, for process vulkandriverque pid 4088 thread vulkandriverque pid 4088) kernel: amdgpu :08:00.0: in page starting at address 0x from 27 kernel: amdgpu :08:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0020153D drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=5205, emitted seq=5207 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process vulkandriverque pid 4088 thread vulkandriverque pid 4088 kernel: [drm] GPU recovery disabled. ** Attachment added: "syslog-5.0-hwe-amd_debug.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839758/+attachment/5282225/+files/syslog-5.0-hwe-amd_debug.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/1839758 Title: [amdgpu] System locks up with VMC page fault on Ryzen 2400G and HWE kernel 5.0. Status in linux package in Ubuntu: Confirmed Bug description: Since kernel 5.0 rolled out through HWE last week my system is consistently locking up upon launch of Steam or 3D applications in WINE. Typical log: https://paste.ubuntu.com/p/WhPYXdkZVw/ Worked around by using pre-update 4.18 kernel. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 11 15:47:27 2019 DistUpgraded: 2018-03-26 22:50:10,989 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.32, 4.18.0-25-generic, x86_64: installed virtualbox, 5.2.32, 5.0.0-23-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last week or two GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c6) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000] InstallationDate: Installed on 2018-03-26 (502 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming K7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to bionic on 2018-03-26 (502 days ago) dmi.bios.date: 01/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F25 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming K7 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se3 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF25:bd01/16/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-GamingK7:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-GamingK7:rvrse3:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming K7 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839758/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
> I am super new to linux. I have read through the thread, and I am pretty sure > that my ASUS ZenBook is having the same problem. I re-installed Ubuntu and > have just not upgraded, but I not happy with that workaround. So, will this > be something that will be fixed with a future update? Or, will I need to do > this from now on? I have no understanding of how to use the "dis_ucode_ldr". Thank you @bmsnider You can see here https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1#issuecomment-495113009 how to add the "dis_ucode_ldr" parameter. You basically need to edit the /etc/default/grub file (using sudo privileges) and append it to the value of GRUB_CMDLINE_LINUX_DEFAULT -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829620 Title: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: Description: - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of booting, after grub) - does not even show the enter cryptsetup passphrase - affected kernels: # apt list --installed |grep linux-signed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 [installed] linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 amd64 [installed] linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 5.0.0.15.71 amd64 [installed] - the setup is not new, has been working perfectly before (about 7 days since my last restart?) System: - HW: ASUS Zenbook 14 UX433FN - Ubuntu 18.04, runing latest HWE, fully updated - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), Suspected/possible cause?: - recent intel-microcode package update - recent kernel package updates Steps taken: - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding nosplash, noplymouth) - completely removed nvidia drivers (apt purge *nvidia*) - completely purged and reinstalled grub (grup-pc) - completely purged and reinstalled all kernels (headers, modules, image, ..) - toggle BIOS "fastboot" (now using OFF) - toggle UEFI SecureBoot (now using ON) - remove plymouth (apt remove *plymouth* , but the workaround is working with plymouth installed) Workaround: - so far, I'm only able to boot with non-Ubuntu kernel! (linux-image-liquorix-amd64) - which needs "splash" option ON - reinstall cryptsetup & update-grub (as suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 ) I am not sure how to get you more debug info, as this setup has been working before, and it's a very eary boot-process bug, so I can't even access dmesg etc. EDIT: Hypothesis: Only affects ASUS with i7-8565U Whiskey Lake Intel CPU Upstream Bug Report: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 WORKAROUND 1: disable intel microcode updates during boot From this bug: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920 1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub 2/ update-grub WORKAROUND 2: downgrade (and hold) intel-microcode to older version from bionic/main apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1 WORKAROUND 3: upgrade BIOS Asus has released updated BIOSes, which probably include the newest microcode. After upgrading workarounds 1,2 are not needed. Please NOTE, unlike workarounds 1,2, BIOS upgrade is permanent and cannot be (easily) reverted. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2337 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge (not installed) Tags: bionic wayland-session Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2339 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge PackageArchitecture: amd64 ProcVersionSignature: Ubuntu
[Kernel-packages] [Bug 1839270] Re: xenial/linux-gcp: 4.15.0-1040.42~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839268 (gcp-kernel), bug 1839269 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839272 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Ready for Testing - phase-changed: Friday, 09. August 2019 20:51 UTC + phase: Holding before Release + phase-changed: Monday, 12. August 2019 16:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-updates: Holding -- master bug not ready for release trackers: xenial/linux-gcp/gcp-kernel: bug 1839268 xenial/linux-gcp/gke-kernel: bug 1839269 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1839270 Title: xenial/linux-gcp: 4.15.0-1040.42~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839268 (gcp-kernel), bug 1839269 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839272 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Release phase-changed: Monday, 12. August 2019 16:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- master bug not ready for release trackers: xenial/linux-gcp/gcp-kernel: bug 1839268 xenial/linux-gcp/gke-kernel: bug 1839269 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839270] Re: xenial/linux-gcp: 4.15.0-1040.42~16.04.1 -proposed tracker
Known Bugs: https://bugs.launchpad.net/ubuntu-kernel- tests/+bugs?field.searchtext==-importance%3Alist=NEW%3Alist=CONFIRMED%3Alist=TRIAGED%3Alist=INPROGRESS%3Alist=FIXCOMMITTED%3Alist=INCOMPLETE_WITH_RESPONSE%3Alist=INCOMPLETE_WITHOUT_RESPONSE_option=any=_reporter=_commenter==_subscriber==sru-20190722+gcp_combinator=ALL_cve.used=_dupes.used=_dupes=on_me.used=_patch.used=_branches.used=_branches=on_no_branches.used=_no_branches=on_blueprints.used=_blueprints=on_no_blueprints.used=_no_blueprints=on=Search -- 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/1839270 Title: xenial/linux-gcp: 4.15.0-1040.42~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839268 (gcp-kernel), bug 1839269 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839272 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Release phase-changed: Monday, 12. August 2019 16:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- master bug not ready for release trackers: xenial/linux-gcp/gcp-kernel: bug 1839268 xenial/linux-gcp/gke-kernel: bug 1839269 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811057] Re: global.get_metadata in seccomp_bpf test from ubuntu_kernel_selftests fails [X & B]
** Tags added: gcp ** Tags added: sru ** Tags removed: sru ** Tags added: sru-20190722 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811057 Title: global.get_metadata in seccomp_bpf test from ubuntu_kernel_selftests fails [X & B] Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Bug description: selftests: seccomp_bpf [==] Running 64 tests from 1 test cases. [ RUN ] global.mode_strict_support [ OK ] global.mode_strict_support [ RUN ] global.mode_strict_cannot_call_prctl [ OK ] global.mode_strict_cannot_call_prctl [ RUN ] global.no_new_privs_support [ OK ] global.no_new_privs_support [ RUN ] global.mode_filter_support [ OK ] global.mode_filter_support [ RUN ] global.mode_filter_without_nnp [ OK ] global.mode_filter_without_nnp [ RUN ] global.filter_size_limits [ OK ] global.filter_size_limits [ RUN ] global.filter_chain_limits [ OK ] global.filter_chain_limits [ RUN ] global.mode_filter_cannot_move_to_strict [ OK ] global.mode_filter_cannot_move_to_strict [ RUN ] global.mode_filter_get_seccomp [ OK ] global.mode_filter_get_seccomp [ RUN ] global.ALLOW_all [ OK ] global.ALLOW_all [ RUN ] global.empty_prog [ OK ] global.empty_prog [ RUN ] global.log_all [ OK ] global.log_all [ RUN ] global.unknown_ret_is_kill_inside [ OK ] global.unknown_ret_is_kill_inside [ RUN ] global.unknown_ret_is_kill_above_allow [ OK ] global.unknown_ret_is_kill_above_allow [ RUN ] global.KILL_all [ OK ] global.KILL_all [ RUN ] global.KILL_one [ OK ] global.KILL_one [ RUN ] global.KILL_one_arg_one [ OK ] global.KILL_one_arg_one [ RUN ] global.KILL_one_arg_six [ OK ] global.KILL_one_arg_six [ RUN ] global.KILL_thread [==] Running 64 tests from 1 test cases. [ RUN ] global.mode_strict_support [ OK ] global.mode_strict_support [ RUN ] global.mode_strict_cannot_call_prctl [ OK ] global.mode_strict_cannot_call_prctl [ RUN ] global.no_new_privs_support [ OK ] global.no_new_privs_support [ RUN ] global.mode_filter_support [ OK ] global.mode_filter_support [ RUN ] global.mode_filter_without_nnp [ OK ] global.mode_filter_without_nnp [ RUN ] global.filter_size_limits [ OK ] global.filter_size_limits [ RUN ] global.filter_chain_limits [ OK ] global.filter_chain_limits [ RUN ] global.mode_filter_cannot_move_to_strict [ OK ] global.mode_filter_cannot_move_to_strict [ RUN ] global.mode_filter_get_seccomp [ OK ] global.mode_filter_get_seccomp [ RUN ] global.ALLOW_all [ OK ] global.ALLOW_all [ RUN ] global.empty_prog [ OK ] global.empty_prog [ RUN ] global.log_all [ OK ] global.log_all [ RUN ] global.unknown_ret_is_kill_inside [ OK ] global.unknown_ret_is_kill_inside [ RUN ] global.unknown_ret_is_kill_above_allow [ OK ] global.unknown_ret_is_kill_above_allow [ RUN ] global.KILL_all [ OK ] global.KILL_all [ RUN ] global.KILL_one [ OK ] global.KILL_one [ RUN ] global.KILL_one_arg_one [ OK ] global.KILL_one_arg_one [ RUN ] global.KILL_one_arg_six [ OK ] global.KILL_one_arg_six [ RUN ] global.KILL_thread [ OK ] global.KILL_thread [ RUN ] global.KILL_process [ OK ] global.KILL_process [ RUN ] global.arg_out_of_range [ OK ] global.arg_out_of_range [ RUN ] global.ERRNO_valid [ OK ] global.ERRNO_valid [ RUN ] global.ERRNO_zero [ OK ] global.ERRNO_zero [ RUN ] global.ERRNO_capped [ OK ] global.ERRNO_capped [ RUN ] global.ERRNO_order [ OK ] global.ERRNO_order [ RUN ] TRAP.dfl [ OK ] TRAP.dfl [ RUN ] TRAP.ign [ OK ] TRAP.ign [ RUN ] TRAP.handler [ OK ] TRAP.handler [ RUN ] precedence.allow_ok [ OK ] precedence.allow_ok [ RUN ] precedence.kill_is_highest [ OK ] precedence.kill_is_highest [ RUN ] precedence.kill_is_highest_in_any_order [ OK ] precedence.kill_is_highest_in_any_order [ RUN ] precedence.trap_is_second [ OK ] precedence.trap_is_second [ RUN ]
[Kernel-packages] [Bug 1838477] Re: [regression] r8169 network device unable to detect link on x86 arch
@Kai-Heng Feng, I've tested v5.3-rc2 and v5.3-rc4 today. v5.3-rc4 seems to be working fine and v5.3-rc2 has same issues as latest kernels from repo. Actual behavior of problematic kernels -- interface is actually working on cold boot, but turns to be unable to detect a link after a several reboots (in 5-10 minutes from initial boot). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838477 Title: [regression] r8169 network device unable to detect link on x86 arch Status in linux package in Ubuntu: Confirmed Bug description: Since changes were introduced with 4.15.0-24 (LP #1752772), the r8169 driver became unusable on x86 machines (16.04 and 18.04 distributions). The device is always in link down state. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-23-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.7 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: MICRO-STAR INTERNATIONAL CO., LTD U90/U100 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=48a31456-880b-4326-960e-2c7e4b8f476d ro splash quiet vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.9 Tags: bionic Uname: Linux 4.15.0-23-generic i686 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 12/01/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: U90/U100 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: Ver.001 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.version: Ver.001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd12/01/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnU90/U100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU90/U100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct10:cvrVer.001: dmi.product.family: To be filled by O.E.M. dmi.product.name: U90/U100 dmi.product.version: Ver.001 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-23-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.7 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: MICRO-STAR INTERNATIONAL CO., LTD U90/U100 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=48a31456-880b-4326-960e-2c7e4b8f476d ro splash quiet vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.9 Tags: bionic Uname: Linux 4.15.0-23-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: U90/U100 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
[Kernel-packages] [Bug 1839270] Re: xenial/linux-gcp: 4.15.0-1040.42~16.04.1 -proposed tracker
** Tags added: regression-testing-passed -- 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/1839270 Title: xenial/linux-gcp: 4.15.0-1040.42~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839268 (gcp-kernel), bug 1839269 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839272 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Release phase-changed: Monday, 12. August 2019 16:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- master bug not ready for release trackers: xenial/linux-gcp/gcp-kernel: bug 1839268 xenial/linux-gcp/gke-kernel: bug 1839269 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1653597] Re: libhugetlbfs test suite failed with brk_near_huge test
** Tags added: sru-20190722 -- 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/1653597 Title: libhugetlbfs test suite failed with brk_near_huge test Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Confirmed Bug description: Kernel: 4.8.0-34.36 The libhugetlbfs failed with the brk_near_huge test on x86_64(gce) 12/24 04:59:42 DEBUG| utils:0153| [stdout] truncate_above_4GB (2M: 64): PASS 12/24 04:59:42 ERROR| utils:0153| [stderr] brk_near_huge: malloc.c:2403: sysmalloc: Assertion `(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed. 12/24 04:59:42 DEBUG| utils:0153| [stdout] brk_near_huge (2M: 64): 12/24 04:59:42 DEBUG| utils:0153| [stdout] task-size-overrun (2M: 64): PASS Full log: http://pastebin.ubuntu.com/23732201/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1653597/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1447664] Re: 14e4:1687 broadcom tg3 network driver disconnects under high load
Still an issue here with Dell Latitude 5495 and Kernel 5.2.7.
I noticed that very much like similar problems I had with Realtek LAN,
it helped as a workaround to boot with iommu=pt kernel parameter.
A rtl8169 report was here
https://bugzilla.kernel.org/show_bug.cgi?id=14962 (and many others
exist)
** Bug watch added: Linux Kernel Bug Tracker #14962
https://bugzilla.kernel.org/show_bug.cgi?id=14962
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1447664
Title:
14e4:1687 broadcom tg3 network driver disconnects under high load
Status in linux package in Ubuntu:
Fix Released
Status in linux package in Debian:
New
Bug description:
The tg3 broadcom network driver that binds with chipset 5762 goes offline and
unable to recover (even with tg3 watchdog timeout) when network transmit is
under high load. Call trace:
https://launchpadlibrarian.net/204185480/dmesg
When this happens, only a reboot would be able to fix it. Sometimes,
however, bringing the interface offline and online (via ifconfig)
would recover networking. I've also tested with the latest tg3 driver
(dec 2014 version) and networking is still problematic. I have also
disabled TSO, GSO etc... with ethtool and the bug still surfaces.
This bug may be related to the integrated Firmware.
Here is the procedure to replicate the issue because it is hard to
replicate it under moderate network load.
1. Bootup a machine with a broadcom 5762 NIC (ie. HP DeskElite 705) using a
Ubuntu/Kubunu Live CD 14.04-15.04.
2. from another machine: start 5 sessions, repetitively copy (scp with public
key authentication) a 70 meg file back and forth to the tg3 machine in each
session. (not sure if this is necessary)
3. create a 1GB file on the tg3 machine, with something like dd
if=/dev/urandom of=/my/test/file bs=1024 count=$((1024*1000))
4. from another machine: repetitively scp copy that 1GB file from the tg3
machine. This can be done with something like:
while [ 0 ]; do
scp -i /my/scp/private.key u...@ip.of.tg3:/my/test/file /tmp
done;
Networking will mostly goes offline in about 10-30 minutes.
WORKAROUND: Add udev rule to make the changes permanent in
/etc/udev/rules.d/80-tg3-fix.rules :
ACTION=="add", SUBSYSTEM=="net", ATTRS{vendor}=="0x14e4",
ATTRS{device}=="0x1687", RUN+="/sbin/ethtool -K %k highdma off"
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-15-generic 3.19.0-15.15
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: kubuntu3748 F pulseaudio
/dev/snd/controlC0: kubuntu3748 F pulseaudio
CasperVersion: 1.360
Date: Thu Apr 23 11:16:24 2015
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
LiveMediaBuild: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Hewlett-Packard HP EliteDesk 705 G1 MT
ProcEnviron:
LANGUAGE=
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi
file=/cdrom/preseed/hostname.seed boot=casper maybe-ubiquity quiet splash ---
PulseList:
Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not
accessible: Permission denied
No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-3.19.0-15-generic N/A
linux-backports-modules-3.19.0-15-generic N/A
linux-firmware 1.143
RfKill:
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/22/2014
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L06 v02.15
dmi.board.asset.tag: 2UA5041TG4
dmi.board.name: 2215
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: 2UA5041TG4
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias:
dmi:bvnHewlett-Packard:bvrL06v02.15:bd10/22/2014:svnHewlett-Packard:pnHPEliteDesk705G1MT:pvr:rvnHewlett-Packard:rn2215:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.product.name: HP EliteDesk 705 G1 MT
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1447664/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839037] Re: Stacked onexec transitions fail when under NO NEW PRIVS restrictions
** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839037 Title: Stacked onexec transitions fail when under NO NEW PRIVS restrictions Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Bug description: running the apparmor nnp regression tests results in the following failure Error: transition failed. Test 'NNP (stack onexec - NNP)' was expected to 'pass'. Reason for failure 'FAIL - execv: Operation not permitted' with a log message of [ 1169.863302] audit: type=1400 audit(1565046042.144:280686): apparmor="DENIED" operation="exec" info="no new privs" error=-1 profile="/home/jj/apparmor.git/tests/regression/apparmor/transition" name="/home/jj/apparmor.git/tests/regression/apparmor/open" pid=1888 comm="transition" requested_mask="x" denied_mask="x" fsuid=0 ouid=1000 target="/home/jj/apparmor.git/tests/regression/apparmor/open" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839758] Re: [amdgpu] System locks up with VMC page fault on Ryzen 2400G and HWE kernel 5.0.
> kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3 That looks more like https://bugs.freedesktop.org/show_bug.cgi?id=22 Try setting AMD_DEBUG="nodcc" environment variable. ** Bug watch added: freedesktop.org Bugzilla #22 https://bugs.freedesktop.org/show_bug.cgi?id=22 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839758 Title: [amdgpu] System locks up with VMC page fault on Ryzen 2400G and HWE kernel 5.0. Status in linux package in Ubuntu: Confirmed Bug description: Since kernel 5.0 rolled out through HWE last week my system is consistently locking up upon launch of Steam or 3D applications in WINE. Typical log: https://paste.ubuntu.com/p/WhPYXdkZVw/ Worked around by using pre-update 4.18 kernel. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 11 15:47:27 2019 DistUpgraded: 2018-03-26 22:50:10,989 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.32, 4.18.0-25-generic, x86_64: installed virtualbox, 5.2.32, 5.0.0-23-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last week or two GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c6) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000] InstallationDate: Installed on 2018-03-26 (502 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming K7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-23-generic root=/dev/mapper/ubuntu--vg-root ro SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to bionic on 2018-03-26 (502 days ago) dmi.bios.date: 01/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F25 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming K7 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se3 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF25:bd01/16/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-GamingK7:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-GamingK7:rvrse3:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming K7 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839758/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839287] Re: xenial/linux-azure: 4.15.0-1055.60 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839286 (trusty/linux-azure) derivatives: bug 1839283 (azure-kernel), bug 1839284 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Ready for Testing - phase-changed: Monday, 12. August 2019 10:10 UTC + phase: Ready for Signoff + phase-changed: Monday, 12. August 2019 14:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-updates: Holding -- stakeholder signoff not verified stakeholder-signoff: Pending -- waiting for signoff trackers: trusty/linux-azure: bug 1839286 xenial/linux-azure-edge: bug 1839284 xenial/linux-azure/azure-kernel: bug 1839283 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1839287 Title: xenial/linux-azure: 4.15.0-1055.60 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839286 (trusty/linux-azure) derivatives: bug 1839283 (azure-kernel), bug 1839284 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Signoff phase-changed: Monday, 12. August 2019 14:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- stakeholder signoff not verified stakeholder-signoff: Pending -- waiting for signoff trackers: trusty/linux-azure: bug 1839286 xenial/linux-azure-edge: bug 1839284 xenial/linux-azure/azure-kernel: bug 1839283 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839287] Re: xenial/linux-azure: 4.15.0-1055.60 -proposed tracker
** Tags added: regression-testing-passed -- 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/1839287 Title: xenial/linux-azure: 4.15.0-1055.60 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839286 (trusty/linux-azure) derivatives: bug 1839283 (azure-kernel), bug 1839284 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Signoff phase-changed: Monday, 12. August 2019 14:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- stakeholder signoff not verified stakeholder-signoff: Pending -- waiting for signoff trackers: trusty/linux-azure: bug 1839286 xenial/linux-azure-edge: bug 1839284 xenial/linux-azure/azure-kernel: bug 1839283 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839107] Re: xenial/linux-aws: 4.4.0-1090.101 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-xenial ** Tags removed: 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 1839104 (aws-kernel) -- swm properties -- kernel-stable-master-bug: 1839119 packages: main: linux-aws meta: linux-meta-aws - phase: Ready for Testing - phase-changed: Thursday, 08. August 2019 11:37 UTC + phase: Ready for Release + phase-changed: Monday, 12. August 2019 14:27 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-updates: Pending -- ready to copy trackers: xenial/linux-aws/aws-kernel: bug 1839104 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1839107 Title: xenial/linux-aws: 4.4.0-1090.101 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839104 (aws-kernel) -- swm properties -- kernel-stable-master-bug: 1839119 packages: main: linux-aws meta: linux-meta-aws phase: Ready for Release phase-changed: Monday, 12. August 2019 14:27 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy trackers: xenial/linux-aws/aws-kernel: bug 1839104 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839107] Re: xenial/linux-aws: 4.4.0-1090.101 -proposed tracker
** Tags added: regression-testing-passed -- 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/1839107 Title: xenial/linux-aws: 4.4.0-1090.101 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1839104 (aws-kernel) -- swm properties -- kernel-stable-master-bug: 1839119 packages: main: linux-aws meta: linux-meta-aws phase: Ready for Release phase-changed: Monday, 12. August 2019 14:27 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy trackers: xenial/linux-aws/aws-kernel: bug 1839104 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824981] Re: cifs set_oplock buffer overflow in strcat
Hi @granjerox, thanks for your report! Let us know how the test with -proposed
goes.
And thanks Kleber for the comment/advice here!
@connork, I've filled a new LP with the bug I've found, thanks for the
attention: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839849
Cheers,
Guilherme
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1824981
Title:
cifs set_oplock buffer overflow in strcat
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Committed
Status in linux source package in Eoan:
Fix Released
Bug description:
[Impact]
* We got reports of a kernel crash in cifs module with the following
signature:
detected buffer overflow in strcat
kernel BUG at <...>/lib/string.c:1052!
invalid opcode: [#1] SMP PTI
RIP: 0010:fortify_panic+0x13/0x1f
Call Trace:
smb21_set_oplock_level+0xde/0x190 [cifs]
smb3_set_oplock_level+0x22/0x90 [cifs]
smb2_set_fid+0x76/0xb0 [cifs]
cifs_new_fileinfo+0x268/0x3c0 [cifs]
? smb2_get_lease_key+0x40/0x40 [cifs]
? cifs_new_fileinfo+0x268/0x3c0 [cifs]
cifs_open+0x57c/0x8d0 [cifs]
do_dentry_open+0x1fe/0x320
[...]
* By analyzing the code of smb21_set_oplock_level(), we've noticed the
only way fortify function strcat() would get overflow was if the value
of cinode->oplock got corrupted in a another thread leading to a
buffer write bigger then buffer size. In this function, the 'message'
buffer writes are governed by cinode->oplock, so only a different
thread cleaning the oplock value would lead to 'message' overflow.
* By the same time we worked this analysis, a fix was proposed
upstream for this issue in the form of commit 6a54b2e002c9 ("cifs:
fix strcat buffer overflow and reduce raciness in
smb21_set_oplock_level()"), by the same reporter of this LP. The fix
is simple and directly addresses this problem, so we hereby request
its SRU into Bionic kernel - it's already present in linux stable
branches.
[Test case]
* Unfortunately we cannot reproduce the issue. The patch proposed here was
validated by us with xfstests (instructions followed from
https://wiki.samba.org/index.php/Xfstesting-cifs) and fio.
* Using xfstest with the exclusions proposed in the link above we
managed to get the same results as a non-patched kernel, i.e., the
same tests failed in both kernels, we didn't get worse results with
the patch. Fio also didn't show noticeable performance regression with
the patch.
[Regression potential]
* The patch was validated by the cifs filesystem maintainers and by
the aforementioned tests; also, the scope is restricted to cifs only
so the likelihood of regressions is considered low. The commit
introduces no functional changes and the only affected path was just
refactored in a way to prevent overflow and reduce race potential.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824981/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839849] Re: ext4 oops when running xfstests on cifs - kernel 5.0.0-x (Disco) only
I've also faced this oops. ** Attachment added: "mem.oops" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839849/+attachment/5282204/+files/mem.oops -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839849 Title: ext4 oops when running xfstests on cifs - kernel 5.0.0-x (Disco) only Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Confirmed Bug description: I've found an issue with kernel 5.0.0-24 while trying to verify LP#1824981 in a qemu guest - xfstests running on CIFS triggers a crash in ext4 with the following signature: BUG: unable to handle kernel NULL pointer dereference at 012c #PF error: [normal kernel read fault] Oops: [#1] SMP PTI CPU: 3 PID: 24980 Comm: 223 Not tainted 5.0.0-24-generic #25-Ubuntu RIP: 0010:call_filldir+0xa2/0x140 [...] Call Trace: ext4_readdir+0x869/0xa80 iterate_dir+0x9a/0x1b0 __x64_sys_getdents+0xa6/0x140 ? __x64_sys_getdents+0x140/0x140 do_syscall_64+0x5a/0x110 The full oops is attached below. I've tested on the following kernels, always in the Disco guest: *Reproduced -> 5.0.0-7 (built that one), 5.0.0-13, 5.0.0-21, 5.0.0-23, 5.0.0-24 (proposed) *No Issue -> 4.18.0-25 (from Cosmic), 5.2.0-10 (from Eoan), and 5.0, 5.1 and 5.2 from mainline builds (https://kernel.ubuntu.com/~kernel-ppa/mainline/) To trigger that I've ran the xfstests on a cifs mount point according to the instructions in https://wiki.samba.org/index.php/Xfstesting- cifs . The issue shows around test generic/208 usually. I've started a "manual" bisect - isolated all commits from v5.0..5.0.0-7, excluded all related with debian folder (and efi- lockdown, due to their complexity) and I'm reverting in a binary search fashion. Reverted 105 commits and still reproduced, and in the next set I've failed to build. I'll investigate the build fault and also I'll try to reproduce in a Bionic VM with bionic-hwe kernel version 5.0 . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839849/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836860] Re: [18.04 FEAT] Enhanced CPU-MF hardware counters - kernel part
** Changed in: linux (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Disco) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836860 Title: [18.04 FEAT] Enhanced CPU-MF hardware counters - kernel part Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Confirmed Status in linux source package in Disco: Confirmed Bug description: SRU Justification: == [Impact] * Enhanced CPU-MF hardware counters - fix lack of support of new hardware [Fix] * 46a984ffb86c8542fa510656fa8cb33befe8ee8f 46a984ff "s390/cpum_cf: Add support for CPU-MF SVN 6" * 820bace734722715c643dcb5f74b502cb912d4eb 820bace "s390/cpumf: Add extended counter set definitions for model 8561 and 8562" [Test Case] * try CPU-Measurement Facility counter on z14 and next generation hardware - only IBM can do that now [Regression Potential] * The regression potential can be considered as low since these changes are limited to arch/s390 * do only touch perf_* code * and mainly add code (rather than modify or remove) [Other Info] * first commit is taken from 5.2, second from 5.3-rc1 __ Enhance the CPU-MF hardware counters for improved HW support . Kernel 5.2 commits and kernel 5.3 patch on top Already requested for Ubuntu 19.10 kernel 5.2 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834201 kernel 5.3 fix https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836739 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1836860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839849] Re: ext4 oops when running xfstests on cifs - kernel 5.0.0-x (Disco) only
** Attachment added: "ext4.oops" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839849/+attachment/5282203/+files/ext4.oops -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839849 Title: ext4 oops when running xfstests on cifs - kernel 5.0.0-x (Disco) only Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Confirmed Bug description: I've found an issue with kernel 5.0.0-24 while trying to verify LP#1824981 in a qemu guest - xfstests running on CIFS triggers a crash in ext4 with the following signature: BUG: unable to handle kernel NULL pointer dereference at 012c #PF error: [normal kernel read fault] Oops: [#1] SMP PTI CPU: 3 PID: 24980 Comm: 223 Not tainted 5.0.0-24-generic #25-Ubuntu RIP: 0010:call_filldir+0xa2/0x140 [...] Call Trace: ext4_readdir+0x869/0xa80 iterate_dir+0x9a/0x1b0 __x64_sys_getdents+0xa6/0x140 ? __x64_sys_getdents+0x140/0x140 do_syscall_64+0x5a/0x110 The full oops is attached below. I've tested on the following kernels, always in the Disco guest: *Reproduced -> 5.0.0-7 (built that one), 5.0.0-13, 5.0.0-21, 5.0.0-23, 5.0.0-24 (proposed) *No Issue -> 4.18.0-25 (from Cosmic), 5.2.0-10 (from Eoan), and 5.0, 5.1 and 5.2 from mainline builds (https://kernel.ubuntu.com/~kernel-ppa/mainline/) To trigger that I've ran the xfstests on a cifs mount point according to the instructions in https://wiki.samba.org/index.php/Xfstesting- cifs . The issue shows around test generic/208 usually. I've started a "manual" bisect - isolated all commits from v5.0..5.0.0-7, excluded all related with debian folder (and efi- lockdown, due to their complexity) and I'm reverting in a binary search fashion. Reverted 105 commits and still reproduced, and in the next set I've failed to build. I'll investigate the build fault and also I'll try to reproduce in a Bionic VM with bionic-hwe kernel version 5.0 . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839849/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839849] [NEW] ext4 oops when running xfstests on cifs - kernel 5.0.0-x (Disco) only
Public bug reported: I've found an issue with kernel 5.0.0-24 while trying to verify LP#1824981 in a qemu guest - xfstests running on CIFS triggers a crash in ext4 with the following signature: BUG: unable to handle kernel NULL pointer dereference at 012c #PF error: [normal kernel read fault] Oops: [#1] SMP PTI CPU: 3 PID: 24980 Comm: 223 Not tainted 5.0.0-24-generic #25-Ubuntu RIP: 0010:call_filldir+0xa2/0x140 [...] Call Trace: ext4_readdir+0x869/0xa80 iterate_dir+0x9a/0x1b0 __x64_sys_getdents+0xa6/0x140 ? __x64_sys_getdents+0x140/0x140 do_syscall_64+0x5a/0x110 The full oops is attached below. I've tested on the following kernels, always in the Disco guest: *Reproduced -> 5.0.0-7 (built that one), 5.0.0-13, 5.0.0-21, 5.0.0-23, 5.0.0-24 (proposed) *No Issue -> 4.18.0-25 (from Cosmic), 5.2.0-10 (from Eoan), and 5.0, 5.1 and 5.2 from mainline builds (https://kernel.ubuntu.com/~kernel-ppa/mainline/) To trigger that I've ran the xfstests on a cifs mount point according to the instructions in https://wiki.samba.org/index.php/Xfstesting-cifs . The issue shows around test generic/208 usually. I've started a "manual" bisect - isolated all commits from v5.0..5.0.0-7, excluded all related with debian folder (and efi- lockdown, due to their complexity) and I'm reverting in a binary search fashion. Reverted 105 commits and still reproduced, and in the next set I've failed to build. I'll investigate the build fault and also I'll try to reproduce in a Bionic VM with bionic-hwe kernel version 5.0 . ** Affects: linux (Ubuntu) Importance: High Assignee: Guilherme G. Piccoli (gpiccoli) Status: Confirmed ** Affects: linux (Ubuntu Disco) Importance: High Assignee: Guilherme G. Piccoli (gpiccoli) Status: Confirmed ** Tags: seg ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Disco) Status: New => Confirmed ** Changed in: linux (Ubuntu Disco) Importance: Undecided => High ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839849 Title: ext4 oops when running xfstests on cifs - kernel 5.0.0-x (Disco) only Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Confirmed Bug description: I've found an issue with kernel 5.0.0-24 while trying to verify LP#1824981 in a qemu guest - xfstests running on CIFS triggers a crash in ext4 with the following signature: BUG: unable to handle kernel NULL pointer dereference at 012c #PF error: [normal kernel read fault] Oops: [#1] SMP PTI CPU: 3 PID: 24980 Comm: 223 Not tainted 5.0.0-24-generic #25-Ubuntu RIP: 0010:call_filldir+0xa2/0x140 [...] Call Trace: ext4_readdir+0x869/0xa80 iterate_dir+0x9a/0x1b0 __x64_sys_getdents+0xa6/0x140 ? __x64_sys_getdents+0x140/0x140 do_syscall_64+0x5a/0x110 The full oops is attached below. I've tested on the following kernels, always in the Disco guest: *Reproduced -> 5.0.0-7 (built that one), 5.0.0-13, 5.0.0-21, 5.0.0-23, 5.0.0-24 (proposed) *No Issue -> 4.18.0-25 (from Cosmic), 5.2.0-10 (from Eoan), and 5.0, 5.1 and 5.2 from mainline builds (https://kernel.ubuntu.com/~kernel-ppa/mainline/) To trigger that I've ran the xfstests on a cifs mount point according to the instructions in https://wiki.samba.org/index.php/Xfstesting- cifs . The issue shows around test generic/208 usually. I've started a "manual" bisect - isolated all commits from v5.0..5.0.0-7, excluded all related with debian folder (and efi- lockdown, due to their complexity) and I'm reverting in a binary search fashion. Reverted 105 commits and still reproduced, and in the next set I've failed to build. I'll investigate the build fault and also I'll try to reproduce in a Bionic VM with bionic-hwe kernel version 5.0 . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839849/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821625] Re: systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-seccomp)
to close this out, the latest systemd build, version 237-3ubuntu10.25,
picked up the correct pkey_mprotect value from the updated kernel and
now does not fail the test.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1821625
Title:
systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-
seccomp)
Status in libseccomp package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Invalid
Status in libseccomp source package in Bionic:
Invalid
Status in linux source package in Bionic:
Fix Released
Status in systemd source package in Bionic:
Invalid
Bug description:
Starting with systemd 237-3ubuntu10.14, the testcase test-seccomp is
failing on Bionic on ppc64el with the error messages:
Operating on architecture: ppc
Failed to add n/a() rule for architecture ppc, skipping: Bad address
Operating on architecture: ppc64
Failed to add n/a() rule for architecture ppc64, skipping: Bad address
Operating on architecture: ppc64-le
Failed to add n/a() rule for architecture ppc64-le, skipping: Numerical
argument out of domain
Assertion 'p == MAP_FAILED' failed at ../src/test/test-seccomp.c:413,
function test_memory_deny_write_execute_mmap(). Aborting.
memoryseccomp-mmap terminated by signal ABRT.
Assertion 'wait_for_terminate_and_check("memoryseccomp-mmap", pid, WAIT_LOG)
== EXIT_SUCCESS' failed at ../src/test/test-seccomp.c:427, function
test_memory_deny_write_execute_mmap(). Aborting.
Aborted (core dumped)
FAIL: test-seccomp (code: 134)
Full logs at:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190302_025135_d0e38@/log.gz
The testcase passed with systemd version 237-3ubuntu10.13 running on the same
4.15.0-45 kernel on ppc64el:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190228_154406_6b12f@/log.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1821625/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839280] Re: bionic/linux-oracle: 4.15.0-1021.23 -proposed tracker
** Tags added: regression-testing-passed -- 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/1839280 Title: bionic/linux-oracle: 4.15.0-1021.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839278 (xenial/linux-oracle) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Holding before Release phase-changed: Monday, 12. August 2019 14:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- master bug not ready for release trackers: xenial/linux-oracle: bug 1839278 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839280/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839280] Re: bionic/linux-oracle: 4.15.0-1021.23 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839278 (xenial/linux-oracle) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Ready for Testing - phase-changed: Friday, 09. August 2019 21:10 UTC + phase: Holding before Release + phase-changed: Monday, 12. August 2019 14:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-updates: Holding -- master bug not ready for release trackers: xenial/linux-oracle: bug 1839278 variant: debs -- 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/1839280 Title: bionic/linux-oracle: 4.15.0-1021.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839278 (xenial/linux-oracle) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1839293 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Holding before Release phase-changed: Monday, 12. August 2019 14:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- master bug not ready for release trackers: xenial/linux-oracle: bug 1839278 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839280/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839847] Re: Chromium snap duplication wonkiness
** Package changed: linux (Ubuntu) => chromium-browser (Ubuntu) ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => New ** Summary changed: - Chromium snap duplication wonkiness + [snap] Chromium snap duplication wonkiness ** Tags added: disco snap -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839847 Title: [snap] Chromium snap duplication wonkiness Status in chromium-browser package in Ubuntu: New Bug description: I'm having issues that are difficult to describe. I also can't reproduce them. At points I will get a browser that has all thumbnails for bookmarks gone and passwords get really wonky. I also get the browser to appear, but there is no dot in the bar with tagged apps. If I press it a new window opens. Doing ALT-F2->r fixes it. (This might be a different bug) Closing the browser and reopening it opens "saved" tabs from a previous session just before the bug happens. I'm using the restore tabs feature a lot. Thanks. Ubuntu 19.04 Chromium Version 76.0.3809.100 (Official Build) snap (64-bit) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1839847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836860] Re: [18.04 FEAT] Enhanced CPU-MF hardware counters - kernel part
** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836860 Title: [18.04 FEAT] Enhanced CPU-MF hardware counters - kernel part Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Confirmed Status in linux source package in Disco: New Bug description: SRU Justification: == [Impact] * Enhanced CPU-MF hardware counters - fix lack of support of new hardware [Fix] * 46a984ffb86c8542fa510656fa8cb33befe8ee8f 46a984ff "s390/cpum_cf: Add support for CPU-MF SVN 6" * 820bace734722715c643dcb5f74b502cb912d4eb 820bace "s390/cpumf: Add extended counter set definitions for model 8561 and 8562" [Test Case] * try CPU-Measurement Facility counter on z14 and next generation hardware - only IBM can do that now [Regression Potential] * The regression potential can be considered as low since these changes are limited to arch/s390 * do only touch perf_* code * and mainly add code (rather than modify or remove) [Other Info] * first commit is taken from 5.2, second from 5.3-rc1 __ Enhance the CPU-MF hardware counters for improved HW support . Kernel 5.2 commits and kernel 5.3 patch on top Already requested for Ubuntu 19.10 kernel 5.2 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834201 kernel 5.3 fix https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836739 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1836860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838677] Re: shiftfs: allow overlayfs
** Changed in: linux (Ubuntu Disco) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838677 Title: shiftfs: allow overlayfs Status in linux package in Ubuntu: Fix Committed Status in linux source package in Disco: In Progress Bug description: SRU Justification Impact: Currently it is not possible to use overlayfs on top of shiftfs. This means Docker inside of LXD cannot make user of the overlay2 graph driver which is blocking users such as Travis from making use of it efficiently. Regression Potential: Limited to shiftfs and overlayfs on top of shiftfs. Overlayfs does prevent "remote" filesystems such as ceph, nfs, etc. from being used as the underlay. With this patch shiftfs however can be used as an underlay and we special case it as a suitable filesystem to be used under overlayfs. I verified that the patch does not lead to regression on overlayfs workloads that do not make use of shiftfs as underlay. Additionally, I tested Docker with the overlay2 graphdriver on top of shiftfs. This also has not lead to any regressions. Test case: Building a kernel with the patch: sudo snap install lxd sudo lxd init sudo lxc launch images:ubuntu/bionic b1 sudo lxc config set b1 security.nesting true sudo lxc restart --force b1 sudo lxc shell b1 sudo apt-get install \ apt-transport-https \ ca-certificates \ curl \ gnupg-agent \ software-properties-common curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add - curl -fsSL get.docker.com | CHANNEL=test sh sudo add-apt-repository \ "deb [arch=amd64] https://download.docker.com/linux/ubuntu \ $(lsb_release -cs) \ stable" sudo apt-get update sudo apt-get install docker-ce docker-ce-cli containerd.io sudo systemctl stop docker cat
[Kernel-packages] [Bug 1839847] 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 1839847 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/1839847 Title: [snap] Chromium snap duplication wonkiness Status in chromium-browser package in Ubuntu: New Bug description: I'm having issues that are difficult to describe. I also can't reproduce them. At points I will get a browser that has all thumbnails for bookmarks gone and passwords get really wonky. I also get the browser to appear, but there is no dot in the bar with tagged apps. If I press it a new window opens. Doing ALT-F2->r fixes it. (This might be a different bug) Closing the browser and reopening it opens "saved" tabs from a previous session just before the bug happens. I'm using the restore tabs feature a lot. Thanks. Ubuntu 19.04 Chromium Version 76.0.3809.100 (Official Build) snap (64-bit) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1839847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839847] [NEW] Chromium snap duplication wonkiness
Public bug reported: I'm having issues that are difficult to describe. I also can't reproduce them. At points I will get a browser that has all thumbnails for bookmarks gone and passwords get really wonky. I also get the browser to appear, but there is no dot in the bar with tagged apps. If I press it a new window opens. Doing ALT-F2->r fixes it. (This might be a different bug) Closing the browser and reopening it opens "saved" tabs from a previous session just before the bug happens. I'm using the restore tabs feature a lot. Thanks. Ubuntu 19.04 Chromium Version 76.0.3809.100 (Official Build) snap (64-bit) ** 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/1839847 Title: Chromium snap duplication wonkiness Status in linux package in Ubuntu: New Bug description: I'm having issues that are difficult to describe. I also can't reproduce them. At points I will get a browser that has all thumbnails for bookmarks gone and passwords get really wonky. I also get the browser to appear, but there is no dot in the bar with tagged apps. If I press it a new window opens. Doing ALT-F2->r fixes it. (This might be a different bug) Closing the browser and reopening it opens "saved" tabs from a previous session just before the bug happens. I'm using the restore tabs feature a lot. Thanks. Ubuntu 19.04 Chromium Version 76.0.3809.100 (Official Build) snap (64-bit) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828596] Re: kdump fails when crash is triggered after DLPAR cpu add operation
** Changed in: ubuntu-power-systems Status: Incomplete => Triaged -- 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/1828596 Title: kdump fails when crash is triggered after DLPAR cpu add operation Status in The Ubuntu-power-systems project: Triaged Status in kexec-tools package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: Fix Released Status in kexec-tools source package in Xenial: New Status in makedumpfile source package in Xenial: New Status in kexec-tools source package in Bionic: New Status in makedumpfile source package in Bionic: New Status in kexec-tools source package in Cosmic: New Status in makedumpfile source package in Cosmic: New Status in kexec-tools source package in Disco: New Status in makedumpfile source package in Disco: New Status in kexec-tools source package in Eoan: Invalid Status in makedumpfile source package in Eoan: Fix Released Bug description: [Impact] After a CPU add/hotplug operation on Power systems, kdump will fail after a crash. The kdump kernel needs to be reloaded after a CPU add/hotplug. [Test case] Do CPU add/hotplug, trigger a crash, and check for a successful kdump. [Regression potential] Multiple reloads caused by multiple sequential CPU adds may cause spurious log results, and systemd may fail to properly reload the kdump kernel. This has been handled by resetting the failure counter when doing such reloads. == Comment: #0 - Hari Krishna Bathini - 2019-05-10 05:55:40 == ---Problem Description--- kdump fails when crash is triggered after CPU add operation. Machine Type = na ---System Hang--- Crashed in early boot process of kdump kernel after crash Had to issue system reset from HMC to reclaim ---Steps to Reproduce--- 1. Configure kdump. 2. Add cpu from HMC. 3. Trigger crash. 4. Machine hangs after crash as below: --- [169250.213166] IPI complete [169250.234331] kexec: Starting switchover sequence. I'm in purgatory --- STRUCK HERE --- ---uname output--- na ---Debugger--- A debugger is not configured == Comment: #1 - Hari Krishna Bathini - 2019-05-10 05:56:46 == The problem is, kexec udev rule to restart kdump-tools service - when a core is added, is not being triggered. The old DT created by kexec (before the core is added) is being used by KDump Kernel. So, when system crashes on a thread from the added core(s), KDump kernel is failing to get the 'boot_cpuid' and eventually failing to boot.. == Comment: #2 - Hari Krishna Bathini - 2019-05-10 06:02:27 == The udev rule when CPU is added is not triggered because ppc64 does not eject add/remove event when a CPU is hot added/removed. It only ejects online/offline event to user space when CPU is hot added/removed. So, the below udev rules are never triggered when needed: SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl try-restart kdump-tools.service" SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl try-restart kdump-tools.service" Also, with how CPU hot add & remove are handled in ppc64, a udev trigger to reload kdump after CPU is hot removed is NOT necessary. So, fix the CPU hot add case by updating the udev rule and drop the udev rule meant for CPU hot remove in the kdump udev rules file: SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl try- restart kdump-tools.service" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828596/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833793] Re: Updating to 19.04 audio keeps clicking when nothing is playing audio
I had this problem after upgrading kernel to 5.0.0-23 and the workaround in comment #5 (turning off the Intel power optimisation) worked for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833793 Title: Updating to 19.04 audio keeps clicking when nothing is playing audio Status in linux package in Ubuntu: Confirmed Bug description: My Ubuntu version: Ubuntu 19.04 My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02) What I expect to happen: Sound is absolutely quiet when no audio is playing What happens now: Audio output starts clicking every second incredibly annoyingly and loud. What previously happened on Ubuntu 18.10: I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 4604 F pulseaudio /dev/snd/pcmC0D0p: a 4604 F...m pulseaudio /dev/snd/controlC1: a 4604 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2017-08-23 (679 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: enp63s0 no wireless extensions. wg0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq dc5700 Microtower NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=/dev/mapper/vgroot-lvroot ro cryptdevice=/dev/sda2:lvm quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-20-generic N/A linux-backports-modules-5.0.0-20-generic N/A linux-firmware1.178.2 RfKill: Tags: disco Uname: Linux 5.0.0-20-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-20 (13 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 11/10/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E2 v02.09 dmi.board.name: 0A60h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E2v02.09:bd11/10/2011:svnHewlett-Packard:pnHPCompaqdc5700Microtower:pvr:rvnHewlett-Packard:rn0A60h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc5700 Microtower dmi.product.sku: EW287AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833793/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836857] Re: [18.04 FEAT] Enhanced hardware support
** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Disco) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836857 Title: [18.04 FEAT] Enhanced hardware support Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: New Status in linux source package in Disco: New Bug description: SRU Justification: == [Impact] * Enhanced hardware support for upcoming machine and make sure it can report new CPU capabilities [Fix] * a8fd61688dfad6fdce95fa64cacd8a66595697b8 a8fd616 "s390: report new CPU capabilities" * 142c52d7bce45d335f48d53fdbf428bb15cf3924 142c52d "s390: add alignment hints to vector load and store" [Test Case] * check /proc/cpuinfo in bionic running on upcoming machine - currently only IBM can do that [Regression Potential] * The regression potential can be considered as very low since these changes are limited to arch/s390 * and mainly adds code for the capability to report new features in cpuinfo - in case of running on new hardware [Other Info] * a8fd616 got upstream accepted with 5.2; 142c52d with 5.1 - hence both are already in eoan __ Feature request to apply this to Ubuntu 18.04 in support of new machine. Summary: kernel: report new CPU capabilities Description: Add hardware capability bits and features tags to /proc/cpuinfo for 4 new CPU features: the "Vector-Enhancements Facility 2", the "Vector-Packed-Decimal-Enhancement Facility", the "Enhanced-Sort Facility" and the "Deflate-Conversion Facility" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1836857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839093] Re: disco/linux-gcp: 5.0.0-1013.13 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-disco ** Tags removed: 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 1839086 (bionic/linux-gke-5.0), bug 1839090 (bionic /linux-gcp-edge) -- swm properties -- kernel-stable-master-bug: 1839106 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Holding before Release - phase-changed: Monday, 12. August 2019 10:25 UTC + phase: Ready for Release + phase-changed: Monday, 12. August 2019 13:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- master bug not ready for release + promote-to-updates: Pending -- ready to copy trackers: bionic/linux-gcp-edge: bug 1839090 bionic/linux-gke-5.0: bug 1839086 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1839093 Title: disco/linux-gcp: 5.0.0-1013.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839086 (bionic/linux-gke-5.0), bug 1839090 (bionic /linux-gcp-edge) -- swm properties -- kernel-stable-master-bug: 1839106 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Ready for Release phase-changed: Monday, 12. August 2019 13:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy trackers: bionic/linux-gcp-edge: bug 1839090 bionic/linux-gke-5.0: bug 1839086 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839072] Re: disco/linux-aws: 5.0.0-1012.13 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-disco ** Tags removed: 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 1839070 (bionic/linux-aws-edge) -- swm properties -- kernel-stable-master-bug: 1839106 packages: main: linux-aws meta: linux-meta-aws - phase: Holding before Release - phase-changed: Monday, 12. August 2019 10:16 UTC + phase: Ready for Release + phase-changed: Monday, 12. August 2019 13:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- master bug not ready for release + promote-to-updates: Pending -- ready to copy trackers: bionic/linux-aws-edge: bug 1839070 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1839072 Title: disco/linux-aws: 5.0.0-1012.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839070 (bionic/linux-aws-edge) -- swm properties -- kernel-stable-master-bug: 1839106 packages: main: linux-aws meta: linux-meta-aws phase: Ready for Release phase-changed: Monday, 12. August 2019 13:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy trackers: bionic/linux-aws-edge: bug 1839070 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839106] Re: disco/linux: 5.0.0-25.26 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-disco ** Tags removed: 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 1839099 (bionic/linux-hwe), bug 1839101 (bionic/linux-oem-osp1) derivatives: bug 1837563 (linux-raspi2), bug 1837573 (linux-snapdragon), bug 1839072 (linux-aws), bug 1839093 (linux-gcp), bug 1839096 (linux-kvm), bug 1839352 (linux-azure) -- swm properties -- bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Ready for Testing - phase-changed: Thursday, 08. August 2019 14:40 UTC + phase: Ready for Release + phase-changed: Monday, 12. August 2019 13:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-updates: Pending -- ready to copy trackers: bionic/linux-hwe: bug 1839099 bionic/linux-oem-osp1: bug 1839101 disco/linux-aws: bug 1839072 disco/linux-azure: bug 1839352 disco/linux-gcp: bug 1839093 disco/linux-kvm: bug 1839096 disco/linux-raspi2: bug 1837563 disco/linux-snapdragon: bug 1837573 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839106 Title: disco/linux: 5.0.0-25.26 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839099 (bionic/linux-hwe), bug 1839101 (bionic/linux-oem-osp1) derivatives: bug 1837563 (linux-raspi2), bug 1837573 (linux-snapdragon), bug 1839072 (linux-aws), bug 1839093 (linux-gcp), bug 1839096 (linux-kvm), bug 1839352 (linux-azure) -- swm properties -- bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Release phase-changed: Monday, 12. August 2019 13:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy trackers: bionic/linux-hwe: bug 1839099 bionic/linux-oem-osp1: bug 1839101 disco/linux-aws: bug 1839072 disco/linux-azure: bug 1839352 disco/linux-gcp: bug 1839093 disco/linux-kvm: bug 1839096 disco/linux-raspi2: bug 1837563 disco/linux-snapdragon: bug 1837573 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839106/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
