[Kernel-packages] [Bug 1831751] Re: rtlwifi: aggresive memory leak
TJ,
Will you send the patch to kernel-team mailing list?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1831751
Title:
rtlwifi: aggresive memory leak
Status in linux package in Ubuntu:
Confirmed
Bug description:
Hey, i got a memory leak on Ubuntu 18.04.2 even in console mode (no X/GUI)
the memory usage grows slowly to take all the available RAM when i let the
computer running over the night (with just top and irssi), and i have to reboot
to get things back to normal. I didn't have this problem on Ubuntu 17.10 but i
was still flooded with message about pci aer taking lots of disk space in the
logs, but pci=noaer fixed this problem and i had no memory leak.
The computer is a common laptop: HP Pavilion.
---
Kernel log gets spammed with AERs so owner uses "pci=noaer"; that was briefly
disabled to capture the AERs.
Memory seems to be consumed (~6 GB of 8GB) just by leaving PC
overnight booted just to console (systemd.unit=multi-user.target).
The memory leak doesn't affect Windows but owner is going to check
Windows Event Log for signs of AERs being logged.
---
Original suspect of AER is not guilty.
This turns out to be a bug in the rtlwifi driver where in some rare
circumstances it fails to free an sk_buf.
Reporter has been testing a DKMS build of rtlwfi with the fix applied
and confirms it solves the issue.
Upstream has the commit. Can we get this cherry-picked into all
releases?
commit 8cfa272b0d321160ebb5b45073e39ef0a6ad73f2
Author: Larry Finger
Date: Sat Nov 17 20:55:03 2018 -0600
rtlwifi: Fix leak of skb when processing C2H_BT_INFO
With commit 0a9f8f0a1ba9 ("rtlwifi: fix btmpinfo timeout while processing
C2H_BT_INFO"), calling rtl_c2hcmd_enqueue() with rtl_c2h_fast_cmd() true,
the routine returns without freeing that skb, thereby leaking it.
This issue has been discussed at
https://github.com/lwfinger/rtlwifi_new/issues/401
and the fix tested there.
Fixes: 0a9f8f0a1ba9 ("rtlwifi: fix btmpinfo timeout while processing
C2H_BT_INFO")
Reported-and-tested-by: Francisco Machado Magalhães Neto
Cc: Francisco Machado Magalhães Neto
Cc: Ping-Ke Shih
Cc: Stable # 4.18+
Signed-off-by: Larry Finger
Signed-off-by: Kalle Valo
diff --git a/drivers/net/wireless/realtek/rtlwifi/base.c
b/drivers/net/wireless/realtek/rtlwifi/base.c
index f4122c8fdd97..ef9b502ce576 100644
--- a/drivers/net/wireless/realtek/rtlwifi/base.c
+++ b/drivers/net/wireless/realtek/rtlwifi/base.c
@@ -2289,6 +2289,7 @@ void rtl_c2hcmd_enqueue(struct ieee80211_hw *hw, struct
sk_buff *skb)
if (rtl_c2h_fast_cmd(hw, skb)) {
rtl_c2h_content_parsing(hw, skb);
+ kfree_skb(skb);
return;
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831751/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
+1 also affected by this. Kubuntu 18.04 kernel 5.0.0-05-generic on Asus ZenBook UX433FN -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle
For distros other than Ubuntu, please compile your own kernel. The simplest way to do it is to use nvme-5.3 branch: http://git.infradead.org/nvme.git/shortlog/refs/heads/nvme-5.3 And pick the following two PCI patches: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d491f2b75237ef37d8867830ab7fad8d9659e853 https://patchwork.kernel.org/patch/10993697/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808957 Title: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle Status in linux package in Ubuntu: Confirmed Bug description: It seems that the Dell 9370 is set to go into s2idle mode rather than deep sleep, forgoing significant power savings. I have confirmed this by suspending and then checking: sudo journalctl | grep "PM: suspend" | tail -2. If the output is PM: suspend entry (s2idle) PM: suspend exit cat /sys/power/mem_sleep showed [s2idle] deep As a temporary fix, I typed echo deep > /sys/power/mem_sleep as a root user (sudo -i). Then the output of cat /sys/power/mem_sleep was s2idle [deep] After suspending now, sudo journalctl | grep "PM: suspend" | tail -2 returns PM: suspend entry (deep) PM: suspend exit I have made this permanent by editing /etc/default/grub and replacing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep" then regenerating my grub configuration (sudo grub-mkconfig -o /boot/grub/grub.cfg). This appears to be working with no ill effects. Credit to https://askubuntu.com/a/1036122/470077 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron-work 3672 F pulseaudio /dev/snd/pcmC0D0p: aaron-work 3672 F...m pulseaudio Date: Tue Dec 18 09:52:44 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/ubuntu-vg/swap_1 InstallationDate: Installed on 2018-09-04 (104 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-26 (52 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796443] Re: HP EliteBook 745 G5 (Ryzen 2500U) fails to boot unless `mce=off` is set on command line
Jon, Please test kernels here: https://people.canonical.com/~khfeng/lp1796443/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796443 Title: HP EliteBook 745 G5 (Ryzen 2500U) fails to boot unless `mce=off` is set on command line Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: My new Elitebook, with the latest bios 1.03.01, refuses to boot any kernel later than 4.10 unless mce=off is appended to the kernel command line. As in, there are no kernel messages at all after grub (yes, quiet and splash were removed from the command line). Perhaps it crashes before the efifb kicks in? System operates fine if mce=off is added to the kernel command line (and iommu=soft, but that's a separate issue, and fails with kernel output in that case). I opened upstream bug here : https://bugzilla.kernel.org/show_bug.cgi?id=201291 I bisected the problem down to this commit (and the few before it, which also added extra MCE output, but didn't actually crash): 18807ddb7f88d4ac3797302bafb18143d573e66f is the first bad commit commit 18807ddb7f88d4ac3797302bafb18143d573e66f Author: Yazen Ghannam Date: Tue Nov 15 15:13:53 2016 -0600 x86/mce/AMD: Reset Threshold Limit after logging error The error count field in MCA_MISC does not get reset by hardware when the threshold has been reached. Software is expected to reset it. Currently, the threshold limit only gets reset during init or when a user writes to sysfs. If the user is not monitoring threshold interrupts and resetting the limit then the user will only see 1 interrupt when the limit is first hit. So if, for example, the limit is set to 10 then only 1 interrupt will be recorded after 10 errors even if 100 errors have occurred. The user may then assume that only 10 errors have occurred. There are threads online about this being related to the latest bios. The upstream bug has acpidump attached. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2015 F pulseaudio /dev/snd/pcmC1D0p: john 2015 F...m pulseaudio /dev/snd/controlC0: john 2015 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Oct 5 23:24:45 2018 InstallationDate: Installed on 2018-09-30 (5 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) Lsusb: Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 004 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 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteBook 745 G5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=5cf73665-d2a3-4203-80fd-659faf1afea4 ro quiet splash iommu=soft mce=off RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: r8822be UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2018 dmi.bios.vendor: HP dmi.bios.version: Q81 Ver. 01.03.01 dmi.board.name: 83D5 dmi.board.vendor: HP dmi.board.version: KBC Version 08.47.00 dmi.chassis.asset.tag: 5CG838305Y dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ81Ver.01.03.01:bd07/26/2018:svnHP:pnHPEliteBook745G5:pvr:rvnHP:rn83D5:rvrKBCVersion08.47.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 745 G5 dmi.product.sku: 2MG23AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796443/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809224] Re: To support Intel Wireless-AX 22000 series
** Changed in: linux-oem-osp1 (Ubuntu) Status: New => 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/1809224 Title: To support Intel Wireless-AX 22000 series Status in linux package in Ubuntu: In Progress Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Committed Bug description: [Impact] New Intel Cyclone Peak Wifi doesn't work without newly added driver. [Fix] Cherry pick iwlwifi commits from v5.0 to v5.1, and confirmed with proper firmware the wifi works. [Test] Verified on AX200NGW & 22560NGW chips & Killer 1653 card, wifi works well. [Regression Potential] Medium, it affects the whole iwlwifi driver, but I've verified it with fwst S3 test, and the wifi is still working after S3 test 30 times. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832795] 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 1832795 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832795 Title: updates to aufs Status in linux package in Ubuntu: Incomplete Bug description: I have found and reported a critical bug in aufs (as shipped with the latest Ubuntu kernels, both on Bionic and Xenial), which potentially affects anyone running Docker on Ubuntu using aufs graph driver. The fix has been developed, tested at least by me to fix the issue, and committed into upstream aufs git repos The nature of the bug is, in case of multiple parallels aufs mounts and unmounts, the kernel can screw up krefs, and once that happens, the only remedy is to reboot it (as commands like mount/umount or cat /proc/mounts are all stuck in syscalls). I would appreciate syncing aufs with the latest upstream release from git, as it was done a few times already, or at least taking the below fix (whatever suits maintainers better). The fixed versions are the ones marked with 20190610, and from what I see they are available for all kernel versions since 4.14 (for example, 4.15 tree is here: https://github.com/sfjro/aufs4-standalone/commits/aufs4.15). For 4.4, a backport might be needed, but it should be trivial. Original bug report: https://sourceforge.net/p/aufs/mailman/message/36680389/ Fix: https://github.com/sfjro/aufs4-linux/commit/b633d7b2635b9615fe294b85257d05008e3747a3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832795/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830822] Re: Killer 1650X Wifi/BT(2723:1654) fails to load correct firmware
This commit is in backport-iwlwifi dkms package and in oem-b-osp1 5.0 kernel, so close it. ** Changed in: linux-oem (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1830822 Title: Killer 1650X Wifi/BT(2723:1654) fails to load correct firmware Status in HWE Next: New Status in linux-oem package in Ubuntu: Fix Released Bug description: Killer series loadded IWL_22000_HR_B_FW_PRE prefixed firmware instead IWL_CC_A_FW_PRE prefixed firmware, and firmware named iwlwifi-QuQnj-b0-hr-b0-XX.ucode doesn't exist. [ 4.252701] iwlwifi :03:00.0: enabling device ( -> 0002) [ 4.263301] iwlwifi :03:00.0: Direct firmware load for iwlwifi-QuQnj-b0-hr-b0-46.ucode failed with error -2 [ 4.263372] iwlwifi :03:00.0: Direct firmware load for iwlwifi-QuQnj-b0-hr-b0-45.ucode failed with error -2 [ 4.263517] iwlwifi :03:00.0: Direct firmware load for iwlwifi-QuQnj-b0-hr-b0-44.ucode failed with error -2 [ 4.263589] iwlwifi :03:00.0: Direct firmware load for iwlwifi-QuQnj-b0-hr-b0-43.ucode failed with error -2 [ 4.263658] iwlwifi :03:00.0: Direct firmware load for iwlwifi-QuQnj-b0-hr-b0-42.ucode failed with error -2 [ 4.263663] iwlwifi :03:00.0: Direct firmware load for iwlwifi-QuQnj-b0-hr-b0-41.ucode failed with error -2 [ 4.263668] iwlwifi :03:00.0: Direct firmware load for iwlwifi-QuQnj-b0-hr-b0-40.ucode failed with error -2 [ 4.263673] iwlwifi :03:00.0: Direct firmware load for iwlwifi-QuQnj-b0-hr-b0-39.ucode failed with error -2 [ 4.263675] iwlwifi :03:00.0: no suitable firmware found! [ 4.263676] iwlwifi :03:00.0: minimum version required: iwlwifi-QuQnj-b0-hr-b0-39 [ 4.263677] iwlwifi :03:00.0: maximum version supported: iwlwifi-QuQnj-b0-hr-b0-46 [ 4.263678] iwlwifi :03:00.0: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1830822/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771252] Re: [ICL] Enable intel_rapl driver for Icelake
** Changed in: linux-oem-osp1 (Ubuntu) Status: New => 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/1771252 Title: [ICL] Enable intel_rapl driver for Icelake Status in intel: Fix Committed Status in linux package in Ubuntu: Incomplete Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Committed Bug description: Desription: This feature is intended to track intel_rapl driver enabling for IceLake. Commit:Powercap/intel_rapl driver enabling for Icelake Target Release: 19.10 Target Kernel: 5.1 SRU Justification [Impact] New CPU is required to be listed in Intel RAPL (Running Average Power Limit) driver. [Fix] From Intel's suggestion, below 2 commits are required ba6f3ec198d5 powercap/intel_rapl: add Ice Lake mobile df7f8e00a50f powercap: intel_rapl: add support for Jacobsville [Test] Boot up Intel ICL-Y SDP with the patched kernel, nothing abnormal, but I'm unable to distinguish the difference. [Regression Potential] Low, the 2 commits add new ID to the table, should affect new CPU only. To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1771252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832795] [NEW] updates to aufs
Public bug reported: I have found and reported a critical bug in aufs (as shipped with the latest Ubuntu kernels, both on Bionic and Xenial), which potentially affects anyone running Docker on Ubuntu using aufs graph driver. The fix has been developed, tested at least by me to fix the issue, and committed into upstream aufs git repos The nature of the bug is, in case of multiple parallels aufs mounts and unmounts, the kernel can screw up krefs, and once that happens, the only remedy is to reboot it (as commands like mount/umount or cat /proc/mounts are all stuck in syscalls). I would appreciate syncing aufs with the latest upstream release from git, as it was done a few times already, or at least taking the below fix (whatever suits maintainers better). The fixed versions are the ones marked with 20190610, and from what I see they are available for all kernel versions since 4.14 (for example, 4.15 tree is here: https://github.com/sfjro/aufs4-standalone/commits/aufs4.15). For 4.4, a backport might be needed, but it should be trivial. Original bug report: https://sourceforge.net/p/aufs/mailman/message/36680389/ Fix: https://github.com/sfjro/aufs4-linux/commit/b633d7b2635b9615fe294b85257d05008e3747a3 ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1832795 Title: updates to aufs Status in linux package in Ubuntu: Incomplete Bug description: I have found and reported a critical bug in aufs (as shipped with the latest Ubuntu kernels, both on Bionic and Xenial), which potentially affects anyone running Docker on Ubuntu using aufs graph driver. The fix has been developed, tested at least by me to fix the issue, and committed into upstream aufs git repos The nature of the bug is, in case of multiple parallels aufs mounts and unmounts, the kernel can screw up krefs, and once that happens, the only remedy is to reboot it (as commands like mount/umount or cat /proc/mounts are all stuck in syscalls). I would appreciate syncing aufs with the latest upstream release from git, as it was done a few times already, or at least taking the below fix (whatever suits maintainers better). The fixed versions are the ones marked with 20190610, and from what I see they are available for all kernel versions since 4.14 (for example, 4.15 tree is here: https://github.com/sfjro/aufs4-standalone/commits/aufs4.15). For 4.4, a backport might be needed, but it should be trivial. Original bug report: https://sourceforge.net/p/aufs/mailman/message/36680389/ Fix: https://github.com/sfjro/aufs4-linux/commit/b633d7b2635b9615fe294b85257d05008e3747a3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832795/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
Nvidia 430.26 behaves a bit differently. It just fails to start as non- root and gives reasons: [ 897.467] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted) ... [ 897.470] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the [ 897.470] (EE) NVIDIA: system's kernel log for additional error messages and [ 897.470] (EE) NVIDIA: consult the NVIDIA README for details. [ 897.470] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the [ 897.470] (EE) NVIDIA: system's kernel log for additional error messages and [ 897.470] (EE) NVIDIA: consult the NVIDIA README for details. [ 897.470] (EE) [drm] Failed to open DRM device for (null): -2 [ 897.470] (EE) [drm] Failed to open DRM device for pci::01:00.0: -2 So then the NVIDIA driver gives up and Xorg tries the modeset driver instead. Modeset seems to detect my monitor fine (got the EDID) but then fails with bug 1813897. This is now a bit off-topic, but I suspect the above problem with nvidia-430 will have the same fix as this bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-375 in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg Status in gdm3 package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827697] Re: Enroll key whiptail prompt blocks kernel header package upgrades
@juliank
To trigger the bug:
1. Install any out-of-tree dkms packages (like bbswitch-dkms)
2. Un-enroll keys from MOK, ensure `mokutil --test-key
/var/lib/shim-signed/mok/MOK.der` command returns
"/var/lib/shim-signed/mok/MOK.der is not enrolled"
3. Ensure SecureBoot is enabled
4. Install any linux-headers-${version}-generic packages that is currently not
installed, verify if it stucks at configurating state
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1827697
Title:
Enroll key whiptail prompt blocks kernel header package upgrades
Status in dkms package in Ubuntu:
Fix Released
Status in dkms source package in Xenial:
Fix Committed
Status in dkms source package in Bionic:
Fix Committed
Status in dkms source package in Cosmic:
Fix Committed
Status in dkms source package in Disco:
Fix Committed
Status in dkms source package in Eoan:
Fix Released
Bug description:
I noticed that sometimes the system upgrade is blocked in the kernel
header package's configure phase, in the process manager I found that
it is blocked by the "Configuring Secure Boot" whiptail prompt started
by `update-secureboot-policy --enroll-key` which doesn't surface to
the terminal and hence not interactable.
Refer the attached screenshot for the process status at the time.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1827697/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
is it because of this? (is the file new?) intel-microcode-blacklist.conf : # The microcode module attempts to apply a microcode update when # it autoloads. This is not always safe, so we block it by default. blacklist microcode -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829620 Title: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: Description: - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of booting, after grub) - does not even show the enter cryptsetup passphrase - affected kernels: # apt list --installed |grep linux-signed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 [installed] linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 amd64 [installed] linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 5.0.0.15.71 amd64 [installed] - the setup is not new, has been working perfectly before (about 7 days since my last restart?) System: - HW: ASUS Zenbook 14 UX433FN - Ubuntu 18.04, runing latest HWE, fully updated - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), Suspected/possible cause?: - recent intel-microcode package update - recent kernel package updates Steps taken: - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding nosplash, noplymouth) - completely removed nvidia drivers (apt purge *nvidia*) - completely purged and reinstalled grub (grup-pc) - completely purged and reinstalled all kernels (headers, modules, image, ..) - toggle BIOS "fastboot" (now using OFF) - toggle UEFI SecureBoot (now using ON) - remove plymouth (apt remove *plymouth* , but the workaround is working with plymouth installed) Workaround: - so far, I'm only able to boot with non-Ubuntu kernel! (linux-image-liquorix-amd64) - which needs "splash" option ON - reinstall cryptsetup & update-grub (as suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 ) I am not sure how to get you more debug info, as this setup has been working before, and it's a very eary boot-process bug, so I can't even access dmesg etc. EDIT: Hypothesis: Only affects ASUS with i7-8565U Whiskey Lake Intel CPU Upstream Bug Report: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 WORKAROUND 1: disable intel microcode updates during boot From this bug: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920 1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub 2/ update-grub WORKAROUND 2: downgrade (and hold) intel-microcode to older version from bionic/main apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2337 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge (not installed) Tags: bionic wayland-session Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2339 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Tags: third-party-packages bionic wayland-session Uname: Linux 5.0.0-15-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
Hey, I'm the OP, I can confirm @felix-ticona 's finding, after the kernel upgrade (atleast HWE to the -21 revision and the issue is "magically" done). # uname -a Linux xxx 4.18.0-21-generic #22~18.04.1-Ubuntu SMP Thu May 16 15:07:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux # dmesg | grep command [0.00] Kernel command line: BOOT_IMAGE=/vmlinuz-4.18.0-21-generic root=UUID=xxx ro rootflags=subvol=@ubuntu ro kaslr resume=xxx mem_sleep_default=deep dm_mod.use_blk_mq=1 acpi_osi=Linux acpi_backlight=vendor quiet Notice no dis_ucode_ldr (=no workaround 1) # apt-cache policy intel-microcode intel-microcode: Installed: 3.20190514.0ubuntu0.18.04.3 Candidate: 3.20190514.0ubuntu0.18.04.3 Version table: *** 3.20190514.0ubuntu0.18.04.3 500 500 mirror://mirrors.ubuntu.com/mirrors.txt bionic-security/main amd64 Packages 500 mirror://mirrors.ubuntu.com/mirrors.txt bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.20180312.0~ubuntu18.04.1 500 500 mirror://mirrors.ubuntu.com/mirrors.txt bionic/main amd64 Packages (=no workaround 2: old intel-microcode package holding) TODO: test main kernel (4.15) and hwe-edge (5.0) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829620 Title: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: Description: - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of booting, after grub) - does not even show the enter cryptsetup passphrase - affected kernels: # apt list --installed |grep linux-signed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 [installed] linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 amd64 [installed] linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 5.0.0.15.71 amd64 [installed] - the setup is not new, has been working perfectly before (about 7 days since my last restart?) System: - HW: ASUS Zenbook 14 UX433FN - Ubuntu 18.04, runing latest HWE, fully updated - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), Suspected/possible cause?: - recent intel-microcode package update - recent kernel package updates Steps taken: - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding nosplash, noplymouth) - completely removed nvidia drivers (apt purge *nvidia*) - completely purged and reinstalled grub (grup-pc) - completely purged and reinstalled all kernels (headers, modules, image, ..) - toggle BIOS "fastboot" (now using OFF) - toggle UEFI SecureBoot (now using ON) - remove plymouth (apt remove *plymouth* , but the workaround is working with plymouth installed) Workaround: - so far, I'm only able to boot with non-Ubuntu kernel! (linux-image-liquorix-amd64) - which needs "splash" option ON - reinstall cryptsetup & update-grub (as suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 ) I am not sure how to get you more debug info, as this setup has been working before, and it's a very eary boot-process bug, so I can't even access dmesg etc. EDIT: Hypothesis: Only affects ASUS with i7-8565U Whiskey Lake Intel CPU Upstream Bug Report: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 WORKAROUND 1: disable intel microcode updates during boot From this bug: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920 1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub 2/ update-grub WORKAROUND 2: downgrade (and hold) intel-microcode to older version from bionic/main apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2337 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge (not installed) Tags: bionic wayland-session Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2339 days ago) InstallationMedia: Kub
[Kernel-packages] [Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
Can someone pin-point what the change is in HWE kernel rebuilds -20 and -21? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829620 Title: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: Description: - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of booting, after grub) - does not even show the enter cryptsetup passphrase - affected kernels: # apt list --installed |grep linux-signed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 [installed] linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 amd64 [installed] linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 5.0.0.15.71 amd64 [installed] - the setup is not new, has been working perfectly before (about 7 days since my last restart?) System: - HW: ASUS Zenbook 14 UX433FN - Ubuntu 18.04, runing latest HWE, fully updated - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), Suspected/possible cause?: - recent intel-microcode package update - recent kernel package updates Steps taken: - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding nosplash, noplymouth) - completely removed nvidia drivers (apt purge *nvidia*) - completely purged and reinstalled grub (grup-pc) - completely purged and reinstalled all kernels (headers, modules, image, ..) - toggle BIOS "fastboot" (now using OFF) - toggle UEFI SecureBoot (now using ON) - remove plymouth (apt remove *plymouth* , but the workaround is working with plymouth installed) Workaround: - so far, I'm only able to boot with non-Ubuntu kernel! (linux-image-liquorix-amd64) - which needs "splash" option ON - reinstall cryptsetup & update-grub (as suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 ) I am not sure how to get you more debug info, as this setup has been working before, and it's a very eary boot-process bug, so I can't even access dmesg etc. EDIT: Hypothesis: Only affects ASUS with i7-8565U Whiskey Lake Intel CPU Upstream Bug Report: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 WORKAROUND 1: disable intel microcode updates during boot From this bug: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920 1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub 2/ update-grub WORKAROUND 2: downgrade (and hold) intel-microcode to older version from bionic/main apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2337 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge (not installed) Tags: bionic wayland-session Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2339 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Tags: third-party-packages bionic wayland-session Uname: Linux 5.0.0-15-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
** Also affects: qemu (Ubuntu Eoan) Importance: Wishlist Assignee: Rafael David Tinoco (rafaeldtinoco) Status: Confirmed ** Also affects: linux (Ubuntu Eoan) Importance: Wishlist Status: Confirmed ** Also affects: qemu (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: qemu (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: qemu (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu Disco) Status: New => Confirmed ** Changed in: qemu (Ubuntu Cosmic) Status: New => Confirmed ** Changed in: qemu (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828495 Title: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM. Status in intel: New Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Confirmed Status in linux source package in Bionic: New Status in qemu source package in Bionic: Confirmed Status in linux source package in Cosmic: New Status in qemu source package in Cosmic: Confirmed Status in linux source package in Disco: New Status in qemu source package in Disco: Confirmed Status in linux source package in Eoan: Confirmed Status in qemu source package in Eoan: Confirmed Bug description: This is a bug. Test Environment: Repro Steps: 1. Boot up guest using: -cpu Cascadelake-Server [root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive if=virtio,id=hd,file=/home/x/x,format=qcow2 -m 4096 -smp 4 -cpu Cascadelake-Server -serial stdio char device redirected to /dev/pts/3 (label serial0) qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] 2. To check CPU ID related to features[FEAT_7_0_EDX] ：CPUID_7_0_EDX_ARCH_CAPABILITIES Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be 1. Actual Result: Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b ecx=0x0818 edx=0xbc00 (EDX bit 29=1) Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9 ecx=0x0818 edx=0x8400 (EDX bit 29=0) Commit:2bdb76c015df7125783d8394d6339d181cb5bc30 Target Kerned: 5.1 Target Release: 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1828495/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832776] Re: Backport VMCI PPN64 patch
** Changed in: linux (Debian) 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/1832776 Title: Backport VMCI PPN64 patch Status in linux package in Ubuntu: Confirmed Status in linux package in Debian: New Bug description: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic? I have already filed a bug with Debian[2]. Here is the commit log: commit f2db7361cb19bf3a6f7fd367f21d8eb325397946 Author: Vishnu DASA Commit: Greg Kroah-Hartman VMCI: Support upto 64-bit PPNs Add support in the VMCI driver to handle upto 64-bit PPNs when the VMCI device exposes the capability for 64-bit PPNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f2db7361cb19bf3a6f7fd367f21d8eb325397946 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929824 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adit 3290 F pulseaudio /dev/snd/controlC0: adit 3290 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723 InstallationDate: Installed on 2018-11-06 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: eno1 no wireless extensions. lono wireless extensions. docker0 no wireless extensions. MachineType: Dell Inc. Precision T3600 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827697] Re: Enroll key whiptail prompt blocks kernel header package upgrades
I have applied the updates on bionic and can no longer reproduce it. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1827697 Title: Enroll key whiptail prompt blocks kernel header package upgrades Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Xenial: Fix Committed Status in dkms source package in Bionic: Fix Committed Status in dkms source package in Cosmic: Fix Committed Status in dkms source package in Disco: Fix Committed Status in dkms source package in Eoan: Fix Released Bug description: I noticed that sometimes the system upgrade is blocked in the kernel header package's configure phase, in the process manager I found that it is blocked by the "Configuring Secure Boot" whiptail prompt started by `update-secureboot-policy --enroll-key` which doesn't surface to the terminal and hence not interactable. Refer the attached screenshot for the process status at the time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1827697/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832641] Re: 4.15.0-46-generic doesn't support ethtool adaptive-tx for mlx5 card
Did this work correctly in previous 4.15.0 kernels? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832641 Title: 4.15.0-46-generic doesn't support ethtool adaptive-tx for mlx5 card Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu Bionic 18.04 LTS: We found that default bionic kernel 4.15.0-46-generic doesn't support ethtool -C adaptive-tx Our ethernet card is Mellanox Connect4-Lx and Connect5, and this will affect performance of latency sensitive workloads like memcached. Maybe we should backport adaptive-tx support to kernel 4.15 LTS? Xeon Skylake 8168 x86_64: ubuntu kernel 4.15.0-46-generic eth: mlx5 connect-5 ethtool doesn't support adaptive-tx (ethernet TX interrupt coalesce) X-Gene3 aarch64: ubuntu kernel 4.18.0-16-generic, eth: mlx5 connect-4lx ethtool supports adaptive-tx (ethernet TX interrupt coalesce) Same Xeon Skylake 8168 x86_64 latest kernel 5.2.0-rc2 eth: mlx5 connect-5 ethtool supports adaptive-tx (ethernet TX interrupt coalesce) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 12 14:42 seq crw-rw 1 root audio 116, 33 Jun 12 14:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: AmpereComputing(R) OSPREY EV-883832-X3-0001 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=698f489c-124b-4ebb-b6c3-14c8b82c978d ro console=ttyAMA0,115200 iommu.passthrough=1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.18.0-16-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/25/2018 dmi.bios.vendor: Ampere(TM) dmi.bios.version: 4.8.19 dmi.board.asset.tag: APCX3A1-A526-16050501200016 dmi.board.name: OSPREY dmi.board.vendor: AmpereComputing(R) dmi.board.version: EV-883832-X3-OD1-2 dmi.chassis.asset.tag: APCX3A1-A526-16050501200016 dmi.chassis.type: 23 dmi.chassis.vendor: AmpereComputing(R) dmi.chassis.version: APCA1A1- dmi.modalias: dmi:bvnAmpere(TM):bvr4.8.19:bd09/25/2018:svnAmpereComputing(R):pnOSPREYEV-883832-X3-0001:pvrPR010:rvnAmpereComputing(R):rnOSPREY:rvrEV-883832-X3-OD1-2:cvnAmpereComputing(R):ct23:cvrAPCA1A1-: dmi.product.family: eMAG dmi.product.name: OSPREY EV-883832-X3-0001 dmi.product.sku: EV-883832-X3-OBX-1 dmi.product.version: PR010 dmi.sys.vendor: AmpereComputing(R) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 12 15:22 seq crw-rw 1 root audio 116, 33 Jun 12 15:22 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1604:10c0 Tascam Bus 001 Device 003: ID 1604:10c0 Tascam Bus 001 Device 002: ID 1604:10c0 Tascam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R640 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=cc79d3b3-63ee-450d-84ff-ddd80ab73c80 ro intel_pstate=disable console=ttyS0,115200n8 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname
[Kernel-packages] [Bug 1832782] Re: Backport VMW_PVRDMA PPN64 patch
Oops, it should be VMW_PVRDMA instead of VMCI in the first comment. Everything else is correct. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832782 Title: Backport VMW_PVRDMA PPN64 patch Status in linux package in Ubuntu: Confirmed Bug description: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic and later? Here is the commit log: commit 8aa04ad3b39396e315b23448c56d5465200fa777 Author: Adit Ranadive Date: Sat Jan 26 05:09:36 2019 + RDMA/vmw_pvrdma: Support upto 64-bit PFNs Update the driver to use the new device capability to report 64-bit UAR PFNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8aa04ad3b39396e315b23448c56d5465200fa777 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2010 F pulseaudio adit 3290 F pulseaudio /dev/snd/controlC0: gdm2010 F pulseaudio adit 3290 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723 InstallationDate: Installed on 2018-11-06 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: eno1 no wireless extensions. lono wireless extensions. docker0 no wireless extensions. MachineType: Dell Inc. Precision T3600 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832782] 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/1832782 Title: Backport VMW_PVRDMA PPN64 patch Status in linux package in Ubuntu: Confirmed Bug description: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic and later? Here is the commit log: commit 8aa04ad3b39396e315b23448c56d5465200fa777 Author: Adit Ranadive Date: Sat Jan 26 05:09:36 2019 + RDMA/vmw_pvrdma: Support upto 64-bit PFNs Update the driver to use the new device capability to report 64-bit UAR PFNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8aa04ad3b39396e315b23448c56d5465200fa777 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2010 F pulseaudio adit 3290 F pulseaudio /dev/snd/controlC0: gdm2010 F pulseaudio adit 3290 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723 InstallationDate: Installed on 2018-11-06 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: eno1 no wireless extensions. lono wireless extensions. docker0 no wireless extensions. MachineType: Dell Inc. Precision T3600 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829749] Re: Please add support for zipl signing
s390-tools in UNAPPROVED
https://launchpad.net/ubuntu/eoan/+queue?queue_state=1&queue_text=s390-tools
s390-tools-signed in source NEW
https://launchpad.net/ubuntu/eoan/+queue?queue_state=0&queue_text=s390-tools-signed
** Summary changed:
- Please add support for zipl signing
+ Please add support for sipl
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1829749
Title:
Please add support for sipl
Status in Launchpad itself:
Fix Released
Status in linux-signed package in Ubuntu:
New
Status in s390-tools package in Ubuntu:
Fix Committed
Bug description:
Please add support for zipl ("z/ecureBoot") signing.
It should be similar to opal signing, but using the new zipl signing
key.
I am expecting to sign s390-tools stage3.bin and kernel images using
this key.
s390-tools -> can be signed already
kernels -> should only sign v5.2+
To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1829749/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832782] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1832782/+attachment/5270676/+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/1832782 Title: Backport VMW_PVRDMA PPN64 patch Status in linux package in Ubuntu: Confirmed Bug description: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic and later? Here is the commit log: commit 8aa04ad3b39396e315b23448c56d5465200fa777 Author: Adit Ranadive Date: Sat Jan 26 05:09:36 2019 + RDMA/vmw_pvrdma: Support upto 64-bit PFNs Update the driver to use the new device capability to report 64-bit UAR PFNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8aa04ad3b39396e315b23448c56d5465200fa777 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2010 F pulseaudio adit 3290 F pulseaudio /dev/snd/controlC0: gdm2010 F pulseaudio adit 3290 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723 InstallationDate: Installed on 2018-11-06 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: eno1 no wireless extensions. lono wireless extensions. docker0 no wireless extensions. MachineType: Dell Inc. Precision T3600 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832782] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1832782/+attachment/5270681/+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/1832782 Title: Backport VMW_PVRDMA PPN64 patch Status in linux package in Ubuntu: Confirmed Bug description: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic and later? Here is the commit log: commit 8aa04ad3b39396e315b23448c56d5465200fa777 Author: Adit Ranadive Date: Sat Jan 26 05:09:36 2019 + RDMA/vmw_pvrdma: Support upto 64-bit PFNs Update the driver to use the new device capability to report 64-bit UAR PFNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8aa04ad3b39396e315b23448c56d5465200fa777 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2010 F pulseaudio adit 3290 F pulseaudio /dev/snd/controlC0: gdm2010 F pulseaudio adit 3290 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723 InstallationDate: Installed on 2018-11-06 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: eno1 no wireless extensions. lono wireless extensions. docker0 no wireless extensions. MachineType: Dell Inc. Precision T3600 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832782] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1832782/+attachment/5270673/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832782 Title: Backport VMW_PVRDMA PPN64 patch Status in linux package in Ubuntu: Confirmed Bug description: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic and later? Here is the commit log: commit 8aa04ad3b39396e315b23448c56d5465200fa777 Author: Adit Ranadive Date: Sat Jan 26 05:09:36 2019 + RDMA/vmw_pvrdma: Support upto 64-bit PFNs Update the driver to use the new device capability to report 64-bit UAR PFNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8aa04ad3b39396e315b23448c56d5465200fa777 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2010 F pulseaudio adit 3290 F pulseaudio /dev/snd/controlC0: gdm2010 F pulseaudio adit 3290 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723 InstallationDate: Installed on 2018-11-06 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: eno1 no wireless extensions. lono wireless extensions. docker0 no wireless extensions. MachineType: Dell Inc. Precision T3600 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832782] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1832782/+attachment/5270683/+files/WifiSyslog.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/1832782 Title: Backport VMW_PVRDMA PPN64 patch Status in linux package in Ubuntu: Confirmed Bug description: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic and later? Here is the commit log: commit 8aa04ad3b39396e315b23448c56d5465200fa777 Author: Adit Ranadive Date: Sat Jan 26 05:09:36 2019 + RDMA/vmw_pvrdma: Support upto 64-bit PFNs Update the driver to use the new device capability to report 64-bit UAR PFNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8aa04ad3b39396e315b23448c56d5465200fa777 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2010 F pulseaudio adit 3290 F pulseaudio /dev/snd/controlC0: gdm2010 F pulseaudio adit 3290 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723 InstallationDate: Installed on 2018-11-06 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: eno1 no wireless extensions. lono wireless extensions. docker0 no wireless extensions. MachineType: Dell Inc. Precision T3600 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832782] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1832782/+attachment/5270682/+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/1832782 Title: Backport VMW_PVRDMA PPN64 patch Status in linux package in Ubuntu: Confirmed Bug description: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic and later? Here is the commit log: commit 8aa04ad3b39396e315b23448c56d5465200fa777 Author: Adit Ranadive Date: Sat Jan 26 05:09:36 2019 + RDMA/vmw_pvrdma: Support upto 64-bit PFNs Update the driver to use the new device capability to report 64-bit UAR PFNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8aa04ad3b39396e315b23448c56d5465200fa777 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2010 F pulseaudio adit 3290 F pulseaudio /dev/snd/controlC0: gdm2010 F pulseaudio adit 3290 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723 InstallationDate: Installed on 2018-11-06 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: eno1 no wireless extensions. lono wireless extensions. docker0 no wireless extensions. MachineType: Dell Inc. Precision T3600 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832782] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1832782/+attachment/5270680/+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/1832782 Title: Backport VMW_PVRDMA PPN64 patch Status in linux package in Ubuntu: Confirmed Bug description: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic and later? Here is the commit log: commit 8aa04ad3b39396e315b23448c56d5465200fa777 Author: Adit Ranadive Date: Sat Jan 26 05:09:36 2019 + RDMA/vmw_pvrdma: Support upto 64-bit PFNs Update the driver to use the new device capability to report 64-bit UAR PFNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8aa04ad3b39396e315b23448c56d5465200fa777 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2010 F pulseaudio adit 3290 F pulseaudio /dev/snd/controlC0: gdm2010 F pulseaudio adit 3290 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723 InstallationDate: Installed on 2018-11-06 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: eno1 no wireless extensions. lono wireless extensions. docker0 no wireless extensions. MachineType: Dell Inc. Precision T3600 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832782] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1832782/+attachment/5270678/+files/ProcCpuinfo.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/1832782 Title: Backport VMW_PVRDMA PPN64 patch Status in linux package in Ubuntu: Confirmed Bug description: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic and later? Here is the commit log: commit 8aa04ad3b39396e315b23448c56d5465200fa777 Author: Adit Ranadive Date: Sat Jan 26 05:09:36 2019 + RDMA/vmw_pvrdma: Support upto 64-bit PFNs Update the driver to use the new device capability to report 64-bit UAR PFNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8aa04ad3b39396e315b23448c56d5465200fa777 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2010 F pulseaudio adit 3290 F pulseaudio /dev/snd/controlC0: gdm2010 F pulseaudio adit 3290 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723 InstallationDate: Installed on 2018-11-06 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: eno1 no wireless extensions. lono wireless extensions. docker0 no wireless extensions. MachineType: Dell Inc. Precision T3600 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832782] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1832782/+attachment/5270679/+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/1832782 Title: Backport VMW_PVRDMA PPN64 patch Status in linux package in Ubuntu: Confirmed Bug description: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic and later? Here is the commit log: commit 8aa04ad3b39396e315b23448c56d5465200fa777 Author: Adit Ranadive Date: Sat Jan 26 05:09:36 2019 + RDMA/vmw_pvrdma: Support upto 64-bit PFNs Update the driver to use the new device capability to report 64-bit UAR PFNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8aa04ad3b39396e315b23448c56d5465200fa777 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2010 F pulseaudio adit 3290 F pulseaudio /dev/snd/controlC0: gdm2010 F pulseaudio adit 3290 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723 InstallationDate: Installed on 2018-11-06 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: eno1 no wireless extensions. lono wireless extensions. docker0 no wireless extensions. MachineType: Dell Inc. Precision T3600 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832782] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1832782/+attachment/5270677/+files/Lsusb.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/1832782 Title: Backport VMW_PVRDMA PPN64 patch Status in linux package in Ubuntu: Confirmed Bug description: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic and later? Here is the commit log: commit 8aa04ad3b39396e315b23448c56d5465200fa777 Author: Adit Ranadive Date: Sat Jan 26 05:09:36 2019 + RDMA/vmw_pvrdma: Support upto 64-bit PFNs Update the driver to use the new device capability to report 64-bit UAR PFNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8aa04ad3b39396e315b23448c56d5465200fa777 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2010 F pulseaudio adit 3290 F pulseaudio /dev/snd/controlC0: gdm2010 F pulseaudio adit 3290 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723 InstallationDate: Installed on 2018-11-06 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: eno1 no wireless extensions. lono wireless extensions. docker0 no wireless extensions. MachineType: Dell Inc. Precision T3600 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832782] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1832782/+attachment/5270675/+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/1832782 Title: Backport VMW_PVRDMA PPN64 patch Status in linux package in Ubuntu: Confirmed Bug description: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic and later? Here is the commit log: commit 8aa04ad3b39396e315b23448c56d5465200fa777 Author: Adit Ranadive Date: Sat Jan 26 05:09:36 2019 + RDMA/vmw_pvrdma: Support upto 64-bit PFNs Update the driver to use the new device capability to report 64-bit UAR PFNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8aa04ad3b39396e315b23448c56d5465200fa777 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2010 F pulseaudio adit 3290 F pulseaudio /dev/snd/controlC0: gdm2010 F pulseaudio adit 3290 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723 InstallationDate: Installed on 2018-11-06 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: eno1 no wireless extensions. lono wireless extensions. docker0 no wireless extensions. MachineType: Dell Inc. Precision T3600 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832782] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1832782/+attachment/5270674/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832782 Title: Backport VMW_PVRDMA PPN64 patch Status in linux package in Ubuntu: Confirmed Bug description: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic and later? Here is the commit log: commit 8aa04ad3b39396e315b23448c56d5465200fa777 Author: Adit Ranadive Date: Sat Jan 26 05:09:36 2019 + RDMA/vmw_pvrdma: Support upto 64-bit PFNs Update the driver to use the new device capability to report 64-bit UAR PFNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8aa04ad3b39396e315b23448c56d5465200fa777 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2010 F pulseaudio adit 3290 F pulseaudio /dev/snd/controlC0: gdm2010 F pulseaudio adit 3290 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723 InstallationDate: Installed on 2018-11-06 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: eno1 no wireless extensions. lono wireless extensions. docker0 no wireless extensions. MachineType: Dell Inc. Precision T3600 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832782] [NEW] Backport VMW_PVRDMA PPN64 patch
Public bug reported: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic and later? Here is the commit log: commit 8aa04ad3b39396e315b23448c56d5465200fa777 Author: Adit Ranadive Date: Sat Jan 26 05:09:36 2019 + RDMA/vmw_pvrdma: Support upto 64-bit PFNs Update the driver to use the new device capability to report 64-bit UAR PFNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8aa04ad3b39396e315b23448c56d5465200fa777 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2010 F pulseaudio adit 3290 F pulseaudio /dev/snd/controlC0: gdm2010 F pulseaudio adit 3290 F pulseaudio DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723 InstallationDate: Installed on 2018-11-06 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: eno1 no wireless extensions. lono wireless extensions. docker0 no wireless extensions. MachineType: Dell Inc. Precision T3600 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-collected bionic ** Tags added: apport-collected bionic ** Description changed: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic and later? Here is the commit log: commit 8aa04ad3b39396e315b23448c56d5465200fa777 Author: Adit Ranadive Date: Sat Jan 26 05:09:36 2019 + RDMA/vmw_pvrdma: Support upto 64-bit PFNs Update the driver to use the new device capability to report 64-bit UAR PFNs. Thanks, Adit - [1] - https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8aa04ad3b39396e315b23448c56d5465200fa777 + [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8aa04ad3b39396e315b23448c56d5465200fa777 + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.6 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: gdm2010 F pulseaudio + adit 3290 F pulseaudio + /dev/snd/controlC0: gdm2010 F pulseaudio + adit 3290 F pulseaudio + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723 + InstallationDate: Installed on 2018-11-06 (219 days ago) + InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) + IwConfig: + eno1 no wireless extensions. + + lono wireless extensions. + + docker0 no wireless extensions. + MachineType: Dell Inc. Precision T3600 + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 nouveaufb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 + PulseList: + Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied + No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-4.15.0-51-generic N/A + linux-backports-modules-4.15.0-51-generic N/A + linux-firmware 1.173.6 + RfKill: + + Tags: bionic + Uname: Linux 4.15.0-51-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups
[Kernel-packages] [Bug 1829749] Re: Please add support for zipl signing
** Changed in: s390-tools (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1829749
Title:
Please add support for zipl signing
Status in Launchpad itself:
Fix Released
Status in linux-signed package in Ubuntu:
New
Status in s390-tools package in Ubuntu:
Fix Committed
Bug description:
Please add support for zipl ("z/ecureBoot") signing.
It should be similar to opal signing, but using the new zipl signing
key.
I am expecting to sign s390-tools stage3.bin and kernel images using
this key.
s390-tools -> can be signed already
kernels -> should only sign v5.2+
To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1829749/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832776] Re: Backport VMCI PPN64 patch
** Bug watch added: Debian Bug tracker #929824 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929824 ** Also affects: linux (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929824 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832776 Title: Backport VMCI PPN64 patch Status in linux package in Ubuntu: Confirmed Status in linux package in Debian: Unknown Bug description: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic? I have already filed a bug with Debian[2]. Here is the commit log: commit f2db7361cb19bf3a6f7fd367f21d8eb325397946 Author: Vishnu DASA Commit: Greg Kroah-Hartman VMCI: Support upto 64-bit PPNs Add support in the VMCI driver to handle upto 64-bit PPNs when the VMCI device exposes the capability for 64-bit PPNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f2db7361cb19bf3a6f7fd367f21d8eb325397946 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929824 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adit 3290 F pulseaudio /dev/snd/controlC0: adit 3290 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723 InstallationDate: Installed on 2018-11-06 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: eno1 no wireless extensions. lono wireless extensions. docker0 no wireless extensions. MachineType: Dell Inc. Precision T3600 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832776] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1832776/+attachment/5270668/+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/1832776 Title: Backport VMCI PPN64 patch Status in linux package in Ubuntu: Confirmed Bug description: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic? I have already filed a bug with Debian[2]. Here is the commit log: commit f2db7361cb19bf3a6f7fd367f21d8eb325397946 Author: Vishnu DASA Commit: Greg Kroah-Hartman VMCI: Support upto 64-bit PPNs Add support in the VMCI driver to handle upto 64-bit PPNs when the VMCI device exposes the capability for 64-bit PPNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f2db7361cb19bf3a6f7fd367f21d8eb325397946 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929824 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adit 3290 F pulseaudio /dev/snd/controlC0: adit 3290 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723 InstallationDate: Installed on 2018-11-06 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: eno1 no wireless extensions. lono wireless extensions. docker0 no wireless extensions. MachineType: Dell Inc. Precision T3600 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832776] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1832776/+attachment/5270670/+files/PulseList.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/1832776 Title: Backport VMCI PPN64 patch Status in linux package in Ubuntu: Confirmed Bug description: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic? I have already filed a bug with Debian[2]. Here is the commit log: commit f2db7361cb19bf3a6f7fd367f21d8eb325397946 Author: Vishnu DASA Commit: Greg Kroah-Hartman VMCI: Support upto 64-bit PPNs Add support in the VMCI driver to handle upto 64-bit PPNs when the VMCI device exposes the capability for 64-bit PPNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f2db7361cb19bf3a6f7fd367f21d8eb325397946 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929824 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adit 3290 F pulseaudio /dev/snd/controlC0: adit 3290 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723 InstallationDate: Installed on 2018-11-06 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: eno1 no wireless extensions. lono wireless extensions. docker0 no wireless extensions. MachineType: Dell Inc. Precision T3600 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832776] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1832776/+attachment/5270669/+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/1832776 Title: Backport VMCI PPN64 patch Status in linux package in Ubuntu: Confirmed Bug description: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic? I have already filed a bug with Debian[2]. Here is the commit log: commit f2db7361cb19bf3a6f7fd367f21d8eb325397946 Author: Vishnu DASA Commit: Greg Kroah-Hartman VMCI: Support upto 64-bit PPNs Add support in the VMCI driver to handle upto 64-bit PPNs when the VMCI device exposes the capability for 64-bit PPNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f2db7361cb19bf3a6f7fd367f21d8eb325397946 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929824 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adit 3290 F pulseaudio /dev/snd/controlC0: adit 3290 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723 InstallationDate: Installed on 2018-11-06 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: eno1 no wireless extensions. lono wireless extensions. docker0 no wireless extensions. MachineType: Dell Inc. Precision T3600 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832776] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1832776/+attachment/5270665/+files/Lsusb.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/1832776 Title: Backport VMCI PPN64 patch Status in linux package in Ubuntu: Confirmed Bug description: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic? I have already filed a bug with Debian[2]. Here is the commit log: commit f2db7361cb19bf3a6f7fd367f21d8eb325397946 Author: Vishnu DASA Commit: Greg Kroah-Hartman VMCI: Support upto 64-bit PPNs Add support in the VMCI driver to handle upto 64-bit PPNs when the VMCI device exposes the capability for 64-bit PPNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f2db7361cb19bf3a6f7fd367f21d8eb325397946 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929824 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adit 3290 F pulseaudio /dev/snd/controlC0: adit 3290 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723 InstallationDate: Installed on 2018-11-06 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: eno1 no wireless extensions. lono wireless extensions. docker0 no wireless extensions. MachineType: Dell Inc. Precision T3600 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832776] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1832776/+attachment/5270663/+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/1832776 Title: Backport VMCI PPN64 patch Status in linux package in Ubuntu: Confirmed Bug description: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic? I have already filed a bug with Debian[2]. Here is the commit log: commit f2db7361cb19bf3a6f7fd367f21d8eb325397946 Author: Vishnu DASA Commit: Greg Kroah-Hartman VMCI: Support upto 64-bit PPNs Add support in the VMCI driver to handle upto 64-bit PPNs when the VMCI device exposes the capability for 64-bit PPNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f2db7361cb19bf3a6f7fd367f21d8eb325397946 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929824 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adit 3290 F pulseaudio /dev/snd/controlC0: adit 3290 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723 InstallationDate: Installed on 2018-11-06 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: eno1 no wireless extensions. lono wireless extensions. docker0 no wireless extensions. MachineType: Dell Inc. Precision T3600 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832776] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1832776/+attachment/5270666/+files/ProcCpuinfo.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/1832776 Title: Backport VMCI PPN64 patch Status in linux package in Ubuntu: Confirmed Bug description: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic? I have already filed a bug with Debian[2]. Here is the commit log: commit f2db7361cb19bf3a6f7fd367f21d8eb325397946 Author: Vishnu DASA Commit: Greg Kroah-Hartman VMCI: Support upto 64-bit PPNs Add support in the VMCI driver to handle upto 64-bit PPNs when the VMCI device exposes the capability for 64-bit PPNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f2db7361cb19bf3a6f7fd367f21d8eb325397946 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929824 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adit 3290 F pulseaudio /dev/snd/controlC0: adit 3290 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723 InstallationDate: Installed on 2018-11-06 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: eno1 no wireless extensions. lono wireless extensions. docker0 no wireless extensions. MachineType: Dell Inc. Precision T3600 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832776] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1832776/+attachment/5270662/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832776 Title: Backport VMCI PPN64 patch Status in linux package in Ubuntu: Confirmed Bug description: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic? I have already filed a bug with Debian[2]. Here is the commit log: commit f2db7361cb19bf3a6f7fd367f21d8eb325397946 Author: Vishnu DASA Commit: Greg Kroah-Hartman VMCI: Support upto 64-bit PPNs Add support in the VMCI driver to handle upto 64-bit PPNs when the VMCI device exposes the capability for 64-bit PPNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f2db7361cb19bf3a6f7fd367f21d8eb325397946 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929824 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adit 3290 F pulseaudio /dev/snd/controlC0: adit 3290 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723 InstallationDate: Installed on 2018-11-06 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: eno1 no wireless extensions. lono wireless extensions. docker0 no wireless extensions. MachineType: Dell Inc. Precision T3600 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832776] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1832776/+attachment/5270664/+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/1832776 Title: Backport VMCI PPN64 patch Status in linux package in Ubuntu: Confirmed Bug description: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic? I have already filed a bug with Debian[2]. Here is the commit log: commit f2db7361cb19bf3a6f7fd367f21d8eb325397946 Author: Vishnu DASA Commit: Greg Kroah-Hartman VMCI: Support upto 64-bit PPNs Add support in the VMCI driver to handle upto 64-bit PPNs when the VMCI device exposes the capability for 64-bit PPNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f2db7361cb19bf3a6f7fd367f21d8eb325397946 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929824 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adit 3290 F pulseaudio /dev/snd/controlC0: adit 3290 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723 InstallationDate: Installed on 2018-11-06 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: eno1 no wireless extensions. lono wireless extensions. docker0 no wireless extensions. MachineType: Dell Inc. Precision T3600 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832776] 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 1832776 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832776 Title: Backport VMCI PPN64 patch Status in linux package in Ubuntu: Incomplete Bug description: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic? I have already filed a bug with Debian[2]. Here is the commit log: commit f2db7361cb19bf3a6f7fd367f21d8eb325397946 Author: Vishnu DASA Commit: Greg Kroah-Hartman VMCI: Support upto 64-bit PPNs Add support in the VMCI driver to handle upto 64-bit PPNs when the VMCI device exposes the capability for 64-bit PPNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f2db7361cb19bf3a6f7fd367f21d8eb325397946 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929824 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832776] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1832776/+attachment/5270672/+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/1832776 Title: Backport VMCI PPN64 patch Status in linux package in Ubuntu: Confirmed Bug description: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic? I have already filed a bug with Debian[2]. Here is the commit log: commit f2db7361cb19bf3a6f7fd367f21d8eb325397946 Author: Vishnu DASA Commit: Greg Kroah-Hartman VMCI: Support upto 64-bit PPNs Add support in the VMCI driver to handle upto 64-bit PPNs when the VMCI device exposes the capability for 64-bit PPNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f2db7361cb19bf3a6f7fd367f21d8eb325397946 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929824 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adit 3290 F pulseaudio /dev/snd/controlC0: adit 3290 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723 InstallationDate: Installed on 2018-11-06 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: eno1 no wireless extensions. lono wireless extensions. docker0 no wireless extensions. MachineType: Dell Inc. Precision T3600 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832776] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1832776/+attachment/5270667/+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/1832776 Title: Backport VMCI PPN64 patch Status in linux package in Ubuntu: Confirmed Bug description: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic? I have already filed a bug with Debian[2]. Here is the commit log: commit f2db7361cb19bf3a6f7fd367f21d8eb325397946 Author: Vishnu DASA Commit: Greg Kroah-Hartman VMCI: Support upto 64-bit PPNs Add support in the VMCI driver to handle upto 64-bit PPNs when the VMCI device exposes the capability for 64-bit PPNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f2db7361cb19bf3a6f7fd367f21d8eb325397946 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929824 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adit 3290 F pulseaudio /dev/snd/controlC0: adit 3290 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723 InstallationDate: Installed on 2018-11-06 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: eno1 no wireless extensions. lono wireless extensions. docker0 no wireless extensions. MachineType: Dell Inc. Precision T3600 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832776] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1832776/+attachment/5270671/+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/1832776 Title: Backport VMCI PPN64 patch Status in linux package in Ubuntu: Confirmed Bug description: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic? I have already filed a bug with Debian[2]. Here is the commit log: commit f2db7361cb19bf3a6f7fd367f21d8eb325397946 Author: Vishnu DASA Commit: Greg Kroah-Hartman VMCI: Support upto 64-bit PPNs Add support in the VMCI driver to handle upto 64-bit PPNs when the VMCI device exposes the capability for 64-bit PPNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f2db7361cb19bf3a6f7fd367f21d8eb325397946 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929824 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adit 3290 F pulseaudio /dev/snd/controlC0: adit 3290 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723 InstallationDate: Installed on 2018-11-06 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: eno1 no wireless extensions. lono wireless extensions. docker0 no wireless extensions. MachineType: Dell Inc. Precision T3600 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/09/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08HPGT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
** Merge proposal linked: https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/qemu/+git/qemu/+merge/368804 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828495 Title: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM. Status in intel: New Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Confirmed Bug description: This is a bug. Test Environment: Repro Steps: 1. Boot up guest using: -cpu Cascadelake-Server [root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive if=virtio,id=hd,file=/home/x/x,format=qcow2 -m 4096 -smp 4 -cpu Cascadelake-Server -serial stdio char device redirected to /dev/pts/3 (label serial0) qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] 2. To check CPU ID related to features[FEAT_7_0_EDX] ：CPUID_7_0_EDX_ARCH_CAPABILITIES Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be 1. Actual Result: Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b ecx=0x0818 edx=0xbc00 (EDX bit 29=1) Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9 ecx=0x0818 edx=0x8400 (EDX bit 29=0) Commit:2bdb76c015df7125783d8394d6339d181cb5bc30 Target Kerned: 5.1 Target Release: 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1828495/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832101] Re: systemd-networkd: Lost carrier e1000
yes and no. I did disabled tso, but still had some problems, after that i enabled tso and disabled rx/tx checksum That also did not resolve the issue, so as last resort i disabled GSO,GRO,TSO offload and ,RX,TX checksum check ethtool -K gso off gro off tso off rx off tx off -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 Status in linux package in Ubuntu: Confirmed Bug description: Just installed a fresh installation of ubuntu 19 on our server and we're having a lot of carrier-lost erros. There is no really good indicaton why this is hapening. Tried the following : disabled ipv6 (just to be sure), on nic set GSO,GRO,TSO to off. removed netplan, switched to systemd-networkd and added configurewithoutcarrier to true, the option ignorecarrierlost is not accepted by systemd. Description:Ubuntu 19.04 Release:19.04 Kernel Log Jun 8 12:11:17 mc2 kernel: [30304.199050] [ cut here ] Jun 8 12:11:17 mc2 kernel: [30304.199052] NETDEV WATCHDOG: eno1 (e1000e): transmit queue 0 timed out Jun 8 12:11:17 mc2 kernel: [30304.199062] WARNING: CPU: 8 PID: 0 at net/sched/sch_generic.c:461 dev_watchdog+0x221/0x230 Jun 8 12:11:17 mc2 kernel: [30304.199062] Modules linked in: intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd glue_helper intel_cstate intel_rapl_perf intel_wmi_thunderbolt wmi_bmof intel_pch_thermal mac_hid acpi_pad ip6t_REJE CT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_limit xt_tcpudp xt_addrtype sch_fq_codel xt_conntrack ip6 table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter ip_ tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 e1000e nvme ahci i2c_i801 libahci nvme_core wmi video pinctrl_cannonlake pinctrl_intel Jun 8 12:11:17 mc2 kernel: [30304.199080] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 5.0.0-16-generic #17-Ubuntu Jun 8 12:11:17 mc2 kernel: [30304.199081] Hardware name: Gigabyte Technology Co., Ltd. B360 HD3P-LM/B360HD3PLM-CF, BIOS F4 HZ 04/30/2019 Jun 8 12:11:17 mc2 kernel: [30304.199082] RIP: 0010:dev_watchdog+0x221/0x230 Jun 8 12:11:17 mc2 kernel: [30304.199083] Code: 00 49 63 4e e0 eb 92 4c 89 ef c6 05 9a 92 f0 00 01 e8 13 38 fc ff 89 d9 4c 89 ee 48 c7 c7 68 5e da 95 48 89 c2 e8 71 f1 79 ff <0f> 0b eb c0 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 Jun 8 12:11:17 mc2 kernel: [30304.199083] RSP: 0018:93adff203e68 EFLAGS: 00010286 Jun 8 12:11:17 mc2 kernel: [30304.199084] RAX: RBX: RCX: 0006 Jun 8 12:11:17 mc2 kernel: [30304.199084] RDX: 0007 RSI: 0096 RDI: 93adff216440 Jun 8 12:11:17 mc2 kernel: [30304.199084] RBP: 93adff203e98 R08: 0001 R09: 0c61 Jun 8 12:11:17 mc2 kernel: [30304.199085] R10: 0004 R11: R12: 0001 Jun 8 12:11:17 mc2 kernel: [30304.199085] R13: 93adec48 R14: 93adec4804c0 R15: 93adeca74080 Jun 8 12:11:17 mc2 kernel: [30304.199086] FS: () GS:93adff20() knlGS: Jun 8 12:11:17 mc2 kernel: [30304.199086] CS: 0010 DS: ES: CR0: 80050033 Jun 8 12:11:17 mc2 kernel: [30304.199086] CR2: 7f7783ea4300 CR3: 00043920e003 CR4: 003606e0 Jun 8 12:11:17 mc2 kernel: [30304.199087] DR0: DR1: DR2: Jun 8 12:11:17 mc2 kernel: [30304.199087] DR3: DR6: fffe0ff0 DR7: 0400 Jun 8 12:11:17 mc2 kernel: [30304.199087] Call Trace: Jun 8 12:11:17 mc2 kernel: [30304.199088] Jun 8 12:11:17 mc2 kernel: [30304.199090] ? pfifo_fast_enqueue+0x120/0x120 Jun 8 12:11:17 mc2 kernel: [30304.199091] call_timer_fn+0x30/0x130 Jun 8 12:11:17 mc2 kernel: [30304.199092] run_timer_softirq+0x3e4/0x420 Jun 8 12:11:17 mc2 kernel: [30304.199093] ? ktime_get+0x3c/0xa0 Jun 8 12:11:17 mc2 kernel: [30304.199095] ? lapic_next_deadline+0x26/0x30 Jun 8 12:11:17 mc2 kernel: [30304.199096] ? clockevents_program_event+0x93/0xf0 Jun 8 12:11:17 mc2 kernel: [30304.199097] __do_softirq+0xdc/0x2f3 Jun 8 12:11:17 mc2 kernel: [30304.199099] irq_exit+0xc0/0xd0 Jun 8 12:11:17 mc2 kernel: [30304.199099] smp_apic_timer_interrupt+0x79/0x140 Jun 8 12:11:17 mc2 kernel: [30304.199100] apic_timer_interrupt+0xf/0x20 Ju
[Kernel-packages] [Bug 1832776] Re: Backport VMCI PPN64 patch
apport information ** Tags added: apport-collected bionic ** Description changed: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic? I have already filed a bug with Debian[2]. Here is the commit log: commit f2db7361cb19bf3a6f7fd367f21d8eb325397946 Author: Vishnu DASA Commit: Greg Kroah-Hartman VMCI: Support upto 64-bit PPNs Add support in the VMCI driver to handle upto 64-bit PPNs when the VMCI device exposes the capability for 64-bit PPNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f2db7361cb19bf3a6f7fd367f21d8eb325397946 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929824 + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.6 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: adit 3290 F pulseaudio + /dev/snd/controlC0: adit 3290 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723 + InstallationDate: Installed on 2018-11-06 (219 days ago) + InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) + IwConfig: + eno1 no wireless extensions. + + lono wireless extensions. + + docker0 no wireless extensions. + MachineType: Dell Inc. Precision T3600 + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/zsh + ProcFB: 0 nouveaufb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-51-generic N/A + linux-backports-modules-4.15.0-51-generic N/A + linux-firmware 1.173.6 + RfKill: + + Tags: bionic + Uname: Linux 4.15.0-51-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 08/09/2013 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A11 + dmi.board.name: 08HPGT + dmi.board.vendor: Dell Inc. + dmi.board.version: A01 + dmi.chassis.type: 7 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/09/2013:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn08HPGT:rvrA01:cvnDellInc.:ct7:cvr: + dmi.product.name: Precision T3600 + dmi.product.version: 01 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1832776/+attachment/5270661/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832776 Title: Backport VMCI PPN64 patch Status in linux package in Ubuntu: Confirmed Bug description: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic? I have already filed a bug with Debian[2]. Here is the commit log: commit f2db7361cb19bf3a6f7fd367f21d8eb325397946 Author: Vishnu DASA Commit: Greg Kroah-Hartman VMCI: Support upto 64-bit PPNs Add support in the VMCI driver to handle upto 64-bit PPNs when the VMCI device exposes the capability for 64-bit PPNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f2db7361cb19bf3a6f7fd367f21d8eb325397946 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929824 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adit 3290 F pulseaudio /dev/snd/controlC0: adit 3290 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=5e12ac9f-b7e5-46f1-aa2a-0091eb5cb723 InstallationDate: Installed on 2018-11-06 (219 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: eno1 no wireless extensions. lono wireless extensions. docker0 no wireless extensions. MachineType: Dell Inc. Precision T3600 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: Tags: bionic Uname: Linux 4.15.0-51-generic x86_64 UpgradeStatus: No upgrade log
[Kernel-packages] [Bug 1832775] [NEW] Disco update: 5.0.14 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 5.0.14 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832775 Title: Disco update: 5.0.14 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 5.0.14 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832775/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832776] [NEW] Backport VMCI PPN64 patch
Public bug reported: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic? I have already filed a bug with Debian[2]. Here is the commit log: commit f2db7361cb19bf3a6f7fd367f21d8eb325397946 Author: Vishnu DASA Commit: Greg Kroah-Hartman VMCI: Support upto 64-bit PPNs Add support in the VMCI driver to handle upto 64-bit PPNs when the VMCI device exposes the capability for 64-bit PPNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f2db7361cb19bf3a6f7fd367f21d8eb325397946 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929824 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832776 Title: Backport VMCI PPN64 patch Status in linux package in Ubuntu: New Bug description: Hi, Can this kernel patch [1] for VMCI be backported to Ubuntu Bionic? I have already filed a bug with Debian[2]. Here is the commit log: commit f2db7361cb19bf3a6f7fd367f21d8eb325397946 Author: Vishnu DASA Commit: Greg Kroah-Hartman VMCI: Support upto 64-bit PPNs Add support in the VMCI driver to handle upto 64-bit PPNs when the VMCI device exposes the capability for 64-bit PPNs. Thanks, Adit [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f2db7361cb19bf3a6f7fd367f21d8eb325397946 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929824 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830433] Re: 32-bit x86 kernel 4.15.0-50 crash in vmalloc_sync_all
** Description changed:
+ [Impact]
+
+ Commit d653420532d580156c8486686899ea6a9eeb7bf0 in bionic enabled kernel
+ page table isolation for x86_32, but also introduced a kernel bug (the
+ BUG_ON() condition in vmalloc_sync_one()) that seems to happen when
+ vmalloc_sync_all() is called multiple times (e.g., in a busy loop).
+
+ The real problem seems to be a race condition with page-table entries'
+ initialization that can be fixed applying the upstream commit
+ 9bc4f28af75a91aea0ae383f50b0a430c4509303 ("x86/mm: Use WRITE_ONCE() when
+ setting PTEs").
+
+ [Test Case]
+
+ The bug can be easily triggered by rebooting the system a couple of
+ times and loading this module:
+
+ https://launchpadlibrarian.net/428142172/vmalloc-stress-test.c
+
+ [Fix]
+
+ The following upstream fix seems to resolve the problem:
+
+
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9bc4f28af75a91aea0ae383f50b0a430c4509303
+
+ In addition to that the following other upstream fixes are required (all
+ clean cherry picks) to do a cleaner backport of
+ 9bc4f28af75a91aea0ae383f50b0a430c4509303:
+
+
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=86fa949b050184ffc53688516a6a83ae5f98d08a
+
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=792adb90fa724ce07c0171cbc96b9215af4b1045
+
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5e0fb5df2ee871b841f96f9cb6a7f2784e96aa4e
+
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=785a19f9d1dd8a4ab2d0633be4656653bd3de1fc
+
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f967db0b9ed44ec3057a28f3b28efc51df51b835
+
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ba6f508d0ec4adb09f0a939af6d5e19cdfa8667d
+
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f77084d96355f5fba8e2c1fb3a51a393b1570de7
+
+ [Regression Potential]
+
+ All upstream fixes, tested on the affected platform, backport changes
+ are minimal.
+
+ [Original bug report]
+
Hi,
I'm reproducing a kernel bug in vmalloc_sync_all() with a 32-bit x86
kernel.
The problem appears in
Linux ubuntu 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:45:45 UTC
2019 i686 i686 i686 GNU/Linux
Kernels 4.15.0-49 and prior work fine.
The kernel 4.18.0-20-generic works fine.
This problem has not been experienced with upstream Linux kernels.
It appears that invoking vmalloc_sync_all() a few times end up
triggering this issue. This can be triggered by restarting the lttng-
sessiond service with lttng-modules-dkms installed (sometimes a few
restarts are needed to trigger the bug). This ends up unloading and
reloading those modules, which issues a few vmalloc_sync_all() as side-
effect.
I'm not reporting this issue with the "ubuntu-bug linux" command because
it crashes the system on that kernel (system hangs, no console output).
My test system runs within a kvm virtual machine on a 64-bit host.
lsb release:
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Information about my kernel:
linux-image-4.15.0-50-generic:
- Installed: 4.15.0-50.54
- Candidate: 4.15.0-50.54
- Version table:
- *** 4.15.0-50.54 500
- 500 http://ca.archive.ubuntu.com/ubuntu bionic-updates/main i386
Packages
- 500 http://security.ubuntu.com/ubuntu bionic-security/main i386
Packages
- 100 /var/lib/dpkg/status
+ Installed: 4.15.0-50.54
+ Candidate: 4.15.0-50.54
+ Version table:
+ *** 4.15.0-50.54 500
+ 500 http://ca.archive.ubuntu.com/ubuntu bionic-updates/main i386
Packages
+ 500 http://security.ubuntu.com/ubuntu bionic-security/main i386
Packages
+ 100 /var/lib/dpkg/status
Information about lttng-modules-dkms:
lttng-modules-dkms:
- Installed: 2.10.5-1ubuntu1.2
- Candidate: 2.10.5-1ubuntu1.2
- Version table:
- *** 2.10.5-1ubuntu1.2 500
- 500 http://ca.archive.ubuntu.com/ubuntu bionic-updates/universe i386
Packages
- 100 /var/lib/dpkg/status
- 2.10.5-1ubuntu1 500
- 500 http://ca.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
+ Installed: 2.10.5-1ubuntu1.2
+ Candidate: 2.10.5-1ubuntu1.2
+ Version table:
+ *** 2.10.5-1ubuntu1.2 500
+ 500 http://ca.archive.ubuntu.com/ubuntu bionic-updates/universe i386
Packages
+ 100 /var/lib/dpkg/status
+ 2.10.5-1ubuntu1 500
+ 500 http://ca.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1830433
Title:
32-bit x86 kernel 4.15.0-50 crash in vmalloc_sync_all
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
[Impact]
Commit d653420532d580156c84866
[Kernel-packages] [Bug 1831775] Re: ss seems broken when using multiple filters in the same cmdline
This bug was fixed in the package iproute2 - 4.18.0-1ubuntu3 --- iproute2 (4.18.0-1ubuntu3) eoan; urgency=medium * d/p/ss-review-ssfilter.patch: fixed issue with ss and ssfilter where ssfilter rejects single expressions if enclosed in braces (LP: #1831775) -- Rafael David Tinoco Wed, 05 Jun 2019 21:26:00 -0300 ** Changed in: iproute2 (Ubuntu Eoan) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1831775 Title: ss seems broken when using multiple filters in the same cmdline Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Cosmic: In Progress Status in iproute2 source package in Disco: In Progress Status in iproute2 source package in Eoan: Fix Released Bug description: [Impact] * ss won't be able to run commands with single filters inside parentheses, like: "( sport == :X )", for example. * A workaround is to remove "( )" from single filters, since it looks the issue does not affect 2 filters being put together in the same parentheses, like: " ( X and Y ) and Y " instead of ( X and Y ) and ( Y )". * CTDB is unable to use ss filter to obtain nodes public IP addresses in order to fail over services (LP: #722201). [Test Case] * Having an Ubuntu Cosmic, Disco or Eoan, try to execute the following command: $ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Independent of the IPs or ports being used. Copying and pasting the command should be enough for you to know if you are affected. Bad Result: ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message ... Expected Result: Recv-QSend-Q Local Address:Port Peer Address:Port ... * test case was discovered during CTDB scripts execution [Regression Potential] * biggest risk would be to affect ss interpreter (worst case scenario). * the proposed patch is based in upstream fix and was tested against the same issue reported as the reproducer (above) and some other generic ss commands. * any problem here is unlikely to change iproute2 most important command interpreter, "ip", since the patch is applied against ss code. [Other Info] ORIGINAL DESCRIPTION: Investigating an issue for CTDB (LP: #722201), after suggesting a fix on ss syntax to CTDB upstream project, we discovered that "ss" seems to be broken in Ubuntu since Ubuntu Cosmic: # Debian Sid inaddy@workstation:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-QSend-Q Local Address:Port Peer Address:Port # Ubuntu Ubuntu 16.04 LTS (Xenial Xerus) (c)inaddy@xenial:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-QLocal Address:Port Peer Address:Port # Ubuntu 18.04 LTS (Bionic Beaver) (c)inaddy@bionic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-Q Local Address:Port Peer Address:Port # Ubuntu 18.10 (Cosmic Cuttlefish) (c)inaddy@cosmic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message # Ubuntu 19.04 (Disco Dingo) (c)inaddy@disco:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] # Ubuntu 19.10 (Eoan Ermine) (c)inaddy@eoan:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] I have generated a pkg using upstream iproute2 source code and it does not suffer the issue. I have generated a package using Ubuntu cosmic source package, without debian/patches/*, and verified the issue still persists (not being introduced by any of our packages, and being present if vanilla upstream version used in Cosmic). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1831775/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.n
[Kernel-packages] [Bug 1830433] Re: 32-bit x86 kernel 4.15.0-50 crash in vmalloc_sync_all
This module in attach (similar to the one posted by @mjeanson) has been
used as an effective reproducer for this bug. It looks like we need to
reboot the system a couple of times and load this module to immediately
trigger the bug.
** Attachment added: "vmalloc_sync_all() stress test"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830433/+attachment/5270656/+files/vmalloc-stress-test.c
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1830433
Title:
32-bit x86 kernel 4.15.0-50 crash in vmalloc_sync_all
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
[Impact]
Commit d653420532d580156c8486686899ea6a9eeb7bf0 in bionic enabled
kernel page table isolation for x86_32, but also introduced a kernel
bug (the BUG_ON() condition in vmalloc_sync_one()) that seems to
happen when vmalloc_sync_all() is called multiple times (e.g., in a
busy loop).
The real problem seems to be a race condition with page-table entries'
initialization that can be fixed applying the upstream commit
9bc4f28af75a91aea0ae383f50b0a430c4509303 ("x86/mm: Use WRITE_ONCE()
when setting PTEs").
[Test Case]
The bug can be easily triggered by rebooting the system a couple of
times and loading this module:
https://launchpadlibrarian.net/428142172/vmalloc-stress-test.c
[Fix]
The following upstream fix seems to resolve the problem:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9bc4f28af75a91aea0ae383f50b0a430c4509303
In addition to that the following other upstream fixes are required
(all clean cherry picks) to do a cleaner backport of
9bc4f28af75a91aea0ae383f50b0a430c4509303:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=86fa949b050184ffc53688516a6a83ae5f98d08a
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=792adb90fa724ce07c0171cbc96b9215af4b1045
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5e0fb5df2ee871b841f96f9cb6a7f2784e96aa4e
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=785a19f9d1dd8a4ab2d0633be4656653bd3de1fc
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f967db0b9ed44ec3057a28f3b28efc51df51b835
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ba6f508d0ec4adb09f0a939af6d5e19cdfa8667d
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f77084d96355f5fba8e2c1fb3a51a393b1570de7
[Regression Potential]
All upstream fixes, tested on the affected platform, backport changes
are minimal.
[Original bug report]
Hi,
I'm reproducing a kernel bug in vmalloc_sync_all() with a 32-bit x86
kernel.
The problem appears in
Linux ubuntu 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:45:45 UTC
2019 i686 i686 i686 GNU/Linux
Kernels 4.15.0-49 and prior work fine.
The kernel 4.18.0-20-generic works fine.
This problem has not been experienced with upstream Linux kernels.
It appears that invoking vmalloc_sync_all() a few times end up
triggering this issue. This can be triggered by restarting the lttng-
sessiond service with lttng-modules-dkms installed (sometimes a few
restarts are needed to trigger the bug). This ends up unloading and
reloading those modules, which issues a few vmalloc_sync_all() as
side-effect.
I'm not reporting this issue with the "ubuntu-bug linux" command
because it crashes the system on that kernel (system hangs, no console
output).
My test system runs within a kvm virtual machine on a 64-bit host.
lsb release:
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Information about my kernel:
linux-image-4.15.0-50-generic:
Installed: 4.15.0-50.54
Candidate: 4.15.0-50.54
Version table:
*** 4.15.0-50.54 500
500 http://ca.archive.ubuntu.com/ubuntu bionic-updates/main i386
Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main i386
Packages
100 /var/lib/dpkg/status
Information about lttng-modules-dkms:
lttng-modules-dkms:
Installed: 2.10.5-1ubuntu1.2
Candidate: 2.10.5-1ubuntu1.2
Version table:
*** 2.10.5-1ubuntu1.2 500
500 http://ca.archive.ubuntu.com/ubuntu bionic-updates/universe i386
Packages
100 /var/lib/dpkg/status
2.10.5-1ubuntu1 500
500 http://ca.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830433/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832749] Re: Disco update: 5.0.13 upstream stable release
These patches had merge conflicts that needed to be resolved when applying: * selftests: fib_rule_tests: Fix icmp proto with ipv6 - minor offset adjustment * udp: fix GRO reception in case of length mismatch - Our tree has had some touch-up work to the variables here. The stable tree was using something like this: "uh->len > uh2->len", but our tree uses "ulen > ntohs(uh2->len)" -- where ulen is declared further up in the function (from uh->len) and we're using "ntohs" on the other value. ** 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: + * Linux 5.0.13 + * ath10k: Drop WARN_ON()s that always trigger during system resume + * iwlwifi: mvm: properly check debugfs dentry before using it + * ALSA: line6: use dynamic buffers + * KVM: nVMX: Fix size checks in vmx_set_nested_state + * KVM: x86: Whitelist port 0x7e for pre-incrementing %rip + * net/tls: fix copy to fragments in reencrypt + * net/tls: don't copy negative amounts of data in reencrypt + * bnxt_en: Fix uninitialized variable usage in bnxt_rx_pkt(). + * bnxt_en: Fix statistics context reservation logic. + * bnxt_en: Pass correct extended TX port statistics size to firmware. + * bnxt_en: Fix possible crash in bnxt_hwrm_ring_free() under error conditions. + * bnxt_en: Free short FW command HWRM memory in error path in bnxt_init_one() + * bnxt_en: Improve multicast address setup logic. + * udp: fix GRO packet of death + * udp: fix GRO reception in case of length mismatch + * tcp: add sanity tests in tcp_add_backlog() + * selftests: fib_rule_tests: Fix icmp proto with ipv6 + * packet: in recvmsg msg_name return at least sizeof sockaddr_ll + * packet: validate msg_namelen in send directly + * selftests: fib_rule_tests: print the result and return 1 if any tests failed + * sctp: avoid running the sctp state machine recursively + * rxrpc: Fix net namespace cleanup + * net/tls: avoid NULL pointer deref on nskb->sk in fallback + * net: phy: marvell: Fix buffer overrun with stats counters + * net: dsa: bcm_sf2: fix buffer overflow doing set_rxnfc + * l2tp: use rcu_dereference_sk_user_data() in l2tp_udp_encap_recv() + * l2ip: fix possible use-after-free + * ipv6: invert flowlabel sharing check in process and user mode + * ipv6/flowlabel: wait rcu grace period before put_pid() + * ipv6: fix races in ip6_dst_destroy() + * ipv6: A few fixes on dereferencing rt->from + * ipv4: ip_do_fragment: Preserve skb_iif during fragmentation -5.0.13 upstream stable release -from git://git.kernel.org/ + + 5.0.13 upstream stable release + from git://git.kernel.org/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832749 Title: Disco update: 5.0.13 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: * Linux 5.0.13 * ath10k: Drop WARN_ON()s that always trigger during system resume * iwlwifi: mvm: properly check debugfs dentry before using it * ALSA: line6: use dynamic buffers * KVM: nVMX: Fix size checks in vmx_set_nested_state * KVM: x86: Whitelist port 0x7e for pre-incrementing %rip * net/tls: fix copy to fragments in reencrypt * net/tls: don't copy negative amounts of data in reencrypt * bnxt_en: Fix uninitialized variable usage in bnxt_rx_pkt(). * bnxt_en: Fix statistics context reservation logic. * bnxt_en: Pass correct extended TX port statistics size to firmware. * bnxt_en: Fix possible crash in bnxt_hwrm_ring_free() under error conditions. * bnxt_en: Free short FW
[Kernel-packages] [Bug 1830930] Re: USB 3 devices are not detected on thunderbolt 3
I got a different USB 3.1 SSD and this works fine so it seems a real edge case that Samsung SSD does not work on this TB controller. I can test with windows soon -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830930 Title: USB 3 devices are not detected on thunderbolt 3 Status in linux package in Ubuntu: Confirmed Bug description: I found a strange problem when trying to connect my Samsung T5 SSD. If I connect it to the Thunderbolt port on my HP EliteDesk Mini G4, with Thunderbolt at boot then the SSD is detected without issues. If I unplug it and reconnect then it's not detected. If I force the thunderbolt controller on (boltctl power -t 1) then I can see the new USB host created in lsusb but the attached device is not added. No additional events are shown in dmesg. If I connect the device using another cable then it also doesn't work I have a USB-C cable only rated to USB 2.0 speed then the device is recognized without any issues. Ubuntu 19.04, 5.0.0-15-generic 04:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 2C 2018] (rev 06) 3a:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 2C 2018] (rev 06) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: toby 1495 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-27 (31 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G4 DM 65W Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=86b0f677-7a3e-4ea6-9d5c-fd7c57d1f964 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-05-26 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q21 Ver. 02.06.03 dmi.board.name: 845A dmi.board.vendor: HP dmi.board.version: KBC Version 07.D2.00 dmi.chassis.asset.tag: 8CC84321CJ dmi.chassis.type: 6 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ21Ver.02.06.03:bd02/15/2019:svnHP:pnHPEliteDesk800G4DM65W:pvr:rvnHP:rn845A:rvrKBCVersion07.D2.00:cvnHP:ct6:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 800 G4 DM 65W dmi.product.sku: 5BA07US#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle
Hi, I have a HP Spectre x360 13t-ap000, with the exact same problem. I also have NVMe and it drains lots of power under s2idle, and the only option I have in /sys/power/mem_sleep is that one. I am running Arch Linux. $ uname -a Linux behemoth 5.1.8-arch1-1-ARCH #1 SMP PREEMPT Sun Jun 9 20:28:28 UTC 2019 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808957 Title: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle Status in linux package in Ubuntu: Confirmed Bug description: It seems that the Dell 9370 is set to go into s2idle mode rather than deep sleep, forgoing significant power savings. I have confirmed this by suspending and then checking: sudo journalctl | grep "PM: suspend" | tail -2. If the output is PM: suspend entry (s2idle) PM: suspend exit cat /sys/power/mem_sleep showed [s2idle] deep As a temporary fix, I typed echo deep > /sys/power/mem_sleep as a root user (sudo -i). Then the output of cat /sys/power/mem_sleep was s2idle [deep] After suspending now, sudo journalctl | grep "PM: suspend" | tail -2 returns PM: suspend entry (deep) PM: suspend exit I have made this permanent by editing /etc/default/grub and replacing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep" then regenerating my grub configuration (sudo grub-mkconfig -o /boot/grub/grub.cfg). This appears to be working with no ill effects. Credit to https://askubuntu.com/a/1036122/470077 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron-work 3672 F pulseaudio /dev/snd/pcmC0D0p: aaron-work 3672 F...m pulseaudio Date: Tue Dec 18 09:52:44 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/ubuntu-vg/swap_1 InstallationDate: Installed on 2018-09-04 (104 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-26 (52 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
In our case downgrade the microcode don't work, instead of that we noticed that our kernel was outdated: uname -r 4.15.0-51-generic so we upgrade the kernel to the recent version with: sudo apt-get install --install-recommends linux-generic-hwe-18.04 xserver-xorg-hwe-18.04 with that the kernel was upgraded to: 4.18.0-21-generic and ubuntu start correctly -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829620 Title: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: Description: - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of booting, after grub) - does not even show the enter cryptsetup passphrase - affected kernels: # apt list --installed |grep linux-signed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 [installed] linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 amd64 [installed] linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 5.0.0.15.71 amd64 [installed] - the setup is not new, has been working perfectly before (about 7 days since my last restart?) System: - HW: ASUS Zenbook 14 UX433FN - Ubuntu 18.04, runing latest HWE, fully updated - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), Suspected/possible cause?: - recent intel-microcode package update - recent kernel package updates Steps taken: - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding nosplash, noplymouth) - completely removed nvidia drivers (apt purge *nvidia*) - completely purged and reinstalled grub (grup-pc) - completely purged and reinstalled all kernels (headers, modules, image, ..) - toggle BIOS "fastboot" (now using OFF) - toggle UEFI SecureBoot (now using ON) - remove plymouth (apt remove *plymouth* , but the workaround is working with plymouth installed) Workaround: - so far, I'm only able to boot with non-Ubuntu kernel! (linux-image-liquorix-amd64) - which needs "splash" option ON - reinstall cryptsetup & update-grub (as suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 ) I am not sure how to get you more debug info, as this setup has been working before, and it's a very eary boot-process bug, so I can't even access dmesg etc. EDIT: Hypothesis: Only affects ASUS with i7-8565U Whiskey Lake Intel CPU Upstream Bug Report: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 WORKAROUND 1: disable intel microcode updates during boot From this bug: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920 1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub 2/ update-grub WORKAROUND 2: downgrade (and hold) intel-microcode to older version from bionic/main apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2337 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge (not installed) Tags: bionic wayland-session Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2339 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Tags: third-party-packages bionic wayland-session Uname: Linux 5.0.0-15-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1832754] [NEW] ubuntu-bug systemd
Public bug reported: I am using Xubuntu 18.04 64 bit and got "shutdown[1]: Failed to wait for process: Protocol error" at shutdown or reboot and hangs. systemd: 237-3ubuntu10.22 It's this issue: https://github.com/systemd/systemd/issues/8155 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Package changed: nvidia-graphics-drivers-390 (Ubuntu) => systemd (Ubuntu) -- 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/1832754 Title: ubuntu-bug systemd Status in systemd package in Ubuntu: New Bug description: I am using Xubuntu 18.04 64 bit and got "shutdown[1]: Failed to wait for process: Protocol error" at shutdown or reboot and hangs. systemd: 237-3ubuntu10.22 It's this issue: https://github.com/systemd/systemd/issues/8155 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1832754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793338] Re: Fix unusable NVIDIA GPU after S3
nvidia-driver-430 430.26 becomes unusable (atleast CUDA and co) after S3. 5.0.0-16-generic #17-Ubuntu SMP Wed May 15 10:52:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux -- 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/1793338 Title: Fix unusable NVIDIA GPU after S3 Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-oem source package in Cosmic: Fix Released Bug description: [Impact] NVIDIA GPU becomes unusable after S3. [Test] The NVIDIA GPU works well after applying this patch. [Fix] Rewrite 0 to Intel PCI bridge 'Prefetchable Base Upper 32 Bits'. This should be done by BIOS S3 code [1], but now the issue reappears, let's do the same via Linux PCI subsystem. [Regression Potential] Low. After applying this patch I haven't noticed any change on already working PCI devices. Also this patch is acked by PCI and ACPI maintainers, so we can be more confident. [1] https://bugzilla.kernel.org/show_bug.cgi?id=116851#c23 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1793338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle
Please test Bionic, Cosmic and Disco kernels under this URL: https://people.canonical.com/~khfeng/lp1808129/ This is the final version I am going to request an SRU. ** Summary changed: - Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep + Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808957 Title: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle Status in linux package in Ubuntu: Confirmed Bug description: It seems that the Dell 9370 is set to go into s2idle mode rather than deep sleep, forgoing significant power savings. I have confirmed this by suspending and then checking: sudo journalctl | grep "PM: suspend" | tail -2. If the output is PM: suspend entry (s2idle) PM: suspend exit cat /sys/power/mem_sleep showed [s2idle] deep As a temporary fix, I typed echo deep > /sys/power/mem_sleep as a root user (sudo -i). Then the output of cat /sys/power/mem_sleep was s2idle [deep] After suspending now, sudo journalctl | grep "PM: suspend" | tail -2 returns PM: suspend entry (deep) PM: suspend exit I have made this permanent by editing /etc/default/grub and replacing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep" then regenerating my grub configuration (sudo grub-mkconfig -o /boot/grub/grub.cfg). This appears to be working with no ill effects. Credit to https://askubuntu.com/a/1036122/470077 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron-work 3672 F pulseaudio /dev/snd/pcmC0D0p: aaron-work 3672 F...m pulseaudio Date: Tue Dec 18 09:52:44 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/ubuntu-vg/swap_1 InstallationDate: Installed on 2018-09-04 (104 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-26 (52 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809843] Re: sky2 ethernet card link not up after suspend
** Changed in: linux (Ubuntu Bionic) Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809843 Title: sky2 ethernet card link not up after suspend Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Status in linux source package in Disco: Fix Released Bug description: Issue is as described by the user 'kris' in #1798921 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921). Sometimes when bringing my laptop up from suspended state my Ethernet card shows link connection and activity via port LEDs but ethtool indicates the link is not up. This does not happen every time I resume from suspend, about one in 5 times. When it does happen, the following additional message is present in my dmesg output: [ 686.804877] do_IRQ: 1.37 No irq handler for vector The lspci -vvnn output for the Ethernet card is: 02:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. 88E8057 PCI-E Gigabit Ethernet Controller [11ab:4380] (rev 10) Subsystem: Acer Incorporated [ALI] 88E8057 PCI-E Gigabit Ethernet Controller [1025:028e] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921/comments/34, in the hopes that this specific card will be added to the relevant MSI quirks table. If I do not suffer from the same issue as kris in the above linked issue, I will be happy to provide any additional information, test fixes etc. I would like to avoid using the 'pci=nomsi,noaer' workaround he mentioned if possible. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: maridius 2260 F...m pulseaudio /dev/snd/controlC0: maridius 2260 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=0840edd3-6052-4916-bcc2-4c5b13edb862 InstallationDate: Installed on 2015-09-01 (1212 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Gateway P-79 NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=ad05ff21-9786-4f03-8641-85f2f416363d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-42.45+PHC-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 09/30/2009 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 79.07.00 dmi.board.name: Godzilla-N10 dmi.board.vendor: Gateway dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Gateway dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr79.07.00:bd09/30/2009:svnGateway:pnP-79:pvr0100:rvnGateway:rnGodzilla-N10:rvrRev:cvnGateway:ct10:cvrN/A: dmi.product.name: P-79 dmi.product.version: 0100 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809843/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778087] Re: ELAN1200 touchpad jumps around and disconnects
Hang on boot with mainline 5.2-rc4 https://photos.app.goo.gl/d9qJxC1DBEJgqUSa7 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1778087 Title: ELAN1200 touchpad jumps around and disconnects Status in linux package in Ubuntu: Confirmed Bug description: This is on an ASUS GL503VD laptop and would probably affect other ASUS laptops equipped with the ELAN1200 touchpad. I am on Kernel 4.17.2 because older kernels did not enable the touchpad at all(It was just unrecognized or i2c-hid stopped the computer from booting) The touchpad works but it has erratic behaviour and disconnects randomly. After it disconnects the only way to bring it back is to `modprobe -r hid-multitouch && modprobe hid-multitouch` Libinput and synaptics can handle the touchpad though I found synaptics to be more stable. dmesg gets spammed with this whenever I move the touchpad: [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad Because from what I understand the "jumpy/disconnect" problem is associated to the incomplete reports and Mishurov managed to mitigate those. Unfortunately some symbols were deprecated in kernel 4.17.2 and it did not compile for my system. While I can use my touchpad as is right now, and "restart" it with modprobe when needed, it would be nice to have it function bug-free. (Right after I typed this my touchpad disconnected and I needed to modprobe again, I am considering making a cronjob for that) Let me know if anything else is needed. Will wait for an apport collection to add log files. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-10 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 4.17.2 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832749] [NEW] Disco update: 5.0.13 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 5.0.13 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832749 Title: Disco update: 5.0.13 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 5.0.13 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831751] Re: rtlwifi: aggresive memory leak
** Changed in: linux (Ubuntu)
Assignee: TJ (tj) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1831751
Title:
rtlwifi: aggresive memory leak
Status in linux package in Ubuntu:
Confirmed
Bug description:
Hey, i got a memory leak on Ubuntu 18.04.2 even in console mode (no X/GUI)
the memory usage grows slowly to take all the available RAM when i let the
computer running over the night (with just top and irssi), and i have to reboot
to get things back to normal. I didn't have this problem on Ubuntu 17.10 but i
was still flooded with message about pci aer taking lots of disk space in the
logs, but pci=noaer fixed this problem and i had no memory leak.
The computer is a common laptop: HP Pavilion.
---
Kernel log gets spammed with AERs so owner uses "pci=noaer"; that was briefly
disabled to capture the AERs.
Memory seems to be consumed (~6 GB of 8GB) just by leaving PC
overnight booted just to console (systemd.unit=multi-user.target).
The memory leak doesn't affect Windows but owner is going to check
Windows Event Log for signs of AERs being logged.
---
Original suspect of AER is not guilty.
This turns out to be a bug in the rtlwifi driver where in some rare
circumstances it fails to free an sk_buf.
Reporter has been testing a DKMS build of rtlwfi with the fix applied
and confirms it solves the issue.
Upstream has the commit. Can we get this cherry-picked into all
releases?
commit 8cfa272b0d321160ebb5b45073e39ef0a6ad73f2
Author: Larry Finger
Date: Sat Nov 17 20:55:03 2018 -0600
rtlwifi: Fix leak of skb when processing C2H_BT_INFO
With commit 0a9f8f0a1ba9 ("rtlwifi: fix btmpinfo timeout while processing
C2H_BT_INFO"), calling rtl_c2hcmd_enqueue() with rtl_c2h_fast_cmd() true,
the routine returns without freeing that skb, thereby leaking it.
This issue has been discussed at
https://github.com/lwfinger/rtlwifi_new/issues/401
and the fix tested there.
Fixes: 0a9f8f0a1ba9 ("rtlwifi: fix btmpinfo timeout while processing
C2H_BT_INFO")
Reported-and-tested-by: Francisco Machado Magalhães Neto
Cc: Francisco Machado Magalhães Neto
Cc: Ping-Ke Shih
Cc: Stable # 4.18+
Signed-off-by: Larry Finger
Signed-off-by: Kalle Valo
diff --git a/drivers/net/wireless/realtek/rtlwifi/base.c
b/drivers/net/wireless/realtek/rtlwifi/base.c
index f4122c8fdd97..ef9b502ce576 100644
--- a/drivers/net/wireless/realtek/rtlwifi/base.c
+++ b/drivers/net/wireless/realtek/rtlwifi/base.c
@@ -2289,6 +2289,7 @@ void rtl_c2hcmd_enqueue(struct ieee80211_hw *hw, struct
sk_buff *skb)
if (rtl_c2h_fast_cmd(hw, skb)) {
rtl_c2h_content_parsing(hw, skb);
+ kfree_skb(skb);
return;
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831751/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826447] Re: Azure: Backport vIOMMU driver (increase vCPU limits)
** Changed in: linux-azure (Ubuntu Disco) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1826447 Title: Azure: Backport vIOMMU driver (increase vCPU limits) Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Cosmic: Fix Committed Status in linux-azure source package in Disco: Confirmed Bug description: Description: To support VM instances with >255 vCPUS, we need the patch set below backported to the Azure 4.18 kernel. These patches include - - New Hyper-V IOMMU driver. This driver will be Hyper-V specific. - Minor update to the Hyper-V specific virtual PCI code. Need to expand the size of an array to allow for a larger number of vCPUs. There are very large VM instance sizes coming to Azure in 2019, and Ubuntu will require the following patches in order to function properly: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=29217a4746835fef35279abbd12c1a1efe83bfca https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=84fdfafab849036b5aefa52824b5cb42e887ef0e https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=c8ccf7599ddac5fa48e06104c44b24709e21eed5 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/controller /pci-hyperv.c?id=9bc1174280ddf7693e8c29a8f1743809e987ac37 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1826447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826447] Re: Azure: Backport vIOMMU driver (increase vCPU limits)
Just confirming, I believe we need to include those patches to the 5.0 disco kernel as well, right? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1826447 Title: Azure: Backport vIOMMU driver (increase vCPU limits) Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Cosmic: Fix Committed Status in linux-azure source package in Disco: Incomplete Bug description: Description: To support VM instances with >255 vCPUS, we need the patch set below backported to the Azure 4.18 kernel. These patches include - - New Hyper-V IOMMU driver. This driver will be Hyper-V specific. - Minor update to the Hyper-V specific virtual PCI code. Need to expand the size of an array to allow for a larger number of vCPUs. There are very large VM instance sizes coming to Azure in 2019, and Ubuntu will require the following patches in order to function properly: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=29217a4746835fef35279abbd12c1a1efe83bfca https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=84fdfafab849036b5aefa52824b5cb42e887ef0e https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=c8ccf7599ddac5fa48e06104c44b24709e21eed5 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/controller /pci-hyperv.c?id=9bc1174280ddf7693e8c29a8f1743809e987ac37 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1826447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826858] Re: XPS 9343 System freezes requiring hard reset
With the workaround from the bug in comment #9 I am no longer experiencing freezes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826858 Title: XPS 9343 System freezes requiring hard reset Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to disco I have started having regular freezes of my laptop. There is no response to key presses, mouse movement etc. Only recourse is to reset the system. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: MATE Date: Mon Apr 29 11:13:13 2019 HibernationDevice: RESUME=UUID=e76f9b75-a3b2-48c0-931f-7af49bda53bb InstallationDate: Installed on 2019-01-06 (112 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. XPS 13 9343 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=/dev/mapper/ubuntu--mate--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-04-13 (15 days ago) dmi.bios.date: 08/29/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd08/29/2016:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.sku: 0665 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1831710] Re: Touchpad not working (Lenevo Ideapad 330 series)
The right click, left click of the touch pad are not working. I am able to navigate with the touchpad, otherwise, Jeremy. On Thu, Jun 13, 2019 at 8:43 PM Sumneet Kaur Bamrah wrote: > Hey Jeremy, > Sorry about the late reply. Executed the commands now, works like a charm, > thank you very much! > > > On Tue, Jun 11, 2019 at 10:50 PM Jeremy <1831...@bugs.launchpad.net> > wrote: > >> Proceed >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1831710 >> >> Title: >> Touchpad not working (Lenevo Ideapad 330 series) >> >> Status in linux package in Ubuntu: >> Confirmed >> >> Bug description: >> The touch pad has not been used since the purchase of the product. >> >> ProblemType: Bug >> DistroRelease: Ubuntu 18.04 >> Package: linux-image-4.18.0-21-generic 4.18.0-21.22~18.04.1 >> ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 >> Uname: Linux 4.18.0-21-generic x86_64 >> ApportVersion: 2.20.9-0ubuntu7.6 >> Architecture: amd64 >> CurrentDesktop: ubuntu:GNOME >> Date: Wed Jun 5 13:41:22 2019 >> InstallationDate: Installed on 2019-06-05 (0 days ago) >> InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 >> (20190210) >> SourcePackage: linux-signed-hwe >> UpgradeStatus: No upgrade log present (probably fresh install) >> --- >> ProblemType: Bug >> ApportVersion: 2.20.9-0ubuntu7.6 >> Architecture: amd64 >> AudioDevicesInUse: >>USERPID ACCESS COMMAND >>/dev/snd/controlC1: athena 1232 F pulseaudio >>/dev/snd/pcmC1D0p: athena 1232 F...m pulseaudio >>/dev/snd/controlC0: athena 1232 F pulseaudio >> CurrentDesktop: ubuntu:GNOME >> DistroRelease: Ubuntu 18.04 >> InstallationDate: Installed on 2019-06-05 (1 days ago) >> InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 >> (20190210) >> MachineType: LENOVO 81D2 >> Package: linux (not installed) >> ProcFB: 0 amdgpudrmfb >> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic >> root=UUID=29a08da7-0f52-4ee8-8424-f2b37885999f ro quiet splash vt.handoff=1 >> ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 >> RelatedPackageVersions: >>linux-restricted-modules-4.18.0-21-generic N/A >>linux-backports-modules-4.18.0-21-generic N/A >>linux-firmware 1.173.6 >> Tags: bionic >> Uname: Linux 4.18.0-21-generic x86_64 >> UpgradeStatus: No upgrade log present (probably fresh install) >> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo >> _MarkForUpload: True >> dmi.bios.date: 12/10/2018 >> dmi.bios.vendor: LENOVO >> dmi.bios.version: 7VCN46WW >> dmi.board.asset.tag: NO Asset Tag >> dmi.board.name: LNVNB161216 >> dmi.board.vendor: LENOVO >> dmi.board.version: NO DPK >> dmi.chassis.asset.tag: NO Asset Tag >> dmi.chassis.type: 10 >> dmi.chassis.vendor: LENOVO >> dmi.chassis.version: Lenovo ideapad 330-15ARR >> dmi.modalias: >> dmi:bvnLENOVO:bvr7VCN46WW:bd12/10/2018:svnLENOVO:pn81D2:pvrLenovoideapad330-15ARR:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15ARR: >> dmi.product.family: ideapad 330-15ARR >> dmi.product.name: 81D2 >> dmi.product.sku: LENOVO_MT_81D2_BU_idea_FM_ideapad 330-15ARR >> dmi.product.version: Lenovo ideapad 330-15ARR >> dmi.sys.vendor: LENOVO >> >> To manage notifications about this bug go to: >> >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831710/+subscriptions >> > > > -- > Thanks and Regards, > Sumneet Kaur Bamrah > > -- Thanks and Regards, Sumneet Kaur Bamrah -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831710 Title: Touchpad not working (Lenevo Ideapad 330 series) Status in linux package in Ubuntu: Confirmed Bug description: The touch pad has not been used since the purchase of the product. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-21-generic 4.18.0-21.22~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 5 13:41:22 2019 InstallationDate: Installed on 2019-06-05 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: athena 1232 F pulseaudio /dev/snd/pcmC1D0p: athena 1232 F...m pulseaudio /dev/snd/controlC0: athena 1232 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on
Re: [Kernel-packages] [Bug 1831710] Re: Touchpad not working (Lenevo Ideapad 330 series)
Hey Jeremy, Sorry about the late reply. Executed the commands now, works like a charm, thank you very much! On Tue, Jun 11, 2019 at 10:50 PM Jeremy <1831...@bugs.launchpad.net> wrote: > Proceed > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1831710 > > Title: > Touchpad not working (Lenevo Ideapad 330 series) > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > The touch pad has not been used since the purchase of the product. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: linux-image-4.18.0-21-generic 4.18.0-21.22~18.04.1 > ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 > Uname: Linux 4.18.0-21-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.6 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Wed Jun 5 13:41:22 2019 > InstallationDate: Installed on 2019-06-05 (0 days ago) > InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 > (20190210) > SourcePackage: linux-signed-hwe > UpgradeStatus: No upgrade log present (probably fresh install) > --- > ProblemType: Bug > ApportVersion: 2.20.9-0ubuntu7.6 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC1: athena 1232 F pulseaudio >/dev/snd/pcmC1D0p: athena 1232 F...m pulseaudio >/dev/snd/controlC0: athena 1232 F pulseaudio > CurrentDesktop: ubuntu:GNOME > DistroRelease: Ubuntu 18.04 > InstallationDate: Installed on 2019-06-05 (1 days ago) > InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 > (20190210) > MachineType: LENOVO 81D2 > Package: linux (not installed) > ProcFB: 0 amdgpudrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic > root=UUID=29a08da7-0f52-4ee8-8424-f2b37885999f ro quiet splash vt.handoff=1 > ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 > RelatedPackageVersions: >linux-restricted-modules-4.18.0-21-generic N/A >linux-backports-modules-4.18.0-21-generic N/A >linux-firmware 1.173.6 > Tags: bionic > Uname: Linux 4.18.0-21-generic x86_64 > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > dmi.bios.date: 12/10/2018 > dmi.bios.vendor: LENOVO > dmi.bios.version: 7VCN46WW > dmi.board.asset.tag: NO Asset Tag > dmi.board.name: LNVNB161216 > dmi.board.vendor: LENOVO > dmi.board.version: NO DPK > dmi.chassis.asset.tag: NO Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: LENOVO > dmi.chassis.version: Lenovo ideapad 330-15ARR > dmi.modalias: > dmi:bvnLENOVO:bvr7VCN46WW:bd12/10/2018:svnLENOVO:pn81D2:pvrLenovoideapad330-15ARR:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15ARR: > dmi.product.family: ideapad 330-15ARR > dmi.product.name: 81D2 > dmi.product.sku: LENOVO_MT_81D2_BU_idea_FM_ideapad 330-15ARR > dmi.product.version: Lenovo ideapad 330-15ARR > dmi.sys.vendor: LENOVO > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831710/+subscriptions > -- Thanks and Regards, Sumneet Kaur Bamrah -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831710 Title: Touchpad not working (Lenevo Ideapad 330 series) Status in linux package in Ubuntu: Confirmed Bug description: The touch pad has not been used since the purchase of the product. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-21-generic 4.18.0-21.22~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 5 13:41:22 2019 InstallationDate: Installed on 2019-06-05 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: athena 1232 F pulseaudio /dev/snd/pcmC1D0p: athena 1232 F...m pulseaudio /dev/snd/controlC0: athena 1232 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-06-05 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 81D2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic root=UUID=29a08da7-0f52-4ee8-8424-f2b37885999f ro quiet splash vt.handoff=1 P
[Kernel-packages] [Bug 1830433] Re: 32-bit x86 kernel 4.15.0-50 crash in vmalloc_sync_all
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux (Ubuntu Bionic) 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/1830433 Title: 32-bit x86 kernel 4.15.0-50 crash in vmalloc_sync_all Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Hi, I'm reproducing a kernel bug in vmalloc_sync_all() with a 32-bit x86 kernel. The problem appears in Linux ubuntu 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:45:45 UTC 2019 i686 i686 i686 GNU/Linux Kernels 4.15.0-49 and prior work fine. The kernel 4.18.0-20-generic works fine. This problem has not been experienced with upstream Linux kernels. It appears that invoking vmalloc_sync_all() a few times end up triggering this issue. This can be triggered by restarting the lttng- sessiond service with lttng-modules-dkms installed (sometimes a few restarts are needed to trigger the bug). This ends up unloading and reloading those modules, which issues a few vmalloc_sync_all() as side-effect. I'm not reporting this issue with the "ubuntu-bug linux" command because it crashes the system on that kernel (system hangs, no console output). My test system runs within a kvm virtual machine on a 64-bit host. lsb release: Description: Ubuntu 18.04.2 LTS Release: 18.04 Information about my kernel: linux-image-4.15.0-50-generic: Installed: 4.15.0-50.54 Candidate: 4.15.0-50.54 Version table: *** 4.15.0-50.54 500 500 http://ca.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages 100 /var/lib/dpkg/status Information about lttng-modules-dkms: lttng-modules-dkms: Installed: 2.10.5-1ubuntu1.2 Candidate: 2.10.5-1ubuntu1.2 Version table: *** 2.10.5-1ubuntu1.2 500 500 http://ca.archive.ubuntu.com/ubuntu bionic-updates/universe i386 Packages 100 /var/lib/dpkg/status 2.10.5-1ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu bionic/universe i386 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832435] Re: Lenovo miix 510 wifi adapter cannot be turned on
Could you try the latest kernel at http://kernel.ubuntu.com/~kernel-ppa/mainline/ And see if the wifi works without blacklisting ideapad-laptop as a new commit may have fixed this https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/platform/x86/ideapad-laptop.c?id=5105e78e5b2414ec39efaadca1802e37e7105bb1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832435 Title: Lenovo miix 510 wifi adapter cannot be turned on Status in linux package in Ubuntu: Confirmed Bug description: This problem appears when you first install ubuntu 18.04, 18.10, and 19.10 on a Lenovo Miix 501 laptop. I have not tried previous versions of ubuntu. After installation or update to a newer versio of ubuntu the network adaptor is set to off and cannot be turned on. I believe this is because of a non-existent or faulty driver for the intel 8260 wifi adapter. It also could be that the driver is waiting for physical or keyboard switch to turn on the adapter. However, no such switch exists in this laptop model. The problem can be resolved by adding "blacklist ideapad_laptop" to the configuration file /etc/modprobe.d/blacklist.conf (this is for ubuntu 19.04. The filename and location are different for 18.04 and 18.10) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: miguel 6912 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-19 (25 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 258a:1015 Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80U1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=b684d0bb-4d92-4580-ac87-40c2ed9a486e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 StagingDrivers: ipu3_imgu Tags: disco staging Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-12 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 2KCN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: MIIX 510-12ISK dmi.modalias: dmi:bvnLENOVO:bvr2KCN33WW:bd06/23/2017:svnLENOVO:pn80U1:pvrMIIX510-12ISK:rvnLENOVO:rnINVALID:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrMIIX510-12ISK: dmi.product.family: IDEAPAD dmi.product.name: 80U1 dmi.product.sku: LENOVO_MT_80U1_BU_idea_FM_MIIX 510-12ISK dmi.product.version: MIIX 510-12ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832435/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829211] Re: linux-fips: 4.15.0-1008.9 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829219 phase: Holding before Release phase-changed: Tuesday, 04. June 2019 09:39 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present ** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1829211 Title: linux-fips: 4.15.0-1008.9 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829219 phase: Holding before Release phase-changed: Tuesday, 04. June 2019 09:39 UTC proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829211/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
I posted here: https://devtalk.nvidia.com/default/topic/1055528/linux/nvidia-driver-in- modeset-1-requires-root-permissions-daniel-van-vugt-canonical-concludes- it-is-an-nvidia-bug/?offset=3#5351122 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-375 in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg Status in gdm3 package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
User generix reports that when gdm3 is compiled without wayland support, this bug is not seen. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-375 in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg Status in gdm3 package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829211] Re: linux-fips: 4.15.0-1008.9 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => 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/1829211 Title: linux-fips: 4.15.0-1008.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829219 phase: Holding before Release phase-changed: Tuesday, 04. June 2019 09:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829211/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1705369] Re: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU)
** Changed in: gnome-shell Status: Unknown => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1705369 Title: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU) Status in GNOME Shell: New Status in gdm3 package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-384 package in Ubuntu: Invalid Bug description: Ubuntu boots to blank screen when using Nvidia drivers (on a desktop with an unused Intel GPU). WORKAROUNDS (you only need one): * Uncomment #WaylandEnable=false in /etc/gdm3/custom.conf * Disable integrated graphics/GPU in your BIOS * Add 'nomodeset' to your kernel cmdline in /etc/default/grub and then run: sudo update-initramfs and reboot. ORIGINAL DESCRIPTION: This bug is very similar to https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576 which is closed. I have been asked to open a new bug report. The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20, 2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04. - Lightdm works - Nouveau driver works - Nvidia driver 375.66 (proprietary) does not work - Nvidia driver 384.47 (open source) does not work (from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - Nvidia drivers work with Ubuntu Gnome 17.04 I am using Nvidia GTX 1080 and Intel i7-4790K lsb_release -rd: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 apt-cache policy gnome-shell: gnome-shell: Installed: 3.24.2-0ubuntu7 Candidate: 3.24.2-0ubuntu7 Version table: *** 3.24.2-0ubuntu7 500 500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status uname -s -r -v -p -i -o: Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1705369/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829749] Re: Please add support for zipl signing
** Changed in: launchpad
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1829749
Title:
Please add support for zipl signing
Status in Launchpad itself:
Fix Released
Status in linux-signed package in Ubuntu:
New
Status in s390-tools package in Ubuntu:
In Progress
Bug description:
Please add support for zipl ("z/ecureBoot") signing.
It should be similar to opal signing, but using the new zipl signing
key.
I am expecting to sign s390-tools stage3.bin and kernel images using
this key.
s390-tools -> can be signed already
kernels -> should only sign v5.2+
To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1829749/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817321] Re: installer does not support iSCSI iBFT
Hello Mauricio, or anyone else affected, Accepted debian-installer into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debian- installer/20101020ubuntu543.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: debian-installer (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags removed: verification-done-bionic ** 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/1817321 Title: installer does not support iSCSI iBFT Status in debian-installer package in Ubuntu: Fix Released Status in hw-detect package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in partman-iscsi package in Ubuntu: Fix Released Status in debian-installer source package in Bionic: Fix Committed Status in hw-detect source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in partman-iscsi source package in Bionic: Fix Released Status in debian-installer source package in Cosmic: Fix Committed Status in hw-detect source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in partman-iscsi source package in Cosmic: Fix Released Status in debian-installer source package in Disco: Fix Committed Status in hw-detect source package in Disco: Fix Released Status in linux source package in Disco: Fix Released Status in partman-iscsi source package in Disco: Fix Released Status in debian-installer source package in Eoan: Fix Released Status in hw-detect source package in Eoan: Fix Released Status in linux source package in Eoan: Fix Released Status in partman-iscsi source package in Eoan: Fix Released Bug description: [Impact] * It's not possible to access iBFT (iSCSI Boot Firmware Table) information (settings for network interface, initiator, and target) in the installer because the 'iscsi_ibft' module is not present in udeb packages. * Even if it was, the installer does not handle iBFT information at all, thus any settings are ignored, and iSCSI-related configuration has to be done manually or with workarounds. * This impacts user-experience and automatic installation on systems and deployments which actually do provide the iBFT feature and information, but cannot use it practically. * With proper iBFT support in the installer (kernel module in udeb package and automatic iSCSI-related configuration) users will be able to rely on iBFT to install/deploy Ubuntu on their servers and datacenters. * These fixes add the 'iscsi_ibft' kernel module in the scsi-modules udeb, and configure network/iSCSI according to iBFT information in disk-detect. This is done in disk-detect so that the iSCSI LUNs are detected as disks (useful in case of no other disks in the system so the installer doesn't complain nor wait too long) and that any partman-related preseed options are not required and may be still available for the user. [Test Case] * linux package / kernel module in udeb: $ dpkg-deb -c scsi-modules_*.udeb | grep iscsi_ibft.ko Check the module loads in the installer environment. See comment with example for disco. * d-i/hw-detect/partman-iscsi package: See comments 11, 12, 13. [Regression Potential] * linux package: low, the kernel module is not loaded by default, and only checks whether iBFT information is present in firmware, then exposes that in sysfs in read-only mode. * d-i/hw-detect/partman-iscsi: - d-i: kernel version update to include iscsi_ibft module, based on kernel released to -updates plus one week monitoring bug reports -- it should be OK. Tested on amd64/i386/arm64/ppc64el on QEMU, plus amd64 on baremetal -- see co
[Kernel-packages] [Bug 1817321] Re: installer does not support iSCSI iBFT
Hello Mauricio, or anyone else affected, Accepted debian-installer into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debian- installer/20101020ubuntu557.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: debian-installer (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags removed: verification-done-cosmic ** 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/1817321 Title: installer does not support iSCSI iBFT Status in debian-installer package in Ubuntu: Fix Released Status in hw-detect package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in partman-iscsi package in Ubuntu: Fix Released Status in debian-installer source package in Bionic: In Progress Status in hw-detect source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in partman-iscsi source package in Bionic: Fix Released Status in debian-installer source package in Cosmic: Fix Committed Status in hw-detect source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in partman-iscsi source package in Cosmic: Fix Released Status in debian-installer source package in Disco: Fix Committed Status in hw-detect source package in Disco: Fix Released Status in linux source package in Disco: Fix Released Status in partman-iscsi source package in Disco: Fix Released Status in debian-installer source package in Eoan: Fix Released Status in hw-detect source package in Eoan: Fix Released Status in linux source package in Eoan: Fix Released Status in partman-iscsi source package in Eoan: Fix Released Bug description: [Impact] * It's not possible to access iBFT (iSCSI Boot Firmware Table) information (settings for network interface, initiator, and target) in the installer because the 'iscsi_ibft' module is not present in udeb packages. * Even if it was, the installer does not handle iBFT information at all, thus any settings are ignored, and iSCSI-related configuration has to be done manually or with workarounds. * This impacts user-experience and automatic installation on systems and deployments which actually do provide the iBFT feature and information, but cannot use it practically. * With proper iBFT support in the installer (kernel module in udeb package and automatic iSCSI-related configuration) users will be able to rely on iBFT to install/deploy Ubuntu on their servers and datacenters. * These fixes add the 'iscsi_ibft' kernel module in the scsi-modules udeb, and configure network/iSCSI according to iBFT information in disk-detect. This is done in disk-detect so that the iSCSI LUNs are detected as disks (useful in case of no other disks in the system so the installer doesn't complain nor wait too long) and that any partman-related preseed options are not required and may be still available for the user. [Test Case] * linux package / kernel module in udeb: $ dpkg-deb -c scsi-modules_*.udeb | grep iscsi_ibft.ko Check the module loads in the installer environment. See comment with example for disco. * d-i/hw-detect/partman-iscsi package: See comments 11, 12, 13. [Regression Potential] * linux package: low, the kernel module is not loaded by default, and only checks whether iBFT information is present in firmware, then exposes that in sysfs in read-only mode. * d-i/hw-detect/partman-iscsi: - d-i: kernel version update to include iscsi_ibft module, based on kernel released to -updates plus one week monitoring bug reports -- it should be OK. Tested on amd64/i386/arm64/ppc64el on QEMU, plus amd64 on baremetal -- see comm
[Kernel-packages] [Bug 1832715] Re: Black screen after reopening lid.
Black screen after reopening lid. Unlocking screen is impossible. SO command in a terminal window: apport-collect 1832715 is impossible. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Jean-Bernard (jb-freelance) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832715 Title: Black screen after reopening lid. Status in linux package in Ubuntu: Confirmed Bug description: Black screen after reopening lid. Configuration : laptop TOSHIBA is running with lid closed but when it is re-opened, the screen still black. Unlocking is impossible. Last OK (operational) nucleus 4.15.0-46. Problem with 4.15.0-47 to 4.15.0-51. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832715/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817321] Re: installer does not support iSCSI iBFT
Hello Mauricio, or anyone else affected, Accepted debian-installer into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debian- installer/20101020ubuntu570.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: debian-installer (Ubuntu Disco) Status: In Progress => Fix Committed ** Tags removed: verification-done verification-done-disco ** Tags added: verification-needed verification-needed-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1817321 Title: installer does not support iSCSI iBFT Status in debian-installer package in Ubuntu: Fix Released Status in hw-detect package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in partman-iscsi package in Ubuntu: Fix Released Status in debian-installer source package in Bionic: In Progress Status in hw-detect source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in partman-iscsi source package in Bionic: Fix Released Status in debian-installer source package in Cosmic: In Progress Status in hw-detect source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in partman-iscsi source package in Cosmic: Fix Released Status in debian-installer source package in Disco: Fix Committed Status in hw-detect source package in Disco: Fix Released Status in linux source package in Disco: Fix Released Status in partman-iscsi source package in Disco: Fix Released Status in debian-installer source package in Eoan: Fix Released Status in hw-detect source package in Eoan: Fix Released Status in linux source package in Eoan: Fix Released Status in partman-iscsi source package in Eoan: Fix Released Bug description: [Impact] * It's not possible to access iBFT (iSCSI Boot Firmware Table) information (settings for network interface, initiator, and target) in the installer because the 'iscsi_ibft' module is not present in udeb packages. * Even if it was, the installer does not handle iBFT information at all, thus any settings are ignored, and iSCSI-related configuration has to be done manually or with workarounds. * This impacts user-experience and automatic installation on systems and deployments which actually do provide the iBFT feature and information, but cannot use it practically. * With proper iBFT support in the installer (kernel module in udeb package and automatic iSCSI-related configuration) users will be able to rely on iBFT to install/deploy Ubuntu on their servers and datacenters. * These fixes add the 'iscsi_ibft' kernel module in the scsi-modules udeb, and configure network/iSCSI according to iBFT information in disk-detect. This is done in disk-detect so that the iSCSI LUNs are detected as disks (useful in case of no other disks in the system so the installer doesn't complain nor wait too long) and that any partman-related preseed options are not required and may be still available for the user. [Test Case] * linux package / kernel module in udeb: $ dpkg-deb -c scsi-modules_*.udeb | grep iscsi_ibft.ko Check the module loads in the installer environment. See comment with example for disco. * d-i/hw-detect/partman-iscsi package: See comments 11, 12, 13. [Regression Potential] * linux package: low, the kernel module is not loaded by default, and only checks whether iBFT information is present in firmware, then exposes that in sysfs in read-only mode. * d-i/hw-detect/partman-iscsi: - d-i: kernel version update to include iscsi_ibft module, based on kernel released to -updates plus one week monitoring bug reports -- it should be OK. Tested on amd64/i386/arm64/ppc64el on QEMU, plus amd64
[Kernel-packages] [Bug 1831736] Re: [MIR] lz4 by default
** Tags added: id-5d0162d5caee4b55443d4eda -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831736 Title: [MIR] lz4 by default Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in live-build package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: Fix Released Status in lz4 package in Ubuntu: Fix Released Status in partman-auto package in Ubuntu: Triaged Status in ubuntu-release-upgrader package in Ubuntu: Triaged Bug description: Use `lz4 -9 -l` compression for initramfs by default as discussed on ubuntu-devel. This would also pull the lz4 package into main https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040726.html [Regression Potential] We are trying to optimize for total boot speed, but performing a micro-optimization upon time to create/unpack kernel/initrd is an insufficient benchmark for total boot speed. This is because it ignores time to load the kernel/initrd, and whether the firmware/bootloader were able to stream decompress it whilst loading it. I.e. it is argued that in the real world, subsecond decompression gains are irrelevant if UEFI firmware, tftp boot, etc. take a lot longer than that to read extra 10s of MBs of boot material. [TODO] Measure pure i/o load speed with stopwatch, to figure out MB/s speed of loading initrds/kernel off FAT32, EXT4, TFTP, HTTP. Re-evaluate if we should provide different compression mechanisms: - ie. gzip instead of lz4 for most cases (revert) - ie. xz for painful i/o cases (e.g. netboot) I booted grub2 and measured loading largish amount of files, ie. $ date; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; date To get a rough speed between 30 and 44 MB/s of loading these files off ext4 on nvme. With lz4 initrd taking 67M, and gzip initrd taking 59M, the grub i/o penalty is 0.18s whilst I gain over a second in faster decompression time. Overall a win. xz initrd is 36M meaning saving e.g. 0.8s of i/o time whilst gaining 2.4s of decompression time, meaning overall worse than gzip. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1831736/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826410] Re: Please package libbpf (which is done out of the kernel src) in Debian [for 19.10]
** No longer affects: linux (Ubuntu Disco) ** Changed in: linux (Ubuntu) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826410 Title: Please package libbpf (which is done out of the kernel src) in Debian [for 19.10] Status in linux package in Ubuntu: Triaged Bug description: Hi, Debian packages libbpf and so far does so out of the kernel source [1]. There is some movement to separate that from the kernel source [2] but this isn't ready yet. So far it is just a sync of the subtree out of the kernel sources. Since we do not share our kernel packaging we will not get this for-free without doing anything. If there will be an ITP about it in Debian I'll let you know and we can abort this, but unless that really happens I wanted to ask if you could as well build the libbpf* packages for 19.10 and onward? Note: this is not the same bpf lib as [3] despite the similarity in names. Reasoning: BPF becomes more and more important in general and is used in the kernel for many things. In the case that brought it to my attention it will be a PMD of DPDK that will need it to control XDP [4]. And XDP in general is an interesting and rising feature for network acceleration - I'd think it would be helpful to have this package around in Ubuntu. [1]: https://packages.debian.org/sid/libbpf-dev [2]: https://github.com/libbpf/libbpf [3]: https://github.com/iovisor/bcc [4]: https://www.iovisor.org/technology/xdp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826410/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832468] Re: linux-oem: 4.15.0-1042.47 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829219 phase: Testing phase-changed: Thursday, 13. June 2019 11: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 - verification-testing: Pending -- Ready variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1832468 Title: linux-oem: 4.15.0-1042.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: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829219 phase: Testing phase-changed: Thursday, 13. June 2019 11: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 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832468/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825942] Re: kernel crash : net_sched race condition in tcindex_destroy()
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Andrea Righi (arighi) ** Changed in: linux (Ubuntu) Importance: Medium => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825942 Title: kernel crash : net_sched race condition in tcindex_destroy() Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: [Impact] It is possible to trigger a NULL pointer dereference in tcindex_delete() with a simple reproducer script, this is because in tcindex_set_parms() when old_r doesn't exist we set the new exts to cr.exts that can be uninitialized, triggering the NULL pointer dereference. In addition to that we may also hit a race condition in tcindex_destroy() (as pointed out in the original bug report and also here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921542#10), that is also fixed upstream, but it requires 4b79817f7add "net_sched: switch to rcu_work". However adding these changes introduces three memory leak problems in cls_tcindex (that can be easily verified using the same test case). These leaks are also fixed upstream by 711ff09f3330 "net_sched: fix a memory leak in cls_tcindex" and 000d2aeda70c "net_sched: fix two more memory leaks in cls_tcindex", so we need to backport also these two additional fixes. After all these fixes are applied the test case doesn't seem to trigger any bug. [Test Case] #!/bin/sh -ex modprobe ifb while true; do tc qdisc add dev ifb0 root handle 2:0 prio bands 5 tc qdisc add dev ifb0 parent 2:5 sfq tc filter add dev ifb0 parent 2:0 protocol ip prio 5 handle 0 tcindex mask 0 classid 2:5 pass_on tc qdisc del dev ifb0 root || true done [Fix] * Fixes required to solve this problem: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2df8bee5654bb2b7312662ca6810d4dc16b0b67f https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8015d93ebd27484418d4952284fd02172fa4b0b2 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=033b228e7f26b29ae37f8bfa1bc6b209a5365e9f https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1db817e75f5b9387b8db11e37d5f0624eb9223e0 [Regression Potential] * All upstream fixes, tested on the affected platform, backport changes are minimal. [Original bug report] I am running into a kernel crash issue using latest Ubuntu 4.15 kernel. It does not appear to have been fixed in Ubuntu-4.15.0-48.51. This crash has also been reported for debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921542 The kernel crash issue was fixed in February in the Linux kernel: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=056a17982adbd52b2a6c5ec6266cee4521cd931b I did test one of the recent kernel-ppa/mainline kernels, more specifically: linux-image-unsigned-4.19.34-041934-generic_4.19.34-041934.201904051741_amd64.deb It seems to fix the problem, that is, no crashes experienced so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825942/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832715] 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 1832715 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832715 Title: Black screen after reopening lid. Status in linux package in Ubuntu: Incomplete Bug description: Black screen after reopening lid. Configuration : laptop TOSHIBA is running with lid closed but when it is re-opened, the screen still black. Unlocking is impossible. Last OK (operational) nucleus 4.15.0-46. Problem with 4.15.0-47 to 4.15.0-51. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832715/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1239459]
ReSharper 2019.1 [Crack Incl License Key]! Resharper Keygen ReSharper 2019.1 Crack– This is the smart tool that works inside the visual studio. It is a productivity extension in the visual studio for detecting errors. In addition, it will work for code correction, redundancies problems, syntax issues, and many more. In addition, You can make your code simple and easy. This will help the user to write the bast codes. Furthermore, it works as an intelligent code correction. Therefore, You can also explore the code using code structure, styles, types, and value chain. This extension will lead you to find problems, particular code, errors, bugs, and more. It has 2000 on the fly code inspection for JAVA, VB, C++ etc. Finally, install and indent your code in a better way.https://crackscoop.com/";>crack scoop Finally, Resharper with License key is now activated. Resharper 2019.1 Keygen With Activation key Resharper 2019.1 Keygen is available for full software. You will get all features after registration. In addition, You can manage C#, XAML, VB>NET, Type Scripts, Java Scripts, HTML, XML, CSS, and ASP. This keygen setup gives robust of the features. Its new features checks code automatically and suggest the best solution. This version provides the best programming solution. In addition, we have fixed the bugs with crack. Get it and make well indent your code for better efficiency. The main feature is the language cross-functionality. You can write any script in IDE. it will work for all languages. Finally, Use the torrent file and download the full version including all new features. Resharper Keygen Key Features Easy to download and install. Ease your code correction. Works for many programming languages. Best programming way. It supports for visual studio 2017 RTM. Easy code testing. Supports for C# Unit testing feature. Easy editor configuration. Code cleaning, code styles, and easy formatting options. It supports for Type Scripts and java scripts. easy command line profiler. What’s New Eliminate errors and indent the code. Provides instantly traversing. Here is code quality analysis. best code editors. How to Crack? Download and run the setup. Extract files into a folder. Run the setup and install it. Configure the setting. Turn off the internet. Run Crack and install it. 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/1239459 Title: 1814:3290 [Asus X200CA] wifi doesn't connect or disconnects after few seconds Status in Linux: Won't Fix Status in linux package in Ubuntu: Fix Released Bug description: With the new 3.11.0-12-generic kernel, wifi has problems to connect with many errors like these: Oct 13 23:50:03 ubuntotto kernel: [ 1186.580726] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:03 ubuntotto kernel: [ 1186.740659] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1186.900544] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1187.060571] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:50:04 ubuntotto kernel: [ 1187.096576] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0 Oct 13 23:50:05 ubuntotto kernel: [ 1188.280106] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:50:05 ubuntotto kernel: [ 1188.440128] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:51:06 ubuntotto kernel: [ 1249.560697] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:51:06 ubuntotto kernel: [ 1249.720644] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush Oct 13 23:51:07 ubuntotto kernel: [ 1249.880590] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush Oct 13 23:51:07 ubuntotto kernel: [ 1250.040543] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: andrea 1791 F pulseaudio Date: Sun Oct 13 23:45:04 2013 HibernationDevice: RESUME=UUID=297ef090-5420-41f6-8439-f1254f3e9e15 InstallationDate: Installed on 2013-10-12 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. X200CA MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=088f2a7d-b78f-4bdd-a184
[Kernel-packages] [Bug 1239459]
Clip Studio Paint 1.9.0 License Key {New Update}
Clip Studio Paint Crack is an efficient and versatile program for creating
different types of digital art. It is a great successor to comic or Manga
studio. And is a very essential tool for creating various types of manga, comic
as well as cartoons. It has specialized features for adding amazing details and
colors to your work.
It has the ability to add new tools such as pens, brushes, color tones,
styles, 3D models and many more. Many new tools and features are
released from manufactures for advanced functionality. allows users to
share different artwork with your social circle as well as the whole
world. It offers perfect functions for creating amazing cartoons,
animations, clip art, illustration and much more with complete ease.
Clip Studio Paint Serial Number is a comprehensive program for creating
different digital art project from start to end phase. It offers a
complete art studio in digital device for any artist. The user can use
it express their creativity in any way they want without any limitation.
The user can easily zoom in and out for adding a different level of
detail to the painting. It has all the required tools for creating
different types of comic strips and manga novels.
With this software, the user can add a different dimension to their
artwork. Clip Studio Paint Crack has features for adding unique
textures, shadows, lights and many other effects to your artwork as
well. It has a large collection of art, clips, animation, and many other
objects. Which you can just add by drag and drop to your drawings.https://windowactivator.org/";>Window Activator Such as user
can add different styles of dialogue balloons for adding conservations
to comic books.
Clip Studio Paint Full Torrent [Mac+Windows]2019
Clip Studio Paint Key Feature:
The pen will be searched for pen color procession strips.
It seems like a real pen.
A large number of drawing tools Markers, brushes, and similar equivalents
Jewelry devices can make a posh sample with a single stroke.
Make samples reminiscent of plants, grasses, chains, and many different things.
Create vector layers and trace them and draw different items.
Clip Studio Paint 1.8.5 Crack, Change the objects on vector layers. Equal to
increase, scale, and scale
of scales width
Get supplies and different things to look great on your artwork.
There are plenty of ruler varieties. To draw the right picture
The symmetrical ruler allows you to create a symmetrical shape in the artwork.
With perspective rulers, you will be able to add an approach to your artwork.
Clip Studio Paint Torrent, Determine and create 3D in your drawing.
Transfer any part of the 3D motion set by the mouse.
Make a great amount of color in your lines.
With auto-action, you will be able to perform many duties without delay.
What’s new in Clip Studio Paint Crack?
Export and import your drawings in Photoshop.
Clip Studio Paint 1.8.5 Crack
Now you can import and export in CMYK color.
You may change the interface and customize the format.
Now export your artwork in PDF format.
System Requirements:
Home windows 7 | 8 \ 8.1 / Mac OS X 10.9 | 10.10 | 10.11 or newer.
2 GHz CPU.
512 MB Graphics.
2 GB RAM
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1239459
Title:
1814:3290 [Asus X200CA] wifi doesn't connect or disconnects after few
seconds
Status in Linux:
Won't Fix
Status in linux package in Ubuntu:
Fix Released
Bug description:
With the new 3.11.0-12-generic kernel, wifi has problems to connect with many
errors like these:
Oct 13 23:50:03 ubuntotto kernel: [ 1186.580726] ieee80211 phy0:
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
Oct 13 23:50:03 ubuntotto kernel: [ 1186.740659] ieee80211 phy0:
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
Oct 13 23:50:04 ubuntotto kernel: [ 1186.900544] ieee80211 phy0:
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
Oct 13 23:50:04 ubuntotto kernel: [ 1187.060571] ieee80211 phy0:
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
Oct 13 23:50:04 ubuntotto kernel: [ 1187.096576] ieee80211 phy0:
rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0
Oct 13 23:50:05 ubuntotto kernel: [ 1188.280106] ieee80211 phy0:
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
Oct 13 23:50:05 ubuntotto kernel: [ 1188.440128] ieee80211 phy0:
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
Oct 13 23:51:06 ubuntotto kernel: [ 1249.560697] ieee80211 phy0:
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
Oct 13 23:51:06 ubuntotto kernel: [ 1249.720644] ieee80211 phy0:
rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
Oct 13 23:51:07 ubuntotto kernel: [ 1249.880590] ieee80211 phy0:
rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
Oct 13 23:51:07 ubuntotto kernel: [ 1250
[Kernel-packages] [Bug 1832435] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1832435/+attachment/5270613/+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/1832435 Title: Lenovo miix 510 wifi adapter cannot be turned on Status in linux package in Ubuntu: Confirmed Bug description: This problem appears when you first install ubuntu 18.04, 18.10, and 19.10 on a Lenovo Miix 501 laptop. I have not tried previous versions of ubuntu. After installation or update to a newer versio of ubuntu the network adaptor is set to off and cannot be turned on. I believe this is because of a non-existent or faulty driver for the intel 8260 wifi adapter. It also could be that the driver is waiting for physical or keyboard switch to turn on the adapter. However, no such switch exists in this laptop model. The problem can be resolved by adding "blacklist ideapad_laptop" to the configuration file /etc/modprobe.d/blacklist.conf (this is for ubuntu 19.04. The filename and location are different for 18.04 and 18.10) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: miguel 6912 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-19 (25 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 258a:1015 Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80U1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=b684d0bb-4d92-4580-ac87-40c2ed9a486e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 StagingDrivers: ipu3_imgu Tags: disco staging Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-12 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 2KCN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: MIIX 510-12ISK dmi.modalias: dmi:bvnLENOVO:bvr2KCN33WW:bd06/23/2017:svnLENOVO:pn80U1:pvrMIIX510-12ISK:rvnLENOVO:rnINVALID:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrMIIX510-12ISK: dmi.product.family: IDEAPAD dmi.product.name: 80U1 dmi.product.sku: LENOVO_MT_80U1_BU_idea_FM_MIIX 510-12ISK dmi.product.version: MIIX 510-12ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832435/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832435] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1832435/+attachment/5270604/+files/IwConfig.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/1832435 Title: Lenovo miix 510 wifi adapter cannot be turned on Status in linux package in Ubuntu: Confirmed Bug description: This problem appears when you first install ubuntu 18.04, 18.10, and 19.10 on a Lenovo Miix 501 laptop. I have not tried previous versions of ubuntu. After installation or update to a newer versio of ubuntu the network adaptor is set to off and cannot be turned on. I believe this is because of a non-existent or faulty driver for the intel 8260 wifi adapter. It also could be that the driver is waiting for physical or keyboard switch to turn on the adapter. However, no such switch exists in this laptop model. The problem can be resolved by adding "blacklist ideapad_laptop" to the configuration file /etc/modprobe.d/blacklist.conf (this is for ubuntu 19.04. The filename and location are different for 18.04 and 18.10) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: miguel 6912 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-19 (25 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 258a:1015 Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80U1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=b684d0bb-4d92-4580-ac87-40c2ed9a486e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 StagingDrivers: ipu3_imgu Tags: disco staging Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-12 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 2KCN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: MIIX 510-12ISK dmi.modalias: dmi:bvnLENOVO:bvr2KCN33WW:bd06/23/2017:svnLENOVO:pn80U1:pvrMIIX510-12ISK:rvnLENOVO:rnINVALID:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrMIIX510-12ISK: dmi.product.family: IDEAPAD dmi.product.name: 80U1 dmi.product.sku: LENOVO_MT_80U1_BU_idea_FM_MIIX 510-12ISK dmi.product.version: MIIX 510-12ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832435/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832435] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1832435/+attachment/5270607/+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/1832435 Title: Lenovo miix 510 wifi adapter cannot be turned on Status in linux package in Ubuntu: Confirmed Bug description: This problem appears when you first install ubuntu 18.04, 18.10, and 19.10 on a Lenovo Miix 501 laptop. I have not tried previous versions of ubuntu. After installation or update to a newer versio of ubuntu the network adaptor is set to off and cannot be turned on. I believe this is because of a non-existent or faulty driver for the intel 8260 wifi adapter. It also could be that the driver is waiting for physical or keyboard switch to turn on the adapter. However, no such switch exists in this laptop model. The problem can be resolved by adding "blacklist ideapad_laptop" to the configuration file /etc/modprobe.d/blacklist.conf (this is for ubuntu 19.04. The filename and location are different for 18.04 and 18.10) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: miguel 6912 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-19 (25 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 258a:1015 Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80U1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=b684d0bb-4d92-4580-ac87-40c2ed9a486e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 StagingDrivers: ipu3_imgu Tags: disco staging Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-12 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 2KCN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: MIIX 510-12ISK dmi.modalias: dmi:bvnLENOVO:bvr2KCN33WW:bd06/23/2017:svnLENOVO:pn80U1:pvrMIIX510-12ISK:rvnLENOVO:rnINVALID:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrMIIX510-12ISK: dmi.product.family: IDEAPAD dmi.product.name: 80U1 dmi.product.sku: LENOVO_MT_80U1_BU_idea_FM_MIIX 510-12ISK dmi.product.version: MIIX 510-12ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832435/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832435] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1832435/+attachment/5270602/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832435 Title: Lenovo miix 510 wifi adapter cannot be turned on Status in linux package in Ubuntu: Confirmed Bug description: This problem appears when you first install ubuntu 18.04, 18.10, and 19.10 on a Lenovo Miix 501 laptop. I have not tried previous versions of ubuntu. After installation or update to a newer versio of ubuntu the network adaptor is set to off and cannot be turned on. I believe this is because of a non-existent or faulty driver for the intel 8260 wifi adapter. It also could be that the driver is waiting for physical or keyboard switch to turn on the adapter. However, no such switch exists in this laptop model. The problem can be resolved by adding "blacklist ideapad_laptop" to the configuration file /etc/modprobe.d/blacklist.conf (this is for ubuntu 19.04. The filename and location are different for 18.04 and 18.10) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: miguel 6912 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-19 (25 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 258a:1015 Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80U1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=b684d0bb-4d92-4580-ac87-40c2ed9a486e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 StagingDrivers: ipu3_imgu Tags: disco staging Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-12 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 2KCN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: MIIX 510-12ISK dmi.modalias: dmi:bvnLENOVO:bvr2KCN33WW:bd06/23/2017:svnLENOVO:pn80U1:pvrMIIX510-12ISK:rvnLENOVO:rnINVALID:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrMIIX510-12ISK: dmi.product.family: IDEAPAD dmi.product.name: 80U1 dmi.product.sku: LENOVO_MT_80U1_BU_idea_FM_MIIX 510-12ISK dmi.product.version: MIIX 510-12ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832435/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832435] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1832435/+attachment/5270608/+files/ProcEnviron.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/1832435 Title: Lenovo miix 510 wifi adapter cannot be turned on Status in linux package in Ubuntu: Confirmed Bug description: This problem appears when you first install ubuntu 18.04, 18.10, and 19.10 on a Lenovo Miix 501 laptop. I have not tried previous versions of ubuntu. After installation or update to a newer versio of ubuntu the network adaptor is set to off and cannot be turned on. I believe this is because of a non-existent or faulty driver for the intel 8260 wifi adapter. It also could be that the driver is waiting for physical or keyboard switch to turn on the adapter. However, no such switch exists in this laptop model. The problem can be resolved by adding "blacklist ideapad_laptop" to the configuration file /etc/modprobe.d/blacklist.conf (this is for ubuntu 19.04. The filename and location are different for 18.04 and 18.10) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: miguel 6912 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-19 (25 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 258a:1015 Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80U1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=b684d0bb-4d92-4580-ac87-40c2ed9a486e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 StagingDrivers: ipu3_imgu Tags: disco staging Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-12 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 2KCN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: MIIX 510-12ISK dmi.modalias: dmi:bvnLENOVO:bvr2KCN33WW:bd06/23/2017:svnLENOVO:pn80U1:pvrMIIX510-12ISK:rvnLENOVO:rnINVALID:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrMIIX510-12ISK: dmi.product.family: IDEAPAD dmi.product.name: 80U1 dmi.product.sku: LENOVO_MT_80U1_BU_idea_FM_MIIX 510-12ISK dmi.product.version: MIIX 510-12ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832435/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832435] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1832435/+attachment/5270605/+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/1832435 Title: Lenovo miix 510 wifi adapter cannot be turned on Status in linux package in Ubuntu: Confirmed Bug description: This problem appears when you first install ubuntu 18.04, 18.10, and 19.10 on a Lenovo Miix 501 laptop. I have not tried previous versions of ubuntu. After installation or update to a newer versio of ubuntu the network adaptor is set to off and cannot be turned on. I believe this is because of a non-existent or faulty driver for the intel 8260 wifi adapter. It also could be that the driver is waiting for physical or keyboard switch to turn on the adapter. However, no such switch exists in this laptop model. The problem can be resolved by adding "blacklist ideapad_laptop" to the configuration file /etc/modprobe.d/blacklist.conf (this is for ubuntu 19.04. The filename and location are different for 18.04 and 18.10) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: miguel 6912 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-19 (25 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 258a:1015 Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80U1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=b684d0bb-4d92-4580-ac87-40c2ed9a486e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 StagingDrivers: ipu3_imgu Tags: disco staging Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-12 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 2KCN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: MIIX 510-12ISK dmi.modalias: dmi:bvnLENOVO:bvr2KCN33WW:bd06/23/2017:svnLENOVO:pn80U1:pvrMIIX510-12ISK:rvnLENOVO:rnINVALID:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrMIIX510-12ISK: dmi.product.family: IDEAPAD dmi.product.name: 80U1 dmi.product.sku: LENOVO_MT_80U1_BU_idea_FM_MIIX 510-12ISK dmi.product.version: MIIX 510-12ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832435/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832435] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1832435/+attachment/5270612/+files/RfKill.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/1832435 Title: Lenovo miix 510 wifi adapter cannot be turned on Status in linux package in Ubuntu: Confirmed Bug description: This problem appears when you first install ubuntu 18.04, 18.10, and 19.10 on a Lenovo Miix 501 laptop. I have not tried previous versions of ubuntu. After installation or update to a newer versio of ubuntu the network adaptor is set to off and cannot be turned on. I believe this is because of a non-existent or faulty driver for the intel 8260 wifi adapter. It also could be that the driver is waiting for physical or keyboard switch to turn on the adapter. However, no such switch exists in this laptop model. The problem can be resolved by adding "blacklist ideapad_laptop" to the configuration file /etc/modprobe.d/blacklist.conf (this is for ubuntu 19.04. The filename and location are different for 18.04 and 18.10) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: miguel 6912 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-19 (25 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 258a:1015 Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80U1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=b684d0bb-4d92-4580-ac87-40c2ed9a486e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 StagingDrivers: ipu3_imgu Tags: disco staging Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-12 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 2KCN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: MIIX 510-12ISK dmi.modalias: dmi:bvnLENOVO:bvr2KCN33WW:bd06/23/2017:svnLENOVO:pn80U1:pvrMIIX510-12ISK:rvnLENOVO:rnINVALID:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrMIIX510-12ISK: dmi.product.family: IDEAPAD dmi.product.name: 80U1 dmi.product.sku: LENOVO_MT_80U1_BU_idea_FM_MIIX 510-12ISK dmi.product.version: MIIX 510-12ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832435/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832435] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1832435/+attachment/5270609/+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/1832435 Title: Lenovo miix 510 wifi adapter cannot be turned on Status in linux package in Ubuntu: Confirmed Bug description: This problem appears when you first install ubuntu 18.04, 18.10, and 19.10 on a Lenovo Miix 501 laptop. I have not tried previous versions of ubuntu. After installation or update to a newer versio of ubuntu the network adaptor is set to off and cannot be turned on. I believe this is because of a non-existent or faulty driver for the intel 8260 wifi adapter. It also could be that the driver is waiting for physical or keyboard switch to turn on the adapter. However, no such switch exists in this laptop model. The problem can be resolved by adding "blacklist ideapad_laptop" to the configuration file /etc/modprobe.d/blacklist.conf (this is for ubuntu 19.04. The filename and location are different for 18.04 and 18.10) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: miguel 6912 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-19 (25 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 258a:1015 Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80U1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=b684d0bb-4d92-4580-ac87-40c2ed9a486e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 StagingDrivers: ipu3_imgu Tags: disco staging Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-12 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 2KCN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: MIIX 510-12ISK dmi.modalias: dmi:bvnLENOVO:bvr2KCN33WW:bd06/23/2017:svnLENOVO:pn80U1:pvrMIIX510-12ISK:rvnLENOVO:rnINVALID:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrMIIX510-12ISK: dmi.product.family: IDEAPAD dmi.product.name: 80U1 dmi.product.sku: LENOVO_MT_80U1_BU_idea_FM_MIIX 510-12ISK dmi.product.version: MIIX 510-12ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832435/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832435] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1832435/+attachment/5270614/+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/1832435 Title: Lenovo miix 510 wifi adapter cannot be turned on Status in linux package in Ubuntu: Confirmed Bug description: This problem appears when you first install ubuntu 18.04, 18.10, and 19.10 on a Lenovo Miix 501 laptop. I have not tried previous versions of ubuntu. After installation or update to a newer versio of ubuntu the network adaptor is set to off and cannot be turned on. I believe this is because of a non-existent or faulty driver for the intel 8260 wifi adapter. It also could be that the driver is waiting for physical or keyboard switch to turn on the adapter. However, no such switch exists in this laptop model. The problem can be resolved by adding "blacklist ideapad_laptop" to the configuration file /etc/modprobe.d/blacklist.conf (this is for ubuntu 19.04. The filename and location are different for 18.04 and 18.10) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: miguel 6912 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-19 (25 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 258a:1015 Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80U1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=b684d0bb-4d92-4580-ac87-40c2ed9a486e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 StagingDrivers: ipu3_imgu Tags: disco staging Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-12 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 2KCN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: MIIX 510-12ISK dmi.modalias: dmi:bvnLENOVO:bvr2KCN33WW:bd06/23/2017:svnLENOVO:pn80U1:pvrMIIX510-12ISK:rvnLENOVO:rnINVALID:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrMIIX510-12ISK: dmi.product.family: IDEAPAD dmi.product.name: 80U1 dmi.product.sku: LENOVO_MT_80U1_BU_idea_FM_MIIX 510-12ISK dmi.product.version: MIIX 510-12ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832435/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832435] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1832435/+attachment/5270606/+files/ProcCpuinfo.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/1832435 Title: Lenovo miix 510 wifi adapter cannot be turned on Status in linux package in Ubuntu: Confirmed Bug description: This problem appears when you first install ubuntu 18.04, 18.10, and 19.10 on a Lenovo Miix 501 laptop. I have not tried previous versions of ubuntu. After installation or update to a newer versio of ubuntu the network adaptor is set to off and cannot be turned on. I believe this is because of a non-existent or faulty driver for the intel 8260 wifi adapter. It also could be that the driver is waiting for physical or keyboard switch to turn on the adapter. However, no such switch exists in this laptop model. The problem can be resolved by adding "blacklist ideapad_laptop" to the configuration file /etc/modprobe.d/blacklist.conf (this is for ubuntu 19.04. The filename and location are different for 18.04 and 18.10) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: miguel 6912 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-19 (25 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 258a:1015 Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80U1 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=b684d0bb-4d92-4580-ac87-40c2ed9a486e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 StagingDrivers: ipu3_imgu Tags: disco staging Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: Upgraded to disco on 2019-06-12 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 2KCN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: MIIX 510-12ISK dmi.modalias: dmi:bvnLENOVO:bvr2KCN33WW:bd06/23/2017:svnLENOVO:pn80U1:pvrMIIX510-12ISK:rvnLENOVO:rnINVALID:rvrSDK0J40697WIN:cvnLENOVO:ct32:cvrMIIX510-12ISK: dmi.product.family: IDEAPAD dmi.product.name: 80U1 dmi.product.sku: LENOVO_MT_80U1_BU_idea_FM_MIIX 510-12ISK dmi.product.version: MIIX 510-12ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832435/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
