[Kernel-packages] [Bug 1804588] Re: Power consumption during s2idle is higher than long idle (Intel SSDPEKKF)
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed- cosmic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804588 Title: Power consumption during s2idle is higher than long idle (Intel SSDPEKKF) Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: New Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: In Progress Bug description: [Impact] On new systems that facilitate s2idle, we observed the power consumption raises higher than long idle does during s2idle with Intel NVMe SSDPEKKF. Short idle: 6 Long idle: 2 S2I: 4.8 [Fix] Windows doesn't put nvme to D3 in modern standby, and uses its own APST feature to do the power management. To leverage its APST feature during s2idle, we can't disable nvme device while suspending, too. So, here is what we did on the driver, 1. prevent nvme from entering D3, 2. prevent nvme from being disabled when suspending. [Test] Verified on the new Intel NVMe, it fixes the power consumption issue with no regression. And the power consumption decreases to 2.8W during s2idle. [Regression Potential] Low, the patches only applied to specific nvme module, and from our test, the system is still stable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1804588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798583] Re: the new Steam Controller driver breaks it on Steam
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed- cosmic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798583 Title: the new Steam Controller driver breaks it on Steam Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Released Bug description: ===SRU Justification=== [Impact] New steam-hid driver breaks Unity games. [Fix] Quote from the commit message: "With this commit, when a HID client starts, the input device is removed; when the HID client ends the input device is recreated." [Test] A guy from Valve comfirms the backport works. [Regression Potential] Low. This fix is specific to hid-steam, which is a new driver introduced in v4.18. ===Original Bug Report=== The new hid_steam driver in kernel 4.18 breaks the use of it within Steam. Games either: - Crash - Don't detect it at all - Only pick it up as player 2 To get it working as normal, it needs blacklisting currently. See here: https://www.gamingonlinux.com/articles/the-steam-controller- on-ubuntu-1810-and-other-distributions-using-linux-kernel-418-needs- quick-a-fix.12775 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: liam 2492 F pulseaudio /dev/snd/controlC0: liam 2492 F pulseaudio /dev/snd/controlC1: liam 2492 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 18 12:49:44 2018 InstallationDate: Installed on 2017-10-18 (364 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. eno1 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=2a8676f3-0045-4e66-9cd1-186ffc6a8c2a ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-18 (0 days ago) dmi.bios.date: 08/10/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: PCS dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1901:bd08/10/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791758] Re: ldisc crash on reopened tty
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1791758
Title:
ldisc crash on reopened tty
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Bug description:
[Impact]
* Line discipline code is racy when we have buffer being flush while
the tty is being initialized or reinitialized. For the first problem,
we have an upstream patch since January 2018: b027e2298bd5 ("tty: fix
data race between tty_init_dev and flush of buf") - although it is not
in Ubuntu kernel 4.4, only in kernels 4.15 and subsequent ones.
* For the race between the buffer flush while tty is being reopened,
we have a patch that addresses this issue recently merged for 5.0-rc1:
83d817f41070 ("tty: Hold tty_ldisc_lock() during tty_reopen()"). No
Ubuntu kernel currently contains this patch, hence we're hereby
submitting the SRU request. The upstream complete patch series for
this is in [0].
* The approach of both patches are similar - they rely in locking/semaphore
to prevent race conditions. Some additional patches are
necessary to prevent correlated issues, like preventing a potential deadlock
due to bad prioritization in servicing I/O over releasing
tty_ldisc_lock() - refer to c96cf923a98d ("tty: Don't block on IO when ldisc
change is pending"). All the necessary fixes are grouped here in this SRU
request.
* The symptom of the race condition between the buffer flush and the
tty reopen routine is a kernel crash with the following trace:
BUG: unable to handle kernel paging request at 2268
IP: [] n_tty_receive_buf_common+0x6a/0xae0
[...]
Call Trace:
[] ? kvm_sched_clock_read+0x1e/0x30
[] n_tty_receive_buf2+0x14/0x20
[] flush_to_ldisc+0xd5/0x120
[] process_one_work+0x156/0x400
[] worker_thread+0x11a/0x480
[...]
* A kernel crash was collected from an user, analysis is present in
comment #4 in this LP.
[Test Case]
* It is not trivial to trigger this fault, but the usual recipe is to
keep accessing a machine through SSH (or keep killing getty when in
IPMI serial console) and in some way run commands before the terminal
is ready in that machine (like hacking some echo into ttySx or pts in
an infinite loop).
* We have reports of users that could reproduce this issue in their
production environment, and with the patches present in this SRU
request the problem was fixed.
[Regression Potential]
* tty subsystem is highly central and patches in that area are always
delicate. For example, the upstream series [0] is a re-spin (V6) due
to a hard to reproduce issue reported in the PA-RISC architecture,
which was found in the V5 iteration [1] but was fixed by the patch
c96cf923a98d, present in this SRU request.
* The patchset [0] is present in tty-next tree since mid-November, and
the patch b027e2298bd5 is available upstream since January/2018 (it's
available in both Ubuntu kernels 4.15 and 4.18), so the overall
likelihood of regressions is low.
* These patches were sniff-tested for the 3 versions (4.4, 4.15 and
4.18) and didn't show any issues.
[0] https://marc.info/?l=linux-kernel=154103190111795
[1] https://marc.info/?l=linux-kernel=153737852618183
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791758/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Confirmed Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Fix Committed Bug description: ===SRU Justification=== Hantick touchpad stops working after reboot. [Fix] Disable runtime power management for the touchpad. [Test] User confirmed it fixed the issue. Some users reported it doesn't work for them, I'll ask them to file new bugs for different touchpads. [Regression Potential] Low. Disable runtime power management doesn't affect devivce's funtionality. In general desktop usage the graphical session opens the touchpad HID device so the touchpad never get runtime suspended, so it won't hurt power in this case. ===Original Bug Report=== On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808912] Re: scsi: libsas: fix a race condition when smp task timeout
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808912 Title: scsi: libsas: fix a race condition when smp task timeout Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] When the lldd is processing the complete sas task in interrupt and set the task stat as SAS_TASK_STATE_DONE, the smp timeout timer is able to be triggered at the same time. And smp_task_timedout() will complete the task wheter the SAS_TASK_STATE_DONE is set or not. Then the sas task may freed before lldd end the interrupt process. Thus a use-after-free will happen. [Test Case] This is hard to reproduce, so regression test only. [Fix] b90cd6f2b9 scsi: libsas: fix a race condition when smp task timeout [Regression Risk] Only 2 line moved in libsas and maintainer has reviewed/approved. I will say it's low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808729] Re: MAC address pass through on RTL8153-BND for docking station
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808729 Title: MAC address pass through on RTL8153-BND for docking station Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] A new chip RTL8153-BND on docks require to be added to the whitelist to support MAC address pass through. [Fix] This commit adds check for RTL8153-BND chip which is in v4.20. 9c27369f4a13 r8152: Add support for MAC address pass through on RTL8153-BND [Regression Potential] Low. It doesn't change the code flow for the old RTL8153-AD chip, so it won't lead to regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1808729/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806534] Re: Fix USB2 device wrongly detected as USB1
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806534 Title: Fix USB2 device wrongly detected as USB1 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: [Impact] USB 2 device may come up as USB 1 if a connection to a USB 1 device is followed by another connection to a USB 2 device, the link will come up as USB 1 for the USB 2 device. [Test Case] Insert 2 USB devices and they shall appear on lsusb with correct address [Fix] 11644a76 xhci: Add quirk to workaround the errata seen on Cavium Thunder-X2 Soc [Regression Risk] It only affect device PCI_VENDOR_ID_CAVIUM:0x9026 and PCI_VENDOR_ID_BROADCOM:0x9026. Low regression to other device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806534/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1620762] Re: Support AverMedia DVD EZMaker 7 USB video capture dongle
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1620762 Title: Support AverMedia DVD EZMaker 7 USB video capture dongle Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: Linux doesn't support this capture. Link to patch https://www.linuxtv.org/wiki/index.php/AVerMedia_DVD_EZMaker_7_(C039). I tested it on Ubuntu 16.04 - OK. It will be great if this patch is built-in to kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1620762/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809488] Re: armhf guests fail to boot in EFI mode
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809488 Title: armhf guests fail to boot in EFI mode Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Released Bug description: [Impact] The fix for bug 1786878 introduced a regression that causes armhf guest booted in EFI mode to panic. [Test Case] Boot an armhf guest in EFI mode. Here's how I do that on an arm64 box that supports AArch32: sudo qemu-system-aarch64 -enable-kvm -M virt,gic_version=host -smp 7 -m 2048 -cpu host,aarch64=off -nographic -pflash AAVMF32_CODE.fd -pflash AAVMF32_VARS.fd -drive if=none,file=bionic-server-cloudimg- armhf.img,id=hd0 -device virtio-blk-device,drive=hd0 -drive if=none,file=my-seed.img,id=hd1 -device virtio-blk- device,drive=hd1 -drive if=none,file=debian.img,id=hd3 -device virtio- blk-device,drive=hd3 -netdev type=tap,id=net0 -device virtio- net-device,netdev=net0,mac= [Fix] 33412b8673135 efi/arm: Revert deferred unmap of early memmap mapping [Regression Risk] This change is specific to efi/arm, which currently doesn't boot. The reverted change was to allow for ACPI BGRT code, which isn't supported on 32-bit ARM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809488/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808465] Re: The mute led can't work anymore on the lenovo x1 carbon
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808465 Title: The mute led can't work anymore on the lenovo x1 carbon Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: [Impact] The mute led can't work on several lenovo laptop models after applying the patch of #1805079, this is a regression introduced by that patch. [Fix] chanin the ALC269_FIXUP_THINKPAD_ACPI, this will make the led work again. [Test Case] press F1 and F4, the mute led and micmute led work well. [Regression Potential] Very low, this patch is specific to ALC285_FIXUP_LENOVO_HEADPHONE_NOISE, and this FIXUP is specific several lenovo laptop models. I have tested audio and led functions on those machines. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811424] Re: linux-gcp: 4.15.0-1027.28 -proposed tracker
** Summary changed: - linux-gcp: -proposed tracker + linux-gcp: 4.15.0-1027.28 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) -- 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/1811424 Title: linux-gcp: 4.15.0-1027.28 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1811419 phase: Packaging -- ready to package phase-changed: Monday, 14. January 2019 11:43 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811424/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1277959] Re: [Asus 1015E] Fn+F2 is not working for activating/deactivating wifi
I have this problem and I see another computer with this problem too. I
just create a file like this.
pablo@pablo-H14SU08:~$ cat /etc/modprobe.d/rtlwifi.conf
###Evitar que a tecla Function (Fn) quebre o WIFI
options rtlwifi wapf=4
pablo@pablo-H14SU08:~$
lspci
03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188EE
Wireless Network Adapter (rev 01)
Using Trisquel 8.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1277959
Title:
[Asus 1015E] Fn+F2 is not working for activating/deactivating wifi
Status in linux package in Ubuntu:
Expired
Bug description:
Fn+F2 is not working for activating/deactivating wifi.
Also wifi led is not working (led located on netbook case)
I have an ASUS 1015E-DS03 netbook with Ubuntu 12.04 LTS.
Linux ASUS-1015E-DS03 3.8.0-35-generic #52~precise1-Ubuntu SMP Thu Jan
30 17:24:40 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
The problem maybe in asus_nb_wmi driver.
Related to https://bugs.launchpad.net/bugs/1173681.
description: Wireless interface
product: AR9485 Wireless Network Adapter
vendor: Qualcomm Atheros
physical id: 0
bus info: pci@:02:00.0
logical name: wlan0
version: 01
serial: 6c:71:d9:7f:70:6b
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list rom ethernet
physical wireless
configuration: broadcast=yes driver=ath9k
driverversion=3.8.0-35-generic firmware=N/A ip=192.168.1.47 latency=0 link=yes
multicast=yes wireless=IEEE 802.11bgn
resources: irq:17 memory:f7d0-f7d7 memory:f7d8-f7d8
Thanks.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.8.0-35-generic 3.8.0-35.52~precise1
ProcVersionSignature: Ubuntu 3.8.0-35.52~precise1-generic 3.8.13.13
Uname: Linux 3.8.0-35-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.8.0-35-generic.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: christian 1836 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xf7e1 irq 44'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:10ec0269,1043115d,00100100
HDA:80862806,80860101,0010'
Controls : 24
Simple ctrls : 9
Date: Sat Feb 8 17:41:06 2014
HibernationDevice: RESUME=UUID=046c9b4b-4f3f-45e2-8edf-e79abc412d11
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
(20130820.1)
MachineType: ASUSTeK COMPUTER INC. 1015E
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-35-generic
root=UUID=671caa58-b12e-4d13-a74e-a34bd55cff02 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.8.0-35-generic N/A
linux-backports-modules-3.8.0-35-generic N/A
linux-firmware1.94
SourcePackage: linux-lts-raring
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/15/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1015E.303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: 1015E
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1015E.303:bd03/15/2013:svnASUSTeKCOMPUTERINC.:pn1015E:pvr1.0:rvnASUSTeKCOMPUTERINC.:rn1015E:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: 1015E
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1277959/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811425] Re: linux-kvm: 4.15.0-1029.29 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 - phase: Testing -- security-signoff needed - phase-changed: Tuesday, 15. January 2019 11:33 UTC + phase: Testing -- regression-testing in progress + phase-changed: Tuesday, 15. January 2019 12:04 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- 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/1811425 Title: linux-kvm: 4.15.0-1029.29 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 phase: Testing -- regression-testing in progress phase-changed: Tuesday, 15. January 2019 12:04 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811425/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811414] Re: linux-aws: 4.18.0-1008.10 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 - phase: Testing -- security-signoff needed - phase-changed: Tuesday, 15. January 2019 11:33 UTC + phase: Testing -- regression-testing in progress + phase-changed: Tuesday, 15. January 2019 12:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- 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/1811414 Title: linux-aws: 4.18.0-1008.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 phase: Testing -- regression-testing in progress phase-changed: Tuesday, 15. January 2019 12:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811414/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811815] 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/1811815 Title: Ubuntu 18.10, Kernel 4.18, Intel Dual Band Wireless-AC 3165 Not Found Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.10 does not detect the Intel Dual Band Wireless-AC 3165 card, specifically on a Lenovo ideapad 330 laptop. A current workaround: - Blacklist the "ideapad-laptop" module. - Edit/create a file in "/etc/modprobe.d/" and name it "blacklist.conf" or something similar (if it does not already exist), and append "blacklist ideapad-laptop" to the file. Save and reboot. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dustin 1948 F pulseaudio /dev/snd/pcmC0D0p: dustin 1948 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 15 04:08:20 2019 InstallationDate: Installed on 2019-01-15 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:210e Acer, Inc Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 3938:1047 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81FK ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=fa5d161c-779c-4cf7-aa07-6da06d655747 ro acpi_osi=! "acpi_osi=Windows 2012" quiet splash nouveau.modeset=0 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN28WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ICH dmi.modalias: dmi:bvnLENOVO:bvr7ZCN28WW:bd07/17/2018:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH: dmi.product.family: ideapad 330-15ICH dmi.product.name: 81FK dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH dmi.product.version: Lenovo ideapad 330-15ICH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810619] Re: Sleep mode doesn't work
> Do you mean a fully charged battery only lasts 4 ~ 6 hours? I will do some other tests next days but if a suspend my laptop at 1:00 with a battery loaded about 40%, when I try to resume at 7:00, the laptop refuse to resume (battery empty). I have to plug in the charger in order to resume (normal boot because a halt was certainly requested by the system on battery low). With : $ sudo sh -c 'echo mem > /sys/power/state' $ sudo sh -c 'echo deep > /sys/power/mem_sleep' the problem disappears. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810619 Title: Sleep mode doesn't work Status in linux package in Ubuntu: Confirmed Bug description: On my Dell XPS 13 laptop (9370), the sleep mode dosn't work anymore with linux-image-4.18.0-13. The screen goes off correctly but any touch resume the laptop. This is the log : Jan 5 11:15:25 skeleton systemd[1]: Reached target Sleep. Jan 5 11:15:25 skeleton systemd[1]: Starting Suspend... Jan 5 11:15:25 skeleton systemd[1]: Starting Network Manager Script Dispatcher Service... Jan 5 11:15:25 skeleton systemd-sleep[6229]: Suspending system... Jan 5 11:15:25 skeleton kernel: [ 6176.006021] PM: suspend entry (s2idle) an 5 11:15:25 skeleton dbus-daemon[1051]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Jan 5 11:15:25 skeleton systemd[1]: Started Network Manager Script Dispatcher Service. Jan 5 11:15:25 skeleton nm-dispatcher: req:1 'down' [wlp2s0]: new request (1 scripts) Jan 5 11:15:25 skeleton nm-dispatcher: req:1 'down' [wlp2s0]: start running ordered scripts... [...] Resume : Jan 5 12:00:02 skeleton kernel: [ 6176.006023] PM: Syncing filesystems ... done. Jan 5 12:00:02 skeleton kernel: [ 6176.016581] Freezing user space processes ... (elapsed 0.088 seconds) done. Jan 5 12:00:02 skeleton kernel: [ 6176.104653] OOM killer disabled. Jan 5 12:00:02 skeleton kernel: [ 6176.104654] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Jan 5 12:00:02 skeleton kernel: [ 6176.106070] Suspending console(s) (use no_console_suspend to debug) Jan 5 12:00:02 skeleton kernel: [ 8852.990035] OOM killer enabled. Jan 5 12:00:02 skeleton kernel: [ 8852.990037] Restarting tasks ... done. Jan 5 12:00:02 skeleton kernel: [ 8853.015639] r8152 2-1.2:1.0 enxe4b97acfa7e9: carrier on Jan 5 12:00:02 skeleton kernel: [ 8853.084055] PM: suspend exit With linux-image-4.18.0-10, it works correcly (but no with 4.18.0-11 and 4.18.0-12). Thanks, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811825] [NEW] linux: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/snap-certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/snap-release-to-beta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-candidate Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-edge Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-stable Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa-dnu Importance: Medium Status: Invalid ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Xenial) Importance: Medium Status: Confirmed ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2019.01.14-1 kernel-sru-master-kernel xenial ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Tags added: xenial ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-beta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-candidate Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-edge
[Kernel-packages] [Bug 1810619] Re: Sleep mode doesn't work
Does that also happen to the test kernel I built? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810619 Title: Sleep mode doesn't work Status in linux package in Ubuntu: Confirmed Bug description: On my Dell XPS 13 laptop (9370), the sleep mode dosn't work anymore with linux-image-4.18.0-13. The screen goes off correctly but any touch resume the laptop. This is the log : Jan 5 11:15:25 skeleton systemd[1]: Reached target Sleep. Jan 5 11:15:25 skeleton systemd[1]: Starting Suspend... Jan 5 11:15:25 skeleton systemd[1]: Starting Network Manager Script Dispatcher Service... Jan 5 11:15:25 skeleton systemd-sleep[6229]: Suspending system... Jan 5 11:15:25 skeleton kernel: [ 6176.006021] PM: suspend entry (s2idle) an 5 11:15:25 skeleton dbus-daemon[1051]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Jan 5 11:15:25 skeleton systemd[1]: Started Network Manager Script Dispatcher Service. Jan 5 11:15:25 skeleton nm-dispatcher: req:1 'down' [wlp2s0]: new request (1 scripts) Jan 5 11:15:25 skeleton nm-dispatcher: req:1 'down' [wlp2s0]: start running ordered scripts... [...] Resume : Jan 5 12:00:02 skeleton kernel: [ 6176.006023] PM: Syncing filesystems ... done. Jan 5 12:00:02 skeleton kernel: [ 6176.016581] Freezing user space processes ... (elapsed 0.088 seconds) done. Jan 5 12:00:02 skeleton kernel: [ 6176.104653] OOM killer disabled. Jan 5 12:00:02 skeleton kernel: [ 6176.104654] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Jan 5 12:00:02 skeleton kernel: [ 6176.106070] Suspending console(s) (use no_console_suspend to debug) Jan 5 12:00:02 skeleton kernel: [ 8852.990035] OOM killer enabled. Jan 5 12:00:02 skeleton kernel: [ 8852.990037] Restarting tasks ... done. Jan 5 12:00:02 skeleton kernel: [ 8853.015639] r8152 2-1.2:1.0 enxe4b97acfa7e9: carrier on Jan 5 12:00:02 skeleton kernel: [ 8853.084055] PM: suspend exit With linux-image-4.18.0-10, it works correcly (but no with 4.18.0-11 and 4.18.0-12). Thanks, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811406] Re: linux: 4.18.0-14.15 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1811407 (linux-hwe), bug 1811408 (linux-hwe-edge), bug 1811409 (linux-aws-edge), bug 1811410 (linux-azure-edge), bug 1811411 (linux-gcp-edge), bug 1811418 (linux-azure-edge) derivatives: bug 1811412 (linux-raspi2), bug 1811414 (linux-aws), bug 1811415 (linux-azure), bug 1811416 (linux-gcp), bug 1811417 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true - phase: Testing -- certification-testing in progress - phase-changed: Tuesday, 15. January 2019 13:31 UTC + phase: Testing -- security-signoff needed + phase-changed: Tuesday, 15. January 2019 14:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing 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/1811406 Title: linux: 4.18.0-14.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1811407 (linux-hwe), bug 1811408 (linux-hwe-edge), bug 1811409 (linux-aws-edge), bug 1811410 (linux-azure-edge), bug 1811411 (linux-gcp-edge), bug 1811418 (linux-azure-edge) derivatives: bug 1811412 (linux-raspi2), bug 1811414 (linux-aws), bug 1811415 (linux-azure), bug 1811416 (linux-gcp), bug 1811417 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing -- security-signoff needed phase-changed: Tuesday, 15. January 2019 14:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811406/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811834] Re: Disco update: 4.19.15 upstream stable release
** Description changed:
+ SRU Justification
- 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:
- 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:
+ 4.19.15 upstream stable release
+ from git://git.kernel.org/
-4.19.15 upstream stable release
-from git://git.kernel.org/
-
-
Linux 4.19.15
bnx2x: Fix NULL pointer dereference in bnx2x_del_all_vlans() on some hw
drm/amd/display: Fix unintialized max_bpc state values
drm/rockchip: psr: do not dereference encoder before it is null checked.
drm/vc4: Set ->is_yuv to false when num_planes == 1
drm/nouveau/drm/nouveau: Check rc from drm_dp_mst_topology_mgr_resume()
lib: fix build failure in CONFIG_DEBUG_VIRTUAL test
of: __of_detach_node() - remove node from phandle cache
of: of_node_get()/of_node_put() nodes held in phandle cache
power: supply: olpc_battery: correct the temperature units
intel_th: msu: Fix an off-by-one in attribute store
genwqe: Fix size check
drivers/perf: hisi: Fixup one DDRC PMU register offset
video: fbdev: pxafb: Fix "WARNING: invalid free of devm_ allocated data"
ceph: don't update importing cap's mseq when handing cap export
sched/fair: Fix infinite loop in update_blocked_averages() by reverting
a9e7f6544b9c
iommu/vt-d: Handle domain agaw being less than iommu agaw
RDMA/srpt: Fix a use-after-free in the channel release code
rxe: fix error completion wr_id and qp_num
9p/net: put a lower bound on msize
iio: dac: ad5686: fix bit shift read register
powerpc/tm: Set MSR[TS] just prior to recheckpoint
Revert "powerpc/tm: Unset MSR[TS] if not recheckpointing"
leds: pwm: silently error out on EPROBE_DEFER
arm64: relocatable: fix inconsistencies in linker script and options
arm64: drop linker script hack to hide __efistub_ symbols
nfsd4: zero-length WRITE should succeed
lockd: Show pid of lockd for remote locks
PCI / PM: Allow runtime PM without callback functions
selinux: policydb - fix byte order and alignment issues
b43: Fix error in cordic routine
gfs2: Fix loop in gfs2_rbm_find
gfs2: Get rid of potential double-freeing in gfs2_create_inode
dlm: memory leaks on error path in dlm_user_request()
dlm: lost put_lkb on error path in receive_convert() and receive_unlock()
dlm: possible memory leak on error path in create_lkb()
dlm: fixed memory leaks after failed ls_remove_names allocation
block: mq-deadline: Fix write completion handling
block: deactivate blk_stat timer in wbt_disable_default()
Fix failure path in alloc_pid()
driver core: Add missing dev->bus->need_parent_lock checks
srcu: Lock srcu_data structure in srcu_gp_start()
ALSA: usb-audio: Always check descriptor sizes in parser code
ALSA: usb-audio: Fix an out-of-bound read in create_composite_quirks
ALSA: usb-audio: Check mixer unit descriptors more strictly
ALSA: usb-audio: Avoid access before bLength check in build_audio_procunit()
ALSA: cs46xx: Potential NULL dereference in probe
media: cx23885: only reset DMA on problematic CPUs
mt76x0: init hw capabilities
dma-direct: do not include SME mask in the DMA supported check
raid6/ppc: Fix build for clang
powerpc/boot: Set target when cross-compiling for clang
Makefile: Export clang toolchain variables
kbuild: consolidate Clang compiler flags
kbuild: add -no-integrated-as Clang option unconditionally
powerpc: Disable -Wbuiltin-requires-header when setjmp is used
powerpc: avoid -mno-sched-epilog on GCC 4.9 and newer
powerpc: consolidate -mno-sched-epilog into FTRACE flags
powerpc: remove old GCC version checks
sunrpc: use SVC_NET() in svcauth_gss_* functions
sunrpc: fix cache_head leak due to queued request
memcg, oom: notify on oom killer invocation from the charge path
mm, swap: fix swapoff with KSM pages
mm, hmm: mark hmm_devmem_{add, add_resource} EXPORT_SYMBOL_GPL
mm, hmm: use devm semantics for hmm_devmem_{add, remove}
mm, devm_memremap_pages: add MEMORY_DEVICE_PRIVATE support
mm, devm_memremap_pages: fix shutdown handling
mm, devm_memremap_pages: kill mapping "System RAM" support
mm, devm_memremap_pages: mark devm_memremap_pages() EXPORT_SYMBOL_GPL
[Kernel-packages] [Bug 1811414] Re: linux-aws: 4.18.0-1008.10 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 - phase: Testing -- security-signoff needed - phase-changed: Tuesday, 15. January 2019 13:06 UTC + phase: Testing -- regression-testing in progress + phase-changed: Tuesday, 15. January 2019 14:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- 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/1811414 Title: linux-aws: 4.18.0-1008.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 phase: Testing -- regression-testing in progress phase-changed: Tuesday, 15. January 2019 14:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811414/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811846] [NEW] linux: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1811847 (linux-aws), bug 1811848 (linux-lts-xenial) derivatives: bug 1811851 (linux-aws), bug 1811852 (linux-euclid), bug 1811853 (linux-kvm), bug 1811854 (linux-raspi2), bug 1811855 (linux-snapdragon) ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/snap-certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/snap-release-to-beta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-candidate Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-edge Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-stable Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa-dnu Importance: Medium Status: Invalid ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Xenial) Importance: Medium Status: Confirmed ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2019.01.14-1 kernel-sru-master-kernel xenial ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Tags added: xenial ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-certification-testing Importance: Undecided Status: New ** Also affects:
[Kernel-packages] [Bug 1811847] [NEW] linux-aws: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1811846 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa-dnu Importance: Medium Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-aws (Ubuntu Trusty) Importance: Medium Status: Confirmed ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-backport-of-1811846 kernel-sru-cycle-2019.01.14-1 trusty ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-aws (Ubuntu Trusty) Importance: Undecided Status: New ** Tags added: trusty ** Changed in: linux-aws (Ubuntu Trusty) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa-dnu Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Ubuntu Stable Release Updates
[Kernel-packages] [Bug 1811423] Re: linux-azure: 4.15.0-1037.39 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1811419 phase: Packaging -- packaging in progress phase-changed: Monday, 14. January 2019 16:01 UTC reason: - prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1811423 Title: linux-azure: 4.15.0-1037.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1811419 phase: Packaging -- packaging in progress phase-changed: Monday, 14. January 2019 16:01 UTC reason: prepare-package-meta: Pending -- package not yet uploaded promote-to-proposed: Ongoing -- builds not complete To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811423/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811415] Re: linux-azure: 4.18.0-1008.8 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1811415 Title: linux-azure: 4.18.0-1008.8 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 phase: Promote to Proposed -- release to Proposed in progress phase-changed: Tuesday, 15. January 2019 10:01 UTC reason: promote-to-proposed: Ongoing -- packages copies requested To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811415/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811415] Re: linux-azure: 4.18.0-1008.8 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 phase: Promote to Proposed -- release to Proposed in progress phase-changed: Tuesday, 15. January 2019 10:01 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Ongoing -- packages copies requested -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1811415 Title: linux-azure: 4.18.0-1008.8 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 phase: Promote to Proposed -- release to Proposed in progress phase-changed: Tuesday, 15. January 2019 10:01 UTC reason: promote-to-proposed: Ongoing -- packages copies requested To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811415/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743026] Re: qemu-nbd -c /dev/nbd0 fails to map partitions
is there a way to workaround this problems? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1743026 Title: qemu-nbd -c /dev/nbd0 fails to map partitions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: [impact] 4.4.0-101+ (also 4.4.0-109) Ubuntu kernels no longer can use qemu-nbd to mount virtual disks onto a local filesystem (see test case for reproducer). 4.4.0-98 works without issue. I was able to bisect the issue down to 907196aba0d891c6d580abe69c36d3b4fd512dcc (a cherry-pick from 37091fdd831f28a6509008542174ed324dd645bc). Reverting this from 4.4 fixes the issue. Installing the mainline kernel shows mainline is _not_ affected by this bug. In addition this is also reported in debian here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829532 [test case] # given a vmdk disk with multiple partitions sudo modprobe nbd sudo qemu-nbd -d /dev/nbd0 sudo qemu-nbd -r -c /dev/nbd0 disk.vmdk ls /dev/nbd0* # here you won't see multiple partition, nor be able to mount a partition locally To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743026/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801102] Re: Bionic shows incorrect warning about number of pointers in TFD
It is all good now. ** Tags removed: bionic verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801102 Title: Bionic shows incorrect warning about number of pointers in TFD Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: ===SRU Justification=== [Impact] iwlwifi spews "Too many chunks: 20" in dmesg. [Fix] From the patch description: " When we free the TFD, we check its number of valid pointers and make sure it doesn't exceed the number of pointers the hardware support. This check had an off by one bug: it is perfectly valid to free the 20 pointers if the TFD has 20 pointers. " [Test] User confirms the patch solves the problem. [Regression Potential] Low. The fix is limited to iwlwifi, and the patch is in mainline for a while. ===Original Bug Report=== Hi: I am having the same issue i.e. when downloading torrent with KTorrent. Please include this fix https://www.spinics.net/lists/linux- wireless/msg169994.html in the release kernel. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801102/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807686] Re: efi-lockdown patch causes -EPERM for some debugfs files even though CONFIG_LOCK_DOWN_KERNEL is not set
--- Comment From dominik.kl...@de.ibm.com 2019-01-15 06:42 EDT--- Just confirmed that the fix in cosmic-proposed is working: linux-image-4.18.0-13-generic - doesn't work linux-image-4.18.0-14-generic - works ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807686 Title: efi-lockdown patch causes -EPERM for some debugfs files even though CONFIG_LOCK_DOWN_KERNEL is not set Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: == Comment: #0 - Dominik Klein - 2018-12-10 03:58:10 == There seems to be a bug in the efi-lockdown patch as applied on top of vanilla for Cosmic kernels: http://kernel.ubuntu.com/git/ubuntu/ubuntu-cosmic.git/commit/fs/debugfs/file.c?id=a1ba65da9ceae481c154bfd1a2c1550e4566d986 Also seems to be present for Disco as of today: http://kernel.ubuntu.com/git/ubuntu/ubuntu-disco.git/commit/fs/debugfs/file.c?id=a1ba65da9ceae481c154bfd1a2c1550e4566d986 The problem is that part of the patch modifies kernel behavior independently of CONFIG_LOCK_DOWN_KERNEL being set or not causing issues on two debugfs files on s390x. Vasily Gorbik has already analyzed the problem and has posted a proposed fix here: https://lkml.org/lkml/2018/11/21/634 https://lkml.org/lkml/2018/11/21/635 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1807686/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811419] Re: linux: 4.15.0-44.47 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1811429 (linux-azure), bug 1811430 (linux-aws-hwe), bug 1811431 (linux-azure), bug 1811432 (linux-gcp), bug 1811434 (linux-hwe), bug 1811435 (linux-hwe-edge), bug 1811436 (linux-oracle) derivatives: bug 1811420 (linux-raspi2), bug 1811421 (linux-oem), bug 1811422 (linux-aws), bug 1811423 (linux-azure), bug 1811424 (linux-gcp), bug 1811425 (linux-kvm), bug 1811427 (linux-oracle) -- swm properties -- boot-testing-requested: true bugs-spammed: true - phase: Promote to Proposed -- snap release to beta ready - phase-changed: Tuesday, 15. January 2019 12:32 UTC + phase: Promote to Proposed -- snap release to edge ready + phase-changed: Tuesday, 15. January 2019 14:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel verification-testing: Ongoing -- testing 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/1811419 Title: linux: 4.15.0-44.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1811429 (linux-azure), bug 1811430 (linux-aws-hwe), bug 1811431 (linux-azure), bug 1811432 (linux-gcp), bug 1811434 (linux-hwe), bug 1811435 (linux-hwe-edge), bug 1811436 (linux-oracle) derivatives: bug 1811420 (linux-raspi2), bug 1811421 (linux-oem), bug 1811422 (linux-aws), bug 1811423 (linux-azure), bug 1811424 (linux-gcp), bug 1811425 (linux-kvm), bug 1811427 (linux-oracle) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promote to Proposed -- snap release to edge ready phase-changed: Tuesday, 15. January 2019 14:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811419/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811416] Re: linux-gcp: 4.18.0-1006.7 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1811406 - phase: Packaging -- packaging in progress - phase-changed: Tuesday, 15. January 2019 11:04 UTC + phase: Packaging -- uploaded + phase-changed: Tuesday, 15. January 2019 14:05 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1811416 Title: linux-gcp: 4.18.0-1006.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1811406 phase: Packaging -- uploaded phase-changed: Tuesday, 15. January 2019 14:05 UTC reason: promote-to-proposed: Ongoing -- builds not complete To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811566] Re: Backported commit breaks audio (fixed upstream)
** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Assignee: Po-Hsu Lin (cypressyew) Status: In Progress ** Changed in: linux (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Cosmic) 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/1811566 Title: Backported commit breaks audio (fixed upstream) Status in linux package in Ubuntu: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: In Progress Bug description: == Justification == Commit 648e921888ad96ea3dc922739e96716ad3225d7f (clk: x86: Stop marking clocks as CLK_IS_CRITICAL) backported to Cosmic kernel fixed the bug that keeps unused clocks on, but it is breaking the audio support on some Chromebooks (Swanky / Clapper/ Gnawty) since we were not using the right clock in the cht_bsw_max98090_ti machine driver. == Fix == a182ecd (ASoC: intel: cht_bsw_max98090_ti: Add quirk for boards using pmc_plt_clk_0) 984bfb3 (ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk) 94ea56c (ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk) These 3 patches can be cherry-picked to Cosmic. == Test == Test kernel with these 3 patches could be found in: http://people.canonical.com/~phlin/kernel/lp-1811566-chromebook-Gnawty/ Bug reporter stated that this kernel can fix the audio issue as expected. == Regression potential == Low, changes are limited in the cht_bsw_max98090_ti driver with a new DMI based quirk table that contains these 3 Chromebook models and some logic to determine the right clock to use. It seems that commit 648e921888ad96ea3dc922739e96716ad3225d7f was backported to ubuntu's 4.18 kernel. That commit breaks audio for some devices (chromebook gnawty) (from 4.19 on). Now 4.19, 4.20, 5.0 are fixed, with patch on commit: 47148001ae12292984ba1b38d9babefb9a46cd3e ASoC: intel: cht_bsw_max98090_ti: Add pmc_plt_clk_0 quirk for Chromebook Gnawty Bug reported: https://bugzilla.kernel.org/show_bug.cgi?id=201787 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811566/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805802] Re: [UBUNTU] qeth: fix length check in SNMP processing
adjusting tags according to #6
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1805802
Title:
[UBUNTU] qeth: fix length check in SNMP processing
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Status in linux source package in Disco:
Fix Committed
Bug description:
== SRU Justification ==
The response for a SNMP request can consist of multiple parts,
which the cmd callback stages into a kernel buffer until all
parts have been received. If the callback detects that the
staging buffer provides insufficient space, it bails out with
error.
This processing is buggy for the first part of the response -
while it initially checks for a length of 'data_len', it later
copies an additional amount of
'offsetof(struct qeth_snmp_cmd, data)' bytes.
== Fix ==
9a764c1e5968 ("s390/qeth: fix length check in SNMP processing")
== Regression Potential ==
Low. Changes limited to s390.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Original bug description ==
Description: qeth: fix length check in SNMP processing
Symptom: Undefined behaviour.
Problem: The response for a SNMP request can consist of multiple parts,
which the cmd callback stages into a kernel buffer until all
parts have been received. If the callback detects that the
staging buffer provides insufficient space, it bails out with
error.
This processing is buggy for the first part of the response -
while it initially checks for a length of 'data_len', it later
copies an additional amount of
'offsetof(struct qeth_snmp_cmd, data)' bytes.
Solution: Fix the calculation of 'data_len' for the first part of the
response.
Upstream-ID: 9a764c1e59684c0358e16ccaafd870629f2cfe67
Should be applied to all Ubuntu Releases in Service
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1805802/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752165] Re: TB16 dock freezes X on hotplug when used with external displays
Following kernel seems to fix the issue (running on 18.10 with kernel installed by UKUU): 4.20.0-042000-generic #201812232030 SMP Mon Dec 24 01:32:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I still see one or two of these errors when hotplugging but the others are gone and the external screen works: [drm:intel_mst_pre_enable_dp [i915]] *ERROR* failed to allocate vcpi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752165 Title: TB16 dock freezes X on hotplug when used with external displays Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: Precision 5520 with Quadro GPU. Latest Ubuntu 16.04, kernel Linux REDACTED 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux, latest BIOS 1.7.0 released 12/15/2017. If it can be of any help, I can get this tested on an XPS 9560 (GTX 1050) too. Steps to reproduce: 1. Plug in monitors into DP and miniDP on the dock. In my case, DP-to-DVI cables are used, but I doubt that it matters. 2. Ubuntu 16.04 GNOME + nVidia drivers with PRIME. 3. Select nVidia GPU in PRIME settings, reboot if needed. 4. Either boot with the dock connected or connect it after booting into user session. 5. Set up monitors if necessary. At this point everything should be working fine. 6. Disconnect the dock, give it a moment to adjust to the new window layout etc. 7. Re-connect the dock. Within a few seconds laptop screen should freeze and external monitors should remain blank, as if not connected. 8. Disconnect the dock. Within a few seconds laptop screen should unfreeze. There is a small chance that it won't if you repeat this procedure multiple times. Errors in dmesg indicate that i915 driver is somehow involved: [ 328.966128] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 328.967848] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF B idle bit [ 329.048839] [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns [ 329.050547] [drm:intel_wait_ddi_buf_idle [i915]] *ERROR* Timeout waiting for DDI BUF C idle bit The kernel logs are flooded with these between steps 7 and 8 above. This behaviour does not occur when Intel GPU is selected in PRIME settings or when nouveau is used. However, nouveau performance leaves a lot to be desired, particularly with 3D acceleration in Windows 10 VMs. I have tried nvidia_drm.modeset=1 in boot options, but it doesn't make any difference. Other reports that may be related: https://devtalk.nvidia.com/default/topic/989704/linux/plugging-a -docking-station-w-two-monitors-into-a-quadro-m1000m-laptop-crashes- hangs-the-whole-machine/ - same error messages https://www.reddit.com/r/Dell/comments/5nas3t/tb16_dock_with_5510_ubuntulinux/ddzjlu8/?st=je63h7lw=40bf8189 - "Connecting and disconnecting the TB16 sometimes freeze the laptop." https://www.dell.com/community/Sputnik/TB16-Dock-Linux-Support/m-p/5109128/highlight/true#M7466 - "Hot-plugging the screen does not work." --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gboiko 2491 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=08bba264-8658-442f-995d-6a745925ac6c InstallationDate: Installed on 2017-10-01 (149 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:24a1 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic root=/dev/mapper/ubuntu--gnome--vg-root ro ipv6.disable=1 net.ifnames=0 biosdevname=0 nvidia_drm.modeset=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.170 Tags: xenial Uname: Linux 4.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/15/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0R6JFH dmi.board.vendor: Dell Inc.
[Kernel-packages] [Bug 1803891] Re: package nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1 failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in packag
I got the same as above, except I'm coming from 16.04.5. The other thing is I only upgrade from 16.04.5 because I couldn't actually boot into it. See bug here: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1800250 I had to upgrade using the debian-method because all normal Ubunutu upgrade paths would not work for me - and although I'm not one to give up a fight on fixing a bug, I had to because I need this system for work. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1803891 Title: package nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1 failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-384 384.130-0ubuntu0.16.04.1 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: upgrade from 16.04.03 > 18.04.01 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Nov 18 17:07:05 2018 Dependencies: ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-384 384.130-0ubuntu0.16.04.1 InstallationDate: Installed on 2013-10-12 (1862 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1 failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-384 384.130-0ubuntu0.16.04.1 UpgradeStatus: Upgraded to bionic on 2018-11-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1803891/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811423] Re: linux-azure: 4.15.0-1037.39 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 - phase: Promote to Proposed -- release to Proposed ready - phase-changed: Tuesday, 15. January 2019 13:02 UTC + phase: Promote to Proposed -- release to Proposed in progress + phase-changed: Tuesday, 15. January 2019 14:04 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress -- 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/1811423 Title: linux-azure: 4.15.0-1037.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 phase: Promote to Proposed -- release to Proposed in progress phase-changed: Tuesday, 15. January 2019 14:04 UTC reason: promote-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811423/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811423] Re: linux-azure: 4.15.0-1037.39 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1811423 Title: linux-azure: 4.15.0-1037.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 phase: Promote to Proposed -- release to Proposed ready phase-changed: Tuesday, 15. January 2019 13:02 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811423/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811417] Re: linux-kvm: 4.18.0-1007.7 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1811406 - phase: Packaging -- ready to package - phase-changed: Monday, 14. January 2019 10:00 UTC + phase: Packaging -- packaging in progress + phase-changed: Tuesday, 15. January 2019 14:00 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded -- 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/1811417 Title: linux-kvm: 4.18.0-1007.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1811406 phase: Packaging -- packaging in progress phase-changed: Tuesday, 15. January 2019 14:00 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811417/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811254] Re: HP ProBook 470 G5, LED's in Hotkeys f5, f8 and f11 without function
** Description changed: Notebook: HP ProBook 470 G5 (3KZ03EA) Distro: Linux Mint 19.1 Tessa Desktop: Cinnamon 4.0.8 Kernel: 4.15.0-43-generic x86_64 bits: 64 The functions of all hotkeys are given, but the LEDs in the f5 LS-mute, f8 micro-mute and f11 wireless on/off buttons do not show the status. The LED in f11 is permanently lit. This is my first bug report to launchpad and I ask for leniency and troubleshooting support. I created 11 logs, unfortunately the upload did not work at once: acpi_listen.txt apt-cache-policy dmesg.log lsb_release lsinput.log lspci-vnvn.log udev-db.txt version.log xev keypress test.txt xkbcomp.txt xkbmap.txt - Previous attempts: - My on-board search for other hotkey LED-issues led me to this bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705586 + My on-board search for other HP ProBook Hotkey LED-issues led me to this bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705586 but the solution to the file: /etc/modprobe.d/alsa-base.conf to supplement the entry: options snd-hda-intel mode = mute-led-gpio did not lead to the solution here. Presumably, the failure results from a different ubuntu-version and/or a another kernel. Information: This problem was previously discussed on linuxmintusers.de: https://www.linuxmintusers.de/index.php?topic=51737.msg710376#msg710376 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811254 Title: HP ProBook 470 G5, LED's in Hotkeys f5, f8 and f11 without function Status in linux package in Ubuntu: Confirmed Bug description: Notebook: HP ProBook 470 G5 (3KZ03EA) Distro: Linux Mint 19.1 Tessa Desktop: Cinnamon 4.0.8 Kernel: 4.15.0-43-generic x86_64 bits: 64 The functions of all hotkeys are given, but the LEDs in the f5 LS- mute, f8 micro-mute and f11 wireless on/off buttons do not show the status. The LED in f11 is permanently lit. This is my first bug report to launchpad and I ask for leniency and troubleshooting support. I created 11 logs, unfortunately the upload did not work at once: acpi_listen.txt apt-cache-policy dmesg.log lsb_release lsinput.log lspci-vnvn.log udev-db.txt version.log xev keypress test.txt xkbcomp.txt xkbmap.txt Previous attempts: My on-board search for other HP ProBook Hotkey LED-issues led me to this bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705586 but the solution to the file: /etc/modprobe.d/alsa-base.conf to supplement the entry: options snd-hda-intel mode = mute-led-gpio did not lead to the solution here. Presumably, the failure results from a different ubuntu-version and/or a another kernel. Information: This problem was previously discussed on linuxmintusers.de: https://www.linuxmintusers.de/index.php?topic=51737.msg710376#msg710376 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811853] [NEW] linux-kvm: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1811846 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa-dnu Importance: Medium Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-kvm (Ubuntu Xenial) Importance: Medium Status: Confirmed ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2019.01.14-1 kernel-sru-derivative-of-1811846 xenial ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-kvm (Ubuntu Xenial) Importance: Undecided Status: New ** Tags added: xenial ** Changed in: linux-kvm (Ubuntu Xenial) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa-dnu Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Ubuntu Stable Release Updates
[Kernel-packages] [Bug 1811851] [NEW] linux-aws: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1811846 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/snap-release-to-beta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-candidate Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-edge Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-stable Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa-dnu Importance: Medium Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-aws (Ubuntu Xenial) Importance: Medium Status: Confirmed ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2019.01.14-1 kernel-sru-derivative-of-1811846 xenial ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-aws (Ubuntu Xenial) Importance: Undecided Status: New ** Tags added: xenial ** Changed in: linux-aws (Ubuntu Xenial) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-beta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-candidate Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-edge Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-stable Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa-dnu Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in:
[Kernel-packages] [Bug 1811850] [NEW] linux-ibm-gt: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa-dnu Importance: Medium Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2019.01.14-1 ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Tags added: bionic ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa-dnu Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru) ** Changed in: kernel-sru-workflow/promote-to-security Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-security Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru) ** Changed in: kernel-sru-workflow/promote-to-updates Importance: Undecided => Medium ** Changed
[Kernel-packages] [Bug 1794387] Re: Colour banding in HP Pavilion 15-n233sl integrated display
Using kernel 4.18.0-14-generic from cosmic-proposed fixes the issue. Thanks! ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1794387 Title: Colour banding in HP Pavilion 15-n233sl integrated display Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Fix Committed Bug description: Colour bandind is visible everywhere in the system, and it appeared after I had my integrated monitor replaced. I believe it's not a hardware problem, since booting with 'nomodeset' works as expected. There were already two similar bugs, https://bugs.launchpad.net/bugs/1749420 and https://bugs.launchpad.net/bugs/1788308, but the fixes provided for those bugs did not work for my specific monitor. I'm running Ubuntu 18.04 with kernel linux-image-4.15.0-34-generic, installing linux-image-4.18.8 with UKUU didn't help. I attached the results of running sudo get-edid | parse-edid in a file named edid.txt sudo get-edid | edid-decode in a file named edid-decoded.txt cat /proc/version_signature in version.log sudo lspci -vnvn in lspci-vnvn.log. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matt 1796 F pulseaudio /dev/snd/controlC1: matt 1796 F pulseaudio CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2018-09-27 (0 days ago) InstallationMedia: neon devunstable "Bionic" - Build amd64 LIVE Binary 20180924-13:08 Lsusb: Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b40e Chicony Electronics Co., Ltd HP Truevision HD camera Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=c3f61207-d13e-474b-a499-98030ddef8e1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UnreportableReason: Questa segnalazione riguarda un pacchetto che non è installato. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: False dmi.bios.date: 03/13/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.71 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2166 dmi.board.vendor: Hewlett-Packard dmi.board.version: 29.42 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.71:bd03/13/2017:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr098B1140410620180:rvnHewlett-Packard:rn2166:rvr29.42:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 098B1140410620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794387/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811803] 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 1811803 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811803 Title: Crash on "ip link add foo type ipip" Status in linux package in Ubuntu: Incomplete Bug description: On 4.18.0-13-generic #14-Ubuntu SMP Wed Dec 5 09:04:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux When I executed "sudo ip link add foo type ipip" kernel crashed, leaving the system working but mostly unusable (networking was flaky). dmesg showed: [156541.500970] ipip: IPv4 and MPLS over IPv4 tunneling driver [156541.502201] BUG: unable to handle kernel NULL pointer dereference at 0108 [156541.502207] PGD 0 P4D 0 [156541.502210] Oops: [#1] SMP PTI [156541.502213] CPU: 9 PID: 29001 Comm: ip Tainted: G OE 4.18.0-13-generic #14-Ubuntu [156541.502215] Hardware name: Dell Inc. XPS 15 9570/0HWTMH, BIOS 1.6.0 11/02/2018 [156541.502223] RIP: 0010:ipip_netlink_fan.isra.11+0x5/0x250 [ipip] [156541.502224] Code: d9 fe ff ff 48 8d 93 78 09 00 00 eb 93 48 89 de 4c 89 e7 e8 cd 78 fe ff eb c3 e8 c6 79 5d e8 66 0f 1f 44 00 00 0f 1f 44 00 00 <48> 8b 87 08 01 00 00 48 85 c0 0f 84 1a 02 00 00 8b 12 85 d2 0f 85 [156541.502245] RSP: 0018:bac005a2b588 EFLAGS: 00010246 [156541.502246] RAX: RBX: RCX: [156541.502248] RDX: bac005a2b5d0 RSI: 9c1122439900 RDI: [156541.502249] RBP: bac005a2b600 R08: R09: bac005a2b594 [156541.502250] R10: c0cb9120 R11: R12: 9c1122439000 [156541.502251] R13: 9c1122439900 R14: bac005a2b930 R15: aa805780 [156541.502253] FS: 7fe219348680() GS:9c136be4() knlGS: [156541.502254] CS: 0010 DS: ES: CR0: 80050033 [156541.502255] CR2: 0108 CR3: 00010f724001 CR4: 003606e0 [156541.502257] DR0: DR1: DR2: [156541.502258] DR3: DR6: fffe0ff0 DR7: 0400 [156541.502259] Call Trace: [156541.502265] ? ipip_newlink+0x8c/0xc6 [ipip] [156541.502273] rtnl_newlink+0x67b/0x8c0 [156541.502279] ? nla_parse+0x35/0xe0 [156541.502280] ? rtnl_newlink+0x12e/0x8c0 [156541.502288] ? get_page_from_freelist+0xf7e/0x1320 [156541.502298] ? mem_cgroup_commit_charge+0x82/0x530 [156541.502302] ? lru_cache_add_active_or_unevictable+0x39/0xb0 [156541.502309] ? handle_pte_fault+0x52c/0xbe0 [156541.502313] rtnetlink_rcv_msg+0x213/0x300 [156541.502318] ? copy_user_generic_unrolled+0x89/0xc0 [156541.502320] ? rtnl_calcit.isra.33+0x100/0x100 [156541.502327] netlink_rcv_skb+0x52/0x130 [156541.502329] rtnetlink_rcv+0x15/0x20 [156541.502331] netlink_unicast+0x1a4/0x260 [156541.502333] netlink_sendmsg+0x20b/0x3d0 [156541.502340] sock_sendmsg+0x3e/0x50 [156541.502342] ___sys_sendmsg+0x295/0x2f0 [156541.502344] ? handle_pte_fault+0x539/0xbe0 [156541.502347] ? __handle_mm_fault+0x42c/0x5b0 [156541.502350] __sys_sendmsg+0x5c/0xa0 [156541.502353] __x64_sys_sendmsg+0x1f/0x30 [156541.502358] do_syscall_64+0x5a/0x110 [156541.502361] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [156541.502364] RIP: 0033:0x7fe219682234 [156541.502365] Code: 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b5 0f 1f 80 00 00 00 00 48 8d 05 c9 d4 0c 00 8b 00 85 c0 75 13 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 c3 0f 1f 00 41 54 41 89 d4 55 48 89 f5 53 [156541.502390] RSP: 002b:7ffe5887fbe8 EFLAGS: 0246 ORIG_RAX: 002e [156541.502392] RAX: ffda RBX: 5c3dbcf0 RCX: 7fe219682234 [156541.502393] RDX: RSI: 7ffe5887fc50 RDI: 0003 [156541.502394] RBP: R08: 0001 R09: [156541.502396] R10: 0008 R11: 0246 R12: 0001 [156541.502397] R13: 5597e7c6c020 R14: 7ffe5887fd4c R15: [156541.502399] Modules linked in: ipip tunnel4 ip_tunnel veth sctp libcrc32c ses enclosure scsi_transport_sas uas usb_storage ath10k_pci thunderbolt rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm arc4 cmac bnep binfmt_misc
[Kernel-packages] [Bug 1811425] Re: linux-kvm: 4.15.0-1029.29 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 - phase: Promote to Proposed -- release to Proposed in progress - phase-changed: Tuesday, 15. January 2019 09:31 UTC + phase: Testing -- security-signoff needed + phase-changed: Tuesday, 15. January 2019 11:33 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress -- 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/1811425 Title: linux-kvm: 4.15.0-1029.29 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 phase: Testing -- security-signoff needed phase-changed: Tuesday, 15. January 2019 11:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811425/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811254] Re: HP ProBook 470 G5, LED's in Hotkeys f5, f8 and f11 without function
** Description changed: Notebook: HP ProBook 470 G5 (3KZ03EA) Distro: Linux Mint 19.1 Tessa Desktop: Cinnamon 4.0.8 Kernel: 4.15.0-43-generic x86_64 bits: 64 The functions of all hotkeys are given, but the LEDs in the f5 LS-mute, f8 micro-mute and f11 wireless on/off buttons do not show the status. The LED in f11 is permanently lit. This is my first bug report to launchpad and I ask for leniency and troubleshooting support. I created 11 logs, unfortunately the upload did not work at once: acpi_listen.txt apt-cache-policy dmesg.log lsb_release lsinput.log lspci-vnvn.log udev-db.txt version.log xev keypress test.txt xkbcomp.txt xkbmap.txt Information: This problem was previously discussed on linuxmintusers.de: https://www.linuxmintusers.de/index.php?topic=51737.msg710376#msg710376 + + + My on-board search for other hotkey LED-issues led me to this bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705586 + + but the solution to the file: /etc/modprobe.d/alsa-base.conf + + to supplement the entry: options snd-hda-intel mode = mute-led-gpio + + did not lead to the solution here. Presumably, the failure results from + a different ubuntu-version and/or a another kernel. ** Description changed: Notebook: HP ProBook 470 G5 (3KZ03EA) Distro: Linux Mint 19.1 Tessa Desktop: Cinnamon 4.0.8 Kernel: 4.15.0-43-generic x86_64 bits: 64 The functions of all hotkeys are given, but the LEDs in the f5 LS-mute, f8 micro-mute and f11 wireless on/off buttons do not show the status. The LED in f11 is permanently lit. This is my first bug report to launchpad and I ask for leniency and troubleshooting support. I created 11 logs, unfortunately the upload did not work at once: acpi_listen.txt apt-cache-policy dmesg.log lsb_release lsinput.log lspci-vnvn.log udev-db.txt version.log xev keypress test.txt xkbcomp.txt xkbmap.txt - Information: This problem was previously discussed on linuxmintusers.de: - https://www.linuxmintusers.de/index.php?topic=51737.msg710376#msg710376 - + Previous attempts: My on-board search for other hotkey LED-issues led me to this bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705586 but the solution to the file: /etc/modprobe.d/alsa-base.conf - to supplement the entry: options snd-hda-intel mode = mute-led-gpio did not lead to the solution here. Presumably, the failure results from a different ubuntu-version and/or a another kernel. + + Information: This problem was previously discussed on linuxmintusers.de: + https://www.linuxmintusers.de/index.php?topic=51737.msg710376#msg710376 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811254 Title: HP ProBook 470 G5, LED's in Hotkeys f5, f8 and f11 without function Status in linux package in Ubuntu: Confirmed Bug description: Notebook: HP ProBook 470 G5 (3KZ03EA) Distro: Linux Mint 19.1 Tessa Desktop: Cinnamon 4.0.8 Kernel: 4.15.0-43-generic x86_64 bits: 64 The functions of all hotkeys are given, but the LEDs in the f5 LS- mute, f8 micro-mute and f11 wireless on/off buttons do not show the status. The LED in f11 is permanently lit. This is my first bug report to launchpad and I ask for leniency and troubleshooting support. I created 11 logs, unfortunately the upload did not work at once: acpi_listen.txt apt-cache-policy dmesg.log lsb_release lsinput.log lspci-vnvn.log udev-db.txt version.log xev keypress test.txt xkbcomp.txt xkbmap.txt Previous attempts: My on-board search for other hotkey LED-issues led me to this bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705586 but the solution to the file: /etc/modprobe.d/alsa-base.conf to supplement the entry: options snd-hda-intel mode = mute-led-gpio did not lead to the solution here. Presumably, the failure results from a different ubuntu-version and/or a another kernel. Information: This problem was previously discussed on linuxmintusers.de: https://www.linuxmintusers.de/index.php?topic=51737.msg710376#msg710376 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811414] Re: linux-aws: 4.18.0-1008.10 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 - phase: Promote to Proposed -- release to Proposed in progress - phase-changed: Tuesday, 15. January 2019 10:03 UTC + phase: Testing -- security-signoff needed + phase-changed: Tuesday, 15. January 2019 11:33 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress -- 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/1811414 Title: linux-aws: 4.18.0-1008.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 phase: Testing -- security-signoff needed phase-changed: Tuesday, 15. January 2019 11:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811414/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811406] Re: linux: 4.18.0-14.15 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1811407 (linux-hwe), bug 1811408 (linux-hwe-edge), bug 1811409 (linux-aws-edge), bug 1811410 (linux-azure-edge), bug 1811411 (linux-gcp-edge), bug 1811418 (linux-azure-edge) derivatives: bug 1811412 (linux-raspi2), bug 1811414 (linux-aws), bug 1811415 (linux-azure), bug 1811416 (linux-gcp), bug 1811417 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true - phase: Testing -- security-signoff needed - phase-changed: Tuesday, 15. January 2019 11:00 UTC + phase: Testing -- regression-testing in progress + phase-changed: Tuesday, 15. January 2019 11:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing 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/1811406 Title: linux: 4.18.0-14.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1811407 (linux-hwe), bug 1811408 (linux-hwe-edge), bug 1811409 (linux-aws-edge), bug 1811410 (linux-azure-edge), bug 1811411 (linux-gcp-edge), bug 1811418 (linux-azure-edge) derivatives: bug 1811412 (linux-raspi2), bug 1811414 (linux-aws), bug 1811415 (linux-azure), bug 1811416 (linux-gcp), bug 1811417 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing -- regression-testing in progress phase-changed: Tuesday, 15. January 2019 11:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811406/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798583] Re: the new Steam Controller driver breaks it on Steam
I don't see anywhere to change/add tags by the way, I assume I don't have permissions? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798583 Title: the new Steam Controller driver breaks it on Steam Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Released Bug description: ===SRU Justification=== [Impact] New steam-hid driver breaks Unity games. [Fix] Quote from the commit message: "With this commit, when a HID client starts, the input device is removed; when the HID client ends the input device is recreated." [Test] A guy from Valve comfirms the backport works. [Regression Potential] Low. This fix is specific to hid-steam, which is a new driver introduced in v4.18. ===Original Bug Report=== The new hid_steam driver in kernel 4.18 breaks the use of it within Steam. Games either: - Crash - Don't detect it at all - Only pick it up as player 2 To get it working as normal, it needs blacklisting currently. See here: https://www.gamingonlinux.com/articles/the-steam-controller- on-ubuntu-1810-and-other-distributions-using-linux-kernel-418-needs- quick-a-fix.12775 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: liam 2492 F pulseaudio /dev/snd/controlC0: liam 2492 F pulseaudio /dev/snd/controlC1: liam 2492 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 18 12:49:44 2018 InstallationDate: Installed on 2017-10-18 (364 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. eno1 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=2a8676f3-0045-4e66-9cd1-186ffc6a8c2a ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-18 (0 days ago) dmi.bios.date: 08/10/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: PCS dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1901:bd08/10/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811832] Re: linux-kvm: -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1811825 + reason: + prepare-package: Stalled -- waiting for master bug -- 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/1811832 Title: linux-kvm: -proposed tracker Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1811825 reason: prepare-package: Stalled -- waiting for master bug To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811845] Re: package thermald (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 1
** Tags removed: need-duplicate-check -- 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/1811845 Title: package thermald (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 Status in thermald package in Ubuntu: New Bug description: error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: thermald (not installed) ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: qnx4 hfsplus hfs minix ntfs jfs rfcomm bnep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_realtek snd_hda_codec_generic sparse_keymap intel_cstate intel_rapl_perf snd_hda_intel snd_hda_codec snd_hda_core rtl8723ae btcoexist input_polldev rtl8723_common rtl_pci rtlwifi i2c_i801 mac80211 btusb btrtl btbcm btintel bluetooth lpc_ich cfg80211 jmb38x_ms memstick mei_me shpchp mei mac_hid i915 jme sdhci_pci sdhci wmi ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Jan 15 19:53:42 2019 ErrorMessage: subprocess installed post-removal script returned error exit status 1 InstallationDate: Installed on 2018-12-19 (26 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 SourcePackage: thermald Title: package thermald (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1811845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811825] Re: linux: -proposed tracker
** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Changed in: linux (Ubuntu Xenial) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811825 Title: linux: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-certification-testing series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811825/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811830] Re: linux-aws: -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Invalid ** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid ** Changed in: kernel-sru-workflow/upload-to-ppa-dnu Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Changed in: linux-aws (Ubuntu Xenial) Status: Confirmed => Invalid ** Tags removed: kernel-release-tracking-bug-live -- 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/1811830 Title: linux-aws: -proposed tracker Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow snap-release-to-beta series: Invalid Status in Kernel SRU Workflow snap-release-to-candidate series: Invalid Status in Kernel SRU Workflow snap-release-to-edge series: Invalid Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1811825 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811830/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811832] Re: linux-kvm: -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/upload-to-ppa-dnu Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Changed in: linux-kvm (Ubuntu Xenial) Status: Confirmed => Invalid ** Tags removed: kernel-release-tracking-bug-live -- 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/1811832 Title: linux-kvm: -proposed tracker Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1811825 reason: prepare-package: Stalled -- waiting for master bug To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811828] Re: linux-aws: -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/upload-to-ppa-dnu Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Changed in: linux-aws (Ubuntu Trusty) Status: Confirmed => Invalid ** Tags removed: kernel-release-tracking-bug-live -- 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/1811828 Title: linux-aws: -proposed tracker Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1811825 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811828/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811785] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1811785/+attachment/5229228/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1811785
Title:
NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840
Status in linux package in Ubuntu:
Confirmed
Status in ndctl package in Ubuntu:
New
Bug description:
On ubuntu 18.04.1 :
1°) With 4.15.0-43 two default namespaces in raw mode are visible
while there shouldn't be any but no settings change could be applied.
root@server:~# ndctl list -R
[
{
"dev":"region1",
"size":103079215104,
"available_size":0,
"type":"pmem",
"numa_node":1,
"persistence_domain":"unknown"
},
{
"dev":"region0",
"size":103079215104,
"available_size":0,
"type":"pmem",
"numa_node":0,
"persistence_domain":"unknown"
}
]
root@server:~# ndctl list
[
{
"dev":"namespace1.0",
"mode":"raw",
"size":103079215104,
"sector_size":512,
"blockdev":"pmem1",
"numa_node":1
},
{
"dev":"namespace0.0",
"mode":"raw",
"size":103079215104,
"sector_size":512,
"blockdev":"pmem0",
"numa_node":0
}
]
root@server:~# ndctl create-namespace --reconfig=namespace1.0 --type=pmem
--mode=sector -f
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
[Kernel-packages] [Bug 1811785] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1811785/+attachment/5229230/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1811785
Title:
NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840
Status in linux package in Ubuntu:
Confirmed
Status in ndctl package in Ubuntu:
New
Bug description:
On ubuntu 18.04.1 :
1°) With 4.15.0-43 two default namespaces in raw mode are visible
while there shouldn't be any but no settings change could be applied.
root@server:~# ndctl list -R
[
{
"dev":"region1",
"size":103079215104,
"available_size":0,
"type":"pmem",
"numa_node":1,
"persistence_domain":"unknown"
},
{
"dev":"region0",
"size":103079215104,
"available_size":0,
"type":"pmem",
"numa_node":0,
"persistence_domain":"unknown"
}
]
root@server:~# ndctl list
[
{
"dev":"namespace1.0",
"mode":"raw",
"size":103079215104,
"sector_size":512,
"blockdev":"pmem1",
"numa_node":1
},
{
"dev":"namespace0.0",
"mode":"raw",
"size":103079215104,
"sector_size":512,
"blockdev":"pmem0",
"numa_node":0
}
]
root@server:~# ndctl create-namespace --reconfig=namespace1.0 --type=pmem
--mode=sector -f
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small
[Kernel-packages] [Bug 1811785] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1811785/+attachment/5229233/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1811785
Title:
NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840
Status in linux package in Ubuntu:
Confirmed
Status in ndctl package in Ubuntu:
New
Bug description:
On ubuntu 18.04.1 :
1°) With 4.15.0-43 two default namespaces in raw mode are visible
while there shouldn't be any but no settings change could be applied.
root@server:~# ndctl list -R
[
{
"dev":"region1",
"size":103079215104,
"available_size":0,
"type":"pmem",
"numa_node":1,
"persistence_domain":"unknown"
},
{
"dev":"region0",
"size":103079215104,
"available_size":0,
"type":"pmem",
"numa_node":0,
"persistence_domain":"unknown"
}
]
root@server:~# ndctl list
[
{
"dev":"namespace1.0",
"mode":"raw",
"size":103079215104,
"sector_size":512,
"blockdev":"pmem1",
"numa_node":1
},
{
"dev":"namespace0.0",
"mode":"raw",
"size":103079215104,
"sector_size":512,
"blockdev":"pmem0",
"numa_node":0
}
]
root@server:~# ndctl create-namespace --reconfig=namespace1.0 --type=pmem
--mode=sector -f
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte)
[Kernel-packages] [Bug 1811785] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1811785/+attachment/5229232/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1811785
Title:
NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840
Status in linux package in Ubuntu:
Confirmed
Status in ndctl package in Ubuntu:
New
Bug description:
On ubuntu 18.04.1 :
1°) With 4.15.0-43 two default namespaces in raw mode are visible
while there shouldn't be any but no settings change could be applied.
root@server:~# ndctl list -R
[
{
"dev":"region1",
"size":103079215104,
"available_size":0,
"type":"pmem",
"numa_node":1,
"persistence_domain":"unknown"
},
{
"dev":"region0",
"size":103079215104,
"available_size":0,
"type":"pmem",
"numa_node":0,
"persistence_domain":"unknown"
}
]
root@server:~# ndctl list
[
{
"dev":"namespace1.0",
"mode":"raw",
"size":103079215104,
"sector_size":512,
"blockdev":"pmem1",
"numa_node":1
},
{
"dev":"namespace0.0",
"mode":"raw",
"size":103079215104,
"sector_size":512,
"blockdev":"pmem0",
"numa_node":0
}
]
root@server:~# ndctl create-namespace --reconfig=namespace1.0 --type=pmem
--mode=sector -f
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256
[Kernel-packages] [Bug 1811785] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1811785/+attachment/5229226/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1811785
Title:
NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840
Status in linux package in Ubuntu:
Confirmed
Status in ndctl package in Ubuntu:
New
Bug description:
On ubuntu 18.04.1 :
1°) With 4.15.0-43 two default namespaces in raw mode are visible
while there shouldn't be any but no settings change could be applied.
root@server:~# ndctl list -R
[
{
"dev":"region1",
"size":103079215104,
"available_size":0,
"type":"pmem",
"numa_node":1,
"persistence_domain":"unknown"
},
{
"dev":"region0",
"size":103079215104,
"available_size":0,
"type":"pmem",
"numa_node":0,
"persistence_domain":"unknown"
}
]
root@server:~# ndctl list
[
{
"dev":"namespace1.0",
"mode":"raw",
"size":103079215104,
"sector_size":512,
"blockdev":"pmem1",
"numa_node":1
},
{
"dev":"namespace0.0",
"mode":"raw",
"size":103079215104,
"sector_size":512,
"blockdev":"pmem0",
"numa_node":0
}
]
root@server:~# ndctl create-namespace --reconfig=namespace1.0 --type=pmem
--mode=sector -f
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
[Kernel-packages] [Bug 1811785] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1811785/+attachment/5229234/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1811785
Title:
NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840
Status in linux package in Ubuntu:
Confirmed
Status in ndctl package in Ubuntu:
New
Bug description:
On ubuntu 18.04.1 :
1°) With 4.15.0-43 two default namespaces in raw mode are visible
while there shouldn't be any but no settings change could be applied.
root@server:~# ndctl list -R
[
{
"dev":"region1",
"size":103079215104,
"available_size":0,
"type":"pmem",
"numa_node":1,
"persistence_domain":"unknown"
},
{
"dev":"region0",
"size":103079215104,
"available_size":0,
"type":"pmem",
"numa_node":0,
"persistence_domain":"unknown"
}
]
root@server:~# ndctl list
[
{
"dev":"namespace1.0",
"mode":"raw",
"size":103079215104,
"sector_size":512,
"blockdev":"pmem1",
"numa_node":1
},
{
"dev":"namespace0.0",
"mode":"raw",
"size":103079215104,
"sector_size":512,
"blockdev":"pmem0",
"numa_node":0
}
]
root@server:~# ndctl create-namespace --reconfig=namespace1.0 --type=pmem
--mode=sector -f
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl:
[Kernel-packages] [Bug 1811785] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1811785/+attachment/5229231/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1811785
Title:
NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840
Status in linux package in Ubuntu:
Confirmed
Status in ndctl package in Ubuntu:
New
Bug description:
On ubuntu 18.04.1 :
1°) With 4.15.0-43 two default namespaces in raw mode are visible
while there shouldn't be any but no settings change could be applied.
root@server:~# ndctl list -R
[
{
"dev":"region1",
"size":103079215104,
"available_size":0,
"type":"pmem",
"numa_node":1,
"persistence_domain":"unknown"
},
{
"dev":"region0",
"size":103079215104,
"available_size":0,
"type":"pmem",
"numa_node":0,
"persistence_domain":"unknown"
}
]
root@server:~# ndctl list
[
{
"dev":"namespace1.0",
"mode":"raw",
"size":103079215104,
"sector_size":512,
"blockdev":"pmem1",
"numa_node":1
},
{
"dev":"namespace0.0",
"mode":"raw",
"size":103079215104,
"sector_size":512,
"blockdev":"pmem0",
"numa_node":0
}
]
root@server:~# ndctl create-namespace --reconfig=namespace1.0 --type=pmem
--mode=sector -f
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
[Kernel-packages] [Bug 1811815] [NEW] Ubuntu 18.10, Kernel 4.18, Intel Dual Band Wireless-AC 3165 Not Found
Public bug reported: Ubuntu 18.10 does not detect the Intel Dual Band Wireless-AC 3165 card, specifically on a Lenovo ideapad 330 laptop. A current workaround: - Blacklist the "ideapad-laptop" module. - Edit/create a file in "/etc/modprobe.d/" and name it "blacklist.conf" or something similar (if it does not already exist), and append "blacklist ideapad-laptop" to the file. Save and reboot. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dustin 1948 F pulseaudio /dev/snd/pcmC0D0p: dustin 1948 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 15 04:08:20 2019 InstallationDate: Installed on 2019-01-15 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:210e Acer, Inc Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 3938:1047 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81FK ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=fa5d161c-779c-4cf7-aa07-6da06d655747 ro acpi_osi=! "acpi_osi=Windows 2012" quiet splash nouveau.modeset=0 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN28WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ICH dmi.modalias: dmi:bvnLENOVO:bvr7ZCN28WW:bd07/17/2018:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH: dmi.product.family: ideapad 330-15ICH dmi.product.name: 81FK dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH dmi.product.version: Lenovo ideapad 330-15ICH dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811815 Title: Ubuntu 18.10, Kernel 4.18, Intel Dual Band Wireless-AC 3165 Not Found Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.10 does not detect the Intel Dual Band Wireless-AC 3165 card, specifically on a Lenovo ideapad 330 laptop. A current workaround: - Blacklist the "ideapad-laptop" module. - Edit/create a file in "/etc/modprobe.d/" and name it "blacklist.conf" or something similar (if it does not already exist), and append "blacklist ideapad-laptop" to the file. Save and reboot. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dustin 1948 F pulseaudio /dev/snd/pcmC0D0p: dustin 1948 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 15 04:08:20 2019 InstallationDate: Installed on 2019-01-15 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:210e Acer, Inc Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 3938:1047 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81FK ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=fa5d161c-779c-4cf7-aa07-6da06d655747 ro acpi_osi=! "acpi_osi=Windows 2012" quiet splash nouveau.modeset=0 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: No upgrade log present
[Kernel-packages] [Bug 1798583] Re: the new Steam Controller driver breaks it on Steam
I enabled proposed updates, upgraded and removed my blacklist on hid_steam and rebooted. Using lsmod after the reboot I can see hid_steam is there. First test with Rocket League, seemed to work fine and it was detected as a gamepad properly. The game did crash just after I got in a game though. Seems fine after, so likely not related. Tested out Hand of Fate 2, works perfectly. So yeah, the fix works. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798583 Title: the new Steam Controller driver breaks it on Steam Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Released Bug description: ===SRU Justification=== [Impact] New steam-hid driver breaks Unity games. [Fix] Quote from the commit message: "With this commit, when a HID client starts, the input device is removed; when the HID client ends the input device is recreated." [Test] A guy from Valve comfirms the backport works. [Regression Potential] Low. This fix is specific to hid-steam, which is a new driver introduced in v4.18. ===Original Bug Report=== The new hid_steam driver in kernel 4.18 breaks the use of it within Steam. Games either: - Crash - Don't detect it at all - Only pick it up as player 2 To get it working as normal, it needs blacklisting currently. See here: https://www.gamingonlinux.com/articles/the-steam-controller- on-ubuntu-1810-and-other-distributions-using-linux-kernel-418-needs- quick-a-fix.12775 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: liam 2492 F pulseaudio /dev/snd/controlC0: liam 2492 F pulseaudio /dev/snd/controlC1: liam 2492 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 18 12:49:44 2018 InstallationDate: Installed on 2017-10-18 (364 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp5s0no wireless extensions. eno1 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=2a8676f3-0045-4e66-9cd1-186ffc6a8c2a ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-18 (0 days ago) dmi.bios.date: 08/10/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: PCS dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1901:bd08/10/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811755] Re: X1 Extreme: only one of the two SSDs is loaded
Please try the test kernel in http://172.104.124.10/lp1811755/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811755 Title: X1 Extreme: only one of the two SSDs is loaded Status in linux package in Ubuntu: Confirmed Bug description: I bought a new Thinkpad X1 Extreme, and had it come with two SSDs, one 256G and the other 512G with the intention of keeping the windows on the 256G disk and using the 512G for linux. When dealing with the installer, it only ever saw one of the SSDs. I did manged to get bionic installed on the 512, but on boot, sometimes it doesn't find the 512G disk and I just get a blank screen. After a hard power-off, and reboot, it drops into the grub selector, and choosing linux, it failed again, but this time dropped into a VT. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tim2003 F pulseaudio /dev/snd/controlC0: tim2003 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 15 18:53:34 2019 InstallationDate: Installed on 2019-01-14 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Beta amd64 (20190109) MachineType: LENOVO 20MFCTO1WW ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=9254da2f-0220-4b41-8770-ae4b0df0d114 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET35W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET35W(1.17):bd12/21/2018:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811755] Re: X1 Extreme: only one of the two SSDs is loaded
Will you ever be able to boot into your 512G disk? If you can, please try the test kernel in http://172.104.124.10/lp1811755/. Otherwise I'm afraid you need a new installer image with a test kernel. ** Changed in: linux (Ubuntu) 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/1811755 Title: X1 Extreme: only one of the two SSDs is loaded Status in linux package in Ubuntu: Confirmed Bug description: I bought a new Thinkpad X1 Extreme, and had it come with two SSDs, one 256G and the other 512G with the intention of keeping the windows on the 256G disk and using the 512G for linux. When dealing with the installer, it only ever saw one of the SSDs. I did manged to get bionic installed on the 512, but on boot, sometimes it doesn't find the 512G disk and I just get a blank screen. After a hard power-off, and reboot, it drops into the grub selector, and choosing linux, it failed again, but this time dropped into a VT. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tim2003 F pulseaudio /dev/snd/controlC0: tim2003 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 15 18:53:34 2019 InstallationDate: Installed on 2019-01-14 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Beta amd64 (20190109) MachineType: LENOVO 20MFCTO1WW ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=9254da2f-0220-4b41-8770-ae4b0df0d114 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET35W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET35W(1.17):bd12/21/2018:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 571770]
(In reply to mirh from comment #79) > Is this still a thing? Let's assume not, thanks for the follow-up. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/571770 Title: Thread [hd-audio0] consuming excessive amounts of CPU, audio crackling Status in linux package in Ubuntu: Fix Released Bug description: Binary package hint: linux-image-2.6.32-22-generic Sometimes during audio playback, a kernel thread named "[hd-audio0]" will consume excessive amounts of CPU and cause audio crackling. It seems to be more easily triggered when displaying video in fullscreen (or Rhythmbox visualizations) or dragging windows around while playing music, somehow relating it graphics operations (running default radeon driver with KMS and Compiz). This all started after moving from Ubuntu Karmic to Lucid (never had this problem before). Setting package to kernel, since it's probably alsa snd_hda_intel kernel module which is to blame. Ubuntu 10.04 x86, Intel Core Duo 2GHz, 3GB RAM, ATI X1400 Radeon Mobility graphics. Audio chip: Analog Devices AD1981 [HDA] WORKAROUND: Disabling radeon KMS makes all the audio crackling go away. Attaching: * Screenshot of top running over Rhythmbox w/fullscreen visualizations, showing [hd-audio0] consuming more CPU than everything else at the time (audio crackles). * Output of "lspci -vvnn" * Output of "dmesg" * Contents of /proc/interrupts * ALSA info, as provided by the alsa-info.sh script. Related to this: https://bugzilla.kernel.org/show_bug.cgi?id=14935 ??? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/571770/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810370] Re: linux-oem: 4.15.0-1031.36 -proposed tracker
*** This bug is a duplicate of bug 1811421 *** https://bugs.launchpad.net/bugs/1811421 ** This bug has been marked a duplicate of bug 1811421 linux-oem: -proposed tracker -- 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/1810370 Title: linux-oem: 4.15.0-1031.36 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid 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 is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1806659 phase: Testing -- automated-testing FAILED phase-changed: Wednesday, 09. January 2019 14:55 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1810370/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811417] Re: linux-kvm: 4.18.0-1007.7 -proposed tracker
** Summary changed: - linux-kvm: -proposed tracker + linux-kvm: 4.18.0-1007.7 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) -- 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/1811417 Title: linux-kvm: 4.18.0-1007.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1811406 phase: Packaging -- ready to package phase-changed: Monday, 14. January 2019 10:00 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811417/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811828] [NEW] linux-aws: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1811825 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa-dnu Importance: Medium Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-aws (Ubuntu Trusty) Importance: Medium Status: Confirmed ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-backport-of-1811825 kernel-sru-cycle-2019.01.14-1 trusty ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-aws (Ubuntu Trusty) Importance: Undecided Status: New ** Tags added: trusty ** Changed in: linux-aws (Ubuntu Trusty) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa-dnu Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Ubuntu Stable Release Updates
[Kernel-packages] [Bug 1811830] [NEW] linux-aws: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1811825 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/snap-release-to-beta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-candidate Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-edge Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/snap-release-to-stable Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa-dnu Importance: Medium Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-aws (Ubuntu Xenial) Importance: Medium Status: Confirmed ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2019.01.14-1 kernel-sru-derivative-of-1811825 xenial ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-aws (Ubuntu Xenial) Importance: Undecided Status: New ** Tags added: xenial ** Changed in: linux-aws (Ubuntu Xenial) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-beta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-candidate Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-edge Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/snap-release-to-stable Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa-dnu Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in:
[Kernel-packages] [Bug 1811832] [NEW] linux-kvm: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1811825 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa-dnu Importance: Medium Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-kvm (Ubuntu Xenial) Importance: Medium Status: Confirmed ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2019.01.14-1 kernel-sru-derivative-of-1811825 xenial ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-kvm (Ubuntu Xenial) Importance: Undecided Status: New ** Tags added: xenial ** Changed in: linux-kvm (Ubuntu Xenial) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa-dnu Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Ubuntu Stable Release Updates
[Kernel-packages] [Bug 1803360] Re: Fanless systems with DPTF shutdown before using any passive cooling device
Ok, then we can leave Xenial out. -- 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/1803360 Title: Fanless systems with DPTF shutdown before using any passive cooling device Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Xenial: New Status in thermald source package in Bionic: In Progress Status in thermald source package in Cosmic: In Progress Status in thermald source package in Disco: Fix Released Bug description: == SRU Justification, Cosmic, Bionic, Xenial == There are some new fanless platforms use DPTF's virtual sensor instead of INT340X devices. Because of that, the _PSV is no longer in use, at least not directly, hence its value may set higher then _CRT. To a fanless system that means no cooling device gets activated before _CRT, so the system will be considered overheated by Linux kernel, and gets shutdown by the kernel. == Fix == Upstream fix https://github.com/intel/thermal_daemon/commit/97976782dd26b4d592ccb97eb89c2a3a871a22a9 == Testing == Exercise CPUs on a fanless INT340X device with _CRT ACPI objects and try and reach the trip point. Without the fix thermal overrun occurs and this trips CPU shutdown. With the fix, thermald will start to throttle the system and get it out of the thermal overrun zone. == Regression Potential == This modifies the behavior for just INT340X devices with ACPI _CRT objects, specifically, now to honor this setting. This is a small subset of devices with these objects and the change will in face make thermald catch systems before they hit thermal overrun, so the risk of regression is small. This fix also has been reviewed by the thermal experts at Intel, so it seems like a very reasonable workaround for these specific use cases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1803360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811335] Re: ELAN900C:00 04F3:2844 touchscreen doesn't work
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verification-needed-cosmic' to 'verification-failed-
cosmic'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-cosmic
** Tags added: verification-needed-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/1811335
Title:
ELAN900C:00 04F3:2844 touchscreen doesn't work
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Bug description:
[Impact]
[ELAN900C:00 04F3:2844] doesn't work
[Fix]
It works under kernel v4.19, so after bisect the kernel and got the first bad
commit
e50d95e2ad12 pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H
variant
[Test]
Verified on the DELL machine, the touchscreen works well.
[Regression Potential]
Low, the 2 commits are all
Fixes: a663ccf0fea1 ("pinctrl: intel: Add Intel Cannon Lake PCH-H pin
controller support")
Should be safe to be included.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1811335/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811337] Re: To reduce the Realtek USB cardreader power consumption
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
--
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/1811337
Title:
To reduce the Realtek USB cardreader power consumption
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux-oem package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Committed
Status in linux-oem source package in Bionic:
In Progress
Status in linux source package in Cosmic:
Fix Committed
Status in linux-oem source package in Cosmic:
Invalid
Status in linux source package in Disco:
Fix Committed
Status in linux-oem source package in Disco:
Invalid
Bug description:
[Impact]
Realtek USB cardreader consumes more than 1 Watt during long idle if it's not
suspended. And it's runtime PM functions are available after v4.20.
[Fix]
To avoid conflicts, have to backport some patches for mmc core.
[Test]
Note: Inside () are the previous value (non-patch)
Sort idle: 7.76W (7.88)
Long idle: 4.658W (5.79)
S3: 0.5W (0.5)
S5: 0.20W (0.208)
[Regression Potential]
Low, most commits are for rtsx_usb_{sdmmc,ms} and are all small changes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1811337/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810702] Re: HP mobile workstations with hybrid graphics support, can not directly output to external monitors by dGPU
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1810702 Title: HP mobile workstations with hybrid graphics support, can not directly output to external monitors by dGPU Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: For HP Inc. mobile workstation with hybrid graphics support, dGPU can directly output to external monitors; however, Nvidia and AMD's Linux drivers aren't able to support this feature. The OEM _OSI string "Linux-HPI-Hybrid-Graphics" is used by BIOS to implement dGPU direct output to external monitors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810702/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811094] Re: iptables connlimit allows more connections than the limit when using multiple CPUs
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verification-needed-cosmic' to 'verification-failed-
cosmic'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-cosmic
** Tags added: verification-needed-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/1811094
Title:
iptables connlimit allows more connections than the limit when using
multiple CPUs
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 Cosmic:
Fix Committed
Bug description:
[Impact]
* The iptables connection count/limit rules can be breached
with multithreaded network driver/server/client (common)
due to a race in the conncount/connlimit code.
* For example:
# iptables -A INPUT -p tcp -m tcp --syn --dport \
-m connlimit --connlimit-above 2000 --connlimit-mask 0 \
-j DROP
* The fix is a backport from an upstream commit that resolves
the problem (plus dependencies for a cleaner backport) that
address the race condition:
commit b36e4523d4d5 ("netfilter: nf_conncount: fix garbage
collection confirm race").
[Test Case]
* Server-side: (relevant kernel side)
(limit TCP port to only 2000 connections)
# iptables -A INPUT -p tcp -m tcp --syn --dport \
-m connlimit --connlimit-above 2000 --connlimit-mask 0 \
-j DROP
# ulimit -SHn 65000 # increase number of open files
# ruby server.rb # multi-threaded server
* Client-side:
# ulimit -SHn 65000
# ruby client.rb<# threads>
* Results with Original kernel:
(client achieves target of 6000 connections > limit of 2000 connections)
# ruby client.rb 10.230.56.100 6000 3
1
2
3
<...>
6000
Target reached. Thread finishing
6001
Target reached. Thread finishing
6002
Target reached. Thread finishing
Threads done. 6002 connections
press enter to exit
* Results with Modified kernel:
(client is limited to 2000 connections, and times out afterward)
# ruby client.rb 10.230.56.100 6000 3
1
2
3
<...>
2000
<... blocks for a few minutes ...>
failed to create connection: Connection timed out - connect(2) for
"10.230.56.100" port
failed to create connection: Connection timed out - connect(2) for
"10.230.56.100" port
failed to create connection: Connection timed out - connect(2) for
"10.230.56.100" port
Threads done. 2000 connections
press enter to exit
* Test cases possibly available upon request,
depending on original author's permission.
[Regression Potential]
* The patchset has been reviewed by a netfilter maintainer [1] in
stable mailing list, and was considered OK for 4.14, and that's
essentially the same backport for 4.15 and 4.4.
* The changes are limited to netfilter connlimit/conncount (names
change between older/newer kernel versions).
[Other Info]
* The backport for 4.14 [2] is applied as of 4.14.92.
[1] https://www.spinics.net/lists/stable/msg276883.html
[2] https://www.spinics.net/lists/stable/msg276910.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811094/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810891] Re: audio output has constant noise on a Dell machine
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed- cosmic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-cosmic ** Tags added: verification-needed-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/1810891 Title: audio output has constant noise on a Dell machine Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Invalid Bug description: [Impact] the audio output (headpohne, lineout and internal speaker) has constant noise when playing sound. [Fix] Set the pin configuration and some secret coeff registers, the noise disappears. This patch is written by Realtek engineer and is upstreamd already. [Test Case] play sound via internal speaker, lineout and headphone, no noise anymore. [Regression Potential] Very low, this patch is upstreamd for a while, no regression is reported. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1810891/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810892] Re: lineout jack can't work on a Dell machine
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed- cosmic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-cosmic ** Tags added: verification-needed-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/1810892 Title: lineout jack can't work on a Dell machine Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] The rear lineout jack can't work. If users plug a headphone or audio cable into the lineout jack, nothing happens, the audio still output from internal speaker. The expected behaviour is the lineout is active and the sound is routed to lineout jack from internal speaker. [Fix] apply the ALC274_FIXUP_DELL_AIO_LINEOUT_VERB, this will set the lineout pin to be a correct configuration value. [Test Case] plug headphone into the rear lineout jack, system can detect lineout jack is plugged and the audio output is routed to lineout jack from internal speaker. [Regression Potential] Very low, this patch is specific to one Dell machine model. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1810892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811335] Re: ELAN900C:00 04F3:2844 touchscreen doesn't work
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1811335
Title:
ELAN900C:00 04F3:2844 touchscreen doesn't work
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Bug description:
[Impact]
[ELAN900C:00 04F3:2844] doesn't work
[Fix]
It works under kernel v4.19, so after bisect the kernel and got the first bad
commit
e50d95e2ad12 pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H
variant
[Test]
Verified on the DELL machine, the touchscreen works well.
[Regression Potential]
Low, the 2 commits are all
Fixes: a663ccf0fea1 ("pinctrl: intel: Add Intel Cannon Lake PCH-H pin
controller support")
Should be safe to be included.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1811335/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811200] Re: Add Cavium ThunderX2 SoC UNCORE PMU driver
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811200 Title: Add Cavium ThunderX2 SoC UNCORE PMU driver Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] No driver for PMU of L3 cache controller (L3C) and the DDR4 Memory Controller (DMC) for Cavium ThunderX2 SoC [Test Case] sudo perf stat -a -e \ > uncore_dmc_0/cnt_cycles/,\ > uncore_dmc_0/data_transfers/,\ > uncore_dmc_0/read_txns/,\ > uncore_dmc_0/write_txns/ sleep 1 sudo perf stat -a -e \ > uncore_l3c_0/read_request/,\ > uncore_l3c_0/read_hit/,\ > uncore_l3c_0/inv_request/,\ > uncore_l3c_0/inv_hit/ sleep 1 sudo perf stat -a -e uncore_dmc_0/cnt_cycles/ sleep 1 [Fix] Backport patches 82975c46da perf: Export perf_event_update_userpage (only for bionic) d6310a3f33 Documentation: perf: Add documentation for ThunderX2 PMU uncore driver 69c32972d5 drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver and enable CONFIG_THUNDERX2_PMU=m [Regression Risk] This driver only loaded when CAV901C in ACPI table, lowest risk for other platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811200/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810781] Re: mpt3sas - driver using the wrong register to update a queue index in FW
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed- cosmic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-cosmic ** Tags added: verification-needed-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/1810781 Title: mpt3sas - driver using the wrong register to update a queue index in FW Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Released Bug description: [Impact] * Adapter resets periodically during high-load activity. * I/O stalls until reset/reinit is complete (latency) and I/O performance degrades across cluster (e.g., low throughput from data spread over nodes). * The mpt3sas driver relies in a FW queue (Reply Post Descriptor Queue) in the I/O completion path; there's a MMIO register that driver uses to flag an empty entry in such queue, called Reply Post Host Index. This value is updated during the driver interrupt routine [in _base_interrupt() function]. * Happens that there are 2 registers representing the Reply Post Host Index according to the type of the adapter. They are differentiated in the driver through the "ioc->combined_reply_queue" check. By the MPI specification (vendor spec), driver should use this combined reply queue according to the number of maximum MSI-X vectors that the adapter exposes and the spec version (SAS 3.0 vs SAS 3.5). * Currently, this is wrong checked for a class of adapters, which was fixed in the upstream kernel commit 2b48be65685a [0]. Without this commit, we can observe spontaneous resets in the driver due to queue overflow (FW is not aware that there are free entries in the Reply Post Descriptor Queue). The dmesg log will show the following output in case of this error: mpt3sas_cm0: fault_state(0x2100)! mpt3sas_cm0: sending diag reset !! mpt3sas_cm0: diag reset: SUCCESS [followed by a lot of driver messages as result of the reset procedure] * During these resets, I/O is stalled so it may affect performance. [Test Case] * It's not trivial to test the problem, but given a machine with an affected device, an I/O benchmark like FIO could be used to exercise the I/O path in a heavy way and trigger the issue. * We have reports that the adapter "LSI Logic / Symbios Logic Device [1000:00ac]" is affected by the issue. And this commit resolved the problem. [Regression Potential] * This is a long-term issue from the mpt3sas driver, affecting only a class of adapters of this vendor. Since it's a clearly bug, the fix is necessary. The potential of regressions is unknown, but likely low - it changes the register used for the index updates given some set of characteristics of the adapter (according to the spec.), which restricts even more the scope of this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810781/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810781] Re: mpt3sas - driver using the wrong register to update a queue index in FW
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810781 Title: mpt3sas - driver using the wrong register to update a queue index in FW Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Won't Fix Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Released Bug description: [Impact] * Adapter resets periodically during high-load activity. * I/O stalls until reset/reinit is complete (latency) and I/O performance degrades across cluster (e.g., low throughput from data spread over nodes). * The mpt3sas driver relies in a FW queue (Reply Post Descriptor Queue) in the I/O completion path; there's a MMIO register that driver uses to flag an empty entry in such queue, called Reply Post Host Index. This value is updated during the driver interrupt routine [in _base_interrupt() function]. * Happens that there are 2 registers representing the Reply Post Host Index according to the type of the adapter. They are differentiated in the driver through the "ioc->combined_reply_queue" check. By the MPI specification (vendor spec), driver should use this combined reply queue according to the number of maximum MSI-X vectors that the adapter exposes and the spec version (SAS 3.0 vs SAS 3.5). * Currently, this is wrong checked for a class of adapters, which was fixed in the upstream kernel commit 2b48be65685a [0]. Without this commit, we can observe spontaneous resets in the driver due to queue overflow (FW is not aware that there are free entries in the Reply Post Descriptor Queue). The dmesg log will show the following output in case of this error: mpt3sas_cm0: fault_state(0x2100)! mpt3sas_cm0: sending diag reset !! mpt3sas_cm0: diag reset: SUCCESS [followed by a lot of driver messages as result of the reset procedure] * During these resets, I/O is stalled so it may affect performance. [Test Case] * It's not trivial to test the problem, but given a machine with an affected device, an I/O benchmark like FIO could be used to exercise the I/O path in a heavy way and trigger the issue. * We have reports that the adapter "LSI Logic / Symbios Logic Device [1000:00ac]" is affected by the issue. And this commit resolved the problem. [Regression Potential] * This is a long-term issue from the mpt3sas driver, affecting only a class of adapters of this vendor. Since it's a clearly bug, the fix is necessary. The potential of regressions is unknown, but likely low - it changes the register used for the index updates given some set of characteristics of the adapter (according to the spec.), which restricts even more the scope of this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810781/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811055] Re: Support new Realtek ethernet chips
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed- cosmic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-cosmic ** Tags added: verification-needed-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/1811055 Title: Support new Realtek ethernet chips Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Incomplete Bug description: [Impact] New Realtek ethernet chips don't work. [Fix] Add new IDs to r8169.ko. [Test] The r8169 is loaded for the Realtek ethernet chip. It works, and I haven't seen any issues so far. [Regression Potential] Low. New IDs to existing driver, no functional change. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1811055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811200] Re: Add Cavium ThunderX2 SoC UNCORE PMU driver
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed- cosmic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-cosmic ** Tags added: verification-needed-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/1811200 Title: Add Cavium ThunderX2 SoC UNCORE PMU driver Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] No driver for PMU of L3 cache controller (L3C) and the DDR4 Memory Controller (DMC) for Cavium ThunderX2 SoC [Test Case] sudo perf stat -a -e \ > uncore_dmc_0/cnt_cycles/,\ > uncore_dmc_0/data_transfers/,\ > uncore_dmc_0/read_txns/,\ > uncore_dmc_0/write_txns/ sleep 1 sudo perf stat -a -e \ > uncore_l3c_0/read_request/,\ > uncore_l3c_0/read_hit/,\ > uncore_l3c_0/inv_request/,\ > uncore_l3c_0/inv_hit/ sleep 1 sudo perf stat -a -e uncore_dmc_0/cnt_cycles/ sleep 1 [Fix] Backport patches 82975c46da perf: Export perf_event_update_userpage (only for bionic) d6310a3f33 Documentation: perf: Add documentation for ThunderX2 PMU uncore driver 69c32972d5 drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver and enable CONFIG_THUNDERX2_PMU=m [Regression Risk] This driver only loaded when CAV901C in ACPI table, lowest risk for other platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811200/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811094] Re: iptables connlimit allows more connections than the limit when using multiple CPUs
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1811094
Title:
iptables connlimit allows more connections than the limit when using
multiple CPUs
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 Cosmic:
Fix Committed
Bug description:
[Impact]
* The iptables connection count/limit rules can be breached
with multithreaded network driver/server/client (common)
due to a race in the conncount/connlimit code.
* For example:
# iptables -A INPUT -p tcp -m tcp --syn --dport \
-m connlimit --connlimit-above 2000 --connlimit-mask 0 \
-j DROP
* The fix is a backport from an upstream commit that resolves
the problem (plus dependencies for a cleaner backport) that
address the race condition:
commit b36e4523d4d5 ("netfilter: nf_conncount: fix garbage
collection confirm race").
[Test Case]
* Server-side: (relevant kernel side)
(limit TCP port to only 2000 connections)
# iptables -A INPUT -p tcp -m tcp --syn --dport \
-m connlimit --connlimit-above 2000 --connlimit-mask 0 \
-j DROP
# ulimit -SHn 65000 # increase number of open files
# ruby server.rb # multi-threaded server
* Client-side:
# ulimit -SHn 65000
# ruby client.rb<# threads>
* Results with Original kernel:
(client achieves target of 6000 connections > limit of 2000 connections)
# ruby client.rb 10.230.56.100 6000 3
1
2
3
<...>
6000
Target reached. Thread finishing
6001
Target reached. Thread finishing
6002
Target reached. Thread finishing
Threads done. 6002 connections
press enter to exit
* Results with Modified kernel:
(client is limited to 2000 connections, and times out afterward)
# ruby client.rb 10.230.56.100 6000 3
1
2
3
<...>
2000
<... blocks for a few minutes ...>
failed to create connection: Connection timed out - connect(2) for
"10.230.56.100" port
failed to create connection: Connection timed out - connect(2) for
"10.230.56.100" port
failed to create connection: Connection timed out - connect(2) for
"10.230.56.100" port
Threads done. 2000 connections
press enter to exit
* Test cases possibly available upon request,
depending on original author's permission.
[Regression Potential]
* The patchset has been reviewed by a netfilter maintainer [1] in
stable mailing list, and was considered OK for 4.14, and that's
essentially the same backport for 4.15 and 4.4.
* The changes are limited to netfilter connlimit/conncount (names
change between older/newer kernel versions).
[Other Info]
* The backport for 4.14 [2] is applied as of 4.14.92.
[1] https://www.spinics.net/lists/stable/msg276883.html
[2] https://www.spinics.net/lists/stable/msg276910.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811094/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811055] Re: Support new Realtek ethernet chips
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811055 Title: Support new Realtek ethernet chips Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Incomplete Bug description: [Impact] New Realtek ethernet chips don't work. [Fix] Add new IDs to r8169.ko. [Test] The r8169 is loaded for the Realtek ethernet chip. It works, and I haven't seen any issues so far. [Regression Potential] Low. New IDs to existing driver, no functional change. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1811055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810891] Re: audio output has constant noise on a Dell machine
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810891 Title: audio output has constant noise on a Dell machine Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Invalid Bug description: [Impact] the audio output (headpohne, lineout and internal speaker) has constant noise when playing sound. [Fix] Set the pin configuration and some secret coeff registers, the noise disappears. This patch is written by Realtek engineer and is upstreamd already. [Test Case] play sound via internal speaker, lineout and headphone, no noise anymore. [Regression Potential] Very low, this patch is upstreamd for a while, no regression is reported. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1810891/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810998] Re: CPU hard lockup with rigorous writes to NVMe drive
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1810998
Title:
CPU hard lockup with rigorous writes to NVMe drive
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Bug description:
[Impact]
* Users may experience cpu hard lockups when performing
rigorous writes to NVMe drives.
* The fix addresses an scheduling issue in the original
implementation of wbt/writeback throttling
* The fix is commit 2887e41b910b ("blk-wbt: Avoid lock
contention and thundering herd issue in wbt_wait"),
plus its fix commit 38cfb5a45ee0 ("blk-wbt: improve
waking of tasks").
* Plus a few dependency commits for each fix.
* Backports are trivial: mainly replace rq_wait_inc_below()
with the equivalent atomic_inc_below(), and maintain the
__wbt_done() signature, both due to the lack of commit
a79050434b45 ("blk-rq-qos: refactor out common elements
of blk-wbt"), that changes lots of other/unrelated code.
[Test Case]
* This command has been reported to reproduce the problem:
$ sudo iozone -R -s 5G -r 1m -S 2048 -i 0 -G -c -o -l 128 -u 128 -t
128
* It generates stack traces as below in the original kernel,
and does not generate them in the modified/patched kernel.
* The user/reporter verified the test kernel with these patches
resolved the problem.
* The developer verified in 2 systems (4-core and 24-core but
no NVMe) for regressions, and no error messages were logged
to dmesg.
[Regression Potential]
* The regression potential is contained within writeback
throttling mechanism (block/blk-wbt.*).
* The commits have been verified for fixes in later commits in
linux-next as of 2019-01-08 and all known fix commits are in.
[Other Info]
* The problem has been introduced with the blk-wbt mechanism,
in v4.10-rc1, and the fix commits in v4.19-rc1 and -rc2,
so only Bionic and Cosmic needs this.
[Stack Traces]
[ 393.628647] NMI watchdog: Watchdog detected hard LOCKUP on cpu 30
...
[ 393.628704] CPU: 30 PID: 0 Comm: swapper/30 Tainted: P OE 4.15.0-20-generic
#21-Ubuntu
...
[ 393.628720] Call Trace:
[ 393.628721]
[ 393.628724] enqueue_task_fair+0x6c/0x7f0
[ 393.628726] ? __update_load_avg_blocked_se.isra.37+0xd1/0x150
[ 393.628728] ? __update_load_avg_blocked_se.isra.37+0xd1/0x150
[ 393.628731] activate_task+0x57/0xc0
[ 393.628735] ? sched_clock+0x9/0x10
[ 393.628736] ? sched_clock+0x9/0x10
[ 393.628738] ttwu_do_activate+0x49/0x90
[ 393.628739] try_to_wake_up+0x1df/0x490
[ 393.628741] default_wake_function+0x12/0x20
[ 393.628743] autoremove_wake_function+0x12/0x40
[ 393.628744] __wake_up_common+0x73/0x130
[ 393.628745] __wake_up_common_lock+0x80/0xc0
[ 393.628746] __wake_up+0x13/0x20
[ 393.628749] __wbt_done.part.21+0xa4/0xb0
[ 393.628749] wbt_done+0x72/0xa0
[ 393.628753] blk_mq_free_request+0xca/0x1a0
[ 393.628755] blk_mq_end_request+0x48/0x90
[ 393.628760] nvme_complete_rq+0x23/0x120 [nvme_core]
[ 393.628763] nvme_pci_complete_rq+0x7a/0x130 [nvme]
[ 393.628764] __blk_mq_complete_request+0xd2/0x140
[ 393.628766] blk_mq_complete_request+0x18/0x20
[ 393.628767] nvme_process_cq+0xe1/0x1b0 [nvme]
[ 393.628768] nvme_irq+0x23/0x50 [nvme]
[ 393.628772] __handle_irq_event_percpu+0x44/0x1a0
[ 393.628773] handle_irq_event_percpu+0x32/0x80
[ 393.628774] handle_irq_event+0x3b/0x60
[ 393.628778] handle_edge_irq+0x7c/0x190
[ 393.628779] handle_irq+0x20/0x30
[ 393.628783] do_IRQ+0x46/0xd0
[ 393.628784] common_interrupt+0x84/0x84
[ 393.628785]
...
[ 393.628794] ? cpuidle_enter_state+0x97/0x2f0
[ 393.628796] cpuidle_enter+0x17/0x20
[ 393.628797] call_cpuidle+0x23/0x40
[ 393.628798] do_idle+0x18c/0x1f0
[ 393.628799] cpu_startup_entry+0x73/0x80
[ 393.628802] start_secondary+0x1a6/0x200
[ 393.628804] secondary_startup_64+0xa5/0xb0
[ 393.628805] Code: ...
[ 405.981597] nvme nvme1: I/O 393 QID 6 timeout, completion polled
[ 435.597209] INFO: rcu_sched detected stalls on CPUs/tasks:
[ 435.602858] 30-...0: (1 GPs behind) idle=e26/1/0 softirq=6834/6834 fqs=4485
[ 435.610203] (detected by 8, t=15005
[Kernel-packages] [Bug 1811416] Re: linux-gcp: 4.18.0-1006.7 -proposed tracker
** Summary changed: - linux-gcp: -proposed tracker + linux-gcp: 4.18.0-1006.7 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader (smb) -- 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/1811416 Title: linux-gcp: 4.18.0-1006.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1811406 phase: Packaging -- ready to package phase-changed: Monday, 14. January 2019 10:01 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811785] Re: NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840
** Changed in: ndctl
Status: Unknown => 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/1811785
Title:
NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840
Status in ndctl:
New
Status in linux package in Ubuntu:
Confirmed
Status in ndctl package in Ubuntu:
New
Bug description:
On ubuntu 18.04.1 :
1°) With 4.15.0-43 two default namespaces in raw mode are visible
while there shouldn't be any but no settings change could be applied.
root@server:~# ndctl list -R
[
{
"dev":"region1",
"size":103079215104,
"available_size":0,
"type":"pmem",
"numa_node":1,
"persistence_domain":"unknown"
},
{
"dev":"region0",
"size":103079215104,
"available_size":0,
"type":"pmem",
"numa_node":0,
"persistence_domain":"unknown"
}
]
root@server:~# ndctl list
[
{
"dev":"namespace1.0",
"mode":"raw",
"size":103079215104,
"sector_size":512,
"blockdev":"pmem1",
"numa_node":1
},
{
"dev":"namespace0.0",
"mode":"raw",
"size":103079215104,
"sector_size":512,
"blockdev":"pmem0",
"numa_node":0
}
]
root@server:~# ndctl create-namespace --reconfig=namespace1.0 --type=pmem
--mode=sector -f
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area
[Kernel-packages] [Bug 1506914] Re: 8086:0416 [Asus G550JK] Changing screen brightness not working using keyboard shortcut Fn+F5/F6
** Tags removed: kernel-bug-exists-upstream ** Tags added: needs-upstream-testing ** Changed in: linux (Ubuntu) Status: Triaged => 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/1506914 Title: 8086:0416 [Asus G550JK] Changing screen brightness not working using keyboard shortcut Fn+F5/F6 Status in linux package in Ubuntu: Incomplete Bug description: WORKAROUND: Change in /etc/default/grub : GRUB_CMDLINE_LINUX_DEFAULT="" to: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi=" run $ sudo update-grub reboot ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6 Uname: Linux 3.19.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Oct 16 17:27:47 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.19.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:11cd] Subsystem: ASUSTeK Computer Inc. Device [1043:11cd] JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] failed with exit code 1: No journal files were found. MachineType: ASUSTeK COMPUTER INC. G550JK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic.efi.signed root=UUID=9a6cce6e-ddfb-40c7-a64c-823140602164 ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G550JK.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G550JK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG550JK.204:bd08/11/2014:svnASUSTeKCOMPUTERINC.:pnG550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sat Oct 10 11:46:59 2015 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [GLAMOR] failed to initialise EGL NOUVEAU(G0): Error creating GPU channel: -19 NOUVEAU(G0): Error initialising acceleration. Falling back to NoAccel xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12876 vendor SDC xserver.version: 2:1.17.1-0ubuntu3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1277959] Re: [Asus 1015E] Fn+F2 is not working for activating/deactivating wifi
Pablo Rossy Bernardes Mozinho Ferreira (santoross08-p), it will help immensely
if you use Ubuntu with the computer the problem is reproducible with and file a
new report via a terminal to provide necessary debugging logs:
ubuntu-bug linux
Please feel free to subscribe me to it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1277959
Title:
[Asus 1015E] Fn+F2 is not working for activating/deactivating wifi
Status in linux package in Ubuntu:
Expired
Bug description:
Fn+F2 is not working for activating/deactivating wifi.
Also wifi led is not working (led located on netbook case)
I have an ASUS 1015E-DS03 netbook with Ubuntu 12.04 LTS.
Linux ASUS-1015E-DS03 3.8.0-35-generic #52~precise1-Ubuntu SMP Thu Jan
30 17:24:40 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
The problem maybe in asus_nb_wmi driver.
Related to https://bugs.launchpad.net/bugs/1173681.
description: Wireless interface
product: AR9485 Wireless Network Adapter
vendor: Qualcomm Atheros
physical id: 0
bus info: pci@:02:00.0
logical name: wlan0
version: 01
serial: 6c:71:d9:7f:70:6b
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list rom ethernet
physical wireless
configuration: broadcast=yes driver=ath9k
driverversion=3.8.0-35-generic firmware=N/A ip=192.168.1.47 latency=0 link=yes
multicast=yes wireless=IEEE 802.11bgn
resources: irq:17 memory:f7d0-f7d7 memory:f7d8-f7d8
Thanks.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.8.0-35-generic 3.8.0-35.52~precise1
ProcVersionSignature: Ubuntu 3.8.0-35.52~precise1-generic 3.8.13.13
Uname: Linux 3.8.0-35-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.8.0-35-generic.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: christian 1836 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xf7e1 irq 44'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:10ec0269,1043115d,00100100
HDA:80862806,80860101,0010'
Controls : 24
Simple ctrls : 9
Date: Sat Feb 8 17:41:06 2014
HibernationDevice: RESUME=UUID=046c9b4b-4f3f-45e2-8edf-e79abc412d11
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64
(20130820.1)
MachineType: ASUSTeK COMPUTER INC. 1015E
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-35-generic
root=UUID=671caa58-b12e-4d13-a74e-a34bd55cff02 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.8.0-35-generic N/A
linux-backports-modules-3.8.0-35-generic N/A
linux-firmware1.94
SourcePackage: linux-lts-raring
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/15/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1015E.303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: 1015E
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1015E.303:bd03/15/2013:svnASUSTeKCOMPUTERINC.:pn1015E:pvr1.0:rvnASUSTeKCOMPUTERINC.:rn1015E:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: 1015E
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1277959/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811857] [NEW] linux-lts-trusty: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1811856 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa-dnu Importance: Medium Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-lts-trusty (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Precise) Importance: Medium Status: Confirmed ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-backport-of-1811856 kernel-sru-cycle-2019.01.14-1 precise ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux-lts-trusty (Ubuntu Precise) Importance: Undecided Status: New ** Tags added: precise ** Changed in: linux-lts-trusty (Ubuntu Precise) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa-dnu Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in:
[Kernel-packages] [Bug 1811856] [NEW] linux: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1811857 (linux-lts-trusty) derivatives: ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa-dnu Importance: Medium Status: Invalid ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: Confirmed ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2019.01.14-1 kernel-sru-master-kernel trusty ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Tags added: trusty ** Changed in: linux (Ubuntu Trusty) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa-dnu Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in:
[Kernel-packages] [Bug 1811850] Re: linux-ibm-gt: -proposed tracker
** Tags added: kernel-sru-cycle-2019.01.14-1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811850 Title: linux-ibm-gt: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811856] Re: linux: -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1811857 (linux-lts-trusty) derivatives: + -- swm properties -- + phase: Packaging -- ready to package + phase-changed: Tuesday, 15. January 2019 15:01 UTC + reason: + prepare-package: Pending -- version not specified -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811856 Title: linux: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1811857 (linux-lts-trusty) derivatives: -- swm properties -- phase: Packaging -- ready to package phase-changed: Tuesday, 15. January 2019 15:01 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811853] Re: linux-kvm: -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1811846 + reason: + prepare-package: Stalled -- waiting for master bug -- 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/1811853 Title: linux-kvm: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1811846 reason: prepare-package: Stalled -- waiting for master bug To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811853/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811850] Re: linux-ibm-gt: -proposed tracker
** Tags added: kernel-sru-derivative-of-1811419 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811850 Title: linux-ibm-gt: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- phase: Packaging -- ready to package phase-changed: Tuesday, 15. January 2019 15:07 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811858] [NEW] package linux-firmware 1.175 failed to install/upgrade: Extrahierte Daten für »./lib/firmware/ath10k/QCA6174/hw2.1/board-2.bin« können nicht nach »/lib/firmware/a
Public bug reported: I dont have further informations, havent seen a thing ProblemType: Package DistroRelease: Ubuntu 18.10 Package: linux-firmware 1.175 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 Date: Tue Jan 15 15:52:19 2019 Dependencies: ErrorMessage: Extrahierte Daten für »./lib/firmware/ath10k/QCA6174/hw2.1/board-2.bin« können nicht nach »/lib/firmware/ath10k/QCA6174/hw2.1/board-2.bin.dpkg-new« kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms InstallationDate: Installed on 2019-01-15 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: linux-firmware Title: package linux-firmware 1.175 failed to install/upgrade: Extrahierte Daten für »./lib/firmware/ath10k/QCA6174/hw2.1/board-2.bin« können nicht nach »/lib/firmware/ath10k/QCA6174/hw2.1/board-2.bin.dpkg-new« kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1811858 Title: package linux-firmware 1.175 failed to install/upgrade: Extrahierte Daten für »./lib/firmware/ath10k/QCA6174/hw2.1/board-2.bin« können nicht nach »/lib/firmware/ath10k/QCA6174/hw2.1/board-2.bin.dpkg-new« kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms Status in linux-firmware package in Ubuntu: New Bug description: I dont have further informations, havent seen a thing ProblemType: Package DistroRelease: Ubuntu 18.10 Package: linux-firmware 1.175 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 Date: Tue Jan 15 15:52:19 2019 Dependencies: ErrorMessage: Extrahierte Daten für »./lib/firmware/ath10k/QCA6174/hw2.1/board-2.bin« können nicht nach »/lib/firmware/ath10k/QCA6174/hw2.1/board-2.bin.dpkg-new« kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms InstallationDate: Installed on 2019-01-15 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: linux-firmware Title: package linux-firmware 1.175 failed to install/upgrade: Extrahierte Daten für »./lib/firmware/ath10k/QCA6174/hw2.1/board-2.bin« können nicht nach »/lib/firmware/ath10k/QCA6174/hw2.1/board-2.bin.dpkg-new« kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1811858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
