[Kernel-packages] [Bug 1956559] Re: sleep/wake-up timeout issue
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1956559
Title:
sleep/wake-up timeout issue
Status in linux package in Ubuntu:
Expired
Bug description:
I have a unexpected issue that related in sleep/wake-up timeout for task,
while device driver develop.
my code use kernel function 'wait_for_completion_interruptible_timeout' when
there is a reason for task sleep, this function parameter need input 'want
timeout in jiffies', so i have try that input any value like
"msecs_to_jiffies(255 * 1000)" for sleep task 255seconds.
I expected this function 'wait_for_completion_interruptible_timeout' return
zero when after almost exactly 255seconds. but I measured the actual time, it
was additionally delayed maximum almost 11 seconds(final time 266 seconds) in
my test case.
so result of have additional test, the additionally delayed time is
different, but the result is the same.
additionally delayed time range was random in 1ms ~ 11seconds.
this issue occur in kernel function 'msleep(255 * 1000)' too... because
schedule_timeout() used in 'wait_for_completion_interruptible_timeout' and
msleep.
※A additionally delayed time occurs even if a different number is
entered like 1ms or 1seconds..
I think it "additionally delayed time" was mean that wake-up task but time to
task racing until active run in cpu. am i guessing right? or not am i doing
something wrong?
If my thoughts are right, How do I get the correct time?
Below is the sample code I tested.
struct completion cmp;
static long g_jiffies = 0;
static int _open(struct inode *inode, struct file *file)
{
init_completion();
g_jiffies = 0;
return 0;
}
static ssize_t _read(struct file *filp, char __user *buffer, size_t count,
loff_t *ppos)
{
long sch = 0;
reinit_completion();
printk(KERN_NOTICE "start checking\n");
g_jiffies = jiffies;
sch = wait_for_completion_interruptible_timeout(,
msecs_to_jiffies(255 * 1000));
//msleep(255 * 1000)
printk(KERN_NOTICE "delay time = %ld\n", jiffies_to_msecs(jiffies -
g_jiffies));
return 0;
}
result dmesg :
[목 1월 6 13:05:30 2022] start checking
[목 1월 6 13:09:52 2022] delay time = 261808
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956559/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956998] Re: kvm SGX numa support
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956998 Title: kvm SGX numa support Status in linux package in Ubuntu: Expired Bug description: The basic SGX patches were merged into Qemu release, the left NUMA function for SGX should be enabled. The patch1 implemented the SGX NUMA ACPI to enable NUMA in the SGX guest. Since Libvirt need detailed host SGX EPC sections info to decide how to allocate EPC sections for SGX NUMA guest, the SGXEPCSection list is introduced to show detailed sections info in the monitor or HMP interface. Please help review this patchset, the link also can be found: https://github.com/intel/qemu-sgx upstream Platform: Ice Lake qemu 6.2 110581238 numa: Enable numa for SGX EPC sections 4755927ae numa: Support SGX numa in the monitor and Libvirt interfaces d1889b360 doc: Add the SGX numa description To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957002] Re: tp-link AC1300 not working in 21.10
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1957002
Title:
tp-link AC1300 not working in 21.10
Status in linux package in Ubuntu:
Expired
Bug description:
A driver exists on github, but is not available in ubuntu 21.10
https://community.tp-link.com/en/home/forum/topic/208022
describes where to find it and how to install it:
git clone https://github.com/cilynx/rtl88x2bu.git
cd rtl88x2bu
VER=$(sed -n 's/\PACKAGE_VERSION="\(.*\)"/\1/p' dkms.conf)
sudo rsync -rvhP ./ /usr/src/rtl88x2bu-${VER}
sudo dkms add -m rtl88x2bu -v ${VER}
sudo dkms build -m rtl88x2bu -v ${VER}
sudo dkms install -m rtl88x2bu -v ${VER}
sudo modprobe 88x2bu
Would be great you could add it to 22.04.
Thanks
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: norbert1472 F pulseaudio
/dev/snd/controlC1: norbert1472 F pulseaudio
/dev/snd/pcmC1D0p: norbert1472 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2022-01-09 (3 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 20AMS4SL00
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic
root=UUID=91eee538-5a80-4d2b-9126-f2d53ad695e6 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-5.13.0-23-generic N/A
linux-backports-modules-5.13.0-23-generic N/A
linux-firmware 1.201.3
Tags: wayland-session impish
Uname: Linux 5.13.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 08/27/2014
dmi.bios.release: 2.26
dmi.bios.vendor: LENOVO
dmi.bios.version: GIET76WW (2.26 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AMS4SL00
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.ec.firmware.release: 1.13
dmi.modalias:
dmi:bvnLENOVO:bvrGIET76WW(2.26):bd08/27/2014:br2.26:efr1.13:svnLENOVO:pn20AMS4SL00:pvrThinkPadX240:rvnLENOVO:rn20AMS4SL00:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AM_BU_Think_FM_ThinkPadX240:
dmi.product.family: ThinkPad X240
dmi.product.name: 20AMS4SL00
dmi.product.sku: LENOVO_MT_20AM_BU_Think_FM_ThinkPad X240
dmi.product.version: ThinkPad X240
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957002/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957714] Re: Computer off, discharge battery
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1957714 Title: Computer off, discharge battery Status in linux package in Ubuntu: Expired Bug description: After having updated the Kernel version to this 5.11.0.46 the battery drains when the computer is off and charges when it is turned on. I tried to see what it could be and in Windows they point to the Intel Management Engine Interface driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957847] Re: display output detection problem
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1957847 Title: display output detection problem Status in linux package in Ubuntu: Expired Bug description: dell precision M6800 KERNEL 5.4.0-94 attempts to activate vga while not plugged in, deactivates, cyclic screen blackout, shape/size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964814] Re: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1
Allan, bsdz: thanks for the workaround(s). However, workarounds don't get to the heart of fixing the problem, which is what bug reports are intended to do. Rest assured, the people that need to fix this are working on it, hence the triage and assignment, and I would expect this to be fixed very soon. For those that would want to use this workaround, that would be done at their own risk, and those workarounds could be undone and unnecessitated by package updates. My best advice, especially if you're running Jammy, is to just wait it out and it will get fixed. These types of problems don't go unnoticed, and certainly don't stick around for long. :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1964814 Title: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1 Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Jammy: Confirmed Bug description: linux-firmware fails to upgrade with: unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg- new': No such file or directory $ sudo apt dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: linux-firmware 1 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade. Need to get 0 B/238 MB of archives. After this operation, 24.9 MB of additional disk space will be used. Do you want to continue? [Y/n] y (Reading database ... 272091 files and directories currently installed.) Preparing to unpack .../linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb ... Unpacking linux-firmware (20220314.gitcd01f857-0ubuntu1) over (20220302.gitee0667aa-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack): unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new': No such file or directory No apport report written because the error message indicates an issue on the local system update-initramfs: Generating /boot/initrd.img-5.15.0-23-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. Errors were encountered while processing: /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1964814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964539] Re: 42beta: screen unlock gets stuck on primary display, secondary display is unlocked
Managed to reproduce at again, this time at 15:54. ** Attachment added: "Second reproduction logs" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964539/+attachment/5568923/+files/repro2.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/1964539 Title: [nouveau] 42beta: screen unlock gets stuck on primary display, secondary display is unlocked Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: [Impact] Occasionally, when the screen has been locked for a medium length of time, > 5 mins, when you press the spacebar, enter your password, the primary display freezes and the lockscreen slider does not slide up. The secondary screen is fine, and unlocks. See screenshot for what it looks like. You can click, interact with the secondary screen. On the primary screen, you can super key and launch an application, but you won't be able to interact with it. You can't see what you are doing. The way to fix is to re-lock the screen, wait a bit, and attempt to unlock. Sometimes you won't be able to unlock immediately, as it is difficult to get the monitor to power on again, it appears gnome-shell does not send the wakeup signal. gnome-shell 42~beta-1ubuntu2 from -proposed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-01-02 (68 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220101) Package: gnome-shell PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 RelatedPackageVersions: mutter-common 42~beta-1ubuntu1 Tags: wayland-session third-party-packages jammy package-from-proposed Uname: Linux 5.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964539] Re: 42beta: screen unlock gets stuck on primary display, secondary display is unlocked
** No longer affects: gnome-shell (Ubuntu) ** Summary changed: - 42beta: screen unlock gets stuck on primary display, secondary display is unlocked + [nouveau] 42beta: screen unlock gets stuck on primary display, secondary display is unlocked ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (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/1964539 Title: [nouveau] 42beta: screen unlock gets stuck on primary display, secondary display is unlocked Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: [Impact] Occasionally, when the screen has been locked for a medium length of time, > 5 mins, when you press the spacebar, enter your password, the primary display freezes and the lockscreen slider does not slide up. The secondary screen is fine, and unlocks. See screenshot for what it looks like. You can click, interact with the secondary screen. On the primary screen, you can super key and launch an application, but you won't be able to interact with it. You can't see what you are doing. The way to fix is to re-lock the screen, wait a bit, and attempt to unlock. Sometimes you won't be able to unlock immediately, as it is difficult to get the monitor to power on again, it appears gnome-shell does not send the wakeup signal. gnome-shell 42~beta-1ubuntu2 from -proposed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-01-02 (68 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220101) Package: gnome-shell PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 RelatedPackageVersions: mutter-common 42~beta-1ubuntu1 Tags: wayland-session third-party-packages jammy package-from-proposed Uname: Linux 5.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964539] Re: 42beta: screen unlock gets stuck on primary display, secondary display is unlocked
Thanks. That shows the 'nouveau' driver is spewing errors which will make the behaviour of the desktop unpredictable. Please use the 'Additional Drivers' app to install the proprietary Nvidia driver instead. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Jammy) ** Changed in: linux (Ubuntu) Status: New => Incomplete ** No longer affects: gnome-shell (Ubuntu Jammy) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964539 Title: [nouveau] 42beta: screen unlock gets stuck on primary display, secondary display is unlocked Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: [Impact] Occasionally, when the screen has been locked for a medium length of time, > 5 mins, when you press the spacebar, enter your password, the primary display freezes and the lockscreen slider does not slide up. The secondary screen is fine, and unlocks. See screenshot for what it looks like. You can click, interact with the secondary screen. On the primary screen, you can super key and launch an application, but you won't be able to interact with it. You can't see what you are doing. The way to fix is to re-lock the screen, wait a bit, and attempt to unlock. Sometimes you won't be able to unlock immediately, as it is difficult to get the monitor to power on again, it appears gnome-shell does not send the wakeup signal. gnome-shell 42~beta-1ubuntu2 from -proposed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-01-02 (68 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220101) Package: gnome-shell PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 RelatedPackageVersions: mutter-common 42~beta-1ubuntu1 Tags: wayland-session third-party-packages jammy package-from-proposed Uname: Linux 5.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961369] Re: iwlwifi: mvm: read 6E enablement flags from DSM and pass to FW
*** This bug is a duplicate of bug 1961971 *** https://bugs.launchpad.net/bugs/1961971 ** This bug has been marked a duplicate of bug 1961971 Disable iwlwifi UHB (ultra high band) channels if we don't support wifi 6e currently -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1961369 Title: iwlwifi: mvm: read 6E enablement flags from DSM and pass to FW Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961369/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964542] Re: [nvidia] One monitor remains black on startup or resume from sleep
** Changed in: mutter (Ubuntu) Status: Incomplete => New ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: Incomplete => New ** Summary changed: - [nvidia] One monitor remains black on startup or resume from sleep + [nvidia][Xorg] One monitor remains black on startup or resume from sleep ** Summary changed: - [nvidia][Xorg] One monitor remains black on startup or resume from sleep + [nvidia][Xorg] One (cloned) monitor remains black on startup or resume from sleep -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1964542 Title: [nvidia][Xorg] One (cloned) monitor remains black on startup or resume from sleep Status in mutter package in Ubuntu: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: when the pc starts up or comes out of sleep mode the primary screen remains black. To reactivate it I have to go through screen clone apply and redo join the screens and apply. Thanks Ps: have done several research and attempt, without success, on the internet including in your forums. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.103.01 Thu Jan 6 12:10:04 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 10 18:45:17 2022 DistUpgraded: 2022-02-23 17:47:37,810 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu DkmsStatus: nvidia, 470.103.01, 5.13.0-32-generic, x86_64: installed nvidia, 470.103.01, 5.13.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GM206 [GeForce GTX 960] [3842:2966] InstallationDate: Installed on 2022-02-15 (23 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUS All Series ProcEnviron: LANGUAGE=fr_CA:fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=c8e08c76-0308-495c-8c5a-83f9aa24b1a0 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2022-02-23 (15 days ago) dmi.bios.date: 07/10/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4101 dmi.board.asset.tag: Default string dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4101:bd07/10/2019:br5.11:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1964542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1964748] Re: Cirrus audio support [1028:0BB5] & [1028:0BB6]
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1964748 Title: Cirrus audio support [1028:0BB5] & [1028:0BB6] Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] These 2 IDs([1028:0BB5],[1028:0BB6]) are required to be added into cs8409 quirk to get it work [Fix] Cherry picked below commit from v5.17-rc1 2a1355f0bf41 ALSA: hda/cs8409: Add new Warlock SKUs to patch_cs8409 [Test] Verified on Dell machines which contains this Cirrus audio. [Where problems could occur] Adding 2 IDs into quirk is trivial, and should not introduce any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1964748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961119] Re: Lower the volume of expected s0i3 WARN_ON
** Changed in: hwe-next Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1961119 Title: Lower the volume of expected s0i3 WARN_ON Status in HWE Next: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: [Impact] AMD has a known BIOS bug right now that leads to the following WARN traceback during s0i3 resume (see below). This doesn't have (measurable) functional impact to the system or GPU, but it is an ugly message to have in place and makes it look like a potentially major problem. AMD is working on fixing this in BIOS, but it may not be ready by the time the first platforms launch. [Fix] Print a shorter message warning instead: "Watermarks table not configured properly by SMU". The fixed was cherry-picked from mainline kernel v5.17-rc4. [Test] This is requested by AMD, and tested and verified on the AMD CRB. [Where problems could occur] Low. This only changes the behavors of message printing There are no functional changes. --- WARN_ON messages --- [ cut here ] WARNING: CPU: 8 PID: 60399 at drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dcn31/dcn31_smu.c:123 dcn31_smu_send_msg_with_param+0xec/0x130 [amdgpu] Modules linked in: btrfs blake2b_generic xor zstd_compress raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c cpuid michael_mic hid_logitech_hidpp snd_usb_audio snd_usbmidi_lib hid_logitech_dj usbhid cdc_ether usbnet r8152 mii qrtr_mhi joydev intel_rapl_msr intel_rapl_common bnep snd_soc_dmic snd_acp6x_pdm_dma snd_soc_acp6x_mach snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine edac_mce_amd amdgpu snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi nls_iso8859_1 kvm_amd kvm snd_hda_intel qrtr snd_intel_dspcfg ns snd_intel_sdw_acpi snd_hda_codec ath11k_pci crct10dif_pclmul input_leds snd_pci_acp6x ghash_clmulni_intel ath11k snd_hda_core snd_hwdep qmi_helpers aesni_intel snd_pcm uvcvideo crypto_simd videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 iommu_v2 cryptd platform_profile btusb snd_seq_midi gpu_sched rapl mac80211 serio_raw snd_seq_midi_event videobuf2_common sparse_keymap drm_ttm_helper btrtl snd_rawmidi btbcm videodev btintel ttm efi_pstore wmi_bmof hid_multitouch mc bluetooth snd_seq drm_kms_helper snd_seq_device ecdh_generic cfg80211 ecc snd_timer cec rc_core i2c_algo_bit snd fb_sys_fops syscopyarea sysfillrect mhi sysimgblt libarc4 soundcore snd_rn_pci_acp3x snd_pci_acp3x ccp ucsi_acpi typec_ucsi amd_pmc wireless_hotkey mac_hid typec acpi_tad sch_fq_codel msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul thunderbolt nvme i2c_piix4 xhci_pci xhci_pci_renesas nvme_core iosm wmi i2c_hid_acpi video i2c_hid hid Workqueue: events_unbound async_run_entry_fn RIP: 0010:dcn31_smu_send_msg_with_param+0xec/0x130 [amdgpu] Code: 00 e8 38 60 fc ff 48 8b 3b 4c 89 ea be 9b 62 01 00 e8 c8 60 fc ff 85 c0 75 40 bf c6 a7 00 00 e8 aa da 0c c6 41 83 ec 01 75 dc <0f> 0b 48 8b 3b b9 80 84 1e 00 44 89 fa 44 89 f6 e8 af 9c fc ff 48 RSP: 0018:b76d03167bc8 EFLAGS: 00010202 RAX: 00ff RBX: 9dc54f492800 RCX: 0008 RDX: RSI: 0001629b RDI: 9dc548bc RBP: b76d03167bf8 R08: 0009 R09: 0320 R10: 0191 R11: 04451a00 R12: 00030b48 R13: c1717d90 R14: 0011 R15: 0001 FS: () GS:9dcc7e80() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 55f79ba89f68 CR3: 00052681 CR4: 00750ee0 PKRU: 5554 Call Trace: dcn31_smu_transfer_wm_table_dram_2_smu+0x23/0x30 [amdgpu] dcn31_notify_wm_ranges+0x145/0x180 [amdgpu] dcn31_init_hw+0x465/0x8e0 [amdgpu] dc_set_power_state+0x113/0x160 [amdgpu] dm_resume+0x2b5/0x610 [amdgpu] amdgpu_device_ip_resume_phase2+0x58/0xc0 [amdgpu] amdgpu_device_resume+0xd9/0x210 [amdgpu] amdgpu_pmops_resume+0x1d/0x40 [amdgpu] pci_pm_resume+0x5b/0x90 ? pci_pm_thaw+0x80/0x80 dpm_run_callback+0x52/0x160 device_resume+0xdd/0x1e0 async_resume+0x1f/0x60 async_run_entry_fn+0x33/0x120 process_one_work+0x236/0x420 worker_thread+0x34/0x410 ? process_one_work+0x420/0x420 kthread+0x12f/0x150 ? set_kthread_struct+0x40/0x40 ret_from_fork+0x22/0x30 ---[ end trace 71d329758d0428b2 ]--- [ cut here ] WARNING: CPU: 8 PID: 60399 at drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dcn31/dcn31_smu.c:105 dcn31_smu_send_msg_with_param+0x56/0x130 [amdgpu] Modules linked in: btrfs blake2b_generic xor zstd_compress raid6_pq ufs qnx4 hfsplus
[Kernel-packages] [Bug 1963568] Re: linux-firmware 20220302.gitee0667aa-0ubuntu1 failed to install/upgrade
Ubuntu 22.04 development branch @ 15/03/2022 with kernel 5.15.0-22-generic This just happened on ubuntu-desktop physical install aswell on this mornings incoming updates regarding linux-firmware stuck on ath11k apt errors: dpkg: fout bij verwerken van archief /var/cache/apt/archives/linux-firmware_2022 0314.gitcd01f857-0ubuntu1_all.deb (--unpack): kan '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new' niet openen: Bestan d of map bestaat niet (file or folder does not exist) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1963568 Title: linux-firmware 20220302.gitee0667aa-0ubuntu1 failed to install/upgrade Status in linux-firmware package in Ubuntu: Incomplete Bug description: QEMU/KVM VM ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220302.gitee0667aa-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marty 1634 F pipewire-media- marty 1635 F pulseaudio /dev/snd/seq:marty 1633 F pipewire CasperMD5CheckResult: pass Date: Thu Mar 3 18:39:26 2022 Dependencies: firmware-sof-signed 1.9-1ubuntu1 DuplicateSignature: package:linux-firmware:20220302.gitee0667aa-0ubuntu1 Setting up libreoffice-pdfimport (1:7.3.1~rc2-0ubuntu1) ... dpkg: error processing package linux-firmware (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2022-02-11 (20 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) IwConfig: lono wireless extensions. enp1s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) PackageArchitecture: all ProcFB: 0 qxldrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_70i6e6@/vmlinuz-5.15.0-18-generic root=ZFS=rpool/ROOT/ubuntu_70i6e6 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.2, python3-minimal, 3.10.1-0ubuntu1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu5 RfKill: SourcePackage: linux-firmware Title: package linux-firmware 20220302.gitee0667aa-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: ArchLinux 1.15.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-6.2 dmi.modalias: dmi:bvnSeaBIOS:bvrArchLinux1.15.0-1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-6.2:cvnQEMU:ct1:cvrpc-q35-6.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-6.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1963568/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964850] Re: Choppy trackpad/USB mouse behavior with oem-1023 or above kernel version
To resolve choppy touchpad/mouse issue, you need pull 2 additional commits below on the top of Ubuntu-oem-5.14-5.14.0-1025.27: 708978487304 drm/amdgpu/display: Only set vblank_disable_immediate when PSR is not enabled 4d22336f9039 drm/amd/display: For vblank_disable_immediate, check PSR is really used ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => Triaged ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964850 Title: Choppy trackpad/USB mouse behavior with oem-1023 or above kernel version Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: Triaged Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: Observed choppy issue for touchpad on HP Lockheed with OEM-1025 kernel, and can't smoothly drag USB mouse if connected. Rolled back to OEM-1023 kernel and observed the same issues. Can't reproduce the issue with OEM-1022 kernel. Bisect identified the problematic commits below, 021e2c1f6143 drm/amdgpu/display: set vblank_disable_immediate for DC 1a4dd5a679da drm/amd/display: check top_pipe_to_program pointer Reverting above 2 commits on the top of oem-5.14-5.14.0-1025.27, touchpad or USB mouse back to normal working behavior on HP Lockheed and we don't see choppy trackpad/mouse issue. $ git log --oneline -5 62e596025e1e (HEAD -> fm_oem-5.14-next) Revert "drm/amd/display: check top_pipe_to_program pointer" 82cab088605f Revert "drm/amdgpu/display: set vblank_disable_immediate for DC" 165041ee003c (tag: Ubuntu-oem-5.14-5.14.0-1025.27, origin/oem-5.14-next) UBUNTU: Ubuntu-oem-5.14-5.14.0-1025.27 8bdd3e2ea820 UBUNTU: [Config] Update config to match upstream stable release 43f3b8b56abe UBUNTU: debian/dkms-versions -- update from kernel-versions (main/2022.02.21) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1964850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964850] [NEW] Choppy trackpad/USB mouse behavior with oem-1023 or above kernel version
Public bug reported: Observed choppy issue for touchpad on HP Lockheed with OEM-1025 kernel, and can't smoothly drag USB mouse if connected. Rolled back to OEM-1023 kernel and observed the same issues. Can't reproduce the issue with OEM-1022 kernel. Bisect identified the problematic commits below, 021e2c1f6143 drm/amdgpu/display: set vblank_disable_immediate for DC 1a4dd5a679da drm/amd/display: check top_pipe_to_program pointer Reverting above 2 commits on the top of oem-5.14-5.14.0-1025.27, touchpad or USB mouse back to normal working behavior on HP Lockheed and we don't see choppy trackpad/mouse issue. $ git log --oneline -5 62e596025e1e (HEAD -> fm_oem-5.14-next) Revert "drm/amd/display: check top_pipe_to_program pointer" 82cab088605f Revert "drm/amdgpu/display: set vblank_disable_immediate for DC" 165041ee003c (tag: Ubuntu-oem-5.14-5.14.0-1025.27, origin/oem-5.14-next) UBUNTU: Ubuntu-oem-5.14-5.14.0-1025.27 8bdd3e2ea820 UBUNTU: [Config] Update config to match upstream stable release 43f3b8b56abe UBUNTU: debian/dkms-versions -- update from kernel-versions (main/2022.02.21) ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: High Assignee: You-Sheng Yang (vicamo) Status: Triaged ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: High Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: High Assignee: You-Sheng Yang (vicamo) Status: Triaged ** Affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Tags: amd oem-priority originate-from-1962738 ** Tags added: amd oem-priority originate-from-1962738 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964850 Title: Choppy trackpad/USB mouse behavior with oem-1023 or above kernel version Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: Triaged Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: Observed choppy issue for touchpad on HP Lockheed with OEM-1025 kernel, and can't smoothly drag USB mouse if connected. Rolled back to OEM-1023 kernel and observed the same issues. Can't reproduce the issue with OEM-1022 kernel. Bisect identified the problematic commits below, 021e2c1f6143 drm/amdgpu/display: set vblank_disable_immediate for DC 1a4dd5a679da drm/amd/display: check top_pipe_to_program pointer Reverting above 2 commits on the top of oem-5.14-5.14.0-1025.27, touchpad or USB mouse back to normal working behavior on HP Lockheed and we don't see choppy trackpad/mouse issue. $ git log --oneline -5 62e596025e1e (HEAD -> fm_oem-5.14-next) Revert "drm/amd/display: check top_pipe_to_program pointer" 82cab088605f Revert "drm/amdgpu/display: set vblank_disable_immediate for DC" 165041ee003c (tag: Ubuntu-oem-5.14-5.14.0-1025.27, origin/oem-5.14-next) UBUNTU: Ubuntu-oem-5.14-5.14.0-1025.27 8bdd3e2ea820 UBUNTU: [Config] Update config to match upstream stable release 43f3b8b56abe UBUNTU: debian/dkms-versions -- update from kernel-versions (main/2022.02.21) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1964850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961739] Re: PS/2 Keyboard wakeup from s2idle not functioning on AMD Yellow Carp platform
Committed in linux/jammy -23.
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1961739
Title:
PS/2 Keyboard wakeup from s2idle not functioning on AMD Yellow Carp
platform
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.14 source package in Focal:
Fix Released
Status in linux source package in Impish:
In Progress
Status in linux-oem-5.14 source package in Impish:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux-oem-5.14 source package in Jammy:
Invalid
Bug description:
[SRU Justification]
[Impact]
On some platforms, PS/2 keyboard cannot wake system up from s2idle.
[Fix]
Mainline commit cb1f65c1e142 ("PM: s2idle: ACPI: Fix wakeup interrupts
handling") picks up the missed wakeup interrupt.
[Test Case]
Use button press on PS/2 keyboard to wake suspended system.
[Where problems could occur]
It may still discard irqs under some very rare corner cases that are not
yet identified, but the implementation can be extended easily when
necessary.
[Other Info]
This affects 5.4+ kernels and has been proposed for linux-stable. While
this is merged in v5.17-rc4, linux-unstable will have this soon so
nomination is skipped.
== original bug report ==
With bug 1957026 and bug 1960434, suspend/resume using rtc and power
button work as expected, but PS/2 or USB keyboard still do not work
well as an wakeup source. This focus on fixes for PS/2.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1961739/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1961120] Re: SFH sensors are not working on some AMD platforms
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: hwe-next Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1961120 Title: SFH sensors are not working on some AMD platforms Status in HWE Next: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: [Impact] When amd-sfh is loaded the sensors connected do not change values at all (ALS sensor). Here is the monitor sensors output, which doesn't change. $ sudo monitor-sensor Waiting for iio-sensor-proxy to appear +++ iio-sensor-proxy appeared === No accelerometer === Has ambient light sensor (value: 0.00, unit: lux) [Fix] The SRU contains two fixes: 1. increasing sensor command timeout from from 80 to 160. 2. using first valid 15 bits only ALS max illuminance values. [Test] This is requested by AMD. This was also verified by an AMD's engineer on CRB. [Where problems could occur] Low. The patches only increase timeout value and discard an invalid bit. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961120/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964822] Re: dpkg won't install latest version published on Jammy
*** This bug is a duplicate of bug 1964814 *** https://bugs.launchpad.net/bugs/1964814 This is also occurring here on two very different machines. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1964822 Title: dpkg won't install latest version published on Jammy Status in linux-firmware package in Ubuntu: Confirmed Bug description: Hello! dpkg fails the package installation with the following message: dpkg: error processing archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack): unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new': No such file or directory No apport report written because the error message indicates an issue on the local system update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic I am reporting this problem because I don't think it is an issue with my local system. I believe it is happening because /lib/firmware/ath11k/WCN6855/hw2.1 is a symlink of the directory /lib/firmware/ath11k/WCN6855/hw2.0, and those were not created by me. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1964822/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958229] Re: UBSAN: array-index-out-of-bounds in dcn31_resources on AMD yellow carp platform
** Changed in: hwe-next
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1958229
Title:
UBSAN: array-index-out-of-bounds in dcn31_resources on AMD yellow carp
platform
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
[SRU Justification]
[Impact]
On HP Lockheed16, following UBSAN warning dumped at boot and the first
USB4 port is disabled:
UBSAN: array-index-out-of-bounds in
/drivers/gpu/drm/amd/amdgpu/../display/dc/dcn31/dcn31_resource.c:1295:22
index 6 is out of range for type 'dcn10_stream_enc_registers[5]'
This is a follow-up for bug 1953008 on Jammy, which only happens when
patches for USB4 alt mode were applied and tested on a HP platform.
[Fix]
Commit d374d3b49321 ("drm/amd/display: Fix out of bounds access on DNC31
stream encoder regs") from Linus' tree.
[Test Case]
Apply and check no more such warning, and USB alt mode should work.
[Where problems could occur]
No. This specifies the expected array size to avoid UBSAN warning.
[Other Info]
While UBSAN is only turned on by default on 5.15 kernels or newer, and
we didn't find this issue on oem-5.14, so only Jammy is nominated here.
== original bug report ==
UBSAN: array-index-out-of-bounds in
drivers/gpu/drm/amd/display/dc/dcn31/dcn31_resource.c:1295:22
This is a follow-up for bug 1953008, which only happens when patches
for USB4 alt mode were applied.
This is found on HP Lockheed16 and will disable one of the tbt port.
Source tree available in
https://git.launchpad.net/~vicamo/+git/ubuntu-
kernel/tree/drivers/gpu/drm/amd/display/dc/dcn31/dcn31_resource.c?h=bug-1953008/amdgpu-
yellow-carp-support-
usb4-altmode/jammy=243857296edd341e5054cc50732b3af3432eaaf6#n1295
1263 static struct stream_encoder *dcn31_stream_encoder_create(
1264 enum engine_id eng_id,
1265 struct dc_context *ctx)
1266 {
...
1293 dcn30_dio_stream_encoder_construct(enc1, ctx, ctx->dc_bios,
1294 eng_id, vpg, afmt,
1295 _enc_regs[eng_id],
1296 _shift, _mask);
[ 5.557065] [drm] amdgpu kernel modesetting enabled.
[ 5.562748] amdgpu: Virtual CRAT table created for CPU
[ 5.562769] amdgpu: Topology: Add CPU node
[ 5.563048] checking generic (32000 8ca000) vs hw (32000 1000)
[ 5.563053] fb0: switching to amdgpu from EFI VGA
[ 5.563274] Console: switching to colour dummy device 80x25
[ 5.563386] amdgpu :64:00.0: vgaarb: deactivate vga console
[ 5.563768] [drm] initializing kernel modesetting (YELLOW_CARP 0x1002:0x1681
0x103C:0x8990 0xD5).
[ 5.563791] amdgpu :64:00.0: amdgpu: Trusted Memory Zone (TMZ) feature
disabled as experimental (default)
[ 5.563968] [drm] register mmio base: 0xA480
[ 5.563969] [drm] register mmio size: 524288
[ 5.563976] [drm] PCIE atomic ops is not supported
[ 5.565481] [drm] add ip block number 0
[ 5.565483] [drm] add ip block number 1
[ 5.565484] [drm] add ip block number 2
[ 5.565485] [drm] add ip block number 3
[ 5.565486] [drm] add ip block number 4
[ 5.565487] [drm] add ip block number 5
[ 5.565488] [drm] add ip block number 6
[ 5.565490] [drm] add ip block number 7
[ 5.565491] [drm] add ip block number 8
[ 5.565492] [drm] add ip block number 9
[ 5.565512] amdgpu :64:00.0: amdgpu: Fetched VBIOS from VFCT
[ 5.565515] amdgpu: ATOM BIOS: 113-REMBRANDT-032
[ 5.565529] [drm] VCN(0) decode is enabled in VM mode
[ 5.565530] [drm] VCN(0) encode is enabled in VM mode
[ 5.565532] [drm] JPEG decode is enabled in VM mode
[ 5.565570] [drm] vm size is 262144 GB, 4 levels, block size is 9-bit,
fragment size is 9-bit
[ 5.565576] amdgpu :64:00.0: amdgpu: VRAM: 512M 0x00F4 -
0x00F41FFF (512M used)
[ 5.565579] amdgpu :64:00.0: amdgpu: GART: 512M 0x -
0x1FFF
[ 5.565580] amdgpu :64:00.0: amdgpu: AGP: 267419648M 0x00F8 -
0x
[ 5.565589] [drm] Detected VRAM RAM=512M, BAR=512M
[ 5.565590] [drm] RAM width 64bits DDR5
[ 5.565640] [drm] amdgpu: 512M of VRAM memory ready
[ 5.565642] [drm] amdgpu: 3072M of GTT memory ready.
[ 5.565658] [drm] GART: num cpu pages 131072, num gpu pages 131072
[ 5.566076] [drm] PCIE GART of 512M enabled (table at 0x00F4008CA000).
[ 5.567973] amdgpu :64:00.0: amdgpu: PSP runtime database doesn't exist
[ 5.573492] [drm] use_doorbell being set to: [true]
[ 5.574279] [drm] Loading DMUB firmware via PSP: version=0x040D
[ 5.574727] [drm] Found VCN firmware Version ENC: 1.14 DEC: 2 VEP: 0
Revision: 3
[ 5.574733] amdgpu :64:00.0: amdgpu: Will use PSP to load VCN firmware
[ 5.599344] [drm] reserve 0xa0 from 0xf41f40 for PSP TMR
[ 5.625250] usb 3-2.4: reset
[Kernel-packages] [Bug 1964827] Re: zfs-linux upstream at 2.1.3, jammy has 2.1.2
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: zfs-linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1964827 Title: zfs-linux upstream at 2.1.3, jammy has 2.1.2 Status in zfs-linux package in Ubuntu: Confirmed Bug description: I know Jammy is in freeze zfs upstream is now at 2.1.3, which has a lovely set of fixes for issues I have noticed (such as zfs complaining when waking for sleep, and also patches to support 5.16 better and also for the support of 5.17.) Please peruse the large number of important patches, which will make supporting this in LTS much easier: https://github.com/openzfs/zfs/pull/13063 I'm running a version of https://launchpad.net/~jonathonf/+archive/ubuntu/zfs built for 2.1.3 on Ubuntu mainline kernel 5.17-rc8 on multiple Jammy-dev systems, and it works beautifully. I have attached the debian dir I put on top of the 2.1.3 source release which I used to generate debs for this release, which I have tested on a server and client desktop x86_64 machine running Ubuntu Jammy 22.04 (as of March 14, 2022). I am having no zfs related issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1964827/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964844] Re: linux-firmware upgrade started failing
*** This bug is a duplicate of bug 1964814 *** https://bugs.launchpad.net/bugs/1964814 ** This bug has been marked a duplicate of bug 1964814 linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1964844 Title: linux-firmware upgrade started failing Status in linux-firmware package in Ubuntu: New Bug description: It was observed that linux-firmware upgrade started failing now. At the end of the apt upgrade process, the following message appeared (messages are in Portuguese): Erros foram encontrados durante o processamento de: /tmp/apt-dpkg-install-WX2tyT/55-linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) In the middle of the upgrade process, there was the following error: A descompactar linux-firmware (20220314.gitcd01f857-0ubuntu1) sobre (20220302.gitee0667aa-0ubuntu1) ... dpkg: erro ao processar o arquivo /tmp/apt-dpkg-install-WX2tyT/55-linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack): não foi possível abrir '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new': Arquivo ou diretório inexistente No apport report written because the error message indicates an issue on the local system update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic The suspect I have is that linux-firmware started requiring an executable /tmp. This computer has the following /tmp mount: tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noexec,relatime,inode64) Considering dpkg/apt are already privileged processes, I find it strange it tries to extract and execute from /tmp when it could, theoretically, do this from another, safer, directory made specifically for dpkg/apt. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220302.gitee0667aa-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario2559 F pipewire usuario2560 F wireplumber /dev/snd/pcmC0D0p: usuario2559 F...m pipewire /dev/snd/seq:usuario2559 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Mon Mar 14 20:43:31 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu2 HibernationDevice: RESUME=none InstallationDate: Installed on 2017-06-13 (1735 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-22-generic root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 i915.enable_gvt=1 nbd.nbds_max=2 nbd.max_part=127 mtrr_gran_size=128M mtrr_chunk_size=256M log_buf_len=128M zswap.enabled=1 zswap.zpool=z3fold usbhid.quirks=0x0079:0x0006:0x10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-22-generic N/A linux-backports-modules-5.15.0-22-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2019-12-22 (813 days ago) dmi.bios.date: 08/09/2018 dmi.bios.release: 1.45 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.ec.firmware.release: 1.45 dmi.modalias: dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:br1.45:efr1.45:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:skuLENOVO_MT_80UG_BU_idea_FM_Lenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1964844/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-pac
[Kernel-packages] [Bug 1964844] [NEW] linux-firmware upgrade started failing
Public bug reported: It was observed that linux-firmware upgrade started failing now. At the end of the apt upgrade process, the following message appeared (messages are in Portuguese): Erros foram encontrados durante o processamento de: /tmp/apt-dpkg-install-WX2tyT/55-linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) In the middle of the upgrade process, there was the following error: A descompactar linux-firmware (20220314.gitcd01f857-0ubuntu1) sobre (20220302.gitee0667aa-0ubuntu1) ... dpkg: erro ao processar o arquivo /tmp/apt-dpkg-install-WX2tyT/55-linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack): não foi possível abrir '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new': Arquivo ou diretório inexistente No apport report written because the error message indicates an issue on the local system update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic The suspect I have is that linux-firmware started requiring an executable /tmp. This computer has the following /tmp mount: tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noexec,relatime,inode64) Considering dpkg/apt are already privileged processes, I find it strange it tries to extract and execute from /tmp when it could, theoretically, do this from another, safer, directory made specifically for dpkg/apt. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220302.gitee0667aa-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario2559 F pipewire usuario2560 F wireplumber /dev/snd/pcmC0D0p: usuario2559 F...m pipewire /dev/snd/seq:usuario2559 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Mon Mar 14 20:43:31 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu2 HibernationDevice: RESUME=none InstallationDate: Installed on 2017-06-13 (1735 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 80UG PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-22-generic root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 i915.enable_gvt=1 nbd.nbds_max=2 nbd.max_part=127 mtrr_gran_size=128M mtrr_chunk_size=256M log_buf_len=128M zswap.enabled=1 zswap.zpool=z3fold usbhid.quirks=0x0079:0x0006:0x10 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-22-generic N/A linux-backports-modules-5.15.0-22-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2019-12-22 (813 days ago) dmi.bios.date: 08/09/2018 dmi.bios.release: 1.45 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.ec.firmware.release: 1.45 dmi.modalias: dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:br1.45:efr1.45:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:skuLENOVO_MT_80UG_BU_idea_FM_Lenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO modified.conffile..etc.cron.daily.apport: [deleted] ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1964844 Title: linux-firmware upgrade started failing Status in linux-firmware package in Ubuntu: New Bug description: It was observed that linux-firmware upgrade started failing now. At the end of the apt upgrade process, the following message appeared (messages are in Portuguese): Erros foram encontrados durante o processamento de: /tmp/apt-dpkg-install-WX2tyT/55-linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) In the middle of the upgrade process, there was the following error: A descompactar linux-firmware (20220314.gitcd01f857-0ubun
[Kernel-packages] [Bug 1964814] Re: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1
What I did to workaround the problem on my system is: rm /lib/firmware/ath11k/WCN6855/hw2.1 cp -R lib/firmware/ath11k/WCN6855/hw2.0 /lib/firmware/ath11k/WCN6855/hw2.1 And then I tried to upgrade the packages again, which I did successfully. I don't actually need those drivers, but I think that would be an okay workaround for those who need it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1964814 Title: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1 Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Jammy: Confirmed Bug description: linux-firmware fails to upgrade with: unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg- new': No such file or directory $ sudo apt dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: linux-firmware 1 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade. Need to get 0 B/238 MB of archives. After this operation, 24.9 MB of additional disk space will be used. Do you want to continue? [Y/n] y (Reading database ... 272091 files and directories currently installed.) Preparing to unpack .../linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb ... Unpacking linux-firmware (20220314.gitcd01f857-0ubuntu1) over (20220302.gitee0667aa-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack): unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new': No such file or directory No apport report written because the error message indicates an issue on the local system update-initramfs: Generating /boot/initrd.img-5.15.0-23-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. Errors were encountered while processing: /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1964814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964814] Re: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1
** Changed in: linux-firmware (Ubuntu Jammy) Milestone: None => ubuntu-22.04-beta ** Changed in: linux-firmware (Ubuntu Jammy) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1964814 Title: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1 Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Jammy: Confirmed Bug description: linux-firmware fails to upgrade with: unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg- new': No such file or directory $ sudo apt dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: linux-firmware 1 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade. Need to get 0 B/238 MB of archives. After this operation, 24.9 MB of additional disk space will be used. Do you want to continue? [Y/n] y (Reading database ... 272091 files and directories currently installed.) Preparing to unpack .../linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb ... Unpacking linux-firmware (20220314.gitcd01f857-0ubuntu1) over (20220302.gitee0667aa-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack): unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new': No such file or directory No apport report written because the error message indicates an issue on the local system update-initramfs: Generating /boot/initrd.img-5.15.0-23-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. Errors were encountered while processing: /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1964814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964814] Re: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1
A potential (temporary) workaround is to remove the offending symlinks from package file as follows: mkdir linux-firmware cd linux-firmware cp /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb ./ ar xf linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb zstd -d data.tar.zst tar vf data.tar --delete ./lib/firmware/ath11k/WCN6855/hw2.1/ zstd -f data.tar ar rcs linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb debian-binary control.tar.zst data.tar.zst sudo dpkg -i linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb One can then create the hw2.1 symlinks manually. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1964814 Title: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1 Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Jammy: Confirmed Bug description: linux-firmware fails to upgrade with: unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg- new': No such file or directory $ sudo apt dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: linux-firmware 1 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade. Need to get 0 B/238 MB of archives. After this operation, 24.9 MB of additional disk space will be used. Do you want to continue? [Y/n] y (Reading database ... 272091 files and directories currently installed.) Preparing to unpack .../linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb ... Unpacking linux-firmware (20220314.gitcd01f857-0ubuntu1) over (20220302.gitee0667aa-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack): unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new': No such file or directory No apport report written because the error message indicates an issue on the local system update-initramfs: Generating /boot/initrd.img-5.15.0-23-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. Errors were encountered while processing: /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1964814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962569] Re: jammy/linux-oem-5.17: 5.17.0-1001.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1962569 Title: jammy/linux-oem-5.17: 5.17.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow boot-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrg series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-lrs 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: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow sru-review series: Fix Released Status in linux-oem-5.17 package in Ubuntu: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true built: route-entry: 2 delta: promote-to-proposed: - signed - lrs - lrm - main - meta - lrg sru-review: - main - lrg - meta - lrm - signed - lrs kernel-stable-master-bug: 1963880 packages: lrg: linux-restricted-generate-oem-5.17 lrm: linux-restricted-modules-oem-5.17 lrs: linux-restricted-signatures-oem-5.17 main: linux-oem-5.17 meta: linux-meta-oem-5.17 signed: linux-signed-oem-5.17 phase: Testing phase-changed: Monday, 14. March 2022 22:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: 'Stalled -- unable to process task: results not valid, seeds missing' regression-testing: Ongoing -s testing in progress synthetic: :promote-to-as-proposed: Fix Released variant: debs versions: lrm: 5.17.0-1001.1+2 main: 5.17.0-1001.1 meta: 5.17.0.1001.1+1 signed: 5.17.0-1001.1 versions-clamp: self: 5.17.0-1001.1 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1962569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964836] 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/1964836 Title: package linux-libc-dev 5.13.0-30.33 failed to install/upgrade: »/usr/share/doc/linux-libc-dev/copyright.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig Status in linux package in Ubuntu: Confirmed Bug description: happened while update ProblemType: Package DistroRelease: Ubuntu 21.10 Package: linux-libc-dev 5.13.0-30.33 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tmk4900 F pulseaudio /dev/snd/controlC0: tmk4900 F pulseaudio CasperMD5CheckResult: unknown Date: Mon Mar 14 23:15:42 2022 Dependencies: ErrorMessage: »/usr/share/doc/linux-libc-dev/copyright.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig HibernationDevice: RESUME=UUID=2b4f4686-beea-42f6-bda8-1cc70f6f2f6d InstallationDate: Installed on 2019-09-27 (899 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Latitude E5450 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.04-1ubuntu47 SourcePackage: linux Title: package linux-libc-dev 5.13.0-30.33 failed to install/upgrade: »/usr/share/doc/linux-libc-dev/copyright.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 65.23 dmi.bios.vendor: Dell Inc. dmi.bios.version: A23 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA23:bd11/25/2019:br65.23:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr:sku062B: dmi.product.name: Latitude E5450 dmi.product.sku: 062B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1963615] Re: Add proper runtime PM support to Realtek PCIe cardreader
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1028.31 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1963615 Title: Add proper runtime PM support to Realtek PCIe cardreader Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] New generations of Realtek PCIe card reader cannot detect card insertion when the device is in PCI D3. [Fix] Rework the runtime PM flow and add chip specific support. [Test] With the series applied, the device can detect card insertion when it's in PCI D3. [Where problems could occur] System wide power management with less usage like hibernation, kexec reboot, etc. are not tested extensively. So these cases may be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1963615/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962569] Re: jammy/linux-oem-5.17: 5.17.0-1001.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => 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 built: route-entry: 2 delta: promote-to-proposed: - signed - lrs - lrm - main - meta - lrg sru-review: - main - lrg - meta - lrm - signed - lrs kernel-stable-master-bug: 1963880 packages: lrg: linux-restricted-generate-oem-5.17 lrm: linux-restricted-modules-oem-5.17 lrs: linux-restricted-signatures-oem-5.17 main: linux-oem-5.17 meta: linux-meta-oem-5.17 signed: linux-signed-oem-5.17 - phase: Promote to Proposed - phase-changed: Monday, 14. March 2022 10:40 UTC + phase: Testing + phase-changed: Monday, 14. March 2022 22:16 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: automated-testing: 'Stalled -- unable to process task: results not valid, seeds missing' - promote-to-proposed: Stalled -- copy FAILED regression-testing: Ongoing -s testing in progress synthetic: :promote-to-as-proposed: Fix Released variant: debs versions: lrm: 5.17.0-1001.1+2 main: 5.17.0-1001.1 meta: 5.17.0.1001.1+1 signed: 5.17.0-1001.1 versions-clamp: self: 5.17.0-1001.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1962569 Title: jammy/linux-oem-5.17: 5.17.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow boot-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrg series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-lrs 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: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Triaged Status in Kernel SRU Workflow sru-review series: Fix Released Status in linux-oem-5.17 package in Ubuntu: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true built: route-entry: 2 delta: promote-to-proposed: - signed - lrs - lrm - main - meta - lrg sru-review: - main - lrg - meta - lrm - signed - lrs kernel-stable-master-bug: 1963880 packages: lrg: linux-restricted-generate-oem-5.17 lrm: linux-restricted-modules-oem-5.17 lrs: linux-restricted-signatures-oem-5.17 main: linux-oem-5.17 meta: linux-meta-oem-5.17 signed: linux-signed-oem-5.17 phase: Testing phase-changed: Monday, 14. March 2022 22:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: 'Stalled -- unable to process task: results not valid, seeds missing' regression-testing: Ongoing -s testing in progress synthetic: :promote-to-as-proposed: Fix Released variant: debs versions: lrm: 5.17.0-1001.1+2 main: 5.17.0-1001.1 meta: 5.17.0.1001.1+1 signed: 5.17.0-1001.1 versions-clamp: self: 5.17.0-1001.1 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1962569/+subscriptions -- Mailing list: https://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 1964542] Re: [nvidia] One monitor remains black on startup or resume from sleep
Thank you very much for your help. It is the LG on Displayport or Hdmi that stays black. I have noticed that when in a dual monitor there is a VGA port connected it is always the VGA port that is recognized in both Linux and Window; I think that this is the characteristic of the X86 architecture. I will try to install Wayland. Thanks Le 2022-03-14 à 01 h 47, Daniel van Vugt a écrit : > Is it the IBM or the LG monitor that remains black? > > I can't see any hints of a problem in the log. It sounds like maybe > GNOME can't uniquely identify one of the monitors and so can't remember > its preferred setting. > > ** Also affects: mutter (Ubuntu) > Importance: Undecided > Status: New > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1964542 Title: [nvidia] One monitor remains black on startup or resume from sleep Status in mutter package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Bug description: when the pc starts up or comes out of sleep mode the primary screen remains black. To reactivate it I have to go through screen clone apply and redo join the screens and apply. Thanks Ps: have done several research and attempt, without success, on the internet including in your forums. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.103.01 Thu Jan 6 12:10:04 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 10 18:45:17 2022 DistUpgraded: 2022-02-23 17:47:37,810 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu DkmsStatus: nvidia, 470.103.01, 5.13.0-32-generic, x86_64: installed nvidia, 470.103.01, 5.13.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GM206 [GeForce GTX 960] [3842:2966] InstallationDate: Installed on 2022-02-15 (23 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUS All Series ProcEnviron: LANGUAGE=fr_CA:fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=c8e08c76-0308-495c-8c5a-83f9aa24b1a0 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2022-02-23 (15 days ago) dmi.bios.date: 07/10/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4101 dmi.board.asset.tag: Default string dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4101:bd07/10/2019:br5.11:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1955882] Re: MT7921[14c3:7961] ASPM is disabled and it affects power consumption
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1028.31 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1955882 Title: MT7921[14c3:7961] ASPM is disabled and it affects power consumption Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] MT7921 is disabled by default, and it affects the power consumption. [Fix] MTK pointed out we need this commit which is included in v5.16-rc1 bf3747ae2e25 mt76: mt7921: enable aspm by default After ASPM is enabled, we found the card disappears after reboot sometimes, so MTK provides another commit for it https://patchwork.kernel.org/project/linux-mediatek/patch/70e27cbc652cbdb78277b9c691a3a5ba02653afb.1641540175.git.obj...@gmail.com/ [Test] Verified on Dell machines with MT7921 wifi card. [Where problems could occur] Enable device ASPM is always risky, we've done our best to test these patches, and no regression could be found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1955882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964748] Re: Cirrus audio support [1028:0BB5] & [1028:0BB6]
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1028.31 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1964748 Title: Cirrus audio support [1028:0BB5] & [1028:0BB6] Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] These 2 IDs([1028:0BB5],[1028:0BB6]) are required to be added into cs8409 quirk to get it work [Fix] Cherry picked below commit from v5.17-rc1 2a1355f0bf41 ALSA: hda/cs8409: Add new Warlock SKUs to patch_cs8409 [Test] Verified on Dell machines which contains this Cirrus audio. [Where problems could occur] Adding 2 IDs into quirk is trivial, and should not introduce any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1964748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964836] [NEW] package linux-libc-dev 5.13.0-30.33 failed to install/upgrade: »/usr/share/doc/linux-libc-dev/copyright.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zuläss
Public bug reported: happened while update ProblemType: Package DistroRelease: Ubuntu 21.10 Package: linux-libc-dev 5.13.0-30.33 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tmk4900 F pulseaudio /dev/snd/controlC0: tmk4900 F pulseaudio CasperMD5CheckResult: unknown Date: Mon Mar 14 23:15:42 2022 Dependencies: ErrorMessage: »/usr/share/doc/linux-libc-dev/copyright.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig HibernationDevice: RESUME=UUID=2b4f4686-beea-42f6-bda8-1cc70f6f2f6d InstallationDate: Installed on 2019-09-27 (899 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Latitude E5450 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.04-1ubuntu47 SourcePackage: linux Title: package linux-libc-dev 5.13.0-30.33 failed to install/upgrade: »/usr/share/doc/linux-libc-dev/copyright.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 65.23 dmi.bios.vendor: Dell Inc. dmi.bios.version: A23 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA23:bd11/25/2019:br65.23:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr:sku062B: dmi.product.name: Latitude E5450 dmi.product.sku: 062B dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964836 Title: package linux-libc-dev 5.13.0-30.33 failed to install/upgrade: »/usr/share/doc/linux-libc-dev/copyright.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig Status in linux package in Ubuntu: New Bug description: happened while update ProblemType: Package DistroRelease: Ubuntu 21.10 Package: linux-libc-dev 5.13.0-30.33 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tmk4900 F pulseaudio /dev/snd/controlC0: tmk4900 F pulseaudio CasperMD5CheckResult: unknown Date: Mon Mar 14 23:15:42 2022 Dependencies: ErrorMessage: »/usr/share/doc/linux-libc-dev/copyright.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig HibernationDevice: RESUME=UUID=2b4f4686-beea-42f6-bda8-1cc70f6f2f6d InstallationDate: Installed on 2019-09-27 (899 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Latitude E5450 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.04-1ubuntu47 SourcePackage: linux Title: package linux-libc-dev 5.13.0-30.33 failed to install/upgrade: »/usr/share/doc/linux-libc-dev/copyright.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 65.23 dmi.bios.vendor: Dell Inc. dmi.bios.version: A23 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA23:bd11/25/2019:br65.23:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr:sku062B: dmi.product.name: Latitude E5450 dmi.product.sku: 062B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More
[Kernel-packages] [Bug 1962569] Re: jammy/linux-oem-5.17: 5.17.0-1001.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1962569 Title: jammy/linux-oem-5.17: 5.17.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow boot-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrg series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-lrs 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: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Triaged Status in Kernel SRU Workflow sru-review series: Fix Released Status in linux-oem-5.17 package in Ubuntu: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true built: route-entry: 2 delta: promote-to-proposed: - signed - lrs - lrm - main - meta - lrg sru-review: - main - lrg - meta - lrm - signed - lrs kernel-stable-master-bug: 1963880 packages: lrg: linux-restricted-generate-oem-5.17 lrm: linux-restricted-modules-oem-5.17 lrs: linux-restricted-signatures-oem-5.17 main: linux-oem-5.17 meta: linux-meta-oem-5.17 signed: linux-signed-oem-5.17 phase: Testing phase-changed: Monday, 14. March 2022 22:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: 'Stalled -- unable to process task: results not valid, seeds missing' regression-testing: Ongoing -s testing in progress synthetic: :promote-to-as-proposed: Fix Released variant: debs versions: lrm: 5.17.0-1001.1+2 main: 5.17.0-1001.1 meta: 5.17.0.1001.1+1 signed: 5.17.0-1001.1 versions-clamp: self: 5.17.0-1001.1 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1962569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964825] Re: linux-firmware can't be upgraded in jammy breaking autopkgtests
*** This bug is a duplicate of bug 1964814 *** https://bugs.launchpad.net/bugs/1964814 ** This bug has been marked a duplicate of bug 1964814 linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1964825 Title: linux-firmware can't be upgraded in jammy breaking autopkgtests Status in linux-firmware package in Ubuntu: Confirmed Bug description: steps to reproduce: jammy chroot: dpkg -i linux-firmware_20220302.gitee0667aa-0ubuntu1_all.deb dpkg -i linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb dpkg: error processing archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack): unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new': No such file or directory example of failing autopkgtests: autopkgtest for pystemd/unknown: arm64: Regression ♻ autopkgtest for samba/unknown: arm64: Regression ♻ autopkgtest for shibboleth-sp/unknown: arm64: Regression ♻ autopkgtest for snapd/unknown: arm64: Regression ♻ autopkgtest for spice-vdagent/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for squid/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for sssd/unknown: arm64: Regression ♻ autopkgtest for strongswan/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for stunnel4/unknown: arm64: Regression ♻ autopkgtest for swupdate/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for systemd/unknown: arm64: Regression ♻ autopkgtest for systemd-bootchart/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for tang/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for tgt/unknown: arm64: Regression ♻ autopkgtest for tinyssh/20220311-1: amd64: Regression ♻ , armhf: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻ autopkgtest for tinyssh/unknown: arm64: Regression ♻ autopkgtest for tpm2-abrmd/unknown: arm64: Regression ♻ autopkgtest for tpm2-pkcs11/unknown: arm64: Regression ♻ autopkgtest for ubuntu-drivers-common/1:0.9.5.1: amd64: Pass, ppc64el: Pass, s390x: Not a regression autopkgtest for ubuntu-drivers-common/unknown: arm64: Regression ♻ autopkgtest for udisks2/unknown: arm64: Regression ♻ autopkgtest for umockdev/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for upower/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for usbauth/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for util-linux/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for vlc/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for vte2.91/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for webhook/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for wireshark/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for wlroots/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for yder/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for zfs-linux/unknown: arm64: Regression ♻ I'm attaching the full strace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1964825/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964827] [NEW] zfs-linux upstream at 2.1.3, jammy has 2.1.2
Public bug reported: I know Jammy is in freeze zfs upstream is now at 2.1.3, which has a lovely set of fixes for issues I have noticed (such as zfs complaining when waking for sleep, and also patches to support 5.16 better and also for the support of 5.17.) Please peruse the large number of important patches, which will make supporting this in LTS much easier: https://github.com/openzfs/zfs/pull/13063 I'm running a version of https://launchpad.net/~jonathonf/+archive/ubuntu/zfs built for 2.1.3 on Ubuntu mainline kernel 5.17-rc8 on multiple Jammy-dev systems, and it works beautifully. I have attached the debian dir I put on top of the 2.1.3 source release which I used to generate debs for this release, which I have tested on a server and client desktop x86_64 machine running Ubuntu Jammy 22.04 (as of March 14, 2022). I am having no zfs related issues. ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "debian dir with relevant patches to make 2.1.3 work with ubuntu jammy" https://bugs.launchpad.net/bugs/1964827/+attachment/5568775/+files/zfs-linux_2.1.3ubuntu1.debian.tar.xz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1964827 Title: zfs-linux upstream at 2.1.3, jammy has 2.1.2 Status in zfs-linux package in Ubuntu: New Bug description: I know Jammy is in freeze zfs upstream is now at 2.1.3, which has a lovely set of fixes for issues I have noticed (such as zfs complaining when waking for sleep, and also patches to support 5.16 better and also for the support of 5.17.) Please peruse the large number of important patches, which will make supporting this in LTS much easier: https://github.com/openzfs/zfs/pull/13063 I'm running a version of https://launchpad.net/~jonathonf/+archive/ubuntu/zfs built for 2.1.3 on Ubuntu mainline kernel 5.17-rc8 on multiple Jammy-dev systems, and it works beautifully. I have attached the debian dir I put on top of the 2.1.3 source release which I used to generate debs for this release, which I have tested on a server and client desktop x86_64 machine running Ubuntu Jammy 22.04 (as of March 14, 2022). I am having no zfs related issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1964827/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964825] [NEW] linux-firmware can't be upgraded in jammy breaking autopkgtests
Public bug reported: steps to reproduce: jammy chroot: dpkg -i linux-firmware_20220302.gitee0667aa-0ubuntu1_all.deb dpkg -i linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb dpkg: error processing archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack): unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new': No such file or directory example of failing autopkgtests: autopkgtest for pystemd/unknown: arm64: Regression ♻ autopkgtest for samba/unknown: arm64: Regression ♻ autopkgtest for shibboleth-sp/unknown: arm64: Regression ♻ autopkgtest for snapd/unknown: arm64: Regression ♻ autopkgtest for spice-vdagent/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for squid/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for sssd/unknown: arm64: Regression ♻ autopkgtest for strongswan/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for stunnel4/unknown: arm64: Regression ♻ autopkgtest for swupdate/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for systemd/unknown: arm64: Regression ♻ autopkgtest for systemd-bootchart/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for tang/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for tgt/unknown: arm64: Regression ♻ autopkgtest for tinyssh/20220311-1: amd64: Regression ♻ , armhf: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻ autopkgtest for tinyssh/unknown: arm64: Regression ♻ autopkgtest for tpm2-abrmd/unknown: arm64: Regression ♻ autopkgtest for tpm2-pkcs11/unknown: arm64: Regression ♻ autopkgtest for ubuntu-drivers-common/1:0.9.5.1: amd64: Pass, ppc64el: Pass, s390x: Not a regression autopkgtest for ubuntu-drivers-common/unknown: arm64: Regression ♻ autopkgtest for udisks2/unknown: arm64: Regression ♻ autopkgtest for umockdev/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for upower/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for usbauth/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for util-linux/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for vlc/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for vte2.91/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for webhook/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for wireshark/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for wlroots/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for yder/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for zfs-linux/unknown: arm64: Regression ♻ I'm attaching the full strace ** Affects: linux-firmware (Ubuntu) Importance: Critical Assignee: Julian Andres Klode (juliank) Status: Confirmed ** Attachment added: "linux-firmware.tar.gz" https://bugs.launchpad.net/bugs/1964825/+attachment/5568774/+files/linux-firmware.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1964825 Title: linux-firmware can't be upgraded in jammy breaking autopkgtests Status in linux-firmware package in Ubuntu: Confirmed Bug description: steps to reproduce: jammy chroot: dpkg -i linux-firmware_20220302.gitee0667aa-0ubuntu1_all.deb dpkg -i linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb dpkg: error processing archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack): unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new': No such file or directory example of failing autopkgtests: autopkgtest for pystemd/unknown: arm64: Regression ♻ autopkgtest for samba/unknown: arm64: Regression ♻ autopkgtest for shibboleth-sp/unknown: arm64: Regression ♻ autopkgtest for snapd/unknown: arm64: Regression ♻ autopkgtest for spice-vdagent/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for squid/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for sssd/unknown: arm64: Regression ♻ autopkgtest for strongswan/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for stunnel4/unknown: arm64: Regression ♻ autopkgtest for swupdate/unknown: arm64: Reference test in progress, but real test failed already ♻ autopkgtest for systemd/unknown: arm64: Regression ♻ autopkgtest for systemd-bootchart/unknown: arm64: Reference test in progress, but real test failed
[Kernel-packages] [Bug 1964822] Re: dpkg won't install latest version published on Jammy
*** This bug is a duplicate of bug 1964814 *** https://bugs.launchpad.net/bugs/1964814 I am also hitting this, more specifically thile unpacking linux-firmware (20220314.gitcd01f857-0ubuntu1) over (20220302.gitee0667aa-0ubuntu1). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1964822 Title: dpkg won't install latest version published on Jammy Status in linux-firmware package in Ubuntu: Confirmed Bug description: Hello! dpkg fails the package installation with the following message: dpkg: error processing archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack): unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new': No such file or directory No apport report written because the error message indicates an issue on the local system update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic I am reporting this problem because I don't think it is an issue with my local system. I believe it is happening because /lib/firmware/ath11k/WCN6855/hw2.1 is a symlink of the directory /lib/firmware/ath11k/WCN6855/hw2.0, and those were not created by me. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1964822/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964822] Re: dpkg won't install latest version published on Jammy
*** This bug is a duplicate of bug 1964814 *** https://bugs.launchpad.net/bugs/1964814 ** This bug has been marked a duplicate of bug 1964814 linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1964822 Title: dpkg won't install latest version published on Jammy Status in linux-firmware package in Ubuntu: Confirmed Bug description: Hello! dpkg fails the package installation with the following message: dpkg: error processing archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack): unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new': No such file or directory No apport report written because the error message indicates an issue on the local system update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic I am reporting this problem because I don't think it is an issue with my local system. I believe it is happening because /lib/firmware/ath11k/WCN6855/hw2.1 is a symlink of the directory /lib/firmware/ath11k/WCN6855/hw2.0, and those were not created by me. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1964822/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964822] Re: dpkg won't install latest version published on Jammy
*** This bug is a duplicate of bug 1964814 *** https://bugs.launchpad.net/bugs/1964814 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1964822 Title: dpkg won't install latest version published on Jammy Status in linux-firmware package in Ubuntu: Confirmed Bug description: Hello! dpkg fails the package installation with the following message: dpkg: error processing archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack): unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new': No such file or directory No apport report written because the error message indicates an issue on the local system update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic I am reporting this problem because I don't think it is an issue with my local system. I believe it is happening because /lib/firmware/ath11k/WCN6855/hw2.1 is a symlink of the directory /lib/firmware/ath11k/WCN6855/hw2.0, and those were not created by me. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1964822/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964814] Re: dpkg error
** Description changed: - dpkg: błąd przetwarzania archiwum linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--install): - nie można otworzyć "/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new": Nie ma takiego pliku ani katalogu + linux-firmware fails to upgrade with: - Kubuntu 22.04 + $ sudo apt dist-upgrade + Reading package lists... Done + Building dependency tree... Done + Reading state information... Done + Calculating upgrade... Done + The following packages will be upgraded: + linux-firmware + 1 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade. + Need to get 0 B/238 MB of archives. + After this operation, 24.9 MB of additional disk space will be used. + Do you want to continue? [Y/n] y + (Reading database ... 272091 files and directories currently installed.) + Preparing to unpack .../linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb ... + Unpacking linux-firmware (20220314.gitcd01f857-0ubuntu1) over (20220302.gitee0667aa-0ubuntu1) ... + dpkg: error processing archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack): + unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new': No such file or directory + No apport report written because the error message indicates an issue on the local system + update-initramfs: Generating /boot/initrd.img-5.15.0-23-generic + I: The initramfs will attempt to resume from /dev/dm-2 + I: (/dev/mapper/vgubuntu-swap_1) + I: Set the RESUME variable to override this. + update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic + I: The initramfs will attempt to resume from /dev/dm-2 + I: (/dev/mapper/vgubuntu-swap_1) + I: Set the RESUME variable to override this. + Errors were encountered while processing: + /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb + E: Sub-process /usr/bin/dpkg returned an error code (1) ** Summary changed: - dpkg error + linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1 ** Description changed: linux-firmware fails to upgrade with: + + unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new': + No such file or directory $ sudo apt dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: - linux-firmware + linux-firmware 1 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade. Need to get 0 B/238 MB of archives. After this operation, 24.9 MB of additional disk space will be used. Do you want to continue? [Y/n] y (Reading database ... 272091 files and directories currently installed.) Preparing to unpack .../linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb ... Unpacking linux-firmware (20220314.gitcd01f857-0ubuntu1) over (20220302.gitee0667aa-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack): - unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new': No such file or directory + unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new': No such file or directory No apport report written because the error message indicates an issue on the local system - update-initramfs: Generating /boot/initrd.img-5.15.0-23-generic + update-initramfs: Generating /boot/initrd.img-5.15.0-23-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. Errors were encountered while processing: - /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb + /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Changed in: linux-firmware (Ubuntu Jammy) Assignee: (unassigned) => Juerg Haefliger (juergh) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1964814 Title: linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1 Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Jammy: Confirmed Bug description: linux-firmware fails to upgrade with: unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg- new': No such file or directory $ sudo apt
[Kernel-packages] [Bug 1964822] [NEW] dpkg won't install latest version published on Jammy
*** This bug is a duplicate of bug 1964814 *** https://bugs.launchpad.net/bugs/1964814 Public bug reported: Hello! dpkg fails the package installation with the following message: dpkg: error processing archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack): unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new': No such file or directory No apport report written because the error message indicates an issue on the local system update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic I am reporting this problem because I don't think it is an issue with my local system. I believe it is happening because /lib/firmware/ath11k/WCN6855/hw2.1 is a symlink of the directory /lib/firmware/ath11k/WCN6855/hw2.0, and those were not created by me. Thank you. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1964822 Title: dpkg won't install latest version published on Jammy Status in linux-firmware package in Ubuntu: Confirmed Bug description: Hello! dpkg fails the package installation with the following message: dpkg: error processing archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack): unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new': No such file or directory No apport report written because the error message indicates an issue on the local system update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic I am reporting this problem because I don't think it is an issue with my local system. I believe it is happening because /lib/firmware/ath11k/WCN6855/hw2.1 is a symlink of the directory /lib/firmware/ath11k/WCN6855/hw2.0, and those were not created by me. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1964822/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964814] Re: dpkg error
Unable to upgrade package: 20220302.gitee0667aa-0ubuntu1 => 20220314.gitcd01f857-0ubuntu1 ** Changed in: linux-firmware (Ubuntu) Status: New => Confirmed ** Tags added: jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1964814 Title: dpkg error Status in linux-firmware package in Ubuntu: Confirmed Bug description: dpkg: błąd przetwarzania archiwum linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--install): nie można otworzyć "/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new": Nie ma takiego pliku ani katalogu Kubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1964814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964814] [NEW] dpkg error
Public bug reported: dpkg: błąd przetwarzania archiwum linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--install): nie można otworzyć "/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new": Nie ma takiego pliku ani katalogu Kubuntu 22.04 ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1964814 Title: dpkg error Status in linux-firmware package in Ubuntu: New Bug description: dpkg: błąd przetwarzania archiwum linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--install): nie można otworzyć "/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new": Nie ma takiego pliku ani katalogu Kubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1964814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818811] Re: The swapfile on the Btrfs file system is not activated
What do you actually mean by "xubuntu-22.04-core-amd64.iso"? Is it official daily image? ** Tags added: jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818811 Title: The swapfile on the Btrfs file system is not activated Status in Ubuntu MATE: New Status in linux package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Confirmed Bug description: From 5.0 kernel is implemented support for the swapfile on Btrfs (https://patchwork.kernel.org/cover/10584515/), today arrived on the repositories of Ubuntu 19.04 proposed kernel 5.0, but the swapfile is not activated. Log: mar 06 11:17:55 notebook-Lenovo-V110 kernel: BTRFS warning (device sda1): swapfile must not be copy-on-write mar 06 11:17:55 notebook-Lenovo-V110 swapon[517]: swapon: /swapfile: swapon failed: Argomento non valido mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: Activating swap /swapfile... mar 06 11:17:57 notebook-Lenovo-V110 swapon[916]: swapon: /swapfile: swapon failed: Argomento non valido mar 06 11:17:57 notebook-Lenovo-V110 kernel: BTRFS warning (device sda1): swapfile must not be copy-on-write mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: swapfile.swap: Swap process exited, code=exited, status=255/EXCEPTION mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: swapfile.swap: Failed with result 'exit-code'. mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: Failed to activate swap /swapfile. mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: Activating swap /swapfile... mar 06 11:17:57 notebook-Lenovo-V110 kernel: BTRFS warning (device sda1): swapfile must not be copy-on-write mar 06 11:17:57 notebook-Lenovo-V110 swapon[1006]: swapon: /swapfile: swapon failed: Argomento non valido mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: swapfile.swap: Swap process exited, code=exited, status=255/EXCEPTION mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: swapfile.swap: Failed with result 'exit-code'. mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: Failed to activate swap /swapfile. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-generic 5.0.0.7.8 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: emanu 1744 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 11:19:52 2019 InstallationDate: Installed on 2019-01-30 (34 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 13d3:5745 IMC Networks Bus 001 Device 002: ID 10c4:8105 Cygnal Integrated Products, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80TL ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-7-generic root=UUID=91fdf6c0-1b5d-4bb5-9aa4-aeb946236b8a ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.177 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 1KCN46WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V110-15ISK dmi.modalias: dmi:bvnLENOVO:bvr1KCN46WW:bd10/29/2018:svnLENOVO:pn80TL:pvrLenovoV110-15ISK:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV110-15ISK: dmi.product.family: V110-15ISK dmi.product.name: 80TL dmi.product.sku: LENOVO_MT_80TL_BU_idea_FM_V110-15ISK dmi.product.version: Lenovo V110-15ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1818811/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964796] Re: Fix unmatched ASMedia ASM2824 PCIe link training
https://lists.ubuntu.com/archives/kernel-team/2022-March/128639.html ** Changed in: linux-riscv (Ubuntu) Milestone: None => ubuntu-22.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1964796 Title: Fix unmatched ASMedia ASM2824 PCIe link training Status in linux-riscv package in Ubuntu: New Bug description: https://lore.kernel.org/all/alpine.deb.2.21.2202010240190.58...@angie.orcam.me.uk/raw It has been discovered that Unmatched board ships ASMedia ASM2824 PCIe which frequently fails to complete link training and negotiate stable and fast speeds. To ensure PCIe devices on Unmatched board can operate with stable and predictable link speeds cherry-pick upstream submitted patch that resolves the issue. It is currently applied as a SAUCE patch, whilst the upstream inclusion review is ongoing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1964796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959532] Re: [22.04 FEAT] Transparent PCI device recovery
** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959532 Title: [22.04 FEAT] Transparent PCI device recovery Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: A Linux on Z admin can make use of PCI-based devices in case of errors without the need to perform manual recovery. Details: Use cooperative recovery strategies that allow drivers to recover from error scenarios without complete tear-down + re-init. See approach documented for Linux on Power in Linux/Documentation/PCI/pci-error-recovery.rst. Business value: Improved reliability, reduced down-times. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964796] [NEW] Fix unmatched ASMedia ASM2824 PCIe link training
Public bug reported: https://lore.kernel.org/all/alpine.deb.2.21.2202010240190.58...@angie.orcam.me.uk/raw It has been discovered that Unmatched board ships ASMedia ASM2824 PCIe which frequently fails to complete link training and negotiate stable and fast speeds. To ensure PCIe devices on Unmatched board can operate with stable and predictable link speeds cherry-pick upstream submitted patch that resolves the issue. It is currently applied as a SAUCE patch, whilst the upstream inclusion review is ongoing. ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1964796 Title: Fix unmatched ASMedia ASM2824 PCIe link training Status in linux-riscv package in Ubuntu: New Bug description: https://lore.kernel.org/all/alpine.deb.2.21.2202010240190.58...@angie.orcam.me.uk/raw It has been discovered that Unmatched board ships ASMedia ASM2824 PCIe which frequently fails to complete link training and negotiate stable and fast speeds. To ensure PCIe devices on Unmatched board can operate with stable and predictable link speeds cherry-pick upstream submitted patch that resolves the issue. It is currently applied as a SAUCE patch, whilst the upstream inclusion review is ongoing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1964796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962299] Re: Add missing firmware for HWE 5.15 kernel
** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1962299 Title: Add missing firmware for HWE 5.15 kernel Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Fix Committed Bug description: [Impact] Firmware files required by the HWE kernel 5.15 which are present in Jammy but missing in Focal: amd/amd_sev_fam17h_model3xh.sbin amd/amd_sev_fam19h_model0xh.sbin amdgpu/aldebaran_mec.bin amdgpu/aldebaran_mec2.bin amdgpu/aldebaran_rlc.bin amdgpu/aldebaran_sdma.bin amdgpu/aldebaran_smc.bin amdgpu/aldebaran_sos.bin amdgpu/aldebaran_ta.bin amdgpu/aldebaran_vcn.bin amdgpu/arcturus_asd.bin amdgpu/arcturus_gpu_info.bin amdgpu/arcturus_mec.bin amdgpu/arcturus_rlc.bin amdgpu/arcturus_sdma.bin amdgpu/arcturus_smc.bin amdgpu/arcturus_sos.bin amdgpu/arcturus_ta.bin amdgpu/arcturus_vcn.bin amdgpu/cyan_skillfish2_ce.bin amdgpu/cyan_skillfish2_me.bin amdgpu/cyan_skillfish2_mec.bin amdgpu/cyan_skillfish2_mec2.bin amdgpu/cyan_skillfish2_pfp.bin amdgpu/cyan_skillfish2_rlc.bin amdgpu/cyan_skillfish2_sdma.bin amdgpu/cyan_skillfish2_sdma1.bin amdgpu/navy_flounder_ce.bin amdgpu/navy_flounder_dmcub.bin amdgpu/navy_flounder_me.bin amdgpu/navy_flounder_mec.bin amdgpu/navy_flounder_mec2.bin amdgpu/navy_flounder_pfp.bin amdgpu/navy_flounder_rlc.bin amdgpu/navy_flounder_sdma.bin amdgpu/navy_flounder_smc.bin amdgpu/navy_flounder_sos.bin amdgpu/navy_flounder_ta.bin amdgpu/navy_flounder_vcn.bin amdgpu/vangogh_asd.bin amdgpu/vangogh_ce.bin amdgpu/vangogh_dmcub.bin amdgpu/vangogh_me.bin amdgpu/vangogh_mec.bin amdgpu/vangogh_mec2.bin amdgpu/vangogh_pfp.bin amdgpu/vangogh_rlc.bin amdgpu/vangogh_sdma.bin amdgpu/vangogh_toc.bin amdgpu/vangogh_vcn.bin atmel/wilc1000_wifi_firmware-1.bin brcm/brcmfmac43340-sdio.predia-basic.txt brcm/brcmfmac43430-sdio.friendlyarm,nanopi-r1.txt brcm/brcmfmac43430-sdio.raspberrypi,model-zero-w.txt brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-plus.txt brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-ultra.txt brcm/brcmfmac43430-sdio.sinovoip,bpi-m2-zero.txt brcm/brcmfmac43430-sdio.sinovoip,bpi-m3.txt brcm/brcmfmac43430a0-sdio.ilife-S806.txt brcm/brcmfmac43455-sdio.Raspberry Pi Foundation-Raspberry Pi 4 Model B.txt brcm/brcmfmac43455-sdio.Raspberry Pi Foundation-Raspberry Pi Compute Module 4.txt brcm/brcmfmac43455-sdio.acepc-t8.txt brcm/brcmfmac43455-sdio.raspberrypi,3-model-a-plus.txt brcm/brcmfmac4356-sdio.khadas,vim2.txt brcm/brcmfmac4356-sdio.vamrs,rock960.txt brcm/brcmfmac43012-sdio.bin brcm/brcmfmac43012-sdio.clm_blob brcm/brcmfmac43430-sdio.clm_blob brcm/brcmfmac43455-sdio.clm_blob brcm/brcmfmac4354-sdio.clm_blob brcm/brcmfmac4356-pcie.clm_blob brcm/brcmfmac4356-sdio.clm_blob brcm/brcmfmac43570-pcie.clm_blob brcm/brcmfmac4373-sdio.clm_blob i915/adlp_guc_62.0.3.bin i915/bxt_guc_62.0.0.bin i915/cml_guc_62.0.0.bin i915/ehl_guc_62.0.0.bin i915/glk_guc_62.0.0.bin i915/icl_guc_62.0.0.bin i915/kbl_guc_62.0.0.bin i915/rkl_dmc_ver2_03.bin i915/skl_guc_62.0.0.bin i915/tgl_dmc_ver2_12.bin i915/tgl_guc_62.0.0.bin i915/tgl_huc_7.9.3.bin iwlwifi-Qu-b0-hr-b0-66.ucode iwlwifi-Qu-b0-jf-b0-66.ucode iwlwifi-Qu-c0-hr-b0-66.ucode iwlwifi-QuZ-a0-hr-b0-66.ucode iwlwifi-QuZ-a0-jf-b0-66.ucode iwlwifi-cc-a0-66.ucode iwlwifi-ty-a0-gf-a0-66.ucode mellanox/mlxsw_spectrum-13.2008.2406.mfa2 mellanox/mlxsw_spectrum2-29.2008.2406.mfa2 mellanox/mlxsw_spectrum3-30.2008.2406.mfa2 nvidia/tegra194/vic.bin rtl_bt/rtl8821a_config.bin rtl_nic/rtl8153c-1.fw rtl_nic/rtl8156a-2.fw rtl_nic/rtl8156b-2.fw [Fix] Add relevant commits for the above files. Except for the brcm files. Some of them are provided by the linux-firmware-raspi2 package and could cause conflicts. [Test Case] Verify that above files are present after package installation (except brcm/*). [Where Problems Could Occur] These are all new firmware files so no regression is expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1962299/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962578] Re: [UBUNTU 20.04] Fix SIGP processing on KVM/s390
** Changed in: ubuntu-z-systems Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1962578 Title: [UBUNTU 20.04] Fix SIGP processing on KVM/s390 Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: SRU Justification: == [Impact] * The SIGP processing on KVM/s390x is incorrect and not fully conform to the 'Principles of Operations', the IBM Z architecture definition and documentation. * KVM: SIGP RESTART is reporting a CPU state 'stopped' after SIGP RESTART was issued, while it should report a 'busy' condition until the CPU is really started. * The fix for this consists of three patches: 812de04661c4 "KVM: s390: Clarify SIGP orders versus STOP/RESTART" 435d17955519 "KVM: s390: Add a routine for setting userspace CPU state" 4563bcad46bf "KVM: s390: Simplify SIGP Set Arch handling" whereas 812de04661c4 already landed via upstream stable, hence only two are left and need to be cherry-picked: [Fix] * 67cf68b6a5ccac8bc7dfef0a220b59af4c83fd2c 67cf68b6a5cc "KVM: s390: Add a routine for setting userspace CPU state" * 8eeba194a32e0f50329354a696baaa2e3d9accc5 8eeba194a32e "KVM: s390: Simplify SIGP Set Arch handling" [Test Case] * Install an LPAR on IBM Z (z13+) or LinuxONE (Emperor / Rockhopper) with Ubuntu Server 20.04 using kernel standard kernel 5.4. * Setup this LPAR as QEMU/KVM host and a focal VM as guest. * The test itself is the following unit test: https://lore.kernel.org/r/20220303210425.1693486-1-far...@linux.ibm.com/ * The test and verification will be done by the IBM Z team. [Where problems could occur] * A broken patch could harm KVM ioctl on s390x or the (virtual) CPU state control in general. * The SIGP handing (on s390x) can become broken, which could lead to incorrect (virtual) CPU states. * In worst case KVM can become broken on s390x entirely. * The modified code is all s390x specific QEMU/KVM code, no common code is touched. [Other] * The two remaining patches are upstream since 5.16, the first one already landed in 5.4 via upstream stable bug LP#1959701 and in 5.13 via upstream stable bug LP#1960861. * The patches already landed in jammy (master-next) based on LP#1959735, hence only SRU to impish and focal is needed. * This patches got discussed here: https://lore.kernel.org/all/20211008203112.1979843-2-far...@linux.ibm.com/ * This not only fixes the SIGP processing, but is also important in terms of long term maintainability. __ Description: KVM: SIGP RESTART is reporting a CPU state 'stopped' after SIGP RESTART was issued, while it should report a 'busy' condition until the CPU is really started. The patches to fix this have already been picked for jammy/master- next: 812de04661c4 "KVM: s390: Clarify SIGP orders versus STOP/RESTART" 435d17955519 "KVM: s390: Add a routine for setting userspace CPU state" 4563bcad46bf "KVM: s390: Simplify SIGP Set Arch handling" For Ubuntu 20.04 the focal/master-next already contains: d74b0d2d38d3 KVM: s390: Clarify SIGP orders versus STOP/RESTART so we additionally need the following two upstream commits in focal 67cf68b6a5cc KVM: s390: Add a routine for setting userspace CPU state 8eeba194a32e KVM: s390: Simplify SIGP Set Arch handling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1962578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941950] Re: linux-riscv: missing kernel signature
** Changed in: linux-riscv (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1941950 Title: linux-riscv: missing kernel signature Status in linux-riscv package in Ubuntu: Opinion Bug description: U-Boot and EDK II both support secure boot. But vmlinuz-5.11.0-1014-generic and vmlinuz-5.13.0-1002-generic are not signed via sbsign. Please, adjust the RISC-V build system to sign new kernels. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1941950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958374] Re: riscv: Improve support for the SiFive Unmatched board
*** This bug is a duplicate of bug 1962010 ***
https://bugs.launchpad.net/bugs/1962010
This will be handled as part of 1962010, marking this bug as duplicate
of that one, as that's the one that will be closed in the changelogs.
** This bug has been marked a duplicate of bug 1962010
Cherrypick features and fixes from v5.17 for sifive dtbs
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1958374
Title:
riscv: Improve support for the SiFive Unmatched board
Status in linux-riscv package in Ubuntu:
New
Bug description:
The following patches should be considered for inclusion into the
v5.15 linux-image-generic kernel for the Jammy release:
commit f6f7fbb89bf8dc9132fde55cfe67483138eea880
Author: Vincent Pelletier
Date: Tue Nov 16 23:57:42 2021 +
riscv: dts: sifive unmatched: Link the tmp451 with its power supply
Fixes the following probe warning:
lm90 0-004c: Looking up vcc-supply from device tree
lm90 0-004c: Looking up vcc-supply property in node
/soc/i2c@1003/temperature-sensor@4c failed
lm90 0-004c: supply vcc not found, using dummy regulator
Signed-off-by: Vincent Pelletier
Signed-off-by: Palmer Dabbelt
commit ad931d9b3b2e21586de8e6b34346d0a30c13721d
Author: Vincent Pelletier
Date: Tue Nov 16 23:57:41 2021 +
riscv: dts: sifive unmatched: Fix regulator for board rev3
The existing values are rejected by the da9063 regulator driver, as they
are unachievable with the declared chip setup (non-merged vcore and bmem
are unable to provide the declared curent).
Fix voltages to match rev3 schematics, which also matches their boot-up
configuration within the chip's available precision.
Declare bcore1/bcore2 and bmem/bio as merged.
Set ldo09 and ldo10 as always-on as their consumers are not declared but
exist.
Drop ldo current limits as there is no current limit feature for these
regulators in the DA9063. Fixes warnings like:
DA9063_LDO3: Operation of current configuration missing
Signed-off-by: Vincent Pelletier
Signed-off-by: Palmer Dabbelt
commit cd29cc8ad2540a4f9a0a3e174394d39e648ef941
Author: Vincent Pelletier
Date: Tue Nov 16 23:57:39 2021 +
riscv: dts: sifive unmatched: Expose the PMIC sub-functions
These sub-functions are available in the chip revision on this board, so
expose them.
Signed-off-by: Vincent Pelletier
Signed-off-by: Palmer Dabbelt
commit 8120393b74b31bbaf293f59896de6b0d50febc48
Author: Vincent Pelletier
Date: Tue Nov 16 23:57:38 2021 +
riscv: dts: sifive unmatched: Expose the board ID eeprom
Mark it as read-only as it is factory-programmed with identifying
information, and no executable nor configuration:
- eth MAC address
- board model (PCB version, BoM version)
- board serial number
Accidental modification would cause misidentification which could brick
the board, so marking read-only seem like both a safe and non-constraining
choice.
Signed-off-by: Vincent Pelletier
Signed-off-by: Palmer Dabbelt
commit ea81b91e4e256b0bb75d47ad3a5c230b2171a005
Author: Vincent Pelletier
Date: Tue Nov 16 23:57:37 2021 +
riscv: dts: sifive unmatched: Name gpio lines
Follow the pin descriptions given in the version 3 of the board
schematics.
Signed-off-by: Vincent Pelletier
Signed-off-by: Palmer Dabbelt
commit 298d03c2d7f1b5daacb6d4f4053fd3d677d67087
Author: Bin Meng
Date: Wed Jun 16 15:46:45 2021 +0800
riscv: dts: unmatched: Add gpio card detect to mmc-spi-slot
Per HiFive Unmatched schematics, the card detect signal of the
micro SD card is connected to gpio pin #15, which should be
reflected in the DT via the property, as described in
Documentation/devicetree/bindings/mmc/mmc-spi-slot.txt.
[1]
https://sifive.cdn.prismic.io/sifive/6a06d6c0-6e66-49b5-8e9e-e68ce76f4192_hifive-unmatched-schematics-v3.pdf
Signed-off-by: Bin Meng
Fixes: d573b5558abb ("riscv: dts: add initial board data for the SiFive
HiFive Unmatched")
Cc: sta...@vger.kernel.org
Signed-off-by: Palmer Dabbelt
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1958374/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms
SRU: https://lists.ubuntu.com/archives/kernel- team/2022-March/128635.html (jammy, V3) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1955383 Title: Support Intel IPU6 MIPI camera on Alder Lake platforms Status in HWE Next: New Status in OEM Priority Project: In Progress Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: == kernel driver SRU == [SRU Justification] [Impact] To support Intel IPU6 MIPI camera on Alder Lake platforms. [Fix] Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has been addressed by bug 1921345 and 1939539. They are backported from https://github.com/intel/ipu6-drivers. Further works to enable IPU6 camera on Alder Lake platforms depend on a few more fixes from same ipu6-drivers repository, as well as an extra https://github.com/intel/ivsc-driver for Intel Vision Sensing Controller(IVSC). [Test Case] This depends on an integral of enablement components inclusive of the kernel drivers that are being proposed, firmware, updates for the userspace camera hardware abstration layer library and a gstreamer element as what we have for Tiger Lake platforms. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. [Other Info] Jammy is planned, but yet the support for 5.15 kernel is not yet started from Intel side. == linux-firmware SRU == [SRU Justification] [Impact] Intel IPU6 MIPI camera on Alder Lake platform takes a different fw blob. [Fix] While Intel has no intention to upstream IPU6 driver before kernel camera is out, it's available in https://github.com/intel/ipu6-camera-bins commit e60fae2b5128 from its main branch. [Test Case] This would take both kernel and firmware fixes, as well as updates for the userspace middleware, gstreamer element plugin, to enable the device. With all of them in position, one should be able to browse camera with legacy camera apps like cheese. [Where problems could occur] It's confirmed Intel IPU6 MIPI camera doesn't support suspend at streaming. == original bug report == This depends on following componenets: * ipu6ep firmware in https://github.com/intel/ipu6-camera-bins/commit/e60fae2b5128cf5b8b948b234dab28e58c93877d * Intel VSC fw version 1.2.3.439 (not yet available publicly) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-tentacool+X188 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-12-20 (7 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 9320 Package: linux-firmware 1.187.23+staging.38 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem root=UUID=f4ad7114-fc86-47d7-b750-86bd1560a5f6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-2013-oem N/A linux-backports-modules-5.14.0-2013-oem N/A linux-firmware 1.187.23+staging.38 Tags: third-party-packages focal Uname: Linux 5.14.0-2013-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 12/02/2021 dmi.bios.release: 0.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.2.7 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.2.7:bd12/02/2021:br0.2:svnDellInc.:pnXPS9320:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0AF3:
[Kernel-packages] [Bug 1932117] Re: Lots of hisi_qm zombie task slow down system after stress test
** Changed in: linux (Ubuntu Focal) 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/1932117 Title: Lots of hisi_qm zombie task slow down system after stress test Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04-hwe series: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Invalid Status in linux source package in Impish: Invalid Bug description: [Impact] hisi_qm does not clean up kernel process after calculation is done. Many zombie processes slow down system. After checkbox cpu stress test, it takes more then 2min to ssh in. [Test Plan] 1) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 2) ps aux | grep hisi_qm | wc -l Expected result is less then 100 [Regression Risk] hisi_qm only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] With focal 5.4 kernel, crypto driver does not clean up its created process when calculation is done. Many zombie processes slow down system. e.g. Takes more then 10sec for ssh connection. [Steps to Reproduce] 1) Install Ubuntu 20.04 with GA (5.4) kernel 2) sudo apt install -y stress-ng 3) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 4) ps aux | grep hisi_qm | wc -l [Actual Results] >10 [Expected Results] <100 [Reproducibility] 100% [Additional information] Can not reproduce with focal HWE (5.8) kernel. [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1932117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943301] Re: 【sec-0911】 fail to reset sec module
** Changed in: linux (Ubuntu Focal) 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/1943301 Title: 【sec-0911】 fail to reset sec module Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 ubuntu-20.04-hwe series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Bug description: [Impact] The crypto accelerator in Hi1620 SoC can not be reset. [Test Plan] 1) echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.1/reset 2) echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.0/reset 3) busybox devmem 0x200141B01018 32 0x1 4) dmesg | grep "FLR resetting" [Regression Risk] hisi_qm only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] [Steps to Reproduce] 1、echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.1/reset 2、echo 1 >/sys/devices/pci:74/:74:00.0/:75:00.0/reset 3、busybox devmem 0x200141B01018 32 0x1, [Actual Results] root@root:~# busybox devmem 0x200141B01018 32 0x1 root@root:~# dmesg root@root:~# [Expected Results] reset ok [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): OS: ubuntu 20.04.2 DRV（driver version）: vermagic: 5.8.0-59-generic SMP mod_unload aarch64 [Resolution] [v2,3/5] crypto: hisilicon/sec2 - update SEC initialization and reset 此patch未合入 https://patchwork.kernel.org/project/linux-crypto/patch/1594084541-22177-4-git-send-email-liulongf...@huawei.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1943301/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962578] Re: [UBUNTU 20.04] Fix SIGP processing on KVM/s390
** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Impish) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1962578 Title: [UBUNTU 20.04] Fix SIGP processing on KVM/s390 Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: SRU Justification: == [Impact] * The SIGP processing on KVM/s390x is incorrect and not fully conform to the 'Principles of Operations', the IBM Z architecture definition and documentation. * KVM: SIGP RESTART is reporting a CPU state 'stopped' after SIGP RESTART was issued, while it should report a 'busy' condition until the CPU is really started. * The fix for this consists of three patches: 812de04661c4 "KVM: s390: Clarify SIGP orders versus STOP/RESTART" 435d17955519 "KVM: s390: Add a routine for setting userspace CPU state" 4563bcad46bf "KVM: s390: Simplify SIGP Set Arch handling" whereas 812de04661c4 already landed via upstream stable, hence only two are left and need to be cherry-picked: [Fix] * 67cf68b6a5ccac8bc7dfef0a220b59af4c83fd2c 67cf68b6a5cc "KVM: s390: Add a routine for setting userspace CPU state" * 8eeba194a32e0f50329354a696baaa2e3d9accc5 8eeba194a32e "KVM: s390: Simplify SIGP Set Arch handling" [Test Case] * Install an LPAR on IBM Z (z13+) or LinuxONE (Emperor / Rockhopper) with Ubuntu Server 20.04 using kernel standard kernel 5.4. * Setup this LPAR as QEMU/KVM host and a focal VM as guest. * The test itself is the following unit test: https://lore.kernel.org/r/20220303210425.1693486-1-far...@linux.ibm.com/ * The test and verification will be done by the IBM Z team. [Where problems could occur] * A broken patch could harm KVM ioctl on s390x or the (virtual) CPU state control in general. * The SIGP handing (on s390x) can become broken, which could lead to incorrect (virtual) CPU states. * In worst case KVM can become broken on s390x entirely. * The modified code is all s390x specific QEMU/KVM code, no common code is touched. [Other] * The two remaining patches are upstream since 5.16, the first one already landed in 5.4 via upstream stable bug LP#1959701 and in 5.13 via upstream stable bug LP#1960861. * The patches already landed in jammy (master-next) based on LP#1959735, hence only SRU to impish and focal is needed. * This patches got discussed here: https://lore.kernel.org/all/20211008203112.1979843-2-far...@linux.ibm.com/ * This not only fixes the SIGP processing, but is also important in terms of long term maintainability. __ Description: KVM: SIGP RESTART is reporting a CPU state 'stopped' after SIGP RESTART was issued, while it should report a 'busy' condition until the CPU is really started. The patches to fix this have already been picked for jammy/master- next: 812de04661c4 "KVM: s390: Clarify SIGP orders versus STOP/RESTART" 435d17955519 "KVM: s390: Add a routine for setting userspace CPU state" 4563bcad46bf "KVM: s390: Simplify SIGP Set Arch handling" For Ubuntu 20.04 the focal/master-next already contains: d74b0d2d38d3 KVM: s390: Clarify SIGP orders versus STOP/RESTART so we additionally need the following two upstream commits in focal 67cf68b6a5cc KVM: s390: Add a routine for setting userspace CPU state 8eeba194a32e KVM: s390: Simplify SIGP Set Arch handling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1962578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960633] Re: Move virtual graphics drivers from linux-modules-extra to linux-modules
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Impish)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1960633
Title:
Move virtual graphics drivers from linux-modules-extra to linux-
modules
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Status in linux source package in Jammy:
Fix Committed
Bug description:
[SRU justification]
Impact: We split the drivers into linux-modules and linux-modules-extra. The
latter is only included for setups geared towards real hardware (desktops,
laptops). For VM guests the recommended setup is to use linux-virtual which
does not include linux-modules-extra but also does not depend on other
packages, like linux-firmware.
We already include most VM related drivers in the linux-modules package and
vboxvideo (since 21.10/Impish). So it makes sense to include the missing ones.
Fix: Move the following modules from linux-modules-extra into linux-modules:
- bochs-drm (though a bit aged, this was the predecessor of qemu)
- cirrus (this is a standard emulated gfx card, might not give the best
performance but better than nothing)
- virtio-gpu (KVM)
- vmwgfx (VMWare)
- drm-xen-front (Xen)
Testcase: Check linux-modules for the mentioned modules.
Regression Potential: There should be no change noticeable. Users with
linux-modules-extra installed will see no difference and those without
have additional drivers. Maybe this shows as moving from low-
resolution graphics to higher ones which maybe perform less.
--- Original Description ---
Kernel: Ubuntu 5.13.0-28.31-generic 5.13.19
Distribution: Ubuntu 21.10 (impish)
I run an Ubuntu desktop as a VMWare virtual machine client.
The linux-modules-extra-${VERSION}-generic package contains
kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko, so at the moment I need to
keep it installed and updated. The only way to do so conveniently is
to install linux-image-generic, which also pulls in linux-firmware,
which is ~760MB installed.
If vmwgfx was moved from linux-modules-extra to linux-modules, I could
use linux-image-virtual instead of linux-image-generic, remove linux-
firmware, linux-modules-extra, and the microcode packages, saving
substantial disk space and bandwidth.
Other virtual graphics drivers in linux-modules-extra that might be
worth moving are:
kernel/drivers/gpu/drm/bochs/bochs-drm.ko
kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
kernel/drivers/gpu/drm/xen/drm_xen_front.ko
Thank you for your consideration.
Note: Edited significantly in response to
https://lists.ubuntu.com/archives/kernel-
team/2022-February/128103.html and
https://lists.ubuntu.com/archives/kernel-
team/2022-February/128104.html to better reflect the underlying
problem and solution.
P.S. There are three other drivers in linux-modules-extra that seem
VMWare-related, but they are not in use in my VM and I don't know
whether they are in common enough use to justify moving them to linux-
modules. I have listed them here for completeness.
kernel/drivers/net/vsockmon.ko
kernel/drivers/ptp/ptp_vmw.ko
kernel/drivers/infiniband/hw/vmw_pvrdma/vmw_pvrdma.ko
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ccherlin 1645 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2021-01-05 (405 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
IwConfig:
lono wireless extensions.
ens33 no wireless extensions.
docker0 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic
[Kernel-packages] [Bug 1958715] Re: nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1958715 Title: nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: message popped up on screen ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.13.0-27-generic Date: Sat Jan 22 08:56:06 2022 DuplicateSignature: dkms:nvidia-dkms-460:460.73.01-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/460.73.01/build/nvidia-drm/nvidia-drm-crtc.c:311:23: error: initialization of ‘int (*)(struct drm_plane *, struct drm_atomic_state *)’ from incompatible pointer type ‘int (*)(struct drm_plane *, struct drm_plane_state *)’ [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2021-02-20 (336 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 460.73.01-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: nvidia-graphics-drivers-460 Title: nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1958715/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962569] Re: jammy/linux-oem-5.17: 5.17.0-1001.1 -proposed tracker
** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1962569 Title: jammy/linux-oem-5.17: 5.17.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow boot-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrg series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-lrs 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: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Incomplete Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Triaged Status in Kernel SRU Workflow sru-review series: Fix Released Status in linux-oem-5.17 package in Ubuntu: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true built: route-entry: 2 delta: promote-to-proposed: - signed - lrs - lrm - main - meta - lrg sru-review: - main - lrg - meta - lrm - signed - lrs kernel-stable-master-bug: 1963880 packages: lrg: linux-restricted-generate-oem-5.17 lrm: linux-restricted-modules-oem-5.17 lrs: linux-restricted-signatures-oem-5.17 main: linux-oem-5.17 meta: linux-meta-oem-5.17 signed: linux-signed-oem-5.17 phase: Promote to Proposed phase-changed: Monday, 14. March 2022 10:40 UTC reason: automated-testing: 'Stalled -- unable to process task: results not valid, seeds missing' promote-to-proposed: Stalled -- copy FAILED regression-testing: Ongoing -s testing in progress synthetic: :promote-to-as-proposed: Fix Released variant: debs versions: lrm: 5.17.0-1001.1+2 main: 5.17.0-1001.1 meta: 5.17.0.1001.1+1 signed: 5.17.0-1001.1 versions-clamp: self: 5.17.0-1001.1 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1962569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964775] [NEW] nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build
Public bug reported: There is a problem with NVIDIA drivers and Ubuntu. The screen starts blinking after suspension, for example. Brightness scale appears low in settings but the screen is quite bright actually, another example. I'd be glad if this conflict/problem is resolved by installing necessary packages with the great contribution of ubuntu developers. Thank you! ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.13.0-35-generic Date: Wed Mar 9 12:07:46 2022 DuplicateSignature: dkms:nvidia-dkms-460:460.73.01-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/460.73.01/build/nvidia-drm/nvidia-drm-crtc.c:311:23: error: initialization of ‘int (*)(struct drm_plane *, struct drm_atomic_state *)’ from incompatible pointer type ‘int (*)(struct drm_plane *, struct drm_plane_state *)’ [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2021-03-31 (347 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 460.73.01-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-460 Title: nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1964775 Title: nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: There is a problem with NVIDIA drivers and Ubuntu. The screen starts blinking after suspension, for example. Brightness scale appears low in settings but the screen is quite bright actually, another example. I'd be glad if this conflict/problem is resolved by installing necessary packages with the great contribution of ubuntu developers. Thank you! ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.13.0-35-generic Date: Wed Mar 9 12:07:46 2022 DuplicateSignature: dkms:nvidia-dkms-460:460.73.01-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/460.73.01/build/nvidia-drm/nvidia-drm-crtc.c:311:23: error: initialization of ‘int (*)(struct drm_plane *, struct drm_atomic_state *)’ from incompatible pointer type ‘int (*)(struct drm_plane *, struct drm_plane_state *)’ [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2021-03-31 (347 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 460.73.01-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-460 Title: nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1964775/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1963615] Re: Add proper runtime PM support to Realtek PCIe cardreader
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1963615 Title: Add proper runtime PM support to Realtek PCIe cardreader Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] New generations of Realtek PCIe card reader cannot detect card insertion when the device is in PCI D3. [Fix] Rework the runtime PM flow and add chip specific support. [Test] With the series applied, the device can detect card insertion when it's in PCI D3. [Where problems could occur] System wide power management with less usage like hibernation, kexec reboot, etc. are not tested extensively. So these cases may be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1963615/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955882] Re: MT7921[14c3:7961] ASPM is disabled and it affects power consumption
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1955882 Title: MT7921[14c3:7961] ASPM is disabled and it affects power consumption Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] MT7921 is disabled by default, and it affects the power consumption. [Fix] MTK pointed out we need this commit which is included in v5.16-rc1 bf3747ae2e25 mt76: mt7921: enable aspm by default After ASPM is enabled, we found the card disappears after reboot sometimes, so MTK provides another commit for it https://patchwork.kernel.org/project/linux-mediatek/patch/70e27cbc652cbdb78277b9c691a3a5ba02653afb.1641540175.git.obj...@gmail.com/ [Test] Verified on Dell machines with MT7921 wifi card. [Where problems could occur] Enable device ASPM is always risky, we've done our best to test these patches, and no regression could be found. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1955882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959215] Re: unshare test in ubuntu_stress_smoke_tests triggers "BUG: unable to handle page fault for address: 0000000000001cc8" on Impish with node vought
Tested with the latest mainline kernel 5.17.0-051700rc8, this issue still exist on node vought. Mar 14 10:18:25 vought stress-ng: system: 'vought' Linux 5.17.0-051700rc8-generic #202203132130 SMP PREEMPT Sun Mar 13 21:33:37 UTC 2022 x86_64 Mar 14 10:18:25 vought stress-ng: memory (MB): total 359930.86, free 354661.62, shared 2.78, buffer 244.86, swap 9215.99, free swap 9214.57 Mar 14 10:18:25 vought stress-ng: info: [223826] setting to a 5 second run per stressor Mar 14 10:18:25 vought stress-ng: info: [223826] dispatching hogs: 4 unshare Mar 14 10:18:25 vought kernel: [ 833.522791] BUG: unable to handle page fault for address: 1cc8 Mar 14 10:18:25 vought kernel: [ 833.522881] #PF: supervisor read access in kernel mode Mar 14 10:18:25 vought kernel: [ 833.522930] #PF: error_code(0x) - not-present page Mar 14 10:18:25 vought kernel: [ 833.522980] PGD 0 P4D 0 Mar 14 10:18:25 vought kernel: [ 833.523012] Oops: [#1] PREEMPT SMP NOPTI Mar 14 10:18:25 vought kernel: [ 833.523059] CPU: 31 PID: 224777 Comm: stress-ng Not tainted 5.17.0-051700rc8-generic #202203132130 Mar 14 10:18:25 vought kernel: [ 833.523143] Hardware name: Intel Corporation S2600WFD/S2600WFD, BIOS SE5C620.86B.0D.01.0395.022720191340 02/27/2019 Mar 14 10:18:25 vought kernel: [ 833.523234] RIP: 0010:__next_zones_zonelist+0x6/0x50 Mar 14 10:18:25 vought kernel: [ 833.523304] Code: d0 0f 4e d0 3d ff 03 00 00 7f 0d 48 63 d2 5d 48 8b 04 d5 a0 04 25 95 c3 31 c0 5d c3 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 <8b> 4f 08 48 89 f8 48 89 e5 48 85 d2 75 10 eb 1d 48 63 49 50 48 0f Mar 14 10:18:25 vought kernel: [ 833.523466] RSP: 0018:c100351b3b10 EFLAGS: 00010286 Mar 14 10:18:25 vought kernel: [ 833.523518] RAX: RBX: RCX: Mar 14 10:18:25 vought kernel: [ 833.523584] RDX: a00d6a05ce00 RSI: 0002 RDI: 1cc0 Mar 14 10:18:25 vought kernel: [ 833.523649] RBP: c100351b3b78 R08: R09: Mar 14 10:18:25 vought kernel: [ 833.523714] R10: 0002 R11: fffc R12: 00052cc0 Mar 14 10:18:25 vought kernel: [ 833.523778] R13: 0002 R14: 0001 R15: 00152cc0 Mar 14 10:18:25 vought kernel: [ 833.523843] FS: 7f6d7078cb80() GS:a0394cbc() knlGS: Mar 14 10:18:25 vought kernel: [ 833.523917] CS: 0010 DS: ES: CR0: 80050033 Mar 14 10:18:25 vought kernel: [ 833.523971] CR2: 1cc8 CR3: 00bd7cd4e006 CR4: 007706e0 Mar 14 10:18:25 vought kernel: [ 833.524036] DR0: DR1: DR2: Mar 14 10:18:25 vought kernel: [ 833.524100] DR3: DR6: fffe0ff0 DR7: 0400 Mar 14 10:18:25 vought kernel: [ 833.524164] PKRU: 5554 Mar 14 10:18:25 vought kernel: [ 833.524192] Call Trace: Mar 14 10:18:25 vought kernel: [ 833.524221] Mar 14 10:18:25 vought kernel: [ 833.524250] ? __alloc_pages+0x304/0x340 Mar 14 10:18:25 vought kernel: [ 833.524308] kmalloc_large_node+0x45/0xa0 Mar 14 10:18:25 vought kernel: [ 833.524358] ? krc_this_cpu_lock+0x36/0x40 Mar 14 10:18:25 vought kernel: [ 833.524408] __kmalloc_node+0x2f8/0x3e0 Mar 14 10:18:25 vought kernel: [ 833.524452] kvmalloc_node+0x4e/0x90 Mar 14 10:18:25 vought kernel: [ 833.524494] expand_one_shrinker_info+0x82/0x180 Mar 14 10:18:25 vought kernel: [ 833.524545] prealloc_shrinker+0x172/0x1d0 Mar 14 10:18:25 vought kernel: [ 833.524588] alloc_super+0x2b3/0x340 Mar 14 10:18:25 vought kernel: [ 833.524633] ? __fput_sync+0x30/0x30 Mar 14 10:18:25 vought kernel: [ 833.524674] sget_fc+0x6f/0x2e0 Mar 14 10:18:25 vought kernel: [ 833.524706] ? kill_litter_super+0x50/0x50 Mar 14 10:18:25 vought kernel: [ 833.526339] ? mqueue_get_tree+0x20/0x20 Mar 14 10:18:25 vought kernel: [ 833.527918] get_tree_keyed+0x34/0xd0 Mar 14 10:18:25 vought kernel: [ 833.529467] mqueue_get_tree+0x1c/0x20 Mar 14 10:18:25 vought kernel: [ 833.531375] vfs_get_tree+0x27/0xc0 Mar 14 10:18:25 vought kernel: [ 833.533453] fc_mount+0x13/0x50 Mar 14 10:18:25 vought kernel: [ 833.535499] mq_init_ns+0x10a/0x1b0 Mar 14 10:18:25 vought kernel: [ 833.537491] copy_ipcs+0x130/0x230 Mar 14 10:18:25 vought kernel: [ 833.539497] create_new_namespaces+0xa6/0x2e0 Mar 14 10:18:25 vought kernel: [ 833.541416] unshare_nsproxy_namespaces+0x5a/0xb0 Mar 14 10:18:25 vought kernel: [ 833.542729] ksys_unshare+0x19f/0x380 Mar 14 10:18:25 vought kernel: [ 833.544063] __x64_sys_unshare+0x12/0x20 Mar 14 10:18:25 vought kernel: [ 833.545421] do_syscall_64+0x59/0xc0 Mar 14 10:18:25 vought kernel: [ 833.546800] ? do_syscall_64+0x69/0xc0 Mar 14 10:18:25 vought kernel: [ 833.548145] ? asm_exc_page_fault+0x8/0x30 Mar 14 10:18:25 vought kernel: [ 833.549446] entry_SYSCALL_64_after_hwframe+0x44/0xae Mar 14 10:18:25 vought kernel: [ 833.550789] RIP: 0033:0x7f6d708c1fcb Mar
[Kernel-packages] [Bug 1963901] Re: [22.04 FEAT] [VS2103] Set KVM_CAP_S390_MEM_OP_EXTENSION capability to 211
Patch request submitted to kernel team's mailing list:
https://lists.ubuntu.com/archives/kernel-team/2022-March/thread.html#128621
changing status to 'In Progress'.
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: ubuntu-z-systems
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Kernel
Team (canonical-kernel-team)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1963901
Title:
[22.04 FEAT] [VS2103] Set KVM_CAP_S390_MEM_OP_EXTENSION capability to
211
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
In Progress
Bug description:
Title:
KVM: Enable storage key checking for intercepted instruction - Set Capability
211
Description:
This patch is required on top of "Bug 193314 - LP#1933179 : [22.04 FEAT]
[VS2103] KVM: Enable storage key checking for intercepted instruction" in order
to set the to set the Capability number to 211
See this merge:
https://git.kernel.org/pub/scm/virt/kvm/kvm.git/commit/?h=next=4dfc4ec2b7f5a3a27d166ac42cf8a583fa2d3284
diff --git a/include/uapi/linux/kvm.h b/include/uapi/linux/kvm.h
index dbc550bbd9fa3..a02bbf8fd0f67 100644
--- a/include/uapi/linux/kvm.h
+++ b/include/uapi/linux/kvm.h
@@ -1140,7 +1140,8 @@ struct kvm_ppc_resize_hpt {
#define KVM_CAP_VM_GPA_BITS 207
#define KVM_CAP_XSAVE2 208
#define KVM_CAP_SYS_ATTRIBUTES 209
-#define KVM_CAP_S390_MEM_OP_EXTENSION 210
+#define KVM_CAP_PPC_AIL_MODE_3 210
+#define KVM_CAP_S390_MEM_OP_EXTENSION 211
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1963901/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929895] Re: [EHL] Enable ISHTP
v5.15 updates are as following https://github.com/intel/linux-intel-quilt/tree/lts-v5.15.21-linux-220222T001242Z-1 0001-hid-intel-ish-hid-add-RTD3-support-for-EHL-platform.patch 0002-hid-intel-ish-hid-ipc-remove-call-pm-api-in-interrup.patch 0003-hid-intel-ish-hid-ipc-add-return-value-check-for-wai.patch 0004-hid-intel-ish-hid-ipc-fix-S0ix-cannot-wakeup-issue.patch 0005-hid-intel-ish-hid-Use-different-pm-callbacks-for-ish.patch 0001-platform-eclite-Fix-for-unwanted-event-sent-during-e.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1929895 Title: [EHL] Enable ISHTP Status in intel: Fix Committed Status in intel lookout-canyon series: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Description This driver enables the OS to talk to eclite firmware on a dedicated low power chip over ISH Transport Protocol (ISHTP) Hardware: Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929895/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1963717] Re: Bionic update: upstream stable patchset 2022-03-04
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1963717 Title: Bionic update: upstream stable patchset 2022-03-04 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed 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: upstream stable patchset 2022-03-04 Ported from the following upstream stable releases: v4.14.264, v4.19.227 v4.14.265, v4.19.228 from git://git.kernel.org/ can: bcm: fix UAF of bcm op net: bridge: clear bridge's private skb space on xmit UBUNTU: upstream stable to v4.14.264, v4.19.227 Bluetooth: refactor malicious adv data check s390/hypfs: include z/VM guests with access control group set scsi: zfcp: Fix failed recovery on gone remote port with non-NPIV FCP devices udf: Restore i_lenAlloc when inode expansion fails udf: Fix NULL ptr deref when converting from inline format PM: wakeup: simplify the output logic of pm_show_wakelocks() netfilter: nft_payload: do not update layer 4 checksum when mangling fragments serial: stm32: fix software flow control transfer tty: n_gsm: fix SW flow control encoding/handling tty: Add support for Brainboxes UC cards. usb-storage: Add unusual-devs entry for VL817 USB-SATA bridge usb: common: ulpi: Fix crash in ulpi_match() usb: gadget: f_sourcesink: Fix isoc transfer for USB_SPEED_SUPER_PLUS USB: core: Fix hang in usb_kill_urb by adding memory barriers usb: typec: tcpm: Do not disconnect while receiving VBUS off net: sfp: ignore disabled SFP node powerpc/32: Fix boot failure with GCC latent entropy plugin lkdtm: Fix content of section containing lkdtm_rodata_do_nothing() i40e: Increase delay to 1 s after global EMP reset i40e: fix unsigned stat widths rpmsg: char: Fix race between the release of rpmsg_ctrldev and cdev rpmsg: char: Fix race between the release of rpmsg_eptdev and cdev scsi: bnx2fc: Flush destroy_work queue before calling bnx2fc_interface_put() ipv6_tunnel: Rate limit warning messages net: fix information leakage in /proc/net/ptype ping: fix the sk_bound_dev_if match in ping_lookup ipv4: avoid using shared IP generator for connected sockets hwmon: (lm90) Reduce maximum conversion rate for G781 NFSv4: Handle case where the lookup of a directory fails NFSv4: nfs_atomic_open() can race when looking up a non-regular file net-procfs: show net devices bound packet types drm/msm: Fix wrong size calculation drm/msm/dsi: invalid parameter check in msm_dsi_phy_enable ibmvnic: don't spin in tasklet yam: fix a memory leak in yam_siocdevprivate() ipv4: raw: lock the socket in raw_bind() ipv4: tcp: send zero IPID in SYNACK messages netfilter: nat: remove l4 protocol port rovers netfilter: nat: limit port clash resolution attempts ipheth: fix EOVERFLOW in ipheth_rcvbulk_callback net: amd-xgbe: ensure to reset the tx_timer_active flag net: amd-xgbe: Fix skb data length underflow rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink() af_packet: fix data-race in packet_setsockopt / packet_setsockopt audit: improve audit queue handling when "audit=1" on cmdline ASoC: ops: Reject out of bounds values in snd_soc_put_volsw() ASoC: ops: Reject out of bounds values in snd_soc_put_volsw_sx() ASoC: ops: Reject out of bounds values in snd_soc_put_xr_sx() drm/nouveau: fix off by one in BIOS boundary checking block: bio-integrity: Advance seed correctly for larger interval sizes RDMA/mlx4: Don't continue event handler after memory allocation failure iommu/vt-d: Fix potential memory leak in intel_setup_irq_remapping() iommu/amd: Fix loop timeout issue in iommu_ga_log_enable() spi: bcm-qspi: check for valid cs before applying chip select spi: mediatek: Avoid NULL pointer crash in interrupt spi: meson-spicc: add IRQ check in meson_spicc_probe net: ieee802154: ca8210: Stop leaking skb's net: ieee802154: Return meaningful error codes from the netlink helpers net: macsec: Verify that send_sci is on when setting Tx sci explicitly drm/i915/overlay: Prevent divide by zero bugs in scaling ASoC: fsl: Add missing error handling in pcm030_fabric_probe scsi: bnx2fc: Make bnx2fc_recv_frame() mp safe nfsd: nfsd4_setclientid_confirm mistakenly expires confirmed client. selftests: futex: Use
[Kernel-packages] [Bug 1964634] Re: Focal update: v5.4.178 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964634 Title: Focal update: v5.4.178 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed 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: v5.4.178 upstream stable release from git://git.kernel.org/ audit: improve audit queue handling when "audit=1" on cmdline ASoC: ops: Reject out of bounds values in snd_soc_put_volsw() ASoC: ops: Reject out of bounds values in snd_soc_put_volsw_sx() ASoC: ops: Reject out of bounds values in snd_soc_put_xr_sx() ALSA: usb-audio: Simplify quirk entries with a macro ALSA: hda/realtek: Add quirk for ASUS GU603 ALSA: hda/realtek: Add missing fixup-model entry for Gigabyte X570 ALC1220 quirks ALSA: hda/realtek: Fix silent output on Gigabyte X570S Aorus Master (newer chipset) ALSA: hda/realtek: Fix silent output on Gigabyte X570 Aorus Xtreme after reboot from Windows btrfs: fix deadlock between quota disable and qgroup rescan worker drm/nouveau: fix off by one in BIOS boundary checking mm/kmemleak: avoid scanning potential huge holes block: bio-integrity: Advance seed correctly for larger interval sizes memcg: charge fs_context and legacy_fs_context IB/rdmavt: Validate remote_addr during loopback atomic tests RDMA/siw: Fix broken RDMA Read Fence/Resume logic. RDMA/mlx4: Don't continue event handler after memory allocation failure iommu/vt-d: Fix potential memory leak in intel_setup_irq_remapping() iommu/amd: Fix loop timeout issue in iommu_ga_log_enable() spi: bcm-qspi: check for valid cs before applying chip select spi: mediatek: Avoid NULL pointer crash in interrupt spi: meson-spicc: add IRQ check in meson_spicc_probe net: ieee802154: hwsim: Ensure proper channel selection at probe time net: ieee802154: mcr20a: Fix lifs/sifs periods net: ieee802154: ca8210: Stop leaking skb's net: ieee802154: Return meaningful error codes from the netlink helpers net: macsec: Verify that send_sci is on when setting Tx sci explicitly net: stmmac: dump gmac4 DMA registers correctly net: stmmac: ensure PTP time register reads are consistent drm/i915/overlay: Prevent divide by zero bugs in scaling ASoC: fsl: Add missing error handling in pcm030_fabric_probe ASoC: xilinx: xlnx_formatter_pcm: Make buffer bytes multiple of period bytes ASoC: cpcap: Check for NULL pointer after calling of_get_child_by_name ASoC: max9759: fix underflow in speaker_gain_control_put() pinctrl: bcm2835: Fix a few error paths scsi: bnx2fc: Make bnx2fc_recv_frame() mp safe nfsd: nfsd4_setclientid_confirm mistakenly expires confirmed client. selftests: futex: Use variable MAKE instead of make rtc: cmos: Evaluate century appropriate EDAC/altera: Fix deferred probing EDAC/xgene: Fix deferred probing ext4: fix error handling in ext4_restore_inline_data() cgroup/cpuset: Fix "suspicious RCU usage" lockdep warning Linux 5.4.178 UBUNTU: upstream stable to v5.4.178 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964634/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964628] Re: Focal update: v5.4.177 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964628 Title: Focal update: v5.4.177 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed 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: v5.4.177 upstream stable release from git://git.kernel.org/ PCI: pciehp: Fix infinite loop in IRQ handler upon power fault psi: Fix uaf issue when psi trigger is destroyed while being polled ipheth: fix EOVERFLOW in ipheth_rcvbulk_callback net: amd-xgbe: ensure to reset the tx_timer_active flag net: amd-xgbe: Fix skb data length underflow net: sched: fix use-after-free in tc_new_tfilter() rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink() cpuset: Fix the bug that subpart_cpus updated wrongly in update_cpumask() af_packet: fix data-race in packet_setsockopt / packet_setsockopt Linux 5.4.177 UBUNTU: upstream stable to v5.4.177 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964628/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962345] Re: Focal update: v5.4.176 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1962345 Title: Focal update: v5.4.176 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed 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: v5.4.176 upstream stable release from git://git.kernel.org/ Bluetooth: refactor malicious adv data check s390/hypfs: include z/VM guests with access control group set scsi: zfcp: Fix failed recovery on gone remote port with non-NPIV FCP devices udf: Restore i_lenAlloc when inode expansion fails udf: Fix NULL ptr deref when converting from inline format PM: wakeup: simplify the output logic of pm_show_wakelocks() tracing/histogram: Fix a potential memory leak for kstrdup() tracing: Don't inc err_log entry count if entry allocation fails fsnotify: fix fsnotify hooks in pseudo filesystems drm/etnaviv: relax submit size limits arm64: errata: Fix exec handling in erratum 1418040 workaround netfilter: nft_payload: do not update layer 4 checksum when mangling fragments serial: 8250: of: Fix mapped region size when using reg-offset property serial: stm32: fix software flow control transfer tty: n_gsm: fix SW flow control encoding/handling tty: Add support for Brainboxes UC cards. usb-storage: Add unusual-devs entry for VL817 USB-SATA bridge usb: common: ulpi: Fix crash in ulpi_match() usb: gadget: f_sourcesink: Fix isoc transfer for USB_SPEED_SUPER_PLUS USB: core: Fix hang in usb_kill_urb by adding memory barriers usb: typec: tcpm: Do not disconnect while receiving VBUS off ucsi_ccg: Check DEV_INT bit only when starting CCG4 net: sfp: ignore disabled SFP node powerpc/32: Fix boot failure with GCC latent entropy plugin i40e: Increase delay to 1 s after global EMP reset i40e: Fix issue when maximum queues is exceeded i40e: Fix queues reservation for XDP i40e: fix unsigned stat widths rpmsg: char: Fix race between the release of rpmsg_ctrldev and cdev rpmsg: char: Fix race between the release of rpmsg_eptdev and cdev scsi: bnx2fc: Flush destroy_work queue before calling bnx2fc_interface_put() ipv6_tunnel: Rate limit warning messages net: fix information leakage in /proc/net/ptype hwmon: (lm90) Mark alert as broken for MAX6646/6647/6649 hwmon: (lm90) Mark alert as broken for MAX6680 ping: fix the sk_bound_dev_if match in ping_lookup ipv4: avoid using shared IP generator for connected sockets hwmon: (lm90) Reduce maximum conversion rate for G781 NFSv4: Handle case where the lookup of a directory fails NFSv4: nfs_atomic_open() can race when looking up a non-regular file net-procfs: show net devices bound packet types drm/msm: Fix wrong size calculation drm/msm/dsi: Fix missing put_device() call in dsi_get_phy drm/msm/dsi: invalid parameter check in msm_dsi_phy_enable ipv6: annotate accesses to fn->fn_sernum NFS: Ensure the server has an up to date ctime before hardlinking NFS: Ensure the server has an up to date ctime before renaming netfilter: conntrack: don't increment invalid counter on NF_REPEAT net: phy: broadcom: hook up soft_reset for BCM54616S phylib: fix potential use-after-free rxrpc: Adjust retransmission backoff hwmon: (lm90) Mark alert as broken for MAX6654 ibmvnic: init ->running_cap_crqs early ibmvnic: don't spin in tasklet drm/msm/hdmi: Fix missing put_device() call in msm_hdmi_get_phy yam: fix a memory leak in yam_siocdevprivate() net: hns3: handle empty unknown interrupt for VF ipv4: raw: lock the socket in raw_bind() ipv4: tcp: send zero IPID in SYNACK messages ipv4: remove sparse error in ip_neigh_gw4() dt-bindings: can: tcan4x5x: fix mram-cfg RX FIFO config fsnotify: invalidate dcache before IN_DELETE event block: Fix wrong offset in bio_truncate() mtd: rawnand: mpc5121: Remove unused variable in ads5121_select_chip() Linux 5.4.176 UBUNTU: upstream stable to v5.4.176 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962330] Re: Focal update: v5.4.175 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1962330 Title: Focal update: v5.4.175 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed 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: v5.4.175 upstream stable release from git://git.kernel.org/ rcu: Tighten rcu_advance_cbs_nowake() checks pinctrl: bcm2835: Drop unused define pinctrl: bcm2835: Refactor platform data pinctrl: bcm2835: Add support for all GPIOs on BCM2711 pinctrl: bcm2835: Match BCM7211 compatible string pinctrl: bcm2835: Add support for wake-up interrupts pinctrl: bcm2835: Change init order for gpio hogs ARM: dts: gpio-ranges property is now required mmc: sdhci-esdhc-imx: disable CMDQ support select: Fix indefinitely sleeping task in poll_schedule_timeout() Linux 5.4.175 UBUNTU: upstream stable to v5.4.175 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962330/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964422] Re: Impish update: upstream stable patchset 2022-03-09
** Changed in: linux (Ubuntu Impish) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964422 Title: Impish update: upstream stable patchset 2022-03-09 Status in linux package in Ubuntu: Invalid Status in linux source package in Impish: Fix Committed 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: upstream stable patchset 2022-03-09 Ported from the following upstream stable releases: v5.10.95, v5.15.18 v5.10.96, v5.15.19 from git://git.kernel.org/ bnx2x: Utilize firmware 7.13.21.0 bnx2x: Invalidate fastpath HSI version for VFs rcu: Tighten rcu_advance_cbs_nowake() checks select: Fix indefinitely sleeping task in poll_schedule_timeout() drm/amdgpu: Use correct VIEWPORT_DIMENSION for DCN2 arm64/bpf: Remove 128MB limit for BPF JIT programs UBUNTU: upstream stable to v5.10.95, v5.15.18 Bluetooth: refactor malicious adv data check net: sfp: ignore disabled SFP node net: stmmac: skip only stmmac_ptp_register when resume from suspend s390/hypfs: include z/VM guests with access control group set bpf: Guard against accessing NULL pt_regs in bpf_get_task_stack() scsi: zfcp: Fix failed recovery on gone remote port with non-NPIV FCP devices udf: Restore i_lenAlloc when inode expansion fails udf: Fix NULL ptr deref when converting from inline format efi: runtime: avoid EFIv2 runtime services on Apple x86 machines PM: wakeup: simplify the output logic of pm_show_wakelocks() tracing/histogram: Fix a potential memory leak for kstrdup() tracing: Don't inc err_log entry count if entry allocation fails ceph: properly put ceph_string reference after async create attempt ceph: set pool_ns in new inode layout for async creates fsnotify: fix fsnotify hooks in pseudo filesystems Revert "KVM: SVM: avoid infinite loop on NPF from bad address" perf/x86/intel/uncore: Fix CAS_COUNT_WRITE issue for ICX drm/etnaviv: relax submit size limits KVM: x86: Update vCPU's runtime CPUID on write to MSR_IA32_XSS netfilter: nft_payload: do not update layer 4 checksum when mangling fragments serial: 8250: of: Fix mapped region size when using reg-offset property serial: stm32: fix software flow control transfer tty: n_gsm: fix SW flow control encoding/handling tty: Add support for Brainboxes UC cards. usb-storage: Add unusual-devs entry for VL817 USB-SATA bridge usb: xhci-plat: fix crash when suspend if remote wake enable usb: common: ulpi: Fix crash in ulpi_match() usb: gadget: f_sourcesink: Fix isoc transfer for USB_SPEED_SUPER_PLUS USB: core: Fix hang in usb_kill_urb by adding memory barriers usb: typec: tcpm: Do not disconnect while receiving VBUS off ucsi_ccg: Check DEV_INT bit only when starting CCG4 jbd2: export jbd2_journal_[grab|put]_journal_head ocfs2: fix a deadlock when commit trans sched/membarrier: Fix membarrier-rseq fence command missing from query bitmask x86/MCE/AMD: Allow thresholding interface updates after init powerpc/32s: Allocate one 256k IBAT instead of two consecutives 128k IBATs powerpc/32s: Fix kasan_init_region() for KASAN powerpc/32: Fix boot failure with GCC latent entropy plugin i40e: Increase delay to 1 s after global EMP reset i40e: Fix issue when maximum queues is exceeded i40e: Fix queues reservation for XDP i40e: Fix for failed to init adminq while VF reset i40e: fix unsigned stat widths usb: roles: fix include/linux/usb/role.h compile issue rpmsg: char: Fix race between the release of rpmsg_ctrldev and cdev rpmsg: char: Fix race between the release of rpmsg_eptdev and cdev scsi: bnx2fc: Flush destroy_work queue before calling bnx2fc_interface_put() ipv6_tunnel: Rate limit warning messages net: fix information leakage in /proc/net/ptype hwmon: (lm90) Mark alert as broken for MAX6646/6647/6649 hwmon: (lm90) Mark alert as broken for MAX6680 ping: fix the sk_bound_dev_if match in ping_lookup ipv4: avoid using shared IP generator for connected sockets hwmon: (lm90) Reduce maximum conversion rate for G781 NFSv4: Handle case where the lookup of a directory fails NFSv4: nfs_atomic_open() can race when looking up a non-regular file net-procfs: show net devices bound packet types drm/msm: Fix wrong size calculation drm/msm/dsi: Fix missing put_device() call in dsi_get_phy drm/msm/dsi: invalid parameter check in
[Kernel-packages] [Bug 1962230] Re: Impish update: upstream stable patchset 2022-02-24
** Changed in: linux (Ubuntu Impish) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1962230 Title: Impish update: upstream stable patchset 2022-02-24 Status in linux package in Ubuntu: Invalid Status in linux source package in Impish: Fix Committed 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: upstream stable patchset 2022-02-24 Ported from the following upstream stable releases: v5.10.94, v5.15.17 from git://git.kernel.org/ KVM: VMX: switch blocked_vcpu_on_cpu_lock to raw spinlock HID: uhid: Fix worker destroying device without any protection HID: wacom: Avoid using stale array indicies to read contact count f2fs: fix to do sanity check in is_alive() nfc: llcp: fix NULL error pointer dereference on sendmsg() after failed bind() mtd: rawnand: gpmi: Add ERR007117 protection for nfc_apply_timings mtd: rawnand: gpmi: Remove explicit default gpmi clock setting for i.MX6 mtd: Fixed breaking list in __mtd_del_partition. mtd: rawnand: davinci: Don't calculate ECC when reading page mtd: rawnand: davinci: Avoid duplicated page read mtd: rawnand: davinci: Rewrite function description x86/gpu: Reserve stolen memory for first integrated Intel GPU tools/nolibc: x86-64: Fix startup code bug tools/nolibc: i386: fix initial stack alignment tools/nolibc: fix incorrect truncation of exit code rtc: cmos: take rtc_lock while reading from CMOS media: v4l2-ioctl.c: readbuffers depends on V4L2_CAP_READWRITE media: flexcop-usb: fix control-message timeouts media: mceusb: fix control-message timeouts media: em28xx: fix control-message timeouts media: cpia2: fix control-message timeouts media: s2255: fix control-message timeouts media: dib0700: fix undefined behavior in tuner shutdown media: redrat3: fix control-message timeouts media: pvrusb2: fix control-message timeouts media: stk1160: fix control-message timeouts media: cec-pin: fix interrupt en/disable handling can: softing_cs: softingcs_probe(): fix memleak on registration failure iio: adc: ti-adc081c: Partial revert of removal of ACPI IDs lkdtm: Fix content of section containing lkdtm_rodata_do_nothing() iommu/io-pgtable-arm-v7s: Add error handle for page table allocation failure gpu: host1x: Add back arm_iommu_detach_device() dma_fence_array: Fix PENDING_ERROR leak in dma_fence_array_signaled() PCI: Add function 1 DMA alias quirk for Marvell 88SE9125 SATA controller mm_zone: add function to check if managed dma zone exists dma/pool: create dma atomic pool only if dma zone has managed pages mm/page_alloc.c: do not warn allocation failure on zone DMA if no managed pages shmem: fix a race between shmem_unused_huge_shrink and shmem_evict_inode drm/ttm: Put BO in its memory manager's lru list Bluetooth: L2CAP: Fix not initializing sk_peer_pid drm/bridge: display-connector: fix an uninitialized pointer in probe() drm: fix null-ptr-deref in drm_dev_init_release() drm/panel: kingdisplay-kd097d04: Delete panel on attach() failure drm/panel: innolux-p079zca: Delete panel on attach() failure drm/rockchip: dsi: Fix unbalanced clock on probe error drm/rockchip: dsi: Hold pm-runtime across bind/unbind drm/rockchip: dsi: Disable PLL clock on bind error drm/rockchip: dsi: Reconfigure hardware on resume() Bluetooth: cmtp: fix possible panic when cmtp_init_sockets() fails clk: bcm-2835: Pick the closest clock rate clk: bcm-2835: Remove rounding up the dividers drm/vc4: hdmi: Set a default HSM rate wcn36xx: ensure pairing of init_scan/finish_scan and start_scan/end_scan wcn36xx: Indicate beacon not connection loss on MISSED_BEACON_IND wcn36xx: Fix DMA channel enable/disable cycle wcn36xx: Release DMA channel descriptor allocations wcn36xx: Put DXE block into reset before freeing memory wcn36xx: populate band before determining rate on RX wcn36xx: fix RX BD rate mapping for 5GHz legacy rates ath11k: Send PPDU_STATS_CFG with proper pdev mask to firmware mtd: hyperbus: rpc-if: Check return value of rpcif_sw_init() media: videobuf2: Fix the size printk format media: atomisp: add missing media_device_cleanup() in atomisp_unregister_entities() media: atomisp: fix punit_ddr_dvfs_enable() argument for mrfld_power up case media: atomisp: fix inverted logic in buffers_needed() media: atomisp: do not use err var when
[Kernel-packages] [Bug 1963901] Re: [22.04 FEAT] [VS2103] Set KVM_CAP_S390_MEM_OP_EXTENSION capability to 211
** Summary changed:
- [22.04 FEAT] [VS2103] KVM: Enable storage key checking for intercepted
instruction - Set KVM_CAP_S390_MEM_OP_EXTENSION capability to 211
+ [22.04 FEAT] [VS2103] Set KVM_CAP_S390_MEM_OP_EXTENSION capability to 211
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1963901
Title:
[22.04 FEAT] [VS2103] Set KVM_CAP_S390_MEM_OP_EXTENSION capability to
211
Status in Ubuntu on IBM z Systems:
New
Status in linux package in Ubuntu:
New
Bug description:
Title:
KVM: Enable storage key checking for intercepted instruction - Set Capability
211
Description:
This patch is required on top of "Bug 193314 - LP#1933179 : [22.04 FEAT]
[VS2103] KVM: Enable storage key checking for intercepted instruction" in order
to set the to set the Capability number to 211
See this merge:
https://git.kernel.org/pub/scm/virt/kvm/kvm.git/commit/?h=next=4dfc4ec2b7f5a3a27d166ac42cf8a583fa2d3284
diff --git a/include/uapi/linux/kvm.h b/include/uapi/linux/kvm.h
index dbc550bbd9fa3..a02bbf8fd0f67 100644
--- a/include/uapi/linux/kvm.h
+++ b/include/uapi/linux/kvm.h
@@ -1140,7 +1140,8 @@ struct kvm_ppc_resize_hpt {
#define KVM_CAP_VM_GPA_BITS 207
#define KVM_CAP_XSAVE2 208
#define KVM_CAP_SYS_ATTRIBUTES 209
-#define KVM_CAP_S390_MEM_OP_EXTENSION 210
+#define KVM_CAP_PPC_AIL_MODE_3 210
+#define KVM_CAP_S390_MEM_OP_EXTENSION 211
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1963901/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937295] Re: [SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU
BTW, would it be possible to include the upstream commit
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/iommu/intel?id=b00833768e170a31af09268f7ab96aecfcca9623)
in Ubuntu 22.04 kernel?
This is another VMD issue. It would be appreciated if it can be merged
in 22.04 kernel.
The commit is also in stable kernel v5.15.27.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1937295
Title:
[SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping
is enabled by IOMMU
Status in subiquity:
Invalid
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Invalid
Status in linux source package in Focal:
In Progress
Status in linux source package in Impish:
Fix Committed
Status in linux source package in Jammy:
In Progress
Bug description:
[Impact]
A hardware partner discovered they were unable to install Ubuntu on
some servers using VROC setups. They point to this issue involving
DMAR that is blocking discovery of the VROC RAID devices:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2565e5b69c44b4e42469afea3cc5a97e74d1ed45
`git bisect` points to this offending commit ee81ee84f873 ("PCI:
vmd: Disable MSI-X remapping when possible"), which disables VMD MSI
remapping. The IOMMU hardware blocks the compatibility format
interrupt request because Interrupt Remapping Enable Status (IRES) and
Extended Interrupt Mode Enable (EIME) are enabled. Please refer to
section "5.1.4 Interrupt-Remapping Hardware Operation" in Intel VT-d
spec.
To fix the issue, VMD driver still enables the interrupt remapping
irrespective of VMD_FEAT_CAN_BYPASS_MSI_REMAP if the IOMMU subsystem
enables the interrupt remapping.
[Fix]
2565e5b69c44 PCI: vmd: Do not disable MSI-X remapping if interrupt
remapping is enabled by IOMMU
[Test Plan]
1. Boot into VRoC controller in uEFI Setup and create a raid10 disk.
2. Install affected Ubuntu release on the RAID10.
3. The system hangs at "Partitions formatting 33%".
[Where problems could occur]
The fix itself is a very small change to drivers/pci/controller/vmd.c
and problems should not occur. The root cause was discovered by the
hardware partner's engineers, who tested and submitted it upstream
where it was accepted and landed in 5.16.
That said, I doubt this will fix 18.04.6 as it would require a respin
to get the patched kernel onto the ISO. 20.04 should pick it up in
ISO in 20.04.5, so there could still be the initial issue since those
ISOs would be lacking the patched kernel.
[Other Info]
As noted, this would need to not only land in the kernel but land in
the kernel in the ISO to resolve the issue in the installation
process. I'll bring this back as far as Focal with the expectation
that while 20.04.4 is too late, it will be present using the GA kernel
in 20.04.5 later on.
*
Original Bug Summary:
A hardware partner has been testing 18.04 subiquity images on their
servers with VROC enabled and configured in a RAID 10 setup.
In their own words:
Steps to reproduce:
1. Boot into VRoC controller in uEFI Setup and create a raid10
disk.
2. Install Ubuntu 18.04.5 on the RAID10.
3. The system hangs at "Partitions formatting 33%".
After looking at the launchpad
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/), the
fix was included in the updated kernel.
[Quotes from the launchpad]
The released kernels are:
Hirsute: 5.11.0-22-generic
Groovy: 5.8.0-59-generic
Focal: 5.4.0-77-generic
Bionic: 4.15.0-147-generic
I've asked them to also confirm this on 20.04.2, and check that
20.04.3 dailies fix the issue.
It is at least a very reasonable hypothesis that this will also break
on all current ISO installs as none of them are respun once released
to include updated SRUs in the installation media. This currently
affects 20.04.2 but that will be resolved shortly when 20.04.3
releases as the GA and HWE kernels in that image should have the SRU
that fixes this issue. However, 18.04 has no further releases, and
even the 18.04.5 daily-live and daily images on cdimages.ubuntu.com
are not built after 18.04.5 was released.
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1937295/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1963901] Re: [22.04 FEAT] [VS2103] KVM: Enable storage key checking for intercepted instruction - Set KVM_CAP_S390_MEM_OP_EXTENSION capability to 211
Thanks for the quick answer.
Ok, so in this case I'll try to keep the patch as small as possible, means only
make sure it's properly in include/uapi/linux/kvm.h.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1963901
Title:
[22.04 FEAT] [VS2103] KVM: Enable storage key checking for intercepted
instruction - Set KVM_CAP_S390_MEM_OP_EXTENSION capability to 211
Status in Ubuntu on IBM z Systems:
New
Status in linux package in Ubuntu:
New
Bug description:
Title:
KVM: Enable storage key checking for intercepted instruction - Set Capability
211
Description:
This patch is required on top of "Bug 193314 - LP#1933179 : [22.04 FEAT]
[VS2103] KVM: Enable storage key checking for intercepted instruction" in order
to set the to set the Capability number to 211
See this merge:
https://git.kernel.org/pub/scm/virt/kvm/kvm.git/commit/?h=next=4dfc4ec2b7f5a3a27d166ac42cf8a583fa2d3284
diff --git a/include/uapi/linux/kvm.h b/include/uapi/linux/kvm.h
index dbc550bbd9fa3..a02bbf8fd0f67 100644
--- a/include/uapi/linux/kvm.h
+++ b/include/uapi/linux/kvm.h
@@ -1140,7 +1140,8 @@ struct kvm_ppc_resize_hpt {
#define KVM_CAP_VM_GPA_BITS 207
#define KVM_CAP_XSAVE2 208
#define KVM_CAP_SYS_ATTRIBUTES 209
-#define KVM_CAP_S390_MEM_OP_EXTENSION 210
+#define KVM_CAP_PPC_AIL_MODE_3 210
+#define KVM_CAP_S390_MEM_OP_EXTENSION 211
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1963901/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962551] Re: unshare test in ubuntu_stress_smoke_tests cause "BUG: unable to handle page fault for address" on F-oem-5.14 with Intel node vought
*** This bug is a duplicate of bug 1959215 *** https://bugs.launchpad.net/bugs/1959215 ** This bug has been marked a duplicate of bug 1959215 unshare test in ubuntu_stress_smoke_tests triggers "BUG: unable to handle page fault for address: 1cc8" on Impish with node vought -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1962551 Title: unshare test in ubuntu_stress_smoke_tests cause "BUG: unable to handle page fault for address" on F-oem-5.14 with Intel node vought Status in Stress-ng: New Status in ubuntu-kernel-tests: New Status in linux-oem-5.14 package in Ubuntu: New Bug description: Issue found on Focal OEM-5.14.0-1025.27 with Intel node vought The sut will stop responding after this, and the test will be killed in the end with the test timeout setting. stress-ng test suite HEAD SHA1: 48be8ff Mar 1 09:07:00 vought stress-ng: system: 'vought' Linux 5.14.0-1025-oem #27-Ubuntu SMP Thu Feb 24 09:13:19 UTC 2022 x86_64 Mar 1 09:07:00 vought stress-ng: memory (MB): total 359934.79, free 353583.48, shared 2.77, buffer 238.38, swap 9215.99, free swap 9214.70 Mar 1 09:07:00 vought stress-ng: info: [195104] setting to a 5 second run per stressor Mar 1 09:07:00 vought stress-ng: info: [195104] dispatching hogs: 4 unshare Mar 1 09:07:00 vought kernel: [ 1061.465476] BUG: unable to handle page fault for address: 1cc8 Mar 1 09:07:00 vought kernel: [ 1061.465554] #PF: supervisor read access in kernel mode Mar 1 09:07:00 vought kernel: [ 1061.465596] #PF: error_code(0x) - not-present page Mar 1 09:07:00 vought kernel: [ 1061.465637] PGD 0 P4D 0 Mar 1 09:07:00 vought kernel: [ 1061.465663] Oops: [#1] SMP NOPTI Mar 1 09:07:00 vought kernel: [ 1061.465698] CPU: 85 PID: 196061 Comm: stress-ng Tainted: P O 5.14.0-1025-oem #27-Ubuntu Mar 1 09:07:00 vought kernel: [ 1061.465771] Hardware name: Intel Corporation S2600WFD/S2600WFD, BIOS SE5C620.86B.0D.01.0395.022720191340 02/27/2019 Mar 1 09:07:00 vought kernel: [ 1061.465846] RIP: 0010:__alloc_pages+0x125/0x310 Mar 1 09:07:00 vought kernel: [ 1061.465895] Code: ff ff 84 c0 0f 85 1b 01 00 00 44 89 e0 48 8b 55 b0 8b 75 c4 c1 e8 0c 48 8b 7d a8 83 e0 01 88 45 c8 48 85 d2 0f 85 3e 01 00 00 <3b> 77 08 0f 82 35 01 00 00 48 89 7d b8 48 8b 07 44 89 e2 81 e2 00 Mar 1 09:07:00 vought kernel: [ 1061.466030] RSP: 0018:b66fac707b50 EFLAGS: 00010246 Mar 1 09:07:00 vought kernel: [ 1061.466074] RAX: RBX: RCX: Mar 1 09:07:00 vought kernel: [ 1061.466128] RDX: RSI: 0002 RDI: 1cc0 Mar 1 09:07:00 vought kernel: [ 1061.466182] RBP: b66fac707ba8 R08: R09: Mar 1 09:07:00 vought kernel: [ 1061.466236] R10: 0002 R11: 94438d0bb730 R12: 00052cc0 Mar 1 09:07:00 vought kernel: [ 1061.466290] R13: 0002 R14: 00052cc0 R15: 0001 Mar 1 09:07:00 vought kernel: [ 1061.466343] FS: 7fbf1cef5380() GS:94438d08() knlGS: Mar 1 09:07:00 vought kernel: [ 1061.466406] CS: 0010 DS: ES: CR0: 80050033 Mar 1 09:07:00 vought kernel: [ 1061.466452] CR2: 1cc8 CR3: 00bd8869a002 CR4: 007706e0 Mar 1 09:07:00 vought kernel: [ 1061.466508] DR0: DR1: DR2: Mar 1 09:07:00 vought kernel: [ 1061.466562] DR3: DR6: fffe0ff0 DR7: 0400 Mar 1 09:07:00 vought kernel: [ 1061.466616] PKRU: 5554 Mar 1 09:07:00 vought kernel: [ 1061.466640] Call Trace: Mar 1 09:07:00 vought kernel: [ 1061.42] Mar 1 09:07:00 vought kernel: [ 1061.466687] kmalloc_large_node+0x45/0xb0 Mar 1 09:07:00 vought kernel: [ 1061.466729] __kmalloc_node+0x430/0x4f0 Mar 1 09:07:00 vought kernel: [ 1061.466766] ? queue_delayed_work_on+0x36/0x50 Mar 1 09:07:00 vought kernel: [ 1061.466810] kvmalloc_node+0x5c/0x90 Mar 1 09:07:00 vought kernel: [ 1061.466843] expand_shrinker_info+0xfa/0x230 Mar 1 09:07:00 vought kernel: [ 1061.466884] prealloc_shrinker+0xba/0x100 Mar 1 09:07:00 vought kernel: [ 1061.468360] alloc_super+0x2c3/0x340 Mar 1 09:07:00 vought kernel: [ 1061.469786] ? __fput_sync+0x30/0x30 Mar 1 09:07:00 vought kernel: [ 1061.471204] sget_fc+0x74/0x2e0 Mar 1 09:07:00 vought kernel: [ 1061.472564] ? compare_single+0x10/0x10 Mar 1 09:07:00 vought kernel: [ 1061.473880] ? mqueue_create+0x20/0x20 Mar 1 09:07:00 vought kernel: [ 1061.475139] vfs_get_super+0x3d/0x100 Mar 1 09:07:00 vought kernel: [ 1061.476351] get_tree_keyed+0x1d/0x20 Mar 1 09:07:00 vought kernel: [ 1061.477314] mqueue_get_tree+0x1c/0x20 Mar 1 09:07:00 vought kernel: [ 1061.478060]
[Kernel-packages] [Bug 1959215] Re: unshare test in ubuntu_stress_smoke_tests triggers "BUG: unable to handle page fault for address: 0000000000001cc8" on Impish with node vought
In a duplicated report (bug 1962551), Colin mentioned that this could be a kernel issue. This issue can be found on focal OEM-5.14.0-1025.27 with Intel node vought, also Jammy 5.15.0-22-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959215 Title: unshare test in ubuntu_stress_smoke_tests triggers "BUG: unable to handle page fault for address: 1cc8" on Impish with node vought Status in Stress-ng: New Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: Issue found on Intel node "vought" with: * 5.13.0-28.31 * 5.13.0-27 * And possibly the 5.13.0-23 from the last cycle (this test didn't finish properly and marked as "Incomplete" back then, just like this cycle). For more earlier Impish kernels, this system was not tested with this test on them. The test will hang with unshare test in ubuntu_stress_smoke_tests: 12:39:39 DEBUG| [stdout] udp RETURNED 0 12:39:39 DEBUG| [stdout] udp PASSED 12:39:39 DEBUG| [stdout] udp-flood STARTING 12:39:41 DEBUG| [stdout] udp-flood RETURNED 0 12:39:41 DEBUG| [stdout] udp-flood PASSED 12:39:41 DEBUG| [stdout] unshare STARTING (Test hangs here) And eventually the test will be killed because of the timeout setting. stress-ng Test suite HEAD SHA1: b81116c Error can be found in dmesg: [ 2371.109961] BUG: unable to handle page fault for address: 1cc8 [ 2371.110074] #PF: supervisor read access in kernel mode [ 2371.114323] #PF: error_code(0x) - not-present page [ 2371.119931] PGD 0 P4D 0 [ 2371.125257] Oops: [#1] SMP NOPTI [ 2371.129247] CPU: 51 PID: 207256 Comm: stress-ng Tainted: P O 5.13.0-27-generic #29-Ubuntu [ 2371.133203] Hardware name: Intel Corporation S2600WFD/S2600WFD, BIOS SE5C620.86B.0D.01.0395.022720191340 02/27/2019 [ 2371.135887] RIP: 0010:__next_zones_zonelist+0x6/0x50 [ 2371.138525] Code: d0 0f 4e d0 3d ff 03 00 00 7f 0d 48 63 d2 5d 48 8b 04 d5 60 e5 35 af c3 31 c0 5d c3 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 <8b> 4f 08 48 89 f8 48 89 e5 48 85 d2 75 10 eb 1d 48 63 49 50 48 0f [ 2371.143813] RSP: 0018:a9c8b399fac0 EFLAGS: 00010282 [ 2371.146078] RAX: RBX: RCX: [ 2371.148293] RDX: 9c98e894ea98 RSI: 0002 RDI: 1cc0 [ 2371.150477] RBP: a9c8b399fb28 R08: R09: [ 2371.152650] R10: 0002 R11: d9bfbfcc5600 R12: 00052cc0 [ 2371.154778] R13: 0002 R14: 0001 R15: 00152cc0 [ 2371.156876] FS: 7fcbd141d740() GS:9cc14ccc() knlGS: [ 2371.158936] CS: 0010 DS: ES: CR0: 80050033 [ 2371.160958] CR2: 1cc8 CR3: 00059f292001 CR4: 007706e0 [ 2371.162950] DR0: DR1: DR2: [ 2371.164888] DR3: DR6: fffe0ff0 DR7: 0400 [ 2371.166811] PKRU: 5554 [ 2371.168694] Call Trace: [ 2371.170544] ? __alloc_pages+0x2f1/0x330 [ 2371.172386] kmalloc_large_node+0x45/0xb0 [ 2371.174222] __kmalloc_node+0x276/0x300 [ 2371.176036] ? queue_delayed_work_on+0x39/0x60 [ 2371.177853] kvmalloc_node+0x5a/0x90 [ 2371.179622] expand_one_shrinker_info+0x82/0x190 [ 2371.181382] prealloc_shrinker+0x175/0x1d0 [ 2371.183091] alloc_super+0x2bf/0x330 [ 2371.184764] ? __fput_sync+0x30/0x30 [ 2371.186384] sget_fc+0x74/0x2e0 [ 2371.187951] ? set_anon_super+0x50/0x50 [ 2371.189473] ? mqueue_create+0x20/0x20 [ 2371.190944] get_tree_keyed+0x34/0xd0 [ 2371.192363] mqueue_get_tree+0x1c/0x20 [ 2371.193734] vfs_get_tree+0x2a/0xc0 [ 2371.195105] fc_mount+0x13/0x50 [ 2371.196409] mq_init_ns+0x10a/0x1b0 [ 2371.197667] copy_ipcs+0x130/0x220 [ 2371.198899] create_new_namespaces+0xa6/0x2e0 [ 2371.200113] unshare_nsproxy_namespaces+0x5a/0xb0 [ 2371.201303] ksys_unshare+0x1db/0x3c0 [ 2371.202480] __x64_sys_unshare+0x12/0x20 [ 2371.203649] do_syscall_64+0x61/0xb0 [ 2371.204804] ? exit_to_user_mode_loop+0xec/0x160 [ 2371.205966] ? exit_to_user_mode_prepare+0x37/0xb0 [ 2371.207102] ? syscall_exit_to_user_mode+0x27/0x50 [ 2371.208222] ? __x64_sys_close+0x11/0x40 [ 2371.209336] ? do_syscall_64+0x6e/0xb0 [ 2371.210438] ? asm_exc_page_fault+0x8/0x30 [ 2371.211545] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 2371.212641] RIP: 0033:0x7fcbd1562c4b [ 2371.213698] Code: 73 01 c3 48 8b 0d e5 e1 0e 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa b8 10 01 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d b5 e1 0e 00 f7 d8 64 89 01 48 [ 2371.215851] RSP: 002b:7ffc5d8eb878 EFLAGS: 0246 ORIG_RAX: 0110 [
[Kernel-packages] [Bug 1818811] Re: The swapfile on the Btrfs file system is not activated
This bug still remains in the latest Xubuntu CORE 22.04 (xubuntu-22.04-core-amd64.iso from the end of Feb 2022). During boot process, I can briefly see "[FAILED] Failed to activate swap /swapfile" and "[DEPEND] Dependency failed for Swaps". When I execute "sudo dmesg | grep -i swap", I get some more BTRFS warnings and swap-related failures: [4.121985] systemd[1]: Activating swap /swapfile... [4.136293] BTRFS warning (device sda6): swapfile must not be copy-on-write [4.160578] systemd[1]: swapfile.swap: Swap process exited, code=exited, status=255/EXCEPTION [4.160586] systemd[1]: swapfile.swap: Failed with result 'exit-code'. [4.161012] systemd[1]: Failed to activate swap /swapfile. [4.161100] systemd[1]: Dependency failed for Swaps. [4.161145] systemd[1]: swap.target: Job swap.target/start failed with result 'dependency'. [6.902501] BTRFS warning (device sda6): swapfile must not be copy-on-write -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818811 Title: The swapfile on the Btrfs file system is not activated Status in Ubuntu MATE: New Status in linux package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Confirmed Bug description: From 5.0 kernel is implemented support for the swapfile on Btrfs (https://patchwork.kernel.org/cover/10584515/), today arrived on the repositories of Ubuntu 19.04 proposed kernel 5.0, but the swapfile is not activated. Log: mar 06 11:17:55 notebook-Lenovo-V110 kernel: BTRFS warning (device sda1): swapfile must not be copy-on-write mar 06 11:17:55 notebook-Lenovo-V110 swapon[517]: swapon: /swapfile: swapon failed: Argomento non valido mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: Activating swap /swapfile... mar 06 11:17:57 notebook-Lenovo-V110 swapon[916]: swapon: /swapfile: swapon failed: Argomento non valido mar 06 11:17:57 notebook-Lenovo-V110 kernel: BTRFS warning (device sda1): swapfile must not be copy-on-write mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: swapfile.swap: Swap process exited, code=exited, status=255/EXCEPTION mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: swapfile.swap: Failed with result 'exit-code'. mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: Failed to activate swap /swapfile. mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: Activating swap /swapfile... mar 06 11:17:57 notebook-Lenovo-V110 kernel: BTRFS warning (device sda1): swapfile must not be copy-on-write mar 06 11:17:57 notebook-Lenovo-V110 swapon[1006]: swapon: /swapfile: swapon failed: Argomento non valido mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: swapfile.swap: Swap process exited, code=exited, status=255/EXCEPTION mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: swapfile.swap: Failed with result 'exit-code'. mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: Failed to activate swap /swapfile. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-generic 5.0.0.7.8 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: emanu 1744 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 11:19:52 2019 InstallationDate: Installed on 2019-01-30 (34 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 13d3:5745 IMC Networks Bus 001 Device 002: ID 10c4:8105 Cygnal Integrated Products, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80TL ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-7-generic root=UUID=91fdf6c0-1b5d-4bb5-9aa4-aeb946236b8a ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.177 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 1KCN46WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V110-15ISK dmi.modalias:
[Kernel-packages] [Bug 1962515] Re: Intermittent AX211 iwlwifi RT ucode init failed -110 at boot
verified linux-firmware/focal-proposed version 1.187.29. ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1962515 Title: Intermittent AX211 iwlwifi RT ucode init failed -110 at boot Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Won't Fix Status in linux source package in Impish: New Status in linux-firmware source package in Impish: New Status in linux-oem-5.14 source package in Impish: New Status in linux source package in Jammy: In Progress Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] AX211 might fail to load -64 firmware on some platforms. iwlwifi :00:14.3: Failed to start RT ucode: -110 [Fix] This can only be fixed in the firmware, and currently v5.14 kernel has FW API 64, v5.15 has 66 and only v5.16 or above has 67. [Test Case] Run checkbox reboot stress tests to try trigger this issue: $ checkbox-cli run com.canonical.certification::stress/reboot [Where problems could occur] The source commit originally contains 67 fw for several models, and yet AX211, which taks iwlwifi-so-a0-gf-a0-*.ucode and its corresponding pnvm file, is the only known problematic model affected. This pull request imports only the needed files to eliminate the possibility of regression as possible. == original bug report == [ 5.675835] iwlwifi :00:14.3: enabling device ( -> 0002) [ 5.693214] iwlwifi :00:14.3: api flags index 2 larger than supported by driver [ 5.693277] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.25 [ 5.698065] iwlwifi :00:14.3: loaded firmware version 64.97bbee0a.0 so-a0-gf-a0-64.ucode op_mode iwlmvm [ 5.933114] iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6E AX211 160MHz, REV=0x370 [ 6.101350] iwlwifi :00:14.3: loaded PNVM version 0x4b50f925 [ 6.113388] iwlwifi :00:14.3: Detected RF GF, rfid=0x2010d000 [ 6.181309] iwlwifi :00:14.3: base HW address: 7c:50:79:c9:29:67 [ 6.201398] iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0 [ 7.396811] iwlwifi :00:14.3: SecBoot CPU1 Status: 0x71f7, CPU2 Status: 0xb03 [ 7.396859] iwlwifi :00:14.3: UMAC PC: 0xc0081906 [ 7.396912] iwlwifi :00:14.3: LMAC PC: 0x1541c [ 7.396914] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [ 7.399116] iwlwifi :00:14.3: Loaded firmware version: 64.97bbee0a.0 so-a0-gf-a0-64.ucode [ 7.399119] iwlwifi :00:14.3: 0x | ADVANCED_SYSASSERT [ 7.399121] iwlwifi :00:14.3: 0x | trm_hw_status0 [ 7.399123] iwlwifi :00:14.3: 0x | trm_hw_status1 [ 7.399124] iwlwifi :00:14.3: 0x | branchlink2 [ 7.399125] iwlwifi :00:14.3: 0x | interruptlink1 [ 7.399127] iwlwifi :00:14.3: 0x | interruptlink2 [ 7.399128] iwlwifi :00:14.3: 0x | data1 [ 7.399129] iwlwifi :00:14.3: 0x | data2 [ 7.399130] iwlwifi :00:14.3: 0x | data3 [ 7.399132] iwlwifi :00:14.3: 0x | beacon time [ 7.399133] iwlwifi :00:14.3: 0x | tsf low [ 7.399134] iwlwifi :00:14.3: 0x | tsf hi [ 7.399135] iwlwifi :00:14.3: 0x | time gp1 [ 7.399136] iwlwifi :00:14.3: 0x | time gp2 [ 7.399137] iwlwifi :00:14.3: 0x | uCode revision type [ 7.399139] iwlwifi :00:14.3: 0x | uCode version major [ 7.399140] iwlwifi :00:14.3: 0x | uCode version minor [ 7.399141] iwlwifi :00:14.3: 0x | hw version [ 7.399143] iwlwifi :00:14.3: 0x | board version [ 7.399144] iwlwifi :00:14.3: 0x | hcmd [ 7.399145] iwlwifi :00:14.3: 0x | isr0 [ 7.399146] iwlwifi :00:14.3: 0x | isr1 [ 7.399147] iwlwifi :00:14.3: 0x | isr2 [ 7.399148] iwlwifi :00:14.3: 0x | isr3 [ 7.399149] iwlwifi :00:14.3: 0x | isr4 [ 7.399150] iwlwifi :00:14.3: 0x | last cmd Id [ 7.399152] iwlwifi :00:14.3: 0x | wait_event [ 7.399153] iwlwifi :00:14.3: 0x | l2p_control [ 7.399154] iwlwifi :00:14.3: 0x | l2p_duration [ 7.399155] iwlwifi :00:14.3: 0x | l2p_mhvalid [ 7.399157] iwlwifi :00:14.3: 0x | l2p_addr_match [ 7.399158] iwlwifi :00:14.3: 0x | lmpm_pmg_sel [ 7.399159] iwlwifi :00:14.3: 0x | timestamp [ 7.399161] iwlwifi
[Kernel-packages] [Bug 1964756] [NEW] The nvidia debian/rules mis-compiles Modaliases
Public bug reported: Although adding support GPU list here: https://github.com/tseliot/nvidia-graphics-drivers/commit/d2533550bc88ef00d6a56f71c4c09e43026a93d7 They are only show in "Pmaliases:" but "Modaliases:". ** Affects: oem-priority Importance: Critical Assignee: jeremyszu (os369510) Status: Confirmed ** Affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Tags: jiayi oem-prioirty oem-priority ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/1964756 Title: The nvidia debian/rules mis-compiles Modaliases Status in OEM Priority Project: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: Although adding support GPU list here: https://github.com/tseliot/nvidia-graphics-drivers/commit/d2533550bc88ef00d6a56f71c4c09e43026a93d7 They are only show in "Pmaliases:" but "Modaliases:". To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1964756/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1963901] Comment bridged from LTC Bugzilla
--- Comment From cborn...@de.ibm.com 2022-03-14 04:15 EDT---
(In reply to comment #8)
> @IBM Am I right assuming that the KVM_CAP_S390_MEM_OP_EXTENSION capability
> level needs to be set to 211 in 'include/uapi/linux/kvm.h', but also in
> 'tools/include/uapi/linux/kvm.h'?
> (That is at least where I see other settings aligned.)
This file in synced lazily upstream for kernel tools like perf. It does
does not hurt to be added there but it is not stricly necessary. So if
its in there, fix it up, if its not in there no need to add it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1963901
Title:
[22.04 FEAT] [VS2103] KVM: Enable storage key checking for intercepted
instruction - Set KVM_CAP_S390_MEM_OP_EXTENSION capability to 211
Status in Ubuntu on IBM z Systems:
New
Status in linux package in Ubuntu:
New
Bug description:
Title:
KVM: Enable storage key checking for intercepted instruction - Set Capability
211
Description:
This patch is required on top of "Bug 193314 - LP#1933179 : [22.04 FEAT]
[VS2103] KVM: Enable storage key checking for intercepted instruction" in order
to set the to set the Capability number to 211
See this merge:
https://git.kernel.org/pub/scm/virt/kvm/kvm.git/commit/?h=next=4dfc4ec2b7f5a3a27d166ac42cf8a583fa2d3284
diff --git a/include/uapi/linux/kvm.h b/include/uapi/linux/kvm.h
index dbc550bbd9fa3..a02bbf8fd0f67 100644
--- a/include/uapi/linux/kvm.h
+++ b/include/uapi/linux/kvm.h
@@ -1140,7 +1140,8 @@ struct kvm_ppc_resize_hpt {
#define KVM_CAP_VM_GPA_BITS 207
#define KVM_CAP_XSAVE2 208
#define KVM_CAP_SYS_ATTRIBUTES 209
-#define KVM_CAP_S390_MEM_OP_EXTENSION 210
+#define KVM_CAP_PPC_AIL_MODE_3 210
+#define KVM_CAP_S390_MEM_OP_EXTENSION 211
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1963901/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1963901] Re: [22.04 FEAT] [VS2103] KVM: Enable storage key checking for intercepted instruction - Set KVM_CAP_S390_MEM_OP_EXTENSION capability to 211
@IBM Am I right assuming that the KVM_CAP_S390_MEM_OP_EXTENSION capability
level needs to be set to 211 in 'include/uapi/linux/kvm.h', but also in
'tools/include/uapi/linux/kvm.h'?
(That is at least where I see other settings aligned.)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1963901
Title:
[22.04 FEAT] [VS2103] KVM: Enable storage key checking for intercepted
instruction - Set KVM_CAP_S390_MEM_OP_EXTENSION capability to 211
Status in Ubuntu on IBM z Systems:
New
Status in linux package in Ubuntu:
New
Bug description:
Title:
KVM: Enable storage key checking for intercepted instruction - Set Capability
211
Description:
This patch is required on top of "Bug 193314 - LP#1933179 : [22.04 FEAT]
[VS2103] KVM: Enable storage key checking for intercepted instruction" in order
to set the to set the Capability number to 211
See this merge:
https://git.kernel.org/pub/scm/virt/kvm/kvm.git/commit/?h=next=4dfc4ec2b7f5a3a27d166ac42cf8a583fa2d3284
diff --git a/include/uapi/linux/kvm.h b/include/uapi/linux/kvm.h
index dbc550bbd9fa3..a02bbf8fd0f67 100644
--- a/include/uapi/linux/kvm.h
+++ b/include/uapi/linux/kvm.h
@@ -1140,7 +1140,8 @@ struct kvm_ppc_resize_hpt {
#define KVM_CAP_VM_GPA_BITS 207
#define KVM_CAP_XSAVE2 208
#define KVM_CAP_SYS_ATTRIBUTES 209
-#define KVM_CAP_S390_MEM_OP_EXTENSION 210
+#define KVM_CAP_PPC_AIL_MODE_3 210
+#define KVM_CAP_S390_MEM_OP_EXTENSION 211
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1963901/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1963901] Re: [22.04 FEAT] [VS2103] KVM: Enable storage key checking for intercepted instruction - Set KVM_CAP_S390_MEM_OP_EXTENSION capability to 211
** Summary changed:
- [22.04 FEAT] [VS2103] KVM: Enable storage key checking for intercepted
instruction - Set Capability 211
+ [22.04 FEAT] [VS2103] KVM: Enable storage key checking for intercepted
instruction - Set KVM_CAP_S390_MEM_OP_EXTENSION capability to 211
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1963901
Title:
[22.04 FEAT] [VS2103] KVM: Enable storage key checking for intercepted
instruction - Set KVM_CAP_S390_MEM_OP_EXTENSION capability to 211
Status in Ubuntu on IBM z Systems:
New
Status in linux package in Ubuntu:
New
Bug description:
Title:
KVM: Enable storage key checking for intercepted instruction - Set Capability
211
Description:
This patch is required on top of "Bug 193314 - LP#1933179 : [22.04 FEAT]
[VS2103] KVM: Enable storage key checking for intercepted instruction" in order
to set the to set the Capability number to 211
See this merge:
https://git.kernel.org/pub/scm/virt/kvm/kvm.git/commit/?h=next=4dfc4ec2b7f5a3a27d166ac42cf8a583fa2d3284
diff --git a/include/uapi/linux/kvm.h b/include/uapi/linux/kvm.h
index dbc550bbd9fa3..a02bbf8fd0f67 100644
--- a/include/uapi/linux/kvm.h
+++ b/include/uapi/linux/kvm.h
@@ -1140,7 +1140,8 @@ struct kvm_ppc_resize_hpt {
#define KVM_CAP_VM_GPA_BITS 207
#define KVM_CAP_XSAVE2 208
#define KVM_CAP_SYS_ATTRIBUTES 209
-#define KVM_CAP_S390_MEM_OP_EXTENSION 210
+#define KVM_CAP_PPC_AIL_MODE_3 210
+#define KVM_CAP_S390_MEM_OP_EXTENSION 211
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1963901/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1963701] Re: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine
This issue has been fixed in 510.54. For installed incorrect version, please see comment#16. ** Also affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Changed in: oem-priority Status: Confirmed => Fix Released ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: New => Fix Released ** No longer affects: gdm3 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu. https://bugs.launchpad.net/bugs/1963701 Title: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine Status in OEM Priority Project: Fix Released Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Bug description: [Steps to reproduce] 1. Have an I+N desktop. 2. Attach monitor to dGPU (nvidia) 3. install jammy daily build with enable third-party (to install nvidia-510) 4. dist-upgrade 5. reboot the system and make sure the system starts with Wayland [Expected result] System launch gdm login screen without problem [Actual result] System stuck with blackscreen [Other information] $ systemctl list-jobs JOB UNIT TYPE STATE 140 system-getty.slice start waiting 2 multi-user.targetstart waiting 1 graphical.target start waiting 165 plymouth-quit-wait.service start running 8 setvtrgb.service start waiting 110 systemd-update-utmp-runlevel.service start waiting 6 jobs listed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 41.3-1ubuntu2 [modified: lib/udev/rules.d/61-gdm.rules] ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Mar 5 00:15:24 2022 InstallationDate: Installed on 2022-01-20 (43 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220109) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2022-03-04T20:36:36.997559 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1963701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964542] Re: [nvidia] One monitor remains black on startup or resume from sleep
** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1964542 Title: [nvidia] One monitor remains black on startup or resume from sleep Status in mutter package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Bug description: when the pc starts up or comes out of sleep mode the primary screen remains black. To reactivate it I have to go through screen clone apply and redo join the screens and apply. Thanks Ps: have done several research and attempt, without success, on the internet including in your forums. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.103.01 Thu Jan 6 12:10:04 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 10 18:45:17 2022 DistUpgraded: 2022-02-23 17:47:37,810 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu DkmsStatus: nvidia, 470.103.01, 5.13.0-32-generic, x86_64: installed nvidia, 470.103.01, 5.13.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GM206 [GeForce GTX 960] [3842:2966] InstallationDate: Installed on 2022-02-15 (23 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUS All Series ProcEnviron: LANGUAGE=fr_CA:fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=c8e08c76-0308-495c-8c5a-83f9aa24b1a0 ro quiet splash nomodeset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2022-02-23 (15 days ago) dmi.bios.date: 07/10/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4101 dmi.board.asset.tag: Default string dmi.board.name: SABERTOOTH X99 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4101:bd07/10/2019:br5.11:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1964542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964586] Re: Mellanox Network Driver Bug Laser Wavelength
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-5.13 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1964586 Title: Mellanox Network Driver Bug Laser Wavelength Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: Kernel Version 5.13.0 introduced a new bug. This bug was eventually fixed on Kernel Version 5.15.20. This Bug causes Mellanox Networking Adapters to a lot of errors, when connected over fibre. The standard laser wavelength of this transceivers is 850nm, with this error it increases to 22560nm and invalid information on "Vendor SN" etc. Initial change on Kernel 5.13.0 -> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e19b0a3474ab9ef90dd110af9f39fc87329755f1 Final fix on this Problem -> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=60c48abf62ca57428f66ed25b982593b57c656c3 Applying this fix to Kernel 5.13.0 solves the problem. We wrote an article on this matter with further details (in German) -> https://www.thomas- krenn.com/de/wiki/Mellanox_ConnectX-4/5/6_Bitfehler_ab_Linux_Kernel_5.13 Would it be possible to backport that fix? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-35-generic 5.13.0-35.40~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Mar 11 10:48:08 2022 InstallationDate: Installed on 2022-03-11 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223.1) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1964586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883919] Re: nvidia-kernel-source-440 440.82+really.440.64-0ubuntu6: nvidia kernel module failed to build
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1883919 Title: nvidia-kernel-source-440 440.82+really.440.64-0ubuntu6: nvidia kernel module failed to build Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: Internal errors keep showing up ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-440 440.82+really.440.64-0ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.4.0-37-generic Date: Tue Jun 16 11:38:14 2020 Dependencies: InstallationDate: Installed on 2019-10-23 (238 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageVersion: 440.82+really.440.64-0ubuntu6 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: nvidia-graphics-drivers-440 Title: nvidia-kernel-source-440 440.82+really.440.64-0ubuntu6: nvidia kernel module failed to build UpgradeStatus: Upgraded to focal on 2020-06-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1883919/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964748] Re: Cirrus audio support [1028:0BB5] & [1028:0BB6]
** Tags added: oem-priority originate-from-1964057 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1964748 Title: Cirrus audio support [1028:0BB5] & [1028:0BB6] Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] These 2 IDs([1028:0BB5],[1028:0BB6]) are required to be added into cs8409 quirk to get it work [Fix] Cherry picked below commit from v5.17-rc1 2a1355f0bf41 ALSA: hda/cs8409: Add new Warlock SKUs to patch_cs8409 [Test] Verified on Dell machines which contains this Cirrus audio. [Where problems could occur] Adding 2 IDs into quirk is trivial, and should not introduce any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1964748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964748] [NEW] Cirrus audio support [1028:0BB5] & [1028:0BB6]
Public bug reported: [Impact] These 2 IDs([1028:0BB5],[1028:0BB6]) are required to be added into cs8409 quirk to get it work [Fix] Cherry picked below commit from v5.17-rc1 2a1355f0bf41 ALSA: hda/cs8409: Add new Warlock SKUs to patch_cs8409 [Test] Verified on Dell machines which contains this Cirrus audio. [Where problems could occur] Adding 2 IDs into quirk is trivial, and should not introduce any regression. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-1964057 somerville ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => AceLan Kao (acelankao) ** Description changed: [Impact] + These 2 IDs([1028:0BB5],[1028:0BB6]) are required to be added into cs8409 quirk to get it work [Fix] + Cherry picked below commit from v5.17-rc1 + 2a1355f0bf41 ALSA: hda/cs8409: Add new Warlock SKUs to patch_cs8409 [Test] + Verified on Dell machines which contains this Cirrus audio. [Where problems could occur] + Adding 2 IDs into quirk is trivial, and should not introduce any regression. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1964748 Title: Cirrus audio support [1028:0BB5] & [1028:0BB6] Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] These 2 IDs([1028:0BB5],[1028:0BB6]) are required to be added into cs8409 quirk to get it work [Fix] Cherry picked below commit from v5.17-rc1 2a1355f0bf41 ALSA: hda/cs8409: Add new Warlock SKUs to patch_cs8409 [Test] Verified on Dell machines which contains this Cirrus audio. [Where problems could occur] Adding 2 IDs into quirk is trivial, and should not introduce any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1964748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
