[Kernel-packages] [Bug 1986852] Re: Support SMBIOS 3.4 and 3.5 in Jammy for Hardware Enablement
Hello Mauricio, or anyone else affected,
Accepted dmidecode into jammy-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/dmidecode/3.3-3ubuntu0.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: dmidecode (Ubuntu Jammy)
Status: Invalid => Fix Committed
** Tags added: verification-needed verification-needed-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
https://bugs.launchpad.net/bugs/1986852
Title:
Support SMBIOS 3.4 and 3.5 in Jammy for Hardware Enablement
Status in dmidecode package in Ubuntu:
In Progress
Status in dmidecode source package in Jammy:
Fix Committed
Status in dmidecode source package in Kinetic:
In Progress
Bug description:
[Impact]
* Support the SMBIOS 3.4 and 3.5 specifications in Jammy
to enable new hardware in LTS release per SRU policy [1].
* Backport of 15 relatively simple patches from dmidecode 3.4
in Kinetic to dmidecode 3.3 in Jammy (vs. 49 for full version).
* Patches are detailed below.
[Test Plan]
* Check no regressions on current systems with SMBIOS < 3.4,
i.e., no output changes in text and binary form.
$ sudo dmidecode > old.txt 2>&1
$ sudo dmidecode --dump-bin old.bin
$ apt install dmidecode # modified package
$ sudo dmidecode > new.txt 2>&1
$ sudo dmidecode --dump-bin new.bin
$ cmp old.txt new.txt; echo $?
0
$ cmp old.bin new.bin; echo $?
0
* Check for expected output on new systems with SMBIOS >= 3.4.
$ diff old.txt new.txt
...
< # SMBIOS implementations newer than version 3.3.0 are not
< # fully supported by this version of dmidecode.
...
< Unknown Type
< Header and Data:
...
> Firmware Inventory Information
> Firmware Component Name: BMC Firmware
...
< Type:
---
> Type: DDR5
...
< Upgrade:
---
> Upgrade: Socket LGA4677
...
< Unknown Type
< Header and Data:
...
> Firmware Inventory Information
> Firmware Component Name: BIOS Firmware
* Possibly perform synthetic testing with crafted C structures.
[Where problems could occur]
* Mostly the patches add support for new bits/codes/strings,
so there's no changes expected for the old spec support,
but some patches lightly change things a little bit (but
only one should change a string, as far as I could tell).
* So, theoretically, parsers that expect a very precise
and constant format/string might have issues *in case*
the changes introduced any. (But such tools maybe are
already using the binary form anyway, for more detail.)
[Other info]
* No additional fixes upstream to the included patches.
(The git repo's commits have the 'Fixes:' tag usage.)
There's only 2 more commits after dmidecode-3-4 now.
[Original Description]
Backport the support for SMBIOS 3.4 and 3.5 specifications
in Ubuntu Kinetic (dmidecode 3.4) to Jammy (dmidecode 3.3)
to enable new hardware in the LTS release per SRU policy [1].
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases
[Patchset Details]
Patches 1-8,10-11 are for SMBIOS 3.4;
Patches 9,12-14 are for SMBIOS 3.5;
Patch 15 updates supported version.
01: SMBIOS 3.4: add new codes/strings for memory device type
02: SMBIOS 3.4: add new codes/strings for processor socket
03: SMBIOS 3.4: add new codes/strings for slot characteristics
04: SMBIOS 3.4: add new codes/strings for memory device speed [string
backward-compatible changes]
05: SMBIOS 3.4: add new codes/strings for slot types [changes append '(U.2)'
to 'PCI Express {2,3} SFF-8639' per spec]
06: SMBIOS 3.4: add new codes/strings for processor characteristics
07: SMBIOS
[Kernel-packages] [Bug 1909422] Re: ubuntu_ftrace_smoke_test timeout on H/F-riscv
https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-
tests/commit/?id=6c4955b36b2806abb402ebafd1978245425581e2
** Summary changed:
- ubuntu_ftrace_smoke_test timeout on H/F-riscv
+ ubuntu_ftrace_smoke_test timeout on F-5.15/H/J/K-riscv
** Changed in: linux-riscv (Ubuntu)
Status: New => Invalid
** Changed in: ubuntu-kernel-tests
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: ubuntu-kernel-tests
Status: New => Fix Released
--
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/1909422
Title:
ubuntu_ftrace_smoke_test timeout on F-5.15/H/J/K-riscv
Status in ubuntu-kernel-tests:
Fix Released
Status in linux-riscv package in Ubuntu:
Invalid
Status in linux-riscv source package in Groovy:
Won't Fix
Status in linux-riscv source package in Hirsute:
Won't Fix
Bug description:
Issue found on 5.8.0-13.15 RISCV with a KVM instance.
Test failed with "Timer expired (1350 sec.), nuking pid 520", test log:
$ AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local
--verbose autotest/client/tests/ubuntu_ftrace_smoke_test/control
03:46:12 INFO | Writing results to
/home/ubuntu/autotest/client/results/default
03:46:12 DEBUG| Initializing the state engine
03:46:12 DEBUG| Persistent state client.steps now set to []
03:46:13 DEBUG| Persistent option harness now set to None
03:46:13 DEBUG| Persistent option harness_args now set to None
03:46:13 DEBUG| Selected harness: standalone
03:46:15 INFO | START timestamp=1609127175localtime=Dec
28 03:46:15
03:46:16 DEBUG| Persistent state client._record_indent now set to 1
03:46:16 DEBUG| Test has timeout: 1350 sec.
03:46:16 INFO | START ubuntu_ftrace_smoke_test.ftrace-smoke-test
ubuntu_ftrace_smoke_test.ftrace-smoke-test timestamp=1609127176
timeout=1350localtime=Dec 28 03:46:16
03:46:16 DEBUG| Persistent state client._record_indent now set to 2
03:46:16 DEBUG| Persistent state client.unexpected_reboot now set to
('ubuntu_ftrace_smoke_test.ftrace-smoke-test',
'ubuntu_ftrace_smoke_test.ftrace-smoke-test')
03:46:16 DEBUG| Waiting for pid 520 for 1350 seconds
03:46:16 WARNI| System python is too old, crash handling disabled
03:46:16 DEBUG| Running
'/home/ubuntu/autotest/client/tests/ubuntu_ftrace_smoke_test/ubuntu_ftrace_smoke_test.sh'
03:46:16 DEBUG| [stdout] PASSED (CONFIG_FUNCTION_TRACER=y in
/boot/config-5.8.0-13-generic)
03:46:17 DEBUG| [stdout] PASSED (CONFIG_FUNCTION_GRAPH_TRACER=y in
/boot/config-5.8.0-13-generic)
03:46:17 DEBUG| [stdout] PASSED (CONFIG_STACK_TRACER=y in
/boot/config-5.8.0-13-generic)
03:46:17 DEBUG| [stdout] PASSED (CONFIG_DYNAMIC_FTRACE=y in
/boot/config-5.8.0-13-generic)
03:46:19 DEBUG| [stdout] PASSED all expected /sys/kernel/debug/tracing files
exist
03:46:19 DEBUG| [stdout] PASSED (function_graph in
/sys/kernel/debug/tracing/available_tracers)
03:46:19 DEBUG| [stdout] PASSED (function in
/sys/kernel/debug/tracing/available_tracers)
03:46:20 DEBUG| [stdout] PASSED (nop in
/sys/kernel/debug/tracing/available_tracers)
03:46:26 DEBUG| [stdout] PASSED (tracer function can be enabled)
03:46:35 DEBUG| [stdout] PASSED (tracer function_graph can be enabled)
03:46:35 DEBUG| [stdout] - tracer function_graph got enough data
03:46:35 DEBUG| [stdout] - tracer function_graph completed
03:46:36 DEBUG| [stdout] - tracer function_graph being turned off
03:46:36 DEBUG| [stdout] - tracer got 532 irq events
03:46:43 DEBUG| [stdout] - tracer hwlat got enough data
03:46:43 DEBUG| [stdout] - tracer hwlat completed
03:46:43 DEBUG| [stdout] - tracer hwlat being turned off
03:46:44 DEBUG| [stdout] - tracer nop being set as current tracer
03:46:46 DEBUG| [stdout] PASSED (tracer hwlat can be enabled (got 12 lines of
tracing output))
03:46:48 DEBUG| [stdout] - tracer blk got enough data
03:46:48 DEBUG| [stdout] - tracer blk completed
03:46:48 DEBUG| [stdout] - tracer blk being turned off
03:46:48 DEBUG| [stdout] - tracer nop being set as current tracer
03:46:50 DEBUG| [stdout] PASSED (tracer blk can be enabled (got 2 lines of
tracing output))
03:46:56 INFO | Timer expired (1350 sec.), nuking pid 520
03:46:57 INFO | ERROR
ubuntu_ftrace_smoke_test.ftrace-smoke-test
ubuntu_ftrace_smoke_test.ftrace-smoke-test timestamp=1609127216
localtime=Dec 28 03:46:56 Unhandled AutoservRunError: Could not kill 520
None
Traceback (most recent call last):
File "/home/ubuntu/autotest/client/job.py", line 510, in _runtest
parallel.fork_waitfor_timed(self.resultdir, pid, timeout)
File "/home/ubuntu/autotest/client/parallel.py", line 112, in
fork_waitfor_timed
utils.nuke_pid(pid)
File "/home/ubuntu/autotest/client/shared/utils.py", line 1214, in
nuke_pid
[Kernel-packages] [Bug 1909422] Re: ubuntu_ftrace_smoke_test timeout on H/F-riscv
This happens with the current 15 min timeout on J-riscv, K-riscv,
F-5.15-riscv
They're failing even with 30 min.
45 works.
** Tags added: 5.15 jammy kinetic sru-20220808
--
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/1909422
Title:
ubuntu_ftrace_smoke_test timeout on H/F-riscv
Status in ubuntu-kernel-tests:
New
Status in linux-riscv package in Ubuntu:
New
Status in linux-riscv source package in Groovy:
Won't Fix
Status in linux-riscv source package in Hirsute:
Won't Fix
Bug description:
Issue found on 5.8.0-13.15 RISCV with a KVM instance.
Test failed with "Timer expired (1350 sec.), nuking pid 520", test log:
$ AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local
--verbose autotest/client/tests/ubuntu_ftrace_smoke_test/control
03:46:12 INFO | Writing results to
/home/ubuntu/autotest/client/results/default
03:46:12 DEBUG| Initializing the state engine
03:46:12 DEBUG| Persistent state client.steps now set to []
03:46:13 DEBUG| Persistent option harness now set to None
03:46:13 DEBUG| Persistent option harness_args now set to None
03:46:13 DEBUG| Selected harness: standalone
03:46:15 INFO | START timestamp=1609127175localtime=Dec
28 03:46:15
03:46:16 DEBUG| Persistent state client._record_indent now set to 1
03:46:16 DEBUG| Test has timeout: 1350 sec.
03:46:16 INFO | START ubuntu_ftrace_smoke_test.ftrace-smoke-test
ubuntu_ftrace_smoke_test.ftrace-smoke-test timestamp=1609127176
timeout=1350localtime=Dec 28 03:46:16
03:46:16 DEBUG| Persistent state client._record_indent now set to 2
03:46:16 DEBUG| Persistent state client.unexpected_reboot now set to
('ubuntu_ftrace_smoke_test.ftrace-smoke-test',
'ubuntu_ftrace_smoke_test.ftrace-smoke-test')
03:46:16 DEBUG| Waiting for pid 520 for 1350 seconds
03:46:16 WARNI| System python is too old, crash handling disabled
03:46:16 DEBUG| Running
'/home/ubuntu/autotest/client/tests/ubuntu_ftrace_smoke_test/ubuntu_ftrace_smoke_test.sh'
03:46:16 DEBUG| [stdout] PASSED (CONFIG_FUNCTION_TRACER=y in
/boot/config-5.8.0-13-generic)
03:46:17 DEBUG| [stdout] PASSED (CONFIG_FUNCTION_GRAPH_TRACER=y in
/boot/config-5.8.0-13-generic)
03:46:17 DEBUG| [stdout] PASSED (CONFIG_STACK_TRACER=y in
/boot/config-5.8.0-13-generic)
03:46:17 DEBUG| [stdout] PASSED (CONFIG_DYNAMIC_FTRACE=y in
/boot/config-5.8.0-13-generic)
03:46:19 DEBUG| [stdout] PASSED all expected /sys/kernel/debug/tracing files
exist
03:46:19 DEBUG| [stdout] PASSED (function_graph in
/sys/kernel/debug/tracing/available_tracers)
03:46:19 DEBUG| [stdout] PASSED (function in
/sys/kernel/debug/tracing/available_tracers)
03:46:20 DEBUG| [stdout] PASSED (nop in
/sys/kernel/debug/tracing/available_tracers)
03:46:26 DEBUG| [stdout] PASSED (tracer function can be enabled)
03:46:35 DEBUG| [stdout] PASSED (tracer function_graph can be enabled)
03:46:35 DEBUG| [stdout] - tracer function_graph got enough data
03:46:35 DEBUG| [stdout] - tracer function_graph completed
03:46:36 DEBUG| [stdout] - tracer function_graph being turned off
03:46:36 DEBUG| [stdout] - tracer got 532 irq events
03:46:43 DEBUG| [stdout] - tracer hwlat got enough data
03:46:43 DEBUG| [stdout] - tracer hwlat completed
03:46:43 DEBUG| [stdout] - tracer hwlat being turned off
03:46:44 DEBUG| [stdout] - tracer nop being set as current tracer
03:46:46 DEBUG| [stdout] PASSED (tracer hwlat can be enabled (got 12 lines of
tracing output))
03:46:48 DEBUG| [stdout] - tracer blk got enough data
03:46:48 DEBUG| [stdout] - tracer blk completed
03:46:48 DEBUG| [stdout] - tracer blk being turned off
03:46:48 DEBUG| [stdout] - tracer nop being set as current tracer
03:46:50 DEBUG| [stdout] PASSED (tracer blk can be enabled (got 2 lines of
tracing output))
03:46:56 INFO | Timer expired (1350 sec.), nuking pid 520
03:46:57 INFO | ERROR
ubuntu_ftrace_smoke_test.ftrace-smoke-test
ubuntu_ftrace_smoke_test.ftrace-smoke-test timestamp=1609127216
localtime=Dec 28 03:46:56 Unhandled AutoservRunError: Could not kill 520
None
Traceback (most recent call last):
File "/home/ubuntu/autotest/client/job.py", line 510, in _runtest
parallel.fork_waitfor_timed(self.resultdir, pid, timeout)
File "/home/ubuntu/autotest/client/parallel.py", line 112, in
fork_waitfor_timed
utils.nuke_pid(pid)
File "/home/ubuntu/autotest/client/shared/utils.py", line 1214, in
nuke_pid
raise error.AutoservRunError('Could not kill %d' % pid, None)
AutoservRunError: Could not kill 520
None
03:46:57 INFO | END ERROR
ubuntu_ftrace_smoke_test.ftrace-smoke-test
ubuntu_ftrace_smoke_test.ftrace-smoke-test timestamp=1609127217
localtime=Dec 28 03:46:57
To manage notifications
[Kernel-packages] [Bug 1930783] Re: integrity: Problem loading X.509 certificate
I also have this issue but on a Lenovo laptop with Ubuntu 22.04. It doesn't seem to affect anything but happens on every boot despite changing SecureBoot options. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930783 Title: integrity: Problem loading X.509 certificate Status in linux package in Ubuntu: Expired Bug description: Following error shows on Acer machines while booting when UEFI boot is enabled. integrity: Problem loading X.509 certificate -65 The issue is discussed at https://bugzilla.opensuse.org/show_bug.cgi?id=1129471 and a patch is available at https://lkml.org/lkml/2019/7/16/23. Seems like this patch is not included in Ubuntu as I'm still getting this error. I'm using Linux Mint 20, which is based on Ubuntu 20.04. This error comes while live booting Ubuntu 20.04 and Ubuntu 18.04 also. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930783/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978333] Update Released
The verification of the Stable Release Update for kdump-tools has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1978333 Title: Remove "ata_piix.prefer_ms_hyperv=0" parameter Status in kdump-tools package in Ubuntu: Fix Released Status in makedumpfile package in Ubuntu: Invalid Status in kdump-tools source package in Bionic: Invalid Status in makedumpfile source package in Bionic: Fix Committed Status in kdump-tools source package in Focal: Invalid Status in makedumpfile source package in Focal: Fix Committed Status in kdump-tools source package in Impish: Invalid Status in makedumpfile source package in Impish: Invalid Status in kdump-tools source package in Jammy: Fix Released Status in makedumpfile source package in Jammy: Invalid Status in kdump-tools source package in Kinetic: Fix Released Status in makedumpfile source package in Kinetic: Invalid Bug description: [Impact] Azure VM instances hit I/O error on boot causing kernel crash [Test Plan] Create Ubuntu Marketplace VM on Azure ``` ssh -i .ssh/id_rsa ubuntu@ipaddr ``` Install crash dump utilities (from guide: https://ubuntu.com/server/docs/kernel-crash-dump) apt-get install kdump-tools Say (y) to all questions during install kdump-config show *shows the vm is not yet ready to kdump root@bionic3: kdump-config show * no crashkernel= parameter in the kernel cmdline DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz kdump initrd: /var/lib/kdump/initrd.img current state:Not ready to kdump kexec command: no kexec command recorded Reboot the VM sudo su As root on the VM after reboot: kdump-config show kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x3200 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.4.0-1086-azure kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.4.0-1086-azure current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.4.0-1086-azure root=UUID=143c811b-9b9c-48f3-b0c8-040f6e65f50a ro console=tty1 console=ttyS0 earlyprintk=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz #verify kdump is on cat /proc/cmdline ... crashkernel=512M-:192M dmesg | grep -i crash [0.071660] kexec: Reserving the low 1M of memory for crashkernel [0.269823] Reserving 192MB of memory at 640MB for crashkernel (System RAM: 4095MB) cat /proc/sys/kernel/sysrq # make sure this value is greater than 0 #set it to 1 sudo sysctl -w kernel.sysrq=1 the directory of /var/crash should have no crashes yet as well. Outcome with "ata_piix.prefer_ms_hyperv=0" in kexec command: # perform crash sudo su echo c > /proc/sysrq-trigger After a couple of minuties Open new terminal and try to ssh to azure VM, It does not succeed Force a reboot of the VM through the portal or serial console #kdump doesnt work and hangs indefinitely #force reboot VM from Azure console # verify package version of kdump-tool # verify parameter is not listed in the kdump-config show output kdump-config unload kdump-config load kdump-config show kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x3200 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.4.0-1086-azure kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.4.0-1086-azure current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.4.0-1086-azure root=UUID=143c811b-9b9c-48f3-b0c8-040f6e65f50a ro console=tty1 console=ttyS0 earlyprintk=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz #trigger another crash echo c > /proc/sysrq-trigger # open new terminal and ssh back into vm cd /var/crash #verify a dump was created
[Kernel-packages] [Bug 1978333] Re: Remove "ata_piix.prefer_ms_hyperv=0" parameter
This bug was fixed in the package kdump-tools - 1:1.6.10ubuntu2 --- kdump-tools (1:1.6.10ubuntu2) jammy; urgency=low * debian/rules: Remove "ata_piix.prefer_ms_hyperv=0" (LP: #1978333) -- Heather Lemon Fri, 10 Jun 2022 16:26:37 + ** Changed in: kdump-tools (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. Matching subscriptions: Maintainer https://bugs.launchpad.net/bugs/1978333 Title: Remove "ata_piix.prefer_ms_hyperv=0" parameter Status in kdump-tools package in Ubuntu: Fix Released Status in makedumpfile package in Ubuntu: Invalid Status in kdump-tools source package in Bionic: Invalid Status in makedumpfile source package in Bionic: Fix Committed Status in kdump-tools source package in Focal: Invalid Status in makedumpfile source package in Focal: Fix Committed Status in kdump-tools source package in Impish: Invalid Status in makedumpfile source package in Impish: Invalid Status in kdump-tools source package in Jammy: Fix Released Status in makedumpfile source package in Jammy: Invalid Status in kdump-tools source package in Kinetic: Fix Released Status in makedumpfile source package in Kinetic: Invalid Bug description: [Impact] Azure VM instances hit I/O error on boot causing kernel crash [Test Plan] Create Ubuntu Marketplace VM on Azure ``` ssh -i .ssh/id_rsa ubuntu@ipaddr ``` Install crash dump utilities (from guide: https://ubuntu.com/server/docs/kernel-crash-dump) apt-get install kdump-tools Say (y) to all questions during install kdump-config show *shows the vm is not yet ready to kdump root@bionic3: kdump-config show * no crashkernel= parameter in the kernel cmdline DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz kdump initrd: /var/lib/kdump/initrd.img current state:Not ready to kdump kexec command: no kexec command recorded Reboot the VM sudo su As root on the VM after reboot: kdump-config show kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x3200 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.4.0-1086-azure kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.4.0-1086-azure current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.4.0-1086-azure root=UUID=143c811b-9b9c-48f3-b0c8-040f6e65f50a ro console=tty1 console=ttyS0 earlyprintk=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz #verify kdump is on cat /proc/cmdline ... crashkernel=512M-:192M dmesg | grep -i crash [0.071660] kexec: Reserving the low 1M of memory for crashkernel [0.269823] Reserving 192MB of memory at 640MB for crashkernel (System RAM: 4095MB) cat /proc/sys/kernel/sysrq # make sure this value is greater than 0 #set it to 1 sudo sysctl -w kernel.sysrq=1 the directory of /var/crash should have no crashes yet as well. Outcome with "ata_piix.prefer_ms_hyperv=0" in kexec command: # perform crash sudo su echo c > /proc/sysrq-trigger After a couple of minuties Open new terminal and try to ssh to azure VM, It does not succeed Force a reboot of the VM through the portal or serial console #kdump doesnt work and hangs indefinitely #force reboot VM from Azure console # verify package version of kdump-tool # verify parameter is not listed in the kdump-config show output kdump-config unload kdump-config load kdump-config show kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x3200 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.4.0-1086-azure kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.4.0-1086-azure current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.4.0-1086-azure root=UUID=143c811b-9b9c-48f3-b0c8-040f6e65f50a ro console=tty1 console=ttyS0 earlyprintk=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz #trigger another crash echo c > /proc/sysrq-trigger # open new terminal and ssh back into vm cd /var/crash #verify a dump was created linux-image-5.4.0-1086-azure-202208041658.crash [Where Problems Could Occur] This change modifies the debian/rules. The
[Kernel-packages] [Bug 1978333] Re: Remove "ata_piix.prefer_ms_hyperv=0" parameter
kdump-tools (1:1.7) unstable; urgency=medium [ Guilherme G. Piccoli ] * kdump-tools.service: Start kdump service a bit earlier in boot. [ Kellen Renshaw ] * rules: Remove "ata_piix.prefer_ms_hyperv=0" (Closes: #1011960). -- dann frazier Thu, 09 Jun 2022 15:29:58 -0600 ** Changed in: kdump-tools (Ubuntu Kinetic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. Matching subscriptions: Maintainer https://bugs.launchpad.net/bugs/1978333 Title: Remove "ata_piix.prefer_ms_hyperv=0" parameter Status in kdump-tools package in Ubuntu: Fix Released Status in makedumpfile package in Ubuntu: Invalid Status in kdump-tools source package in Bionic: Invalid Status in makedumpfile source package in Bionic: Fix Committed Status in kdump-tools source package in Focal: Invalid Status in makedumpfile source package in Focal: Fix Committed Status in kdump-tools source package in Impish: Invalid Status in makedumpfile source package in Impish: Invalid Status in kdump-tools source package in Jammy: Fix Released Status in makedumpfile source package in Jammy: Invalid Status in kdump-tools source package in Kinetic: Fix Released Status in makedumpfile source package in Kinetic: Invalid Bug description: [Impact] Azure VM instances hit I/O error on boot causing kernel crash [Test Plan] Create Ubuntu Marketplace VM on Azure ``` ssh -i .ssh/id_rsa ubuntu@ipaddr ``` Install crash dump utilities (from guide: https://ubuntu.com/server/docs/kernel-crash-dump) apt-get install kdump-tools Say (y) to all questions during install kdump-config show *shows the vm is not yet ready to kdump root@bionic3: kdump-config show * no crashkernel= parameter in the kernel cmdline DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz kdump initrd: /var/lib/kdump/initrd.img current state:Not ready to kdump kexec command: no kexec command recorded Reboot the VM sudo su As root on the VM after reboot: kdump-config show kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x3200 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.4.0-1086-azure kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.4.0-1086-azure current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.4.0-1086-azure root=UUID=143c811b-9b9c-48f3-b0c8-040f6e65f50a ro console=tty1 console=ttyS0 earlyprintk=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz #verify kdump is on cat /proc/cmdline ... crashkernel=512M-:192M dmesg | grep -i crash [0.071660] kexec: Reserving the low 1M of memory for crashkernel [0.269823] Reserving 192MB of memory at 640MB for crashkernel (System RAM: 4095MB) cat /proc/sys/kernel/sysrq # make sure this value is greater than 0 #set it to 1 sudo sysctl -w kernel.sysrq=1 the directory of /var/crash should have no crashes yet as well. Outcome with "ata_piix.prefer_ms_hyperv=0" in kexec command: # perform crash sudo su echo c > /proc/sysrq-trigger After a couple of minuties Open new terminal and try to ssh to azure VM, It does not succeed Force a reboot of the VM through the portal or serial console #kdump doesnt work and hangs indefinitely #force reboot VM from Azure console # verify package version of kdump-tool # verify parameter is not listed in the kdump-config show output kdump-config unload kdump-config load kdump-config show kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x3200 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.4.0-1086-azure kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.4.0-1086-azure current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.4.0-1086-azure root=UUID=143c811b-9b9c-48f3-b0c8-040f6e65f50a ro console=tty1 console=ttyS0 earlyprintk=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz #trigger another crash echo c > /proc/sysrq-trigger # open new terminal and ssh back into vm cd /var/crash #verify a dump was created linux-image-5.4.0-1086-azure-202208041658.crash [Where Problems Could Occur] This change
[Kernel-packages] [Bug 1988108] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1988108 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1988108 Title: kernal 5.15.0-46 error out of memory when boosting Status in linux package in Ubuntu: Incomplete Bug description: System: Kernel: 5.15.0-41-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: Cinnamon 5.4.11 tk: GTK 3.24.33 wm: Mutter dm: LightDM Distro: Linux Mint 21 Vanessa base: Ubuntu 22.04 jammy Machine: Type: Laptop System: Alienware product: Alienware 17 R3 v: 1.13.1 serial: Chassis: type: 10 serial: Mobo: Alienware model: 0M5CM7 v: A00 serial: UEFI: Alienware v: 1.13.1 date: 06/10/2021 Battery: ID-1: BAT1 charge: 85.2 Wh (92.0%) condition: 92.6/96.5 Wh (96.0%) volts: 16.6 min: 14.4 model: COMPAL PABAS0241231 serial: status: Charging CPU: Info: quad core model: Intel Core i7-6820HK bits: 64 type: MT MCP arch: Skylake-S rev: 3 cache: L1: 256 KiB L2: 1024 KiB L3: 8 MiB Speed (MHz): avg: 1064 high: 2225 min/max: 800/3600 cores: 1: 900 2: 894 3: 900 4: 900 5: 900 6: 900 7: 900 8: 2225 bogomips: 43198 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel HD Graphics 530 vendor: Dell driver: i915 v: kernel ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2, HDMI-A-3 bus-ID: 00:02.0 chip-ID: 8086:191b Device-2: NVIDIA GM204M [GeForce GTX 980M] vendor: Dell driver: N/A pcie: speed: 8 GT/s lanes: 8 bus-ID: 01:00.0 chip-ID: 10de:13d7 Device-3: Sunplus Innovation Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-7:5 chip-ID: 1bcf:2b8c Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 3840x2160 s-dpi: 96 Monitor-1: eDP-1 model: AU Optronics res: 3840x2160 dpi: 255 diag: 438mm (17.2") OpenGL: renderer: Mesa Intel HD Graphics 530 (SKL GT2) v: 4.6 Mesa 22.0.5 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a170 Device-2: NVIDIA GM204 High Definition Audio driver: snd_hda_intel v: kernel pcie: speed: Unknown lanes: 63 bus-ID: 01:00.1 chip-ID: 10de:0fbb Sound Server-1: ALSA v: k5.15.0-41-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: yes Sound Server-3: PipeWire v: 0.3.48 running: yes Network: Device-1: Qualcomm Atheros Killer E2400 Gigabit Ethernet driver: alx v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 3b:00.0 chip-ID: 1969:e0a1 IF: enp59s0 state: down mac: Device-2: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter vendor: Rivet Networks Killer Wireless-n/a/ac 1535 driver: ath10k_pci v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 3c:00.0 chip-ID: 168c:003e IF: wlp60s0 state: up mac: Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 1-5:4 chip-ID: 0cf3:e301 Report: hciconfig ID: hci0 rfk-id: 1 state: up address: bt-v: 2.1 lmp-v: 4.2 sub-v: 25a Drives: Local Storage: total: 1.82 TiB used: 15.06 GiB (0.8%) ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 980 PRO 1TB size: 931.51 GiB speed: 63.2 Gb/s lanes: 4 serial: temp: 50.9 C ID-2: /dev/sda vendor: HGST (Hitachi) model: HTS721010A9E630 size: 931.51 GiB speed: 6.0 Gb/s serial: Partition: ID-1: / size: 915.32 GiB used: 15.06 GiB (1.6%) fs: ext4 dev: /dev/nvme0n1p2 ID-2: /boot/efi size: 511 MiB used: 5.2 MiB (1.0%) fs: vfat dev: /dev/nvme0n1p1 Swap: ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile Sensors: System Temperatures: cpu: 50.0 C pch: 62.0 C mobo: N/A Fan Speeds (RPM): N/A Repos: Packages: apt: 2489 No active apt repos in: /etc/apt/sources.list Active apt repos in: /etc/apt/sources.list.d/1password.list 1: deb [arch=amd64 signed-by=/usr/share/keyrings/1password-archive-keyring.gpg] https: //downloads.1password.com/linux/debian/amd64 stable main Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 1: deb http: //packages.linuxmint.com vanessa main upstream import backport
[Kernel-packages] [Bug 1914881] Re: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245,
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Public Security 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/1914881 Title: No sound from internal speakers HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, Status in linux package in Ubuntu: Confirmed Bug description: There is no sound output from the laptop internal speakers when running Ubuntu 20.10. This is a dual-boot system; - Booting Windows first and then rebooting to Ubuntu -> sound works fine - Booting Ubuntu first and then rebooting to Windows -> Windows identifies sound as not enables and runs its troubleshooter to enable it The card seems to be recognised OK (system sound settings report output device as Speaker - Tiger Lake-LP Smart Sound technology Audio Controller. VU meters etc all appear as if sound is playing, but no sound. Headphone socket works perfectly. Similar bug reports for different laptops in the HP x360 series suggest this is a pinning problem and that the extract below from the boot logs may support this. lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 aplay -l List of PLAYBACK Hardware Devices card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 extract from journalctl -b kernel: snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC245: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:> kernel: snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) kernel: snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) kernel: snd_hda_codec_realtek ehdaudio0D0:mono: mono_out=0x0 kernel: snd_hda_codec_realtek ehdaudio0D0:inputs: kernel: snd_hda_codec_realtek ehdaudio0D0: Mic=0x19 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: derek 1460 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Feb 6 20:48:52 2021 InstallationDate: Installed on 2021-02-04 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: derek 1460 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Spectre x360 Convertible 14-ea0xxx, Realtek ALC245, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2021 dmi.bios.release: 15.9 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87F7 dmi.board.vendor: HP dmi.board.version: 40.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.43 dmi.modalias: dmi:bvnAMI:bvrF.09:bd01/13/2021:br15.9:efr40.43:svnHP:pnHPSpectrex360Convertible14-ea0xxx:pvr:rvnHP:rn87F7:rvr40.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 14-ea0xxx dmi.product.sku: 2G2C7EA#ABU dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: derek 1481 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-02-04 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
[Kernel-packages] [Bug 1988108] Re: kernal 5.15.0-46 error out of memory when boosting
** Information type changed from Private Security 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/1988108 Title: kernal 5.15.0-46 error out of memory when boosting Status in linux package in Ubuntu: New Bug description: System: Kernel: 5.15.0-41-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: Cinnamon 5.4.11 tk: GTK 3.24.33 wm: Mutter dm: LightDM Distro: Linux Mint 21 Vanessa base: Ubuntu 22.04 jammy Machine: Type: Laptop System: Alienware product: Alienware 17 R3 v: 1.13.1 serial: Chassis: type: 10 serial: Mobo: Alienware model: 0M5CM7 v: A00 serial: UEFI: Alienware v: 1.13.1 date: 06/10/2021 Battery: ID-1: BAT1 charge: 85.2 Wh (92.0%) condition: 92.6/96.5 Wh (96.0%) volts: 16.6 min: 14.4 model: COMPAL PABAS0241231 serial: status: Charging CPU: Info: quad core model: Intel Core i7-6820HK bits: 64 type: MT MCP arch: Skylake-S rev: 3 cache: L1: 256 KiB L2: 1024 KiB L3: 8 MiB Speed (MHz): avg: 1064 high: 2225 min/max: 800/3600 cores: 1: 900 2: 894 3: 900 4: 900 5: 900 6: 900 7: 900 8: 2225 bogomips: 43198 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel HD Graphics 530 vendor: Dell driver: i915 v: kernel ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2, HDMI-A-3 bus-ID: 00:02.0 chip-ID: 8086:191b Device-2: NVIDIA GM204M [GeForce GTX 980M] vendor: Dell driver: N/A pcie: speed: 8 GT/s lanes: 8 bus-ID: 01:00.0 chip-ID: 10de:13d7 Device-3: Sunplus Innovation Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-7:5 chip-ID: 1bcf:2b8c Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 3840x2160 s-dpi: 96 Monitor-1: eDP-1 model: AU Optronics res: 3840x2160 dpi: 255 diag: 438mm (17.2") OpenGL: renderer: Mesa Intel HD Graphics 530 (SKL GT2) v: 4.6 Mesa 22.0.5 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a170 Device-2: NVIDIA GM204 High Definition Audio driver: snd_hda_intel v: kernel pcie: speed: Unknown lanes: 63 bus-ID: 01:00.1 chip-ID: 10de:0fbb Sound Server-1: ALSA v: k5.15.0-41-generic running: yes Sound Server-2: PulseAudio v: 15.99.1 running: yes Sound Server-3: PipeWire v: 0.3.48 running: yes Network: Device-1: Qualcomm Atheros Killer E2400 Gigabit Ethernet driver: alx v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 3b:00.0 chip-ID: 1969:e0a1 IF: enp59s0 state: down mac: Device-2: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter vendor: Rivet Networks Killer Wireless-n/a/ac 1535 driver: ath10k_pci v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 3c:00.0 chip-ID: 168c:003e IF: wlp60s0 state: up mac: Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 1-5:4 chip-ID: 0cf3:e301 Report: hciconfig ID: hci0 rfk-id: 1 state: up address: bt-v: 2.1 lmp-v: 4.2 sub-v: 25a Drives: Local Storage: total: 1.82 TiB used: 15.06 GiB (0.8%) ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 980 PRO 1TB size: 931.51 GiB speed: 63.2 Gb/s lanes: 4 serial: temp: 50.9 C ID-2: /dev/sda vendor: HGST (Hitachi) model: HTS721010A9E630 size: 931.51 GiB speed: 6.0 Gb/s serial: Partition: ID-1: / size: 915.32 GiB used: 15.06 GiB (1.6%) fs: ext4 dev: /dev/nvme0n1p2 ID-2: /boot/efi size: 511 MiB used: 5.2 MiB (1.0%) fs: vfat dev: /dev/nvme0n1p1 Swap: ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile Sensors: System Temperatures: cpu: 50.0 C pch: 62.0 C mobo: N/A Fan Speeds (RPM): N/A Repos: Packages: apt: 2489 No active apt repos in: /etc/apt/sources.list Active apt repos in: /etc/apt/sources.list.d/1password.list 1: deb [arch=amd64 signed-by=/usr/share/keyrings/1password-archive-keyring.gpg] https: //downloads.1password.com/linux/debian/amd64 stable main Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 1: deb http: //packages.linuxmint.com vanessa main upstream import backport 2: deb http: //archive.ubuntu.com/ubuntu jammy main restricted universe multiverse 3: deb http: //archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse 4: deb http: //archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse 5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse Info: Processes: 288 Uptime: 5m Memory: 31.23 GiB used: 2.92 GiB (9.3%) Init: systemd v: 249 runlevel: 5 Compilers: gcc: 11.2.0 alt: 11 Client: Cinnamon
[Kernel-packages] [Bug 1988143] Update Released
The verification of the Stable Release Update for linux-restricted- modules-hwe-5.15 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1988143 Title: 20.04.5 (20220829.1 build) has kernel 5.13 packages Status in linux-restricted-modules-hwe-5.15 package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Invalid Bug description: [Impact] * Linux-restricted-modules for the 390 drivers were disabled temporarily back in January, however they were not re-enabled when support for the new kernel was added. * Including the 390 release in the ISO causes the 5.13 packages to be pulled in. [Test Plan] * Install the hwe-515 kernel and make sure that the NVIDIA 390 driver can be installed with its linux-restricted-modules. [Where problems could occur] * The addition of modules for an already existing driver series would not cause any regressions, since the whole package generation process is automated, and this is the only commit that we are going to revert: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-restricted-modules/+git/focal/commit/?h=hwe-5.15=0dfff8472e3e4e75e8effc5957ba6b89a9eaf020 [Other Info] * Other kernel releases support the 390 series. _ Examining the .list file for the amd64 image it contains various kernel 5.13 .deb packages. http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop- amd64.list e.g. /pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb /pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb This is a little unexpected given that 5.15 is the default kernel. Possibly nvidia-390 doesn't have 5.15 packages? This impacts all flavours as well that include nvidia stuff in their ISO - so if the solution is to change the meta file for a revised regexp for nvidia then all flavours that include nvidia will likewise need their meta packages updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.15/+bug/1988143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988143] Re: 20.04.5 (20220829.1 build) has kernel 5.13 packages
This bug was fixed in the package linux-restricted-modules-hwe-5.15 - 5.15.0-46.49~20.04.1+1 --- linux-restricted-modules-hwe-5.15 (5.15.0-46.49~20.04.1+1) focal; urgency=medium * Miscellaneous Ubuntu changes (LP: #1988143) - [packaging] revert drop nvidia 390 -- Alberto Milone Tue, 30 Aug 2022 11:40:45 + ** Changed in: linux-restricted-modules-hwe-5.15 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1988143 Title: 20.04.5 (20220829.1 build) has kernel 5.13 packages Status in linux-restricted-modules-hwe-5.15 package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Invalid Bug description: [Impact] * Linux-restricted-modules for the 390 drivers were disabled temporarily back in January, however they were not re-enabled when support for the new kernel was added. * Including the 390 release in the ISO causes the 5.13 packages to be pulled in. [Test Plan] * Install the hwe-515 kernel and make sure that the NVIDIA 390 driver can be installed with its linux-restricted-modules. [Where problems could occur] * The addition of modules for an already existing driver series would not cause any regressions, since the whole package generation process is automated, and this is the only commit that we are going to revert: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-restricted-modules/+git/focal/commit/?h=hwe-5.15=0dfff8472e3e4e75e8effc5957ba6b89a9eaf020 [Other Info] * Other kernel releases support the 390 series. _ Examining the .list file for the amd64 image it contains various kernel 5.13 .deb packages. http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop- amd64.list e.g. /pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb /pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb This is a little unexpected given that 5.15 is the default kernel. Possibly nvidia-390 doesn't have 5.15 packages? This impacts all flavours as well that include nvidia stuff in their ISO - so if the solution is to change the meta file for a revised regexp for nvidia then all flavours that include nvidia will likewise need their meta packages updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.15/+bug/1988143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981525] Update Released
The verification of the Stable Release Update for thermald has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1981525 Title: Add support for Raptor Lake CPUs Status in OEM Priority Project: Fix Committed Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Fix Released Bug description: [Impact] * Support thermald on Raptor Lake CPU. [Test Plan] * Use a machine with a Raptor Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Raptor Lake in thermald, which won't impact other hardware. [Other Info] * https://github.com/intel/thermal_daemon/issues/354 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1981525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981525] Re: Add support for Raptor Lake CPUs
This bug was fixed in the package thermald - 2.4.9-1ubuntu0.1 --- thermald (2.4.9-1ubuntu0.1) jammy; urgency=medium * Add support for Raptor Lake CPUs. (LP: #1981525) -- Dirk Su Wed, 13 Jul 2022 14:06:08 +0800 ** Changed in: thermald (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1981525 Title: Add support for Raptor Lake CPUs Status in OEM Priority Project: Fix Committed Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Fix Released Bug description: [Impact] * Support thermald on Raptor Lake CPU. [Test Plan] * Use a machine with a Raptor Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Raptor Lake in thermald, which won't impact other hardware. [Other Info] * https://github.com/intel/thermal_daemon/issues/354 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1981525/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986921] Update Released
The verification of the Stable Release Update for lttng-modules has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1986921 Title: lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Won't Fix Status in lttng-modules package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in lttng-modules source package in Focal: Fix Committed Status in linux source package in Jammy: Won't Fix Status in lttng-modules source package in Jammy: Fix Released Bug description: SRU Justification: Impact: The kernel upstream changed in v5.18 and dropped tracepoints for random. This change was backported to 5.15/jammy in upstream stable 5.15.44. With that the build of lttng-modules-dkms fails. Fix: Backport of an upstream change which checks for the kernel header file which got removed in the process. Additionally the DKMS spec file has to do the same check to be aware of the missing probe module. Testcase: Installing lttng-modules-dkms for a kernel < 5.15.0-47 and -47 or later. Currently -47 and later will fail. With the change both should complete. Regression Potential: This changes whether lttng-probe-random.ko is available or not (if it is available the code is unchanged). User- space might be affected if this module is always expected. --- This is a scripted bug report about ADT failures while running lttng- modules tests for linux/5.15.0-47.51 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/lttng-modules/20220817_074711_55044@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/l/lttng-modules/20220817_075639_1a4d1@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/l/lttng-modules/20220817_074544_d2849@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/l/lttng-modules/20220817_075106_d2849@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1986921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986921] Re: lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51
This bug was fixed in the package lttng-modules - 2.13.1-1ubuntu0.22.04.1 --- lttng-modules (2.13.1-1ubuntu0.22.04.1) jammy; urgency=medium * [ed1149ef] Backport upstream fix to handle removal of random.h (LP: #1986921) -- Stefan Bader Thu, 18 Aug 2022 10:13:02 +0200 ** Changed in: lttng-modules (Ubuntu Jammy) Status: Fix Committed => 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/1986921 Title: lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Won't Fix Status in lttng-modules package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in lttng-modules source package in Focal: Fix Committed Status in linux source package in Jammy: Won't Fix Status in lttng-modules source package in Jammy: Fix Released Bug description: SRU Justification: Impact: The kernel upstream changed in v5.18 and dropped tracepoints for random. This change was backported to 5.15/jammy in upstream stable 5.15.44. With that the build of lttng-modules-dkms fails. Fix: Backport of an upstream change which checks for the kernel header file which got removed in the process. Additionally the DKMS spec file has to do the same check to be aware of the missing probe module. Testcase: Installing lttng-modules-dkms for a kernel < 5.15.0-47 and -47 or later. Currently -47 and later will fail. With the change both should complete. Regression Potential: This changes whether lttng-probe-random.ko is available or not (if it is available the code is unchanged). User- space might be affected if this module is always expected. --- This is a scripted bug report about ADT failures while running lttng- modules tests for linux/5.15.0-47.51 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/lttng-modules/20220817_074711_55044@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/l/lttng-modules/20220817_075639_1a4d1@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/l/lttng-modules/20220817_074544_d2849@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/l/lttng-modules/20220817_075106_d2849@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1986921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988225] [NEW] Focal update: v5.4.208 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.4.208 upstream stable release
from git://git.kernel.org/
pinctrl: stm32: fix optional IRQ support to gpios
riscv: add as-options for modules with assembly compontents
mlxsw: spectrum_router: Fix IPv4 nexthop gateway indication
lockdown: Fix kexec lockdown bypass with ima policy
xen/gntdev: Ignore failure to unmap INVALID_GRANT_HANDLE
PCI: hv: Fix multi-MSI to allow more than one MSI vector
PCI: hv: Fix hv_arch_irq_unmask() for multi-MSI
PCI: hv: Reuse existing IRTE allocation in compose_msi_msg()
PCI: hv: Fix interrupt mapping for multi-MSI
serial: mvebu-uart: correctly report configured baudrate value
xfrm: xfrm_policy: fix a possible double xfrm_pols_put() in xfrm_bundle_lookup()
power/reset: arm-versatile: Fix refcount leak in versatile_reboot_probe
pinctrl: ralink: Check for null return of devm_kcalloc
perf/core: Fix data race between perf_event_set_output() and perf_mmap_close()
igc: Reinstate IGC_REMOVED logic and implement it properly
ip: Fix data-races around sysctl_ip_no_pmtu_disc.
ip: Fix data-races around sysctl_ip_fwd_use_pmtu.
ip: Fix data-races around sysctl_ip_nonlocal_bind.
ip: Fix a data-race around sysctl_fwmark_reflect.
tcp/dccp: Fix a data-race around sysctl_tcp_fwmark_accept.
tcp: Fix data-races around sysctl_tcp_mtu_probing.
tcp: Fix data-races around sysctl_tcp_base_mss.
tcp: Fix data-races around sysctl_tcp_min_snd_mss.
tcp: Fix a data-race around sysctl_tcp_mtu_probe_floor.
tcp: Fix a data-race around sysctl_tcp_probe_threshold.
tcp: Fix a data-race around sysctl_tcp_probe_interval.
i2c: cadence: Change large transfer count reset logic to be unconditional
net: stmmac: fix dma queue left shift overflow issue
net/tls: Fix race in TLS device down flow
igmp: Fix data-races around sysctl_igmp_llm_reports.
igmp: Fix a data-race around sysctl_igmp_max_memberships.
tcp: Fix data-races around sysctl_tcp_syncookies.
tcp: Fix data-races around sysctl_tcp_reordering.
tcp: Fix data-races around some timeout sysctl knobs.
tcp: Fix a data-race around sysctl_tcp_notsent_lowat.
tcp: Fix a data-race around sysctl_tcp_tw_reuse.
tcp: Fix data-races around sysctl_max_syn_backlog.
tcp: Fix data-races around sysctl_tcp_fastopen.
iavf: Fix handling of dummy receive descriptors
i40e: Fix erroneous adapter reinitialization during recovery process
ixgbe: Add locking to prevent panic when setting sriov_numvfs to zero
gpio: pca953x: only use single read/write for No AI mode
be2net: Fix buffer overflow in be_get_module_eeprom
ipv4: Fix a data-race around sysctl_fib_multipath_use_neigh.
udp: Fix a data-race around sysctl_udp_l3mdev_accept.
tcp: Fix data-races around sysctl knobs related to SYN option.
tcp: Fix a data-race around sysctl_tcp_early_retrans.
tcp: Fix data-races around sysctl_tcp_recovery.
tcp: Fix a data-race around sysctl_tcp_thin_linear_timeouts.
tcp: Fix data-races around sysctl_tcp_slow_start_after_idle.
tcp: Fix a data-race around sysctl_tcp_retrans_collapse.
tcp: Fix a data-race around sysctl_tcp_stdurg.
tcp: Fix a data-race around sysctl_tcp_rfc1337.
tcp: Fix data-races around sysctl_tcp_max_reordering.
spi: bcm2835: bcm2835_spi_handle_err(): fix NULL pointer deref for non DMA
transfers
mm/mempolicy: fix uninit-value in mpol_rebind_policy()
bpf: Make sure mac_header was set before using it
dlm: fix pending remove if msg allocation fails
ima: remove the IMA_TEMPLATE Kconfig option
UBUNTU: [Config] updateconfigs for IMA_TEMPLATE
locking/refcount: Define constants for saturation and max refcount values
locking/refcount: Ensure integer operands are treated as signed
locking/refcount: Remove unused refcount_*_checked() variants
locking/refcount: Move the bulk of the REFCOUNT_FULL implementation into the
header
locking/refcount: Improve performance of generic REFCOUNT_FULL code
locking/refcount: Move saturation warnings out of line
locking/refcount: Consolidate REFCOUNT_{MAX,SATURATED} definitions
locking/refcount: Consolidate implementations of refcount_t
UBUNTU: [Config] updateconfigs for REFCOUNT_FULL
x86: get rid of small constant size cases in raw_copy_{to,from}_user()
x86/uaccess: Implement macros for CMPXCHG on user addresses
mmap locking API: initial implementation as rwsem wrappers
x86/mce: Deduplicate exception handling
bitfield.h: Fix "type of reg too small for mask" test
ALSA: memalloc: Align buffer allocations in page size
Bluetooth: Add bt_skb_sendmsg helper
Bluetooth: Add bt_skb_sendmmsg helper
Bluetooth: SCO: Replace use of memcpy_from_msg with bt_skb_sendmsg
Bluetooth: RFCOMM: Replace use of
[Kernel-packages] [Bug 1987287] Re: [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery
Hello 'nafeiy', we indeed wanted to pick this up in the next days. Just notice that this is a development bug, opened at the Launchpad bug tracking system, that is mainly used for development. We will usually produce a patched 20.04/focal/5.4 test kernel, that we make a available via a so called PPA (a special repository). It will take then some steps in our SRU cycle until this patched kernel gets released. These are the upcoming kernel Service Release Cycles (SRUs): https://kernel.ubuntu.com/ This 5.4 kernel will then be migrated by our kernel team to 18.04/bionic/hwe-5.4. But in this case we may also create a dedicated hwe-5.4 test kernel for bionic for you, to save you some time. The process for hotfixes is a different. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987287 Title: [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: New Bug description: We recently got a bug report for systems running Ubuntu 20.04 that were crashing with backtraces pointing at the mlx5 driver's handling of mlx5_ethtool_get_link_ksettings() when this is called through the sysfs (going through ethtool might have different checks). I managed to find a reliable way to reproduce the issue that I believe isn't tied to IBM Z at all. The procedure to reproduce is as follows. I created a script to read the sysfs attributes for the link's speed and duplex mode in a loop: #!/usr/bin/env bash if [ $# -lt 1 ]; then echo "Usage: $0 " exit 1 fi while true; do cat /sys/class/net/$1/duplex > /dev/null cat /sys/class/net/$1/speed > /dev/null done Executed with: # ./script.sh enP10p0s0 I ran this in one bash session and then in another one I triggered a PCI reset with the follwoing command where one needs to replace with the PCI address of the NIC: echo 1 > /sys/bus/pci/devices//reset Then first I got a lot of the following messages: mlx5_core 0010:00:00.0 enP16p0s0: mlx5e_ethtool_get_link_ksettings: query port ptys failed: -5 And then as the mlx5 driver's recovery kicks in the oops as below: [ 659.103947] mlx5_core 0010:00:00.0: wait vital counter value 0x7b399f after 1 iterations [ 659.103947] mlx5_core 0010:00:00.0: mlx5_pci_resume was called [ 659.103966] mlx5_core 0010:00:00.0: firmware version: 14.32.1010 [ 659.104169] Unable to handle kernel pointer dereference in virtual kernel address space [ 659.104171] Failing address: TEID: 0483 [ 659.104172] Fault in home space mode while using kernel ASCE. [ 659.104173] AS:3d29c007 R3:fffd0007 S:fffd5800 P:003d [ 659.104200] Oops: 0004 ilc:2 [#1] SMP [ 659.104202] Modules linked in: s390_trng ism smc pnet chsc_sch eadm_sch vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel drm drm_panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear mlx5_ib dm_service_time pkey zcrypt crc32_vx_s390 ib_uverbs ghash_s390 ib_core qeth_l2 prng aes_s390 des_s390 nvme libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common mlx5_core tls mlxfw ptp nvme_core pps_core dasd_eckd_mod dasd_mod zfcp scsi_transport_fc qeth qdio ccwgroup scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [ 659.104232] CPU: 6 PID: 438216 Comm: cat Not tainted 5.4.0-124-generic #140-Ubuntu [ 659.104233] Hardware name: IBM 3931 XYZ (LPAR) [ 659.104234] Krnl PSW : 0404c0018000 3bfa661e (__queue_work+0xfe/0x520) [ 659.104241]R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 [ 659.104242] Krnl GPRS: 3c291570 0007 7fff [ 659.104243]e2fe46e0 000fffe0 0006 3d039588 [ 659.104244] e2fe46e0 bfb3e000 [ 659.104245]e194c400 03e007d6fb78 3bfa6602 03e007d6f860 [ 659.104251] Krnl Code: 3bfa6612: a77400e5brc 7,3bfa67dc 3bfa6616: 582003acl %r2,940 #3bfa661a: a718lhi %r1,0 >3bfa661e: ba129000cs %r1,%r2,0(%r9) 3bfa6622: a77401a7brc 7,3bfa6970 3bfa6626: e310b0180012lt %r1,24(%r11) 3bfa662c: a78400ff
[Kernel-packages] [Bug 1988219] [NEW] Focal update: v5.4.207 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.207 upstream stable release from git://git.kernel.org/ ALSA: hda - Add fixup for Dell Latitidue E5430 ALSA: hda/conexant: Apply quirk for another HP ProDesk 600 G3 model ALSA: hda/realtek - Fix headset mic problem for a HP machine with alc671 ALSA: hda/realtek - Fix headset mic problem for a HP machine with alc221 ALSA: hda/realtek - Enable the headset-mic on a Xiaomi's laptop xen/netback: avoid entering xenvif_rx_next_skb() with an empty rx queue tracing/histograms: Fix memory leak problem net: sock: tracing: Fix sock_exceed_buf_limit not to dereference stale pointer ip: fix dflt addr selection for connected nexthop ARM: 9213/1: Print message about disabled Spectre workarounds only once ARM: 9214/1: alignment: advance IT state after emulating Thumb instruction wifi: mac80211: fix queue selection for mesh/OCB interfaces cgroup: Use separate src/dst nodes when preloading css_sets for migration drm/panfrost: Fix shrinker list corruption by madvise IOCTL nilfs2: fix incorrect masking of permission flags for symlinks Revert "evm: Fix memleak in init_desc" sched/rt: Disable RT_RUNTIME_SHARE by default ext4: fix race condition between ext4_write and ext4_convert_inline_data ARM: dts: imx6qdl-ts7970: Fix ngpio typo and count ARM: 9209/1: Spectre-BHB: avoid pr_info() every time a CPU comes out of idle ARM: 9210/1: Mark the FDT_FIXED sections as shareable drm/i915: fix a possible refcount leak in intel_dp_add_mst_connector() ima: Fix a potential integer overflow in ima_appraise_measurement ASoC: sgtl5000: Fix noise on shutdown/remove net: stmmac: dwc-qos: Disable split header for Tegra194 inetpeer: Fix data-races around sysctl. net: Fix data-races around sysctl_mem. cipso: Fix data-races around sysctl. icmp: Fix data-races around sysctl. ipv4: Fix a data-race around sysctl_fib_sync_mem. ARM: dts: at91: sama5d2: Fix typo in i2s1 node ARM: dts: sunxi: Fix SPI NOR campatible on Orange Pi Zero drm/i915/gt: Serialize TLB invalidates with GT resets icmp: Fix a data-race around sysctl_icmp_ratelimit. icmp: Fix a data-race around sysctl_icmp_ratemask. raw: Fix a data-race around sysctl_raw_l3mdev_accept. ipv4: Fix data-races around sysctl_ip_dynaddr. net: ftgmac100: Hold reference returned by of_get_child_by_name() sfc: fix use after free when disabling sriov seg6: fix skb checksum evaluation in SRH encapsulation/insertion seg6: fix skb checksum in SRv6 End.B6 and End.B6.Encaps behaviors seg6: bpf: fix skb checksum in bpf_push_seg6_encap() sfc: fix kernel panic when creating VF mm: sysctl: fix missing numa_stat when !CONFIG_HUGETLB_PAGE virtio_mmio: Add missing PM calls to freeze/restore virtio_mmio: Restore guest page size on resume netfilter: br_netfilter: do not skip all hooks with 0 priority cpufreq: pmac32-cpufreq: Fix refcount leak bug platform/x86: hp-wmi: Ignore Sanitization Mode event net: tipc: fix possible refcount leak in tipc_sk_create() NFC: nxp-nci: don't print header length mismatch on i2c error nvme: fix regression when disconnect a recovering ctrl net: sfp: fix memory leak in sfp_probe() ASoC: ops: Fix off by one in range control validation ASoC: wm5110: Fix DRE control ASoC: cs47l15: Fix event generation for low power mux control ASoC: madera: Fix event generation for OUT1 demux ASoC: madera: Fix event generation for rate controls irqchip: or1k-pic: Undefine mask_ack for level triggered hardware x86: Clear .brk area at early boot soc: ixp4xx/npe: Fix unused match warning ARM: dts: stm32: use the correct clock source for CEC on stm32mp151 signal handling: don't use BUG_ON() for debugging USB: serial: ftdi_sio: add Belimo device ids usb: typec: add missing uevent when partner support PD usb: dwc3: gadget: Fix event pending check tty: serial: samsung_tty: set dma burst_size to 1 serial: 8250: fix return error code in serial8250_request_std_resource() serial: stm32: Clear prev values before setting RTS delays serial: pl011: UPSTAT_AUTORTS requires .throttle/unthrottle can: m_can: m_can_tx_handler(): fix use after free of skb Linux 5.4.207 UBUNTU: Upstream stable to v5.4.207 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux
[Kernel-packages] [Bug 1988215] [NEW] Focal update: v5.4.206 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.206 upstream stable release from git://git.kernel.org/ NOTE: This patch set (v5.4.206) is empty; it contained only one revert: Revert "mtd: rawnand: gpmi: Fix setting busy timeout setting" which was never applied to Focal. Linux 5.4.206 UBUNTU: Upstream stable to v5.4.206 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.4.206 upstream stable release + from git://git.kernel.org/ -v5.4.206 upstream stable release -from git://git.kernel.org/ + NOTE: This patch set (v5.4.206) is empty; it contained only one revert: + Revert "mtd: rawnand: gpmi: Fix setting busy timeout setting" + which was never applied to Focal. + + + Linux 5.4.206 + UBUNTU: Upstream stable to v5.4.206 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1988215 Title: Focal update: v5.4.206 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress 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.206 upstream stable release from git://git.kernel.org/ NOTE: This patch set (v5.4.206) is empty; it contained only one revert: Revert "mtd: rawnand: gpmi: Fix setting busy timeout setting" which was never applied to Focal. Linux 5.4.206 UBUNTU: Upstream stable to v5.4.206 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988215/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988214] [NEW] Focal update: v5.4.205 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.205 upstream stable release from git://git.kernel.org/ esp: limit skb_page_frag_refill use to a single page mm/slub: add missing TID updates on slab deactivation can: bcm: use call_rcu() instead of costly synchronize_rcu() can: grcan: grcan_probe(): remove extra of_node_get() can: gs_usb: gs_usb_open/close(): fix memory leak usbnet: fix memory leak in error case net: rose: fix UAF bug caused by rose_t0timer_expiry iommu/vt-d: Fix PCI bus rescan device hot add fbdev: fbmem: Fix logo center image dx issue video: of_display_timing.h: include errno.h powerpc/powernv: delay rng platform device creation until later in boot can: kvaser_usb: replace run-time checks with struct kvaser_usb_driver_info can: kvaser_usb: kvaser_usb_leaf: fix CAN clock frequency regression can: kvaser_usb: kvaser_usb_leaf: fix bittiming limits xfs: remove incorrect ASSERT in xfs_rename ARM: meson: Fix refcount leak in meson_smp_prepare_cpus pinctrl: sunxi: a83t: Fix NAND function name for some pins pinctrl: sunxi: sunxi_pconf_set: use correct offset ARM: at91: pm: use proper compatible for sama5d2's rtc ARM: at91: pm: use proper compatibles for sam9x60's rtc and rtt ibmvnic: Properly dispose of all skbs during a failover. selftests: forwarding: fix flood_unicast_test when h2 supports IFF_UNICAST_FLT selftests: forwarding: fix learning_test when h1 supports IFF_UNICAST_FLT selftests: forwarding: fix error message in learning_test i2c: cadence: Unregister the clk notifier in error path dmaengine: imx-sdma: Allow imx8m for imx7 FW revs misc: rtsx_usb: fix use of dma mapped buffer for usb bulk transfer misc: rtsx_usb: use separate command and response buffers misc: rtsx_usb: set return value in rsp_buf alloc err path dt-bindings: dma: allwinner,sun50i-a64-dma: Fix min/max typo ida: don't use BUG_ON() for debugging dmaengine: pl330: Fix lockdep warning about non-static key dmaengine: at_xdma: handle errors of at_xdmac_alloc_desc() correctly dmaengine: ti: Fix refcount leak in ti_dra7_xbar_route_allocate dmaengine: ti: Add missing put_device in ti_dra7_xbar_route_allocate Linux 5.4.205 UBUNTU: Upstream stable to v5.4.205 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.4.205 upstream stable release + from git://git.kernel.org/ -v5.4.205 upstream stable release -from git://git.kernel.org/ + esp: limit skb_page_frag_refill use to a single page + mm/slub: add missing TID updates on slab deactivation + can: bcm: use call_rcu() instead of costly synchronize_rcu() + can: grcan: grcan_probe(): remove extra of_node_get() + can: gs_usb: gs_usb_open/close(): fix memory leak + usbnet: fix memory leak in error case + net: rose: fix UAF bug caused by rose_t0timer_expiry + iommu/vt-d: Fix PCI bus rescan device hot add + fbdev: fbmem: Fix logo center image dx issue + video: of_display_timing.h: include errno.h +
[Kernel-packages] [Bug 1988209] Re: application does not display anything
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: https://iso.qa.ubuntu.com/qatracker/reports/bugs/1988209 ** Tags added: iso-testing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1988209 Title: application does not display anything Status in nvidia-settings package in Ubuntu: New Bug description: I just did a fresh install of Ubuntu 20.04.5 and the when launching nvidia-settings the GUI does not display anything. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-settings 470.57.01-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 30 11:06:06 2022 InstallationDate: Installed on 2022-08-30 (0 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220829.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1988209/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988209] Re: application does not display anything
This was visible in the terminal when I ran nvidia-settings: ERROR: Unable to load info from any available system (nvidia-settings:7822): GLib-GObject-CRITICAL **: 11:42:14.321: g_object_unref: assertion 'G_IS_OBJECT (object)' failed ** Message: 11:42:14.326: PRIME: No offloading required. Abort ** Message: 11:42:14.326: PRIME: is it supported? no However, I am using the nvidia driver: bdmurray@bdmurray-Standard-PC-Q35-ICH9-2009:~$ nvidia-detector nvidia-driver-470 bdmurray@bdmurray-Standard-PC-Q35-ICH9-2009:~$ lsmod | grep nvidia nvidia_uvm 1204224 0 nvidia_drm 69632 0 nvidia_modeset 1200128 1 nvidia_drm nvidia 35446784 8 nvidia_uvm,nvidia_modeset drm_kms_helper307200 4 qxl,nvidia_drm drm 618496 9 drm_kms_helper,qxl,nvidia,drm_ttm_helper,nvidia_drm,ttm -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1988209 Title: application does not display anything Status in nvidia-settings package in Ubuntu: New Bug description: I just did a fresh install of Ubuntu 20.04.5 and the when launching nvidia-settings the GUI does not display anything. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-settings 470.57.01-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 30 11:06:06 2022 InstallationDate: Installed on 2022-08-30 (0 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220829.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1988209/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988212] [NEW] Focal update: v5.4.204 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.204 upstream stable release from git://git.kernel.org/ ipv6: take care of disable_policy when restoring routes nvdimm: Fix badblocks clear off-by-one error powerpc/prom_init: Fix kernel config grep powerpc/bpf: Fix use of user_pt_regs in uapi dm raid: fix accesses beyond end of raid member array dm raid: fix KASAN warning in raid5_add_disks s390/archrandom: simplify back to earlier design and initialize earlier SUNRPC: Fix READ_PLUS crasher net: rose: fix UAF bugs caused by timer handler net: usb: ax88179_178a: Fix packet receiving virtio-net: fix race between ndo_open() and virtio_device_ready() selftests/net: pass ipv6_args to udpgso_bench's IPv6 TCP test net: tun: unlink NAPI from device on destruction net: tun: stop NAPI when detaching queues RDMA/qedr: Fix reporting QP timeout attribute linux/dim: Fix divide by 0 in RDMA DIM usbnet: fix memory allocation in helpers net: ipv6: unexport __init-annotated seg6_hmac_net_init() caif_virtio: fix race between virtio_device_ready() and ndo_open() PM / devfreq: exynos-ppmu: Fix refcount leak in of_get_devfreq_events s390: remove unneeded 'select BUILD_BIN2C' netfilter: nft_dynset: restore set element counter when failing to update net/sched: act_api: Notify user space if any actions were flushed before error net: bonding: fix possible NULL deref in rlb code net: bonding: fix use-after-free after 802.3ad slave unbind nfc: nfcmrvl: Fix irq_of_parse_and_map() return value NFC: nxp-nci: Don't issue a zero length i2c_master_read() net: tun: avoid disabling NAPI twice xen/gntdev: Avoid blocking in unmap_grant_pages() hwmon: (ibmaem) don't call platform_device_del() if platform_device_add() fails net: dsa: bcm_sf2: force pause link settings sit: use min ipv6/sit: fix ipip6_tunnel_get_prl return value rseq/selftests,x86_64: Add rseq_offset_deref_addv() selftests/rseq: remove ARRAY_SIZE define from individual tests selftests/rseq: introduce own copy of rseq uapi header selftests/rseq: Remove useless assignment to cpu variable selftests/rseq: Remove volatile from __rseq_abi selftests/rseq: Introduce rseq_get_abi() helper selftests/rseq: Introduce thread pointer getters selftests/rseq: Uplift rseq selftests for compatibility with glibc-2.35 selftests/rseq: Fix ppc32: wrong rseq_cs 32-bit field pointer on big endian selftests/rseq: Fix ppc32 missing instruction selection "u" and "x" for load/store selftests/rseq: Fix ppc32 offsets by using long rather than off_t selftests/rseq: Fix warnings about #if checks of undefined tokens selftests/rseq: Remove arm/mips asm goto compiler work-around selftests/rseq: Fix: work-around asm goto compiler bugs selftests/rseq: x86-64: use %fs segment selector for accessing rseq thread area selftests/rseq: x86-32: use %gs segment selector for accessing rseq thread area selftests/rseq: Change type of rseq_offset to ptrdiff_t xen/blkfront: fix leaking data in shared pages xen/netfront: fix leaking data in shared pages xen/netfront: force data bouncing when backend is untrusted xen/blkfront: force data bouncing when backend is untrusted xen/arm: Fix race in RB-tree based P2M accounting net: usb: qmi_wwan: add Telit 0x1060 composition net: usb: qmi_wwan: add Telit 0x1070 composition clocksource/drivers/ixp4xx: remove EXPORT_SYMBOL_GPL from ixp4xx_timer_setup() Linux 5.4.204 UBUNTU: Upstream stable to v5.4.204 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The
[Kernel-packages] [Bug 1988207] Re: Kinetic update: v5.19.5 upstream stable release
** Changed in: linux (Ubuntu Kinetic) 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/1988207 Title: Kinetic update: v5.19.5 upstream stable release Status in linux package in Ubuntu: Fix Committed Status in linux source package in Kinetic: 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.19.5 upstream stable release from git://git.kernel.org/ kbuild: dummy-tools: avoid tmpdir leak in dummy gcc Linux 5.19.5 UBUNTU: Upstream stable to v5.19.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988207/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900929] Re: after install, invoking nvidia-settings shows no driver
I'm going to go ahead and close this given we are missing some information and I've reported a similar bug (1988209) already. ** Changed in: nvidia-settings (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1900929 Title: after install, invoking nvidia-settings shows no driver Status in NVIDIA Drivers Ubuntu: New Status in nvidia-settings package in Ubuntu: Invalid Bug description: Using MUON, installed the nvidia driver metapackage for 450. [note; this bug applies to all packages, 390, 330, etc]. Using terminal, when invoking nvidia-settings, the nvidia window is completely blank and the following errors are reported... (process:18974): Gtk-WARNING **: 08:23:46.948: Locale not supported by C library. Using the fallback 'C' locale. ERROR: NVIDIA driver is not loaded ERROR: Unable to load info from any available system (nvidia-settings:18974): GLib-GObject-CRITICAL **: 08:23:47.413: g_object_unref: assertion 'G_IS_OBJECT (object)' failed ** Message: 08:23:47.420: PRIME: No offloading required. Abort ** Message: 08:23:47.420: PRIME: is it supported? no Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.4.0-52-generic OS Type: 64-bit Processors: 6 × AMD FX(tm)-6300 Six-Core Processor Memory: 31.3 GiB of RAM To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1900929/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988209] Re: application does not display anything
Its empty. ** Attachment added: "Screenshot from 2022-08-30 11-09-59.png" https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1988209/+attachment/5612573/+files/Screenshot%20from%202022-08-30%2011-09-59.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1988209 Title: application does not display anything Status in nvidia-settings package in Ubuntu: New Bug description: I just did a fresh install of Ubuntu 20.04.5 and the when launching nvidia-settings the GUI does not display anything. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-settings 470.57.01-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 30 11:06:06 2022 InstallationDate: Installed on 2022-08-30 (0 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220829.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1988209/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988209] [NEW] application does not display anything
Public bug reported: I just did a fresh install of Ubuntu 20.04.5 and the when launching nvidia-settings the GUI does not display anything. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-settings 470.57.01-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 30 11:06:06 2022 InstallationDate: Installed on 2022-08-30 (0 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220829.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1988209 Title: application does not display anything Status in nvidia-settings package in Ubuntu: New Bug description: I just did a fresh install of Ubuntu 20.04.5 and the when launching nvidia-settings the GUI does not display anything. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-settings 470.57.01-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 30 11:06:06 2022 InstallationDate: Installed on 2022-08-30 (0 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220829.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1988209/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988207] [NEW] Kinetic update: v5.19.5 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.19.5 upstream stable release from git://git.kernel.org/ kbuild: dummy-tools: avoid tmpdir leak in dummy gcc Linux 5.19.5 UBUNTU: Upstream stable to v5.19.5 ** Affects: linux (Ubuntu) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Affects: linux (Ubuntu Kinetic) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: Confirmed ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.19.5 upstream stable release + from git://git.kernel.org/ -v5.19.5 upstream stable release -from git://git.kernel.org/ + kbuild: dummy-tools: avoid tmpdir leak in dummy gcc + Linux 5.19.5 + UBUNTU: Upstream stable to v5.19.5 ** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu Kinetic) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1988207 Title: Kinetic update: v5.19.5 upstream stable release Status in linux package in Ubuntu: In Progress Status in linux source package in Kinetic: In Progress 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.19.5 upstream stable release from git://git.kernel.org/ kbuild: dummy-tools: avoid tmpdir leak in dummy gcc Linux 5.19.5 UBUNTU: Upstream stable to v5.19.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988207/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987287] Comment bridged from LTC Bugzilla
--- Comment From naf...@cn.ibm.com 2022-08-30 12:28 EDT--- @Canonical, I'd like to know that when will the fix be back ported to hwe-5.4 kernel? Will it be a new hotpatch like this one ? https://launchpad.net/~canonical-support-eng/+archive/ubuntu/sf334332 or something else. Thanks so much. Sorry I am not familiar with the process, and just like to know how can I include the fix in our cloud environment. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987287 Title: [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: New Bug description: We recently got a bug report for systems running Ubuntu 20.04 that were crashing with backtraces pointing at the mlx5 driver's handling of mlx5_ethtool_get_link_ksettings() when this is called through the sysfs (going through ethtool might have different checks). I managed to find a reliable way to reproduce the issue that I believe isn't tied to IBM Z at all. The procedure to reproduce is as follows. I created a script to read the sysfs attributes for the link's speed and duplex mode in a loop: #!/usr/bin/env bash if [ $# -lt 1 ]; then echo "Usage: $0 " exit 1 fi while true; do cat /sys/class/net/$1/duplex > /dev/null cat /sys/class/net/$1/speed > /dev/null done Executed with: # ./script.sh enP10p0s0 I ran this in one bash session and then in another one I triggered a PCI reset with the follwoing command where one needs to replace with the PCI address of the NIC: echo 1 > /sys/bus/pci/devices//reset Then first I got a lot of the following messages: mlx5_core 0010:00:00.0 enP16p0s0: mlx5e_ethtool_get_link_ksettings: query port ptys failed: -5 And then as the mlx5 driver's recovery kicks in the oops as below: [ 659.103947] mlx5_core 0010:00:00.0: wait vital counter value 0x7b399f after 1 iterations [ 659.103947] mlx5_core 0010:00:00.0: mlx5_pci_resume was called [ 659.103966] mlx5_core 0010:00:00.0: firmware version: 14.32.1010 [ 659.104169] Unable to handle kernel pointer dereference in virtual kernel address space [ 659.104171] Failing address: TEID: 0483 [ 659.104172] Fault in home space mode while using kernel ASCE. [ 659.104173] AS:3d29c007 R3:fffd0007 S:fffd5800 P:003d [ 659.104200] Oops: 0004 ilc:2 [#1] SMP [ 659.104202] Modules linked in: s390_trng ism smc pnet chsc_sch eadm_sch vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel drm drm_panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear mlx5_ib dm_service_time pkey zcrypt crc32_vx_s390 ib_uverbs ghash_s390 ib_core qeth_l2 prng aes_s390 des_s390 nvme libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common mlx5_core tls mlxfw ptp nvme_core pps_core dasd_eckd_mod dasd_mod zfcp scsi_transport_fc qeth qdio ccwgroup scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath [ 659.104232] CPU: 6 PID: 438216 Comm: cat Not tainted 5.4.0-124-generic #140-Ubuntu [ 659.104233] Hardware name: IBM 3931 XYZ (LPAR) [ 659.104234] Krnl PSW : 0404c0018000 3bfa661e (__queue_work+0xfe/0x520) [ 659.104241]R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 [ 659.104242] Krnl GPRS: 3c291570 0007 7fff [ 659.104243]e2fe46e0 000fffe0 0006 3d039588 [ 659.104244] e2fe46e0 bfb3e000 [ 659.104245]e194c400 03e007d6fb78 3bfa6602 03e007d6f860 [ 659.104251] Krnl Code: 3bfa6612: a77400e5brc 7,3bfa67dc 3bfa6616: 582003acl %r2,940 #3bfa661a: a718lhi %r1,0 >3bfa661e: ba129000cs %r1,%r2,0(%r9) 3bfa6622: a77401a7brc 7,3bfa6970 3bfa6626: e310b0180012lt %r1,24(%r11) 3bfa662c: a78400ffbrc 8,3bfa682a 3bfa6630: c004004bbrcl 0,3bfa66c6 [ 659.104261] Call Trace: [ 659.104263] ([<>] 0x0) [ 659.104265] [<3bfa6aa2>] queue_work_on+0x62/0x70 [ 659.104329] [<03ff80a2920a>]
[Kernel-packages] [Bug 1984103] Re: [UBUNTU 22.04] s390/qeth: cache link_info for ethtool
** Tags added: patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1984103
Title:
[UBUNTU 22.04] s390/qeth: cache link_info for ethtool
Status in Ubuntu on IBM z Systems:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
Confirmed
Status in linux source package in Kinetic:
Confirmed
Bug description:
== Comment: #0 - J?rn Siglen - 2022-08-09 07:38:27 ==
+++ This bug was initially created as a clone of Bug #199319 +++
Description: s390/qeth: cache link_info for ethtool
Symptom: lost of IP connection and log entries in journalctl:
kernel: qeth 0.0.0365: The qeth device driver failed to
recover an error on the device
Problem: Since commit e6e771b3d897
("s390/qeth: detach netdevice while card is offline")
there was a timing window during recovery, that
qeth_query_card_info could be sent to the card, even before it
was ready for it, leading to a failing card recovery. There is
evidence that this window was hit, as not all callers of
get_link_ksettings() check for netif_device_present.
Solution: Use cached values in qeth_get_link_ksettings(), instead of
calling qeth_query_card_info() and falling back to default
values in case it fails. Link info is already updated when the
card goes online, e.g. after STARTLAN (physical link up). Set
the link info to default values, when the card goes offline or
at STOPLAN (physical link down). A follow-on patch will improve
values reported for link down.
Fixes: e6e771b3d897
("s390/qeth: detach netdevice while card is offline")
Reproduction: enforce a eth device recvoery, while running ethtool multiple
times in parallel and using iperf to get load on the interface.
Upstream-ID: 7a07a29e4f6713b224f3bcde5f835e777301bdb8
https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f
applicable for most kernel > 3.14
== Comment: #3 - J?rn Siglen - 2022-08-09 07:54:41 ==
the inital update came in with kernel 5.1 upstream, but we found it
backported in many older kernel versions
== Comment: #4 - J?rn Siglen - 2022-08-09 08:03:09 ==
the acceptance info of the patch can be found here:
https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1984103/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988198] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1988198 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1988198 Title: cheese reports error on webcam Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 5.15.0-46.49-generic 5.15.39 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [8086:1904] (rev 08) Subsystem: Fujitsu Limited. Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [10cf:18d0] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Skylake GT2 [HD Graphics 520] [10cf:18d3] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ FLReset+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis- NROPrPrP- LTR- 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS- AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- OBFF Disabled, AtomicOpsCtl: ReqEn- Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee02004 Data: 0023 Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec+ Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped- Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI]) Subsystem: Fujitsu Limited. Sunrise Point-LP USB 3.0 xHCI Controller [10cf:18d0] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend- LnkCap: Port #5, Speed 8GT/s, Width x1, ASPM L1, Exit Latency L1 <16us ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+ LnkCtl: ASPM L1
[Kernel-packages] [Bug 1002952] Re: [meta-bug] Invalid extra "Digital output S/PDIF" device for USB cards
This issue also exists for "Yeti Stereo Microphone" and "HD Pro Webcam C920". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1002952 Title: [meta-bug] Invalid extra "Digital output S/PDIF" device for USB cards Status in alsa-lib package in Ubuntu: Confirmed Bug description: === Read me first === = Symptom = If you have a USB headset, or other USB device that does not have any S/PDIF output, but yet sometimes there is an extra device called "Digital Output (S/PDIF)" for that device, you're suffering from this bug. This bug is only for USB devices - if you have an invalid digital output for some other type of device, please file a separate bug instead. = Workaround = If you're affected, please try this workaround: first check the output of "aplay -l" (lowercase L), or "arecord -l" if it's an input device, and grab the first of two name in brackets: Example: card 3: Headset [Sennheiser USB Headset], device 0: USB Audio [USB Audio] here grab the name "Sennheiser USB Headset". Now edit the file /usr/share/alsa/cards/USB-Audio.conf (requires root permissions) Around line 40, you will find a line saying "Logitech USB Headset" 999 Add a new line after this line, so that there is now a new line called "Sennheiser USB Headset" 999 (including quotes, and replace "Sennheiser USB Headset" with whatever your particular card was named.) Save the file and reboot your computer for the changes to take effect. = Already known devices = These card names are already in 12.04: "Blue Snowball" "Logitech USB Headset" "Logitech Web Camera" These card names are on their way into 12.04: "Logitech Speaker Lapdesk N700" "Logitech Wireless Headset" "Plantronics USB Headset" "Sennheiser USB headset" If you have one of the above four, please help out by testing the proposed repository and report back in bug 987163. If your name is not listed above, please add a comment to this bug, including your alsa-info: https://wiki.ubuntu.com/Audio/AlsaInfo - they will be collected for a SRU later on, or at least make it into the next release of Ubuntu. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1002952/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988198] [NEW] cheese reports error on webcam
Public bug reported: Ubuntu 5.15.0-46.49-generic 5.15.39 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [8086:1904] (rev 08) Subsystem: Fujitsu Limited. Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [10cf:18d0] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Skylake GT2 [HD Graphics 520] [10cf:18d3] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ FLReset+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis- NROPrPrP- LTR- 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS- AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- OBFF Disabled, AtomicOpsCtl: ReqEn- Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee02004 Data: 0023 Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec+ Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped- Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI]) Subsystem: Fujitsu Limited. Sunrise Point-LP USB 3.0 xHCI Controller [10cf:18d0] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend- LnkCap: Port #5, Speed 8GT/s, Width x1, ASPM L1, Exit Latency L1 <16us ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+ LnkCtl: ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s (downgraded), Width x1 (ok) TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #4, PowerLimit 10.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet- LinkState+ RootCap: CRSVisible- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible-
[Kernel-packages] [Bug 386799] Re: Restart required for webcam to work; how to manually restart?
The bug seems to be unbeatable. Still happening on Ubuntu 22.04 LTS on a Samsung NP550XDAE laptop. I'm using an integrated camera: $ lsmod | grep uvcvideo uvcvideo 106496 2 videobuf2_vmalloc 20480 1 uvcvideo videobuf2_v4l2 32768 1 uvcvideo videobuf2_common 77824 4 videobuf2_vmalloc,videobuf2_v4l2,uvcvideo,videobuf2_memops videodev 258048 5 videobuf2_v4l2,uvcvideo,videobuf2_common mc 65536 4 videodev,videobuf2_v4l2,uvcvideo,videobuf2_common $ lsusb |grep -i camera Bus 003 Device 003: ID 05c8:023a Cheng Uei Precision Industry Co., Ltd (Foxlink) VGA Camera -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/386799 Title: Restart required for webcam to work; how to manually restart? Status in linux package in Ubuntu: Won't Fix Bug description: http://ubuntuforums.org/showthread.php?p=7451356#post7451356 shows another user with the same problem. I have a lapto HP pavillion Linux patricio-laptop 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux From the kern.log: /var/log/kern.log:Jun 13 15:20:31 patricio-laptop kernel: [29606.529587] uvcvideo 2-4:1.1: resume error -5 /var/log/kern.log:Jun 13 15:26:01 patricio-laptop kernel: [29937.049414] uvcvideo: Failed to query (135) UVC control 2 (unit 3) : -71 (exp. 2). /var/log/kern.log:Jun 13 15:32:04 patricio-laptop kernel: [30300.054961] uvcvideo: Failed to query (135) UVC control 2 (unit 3) : -71 (exp. 2). lsusb Bus 002 Device 002: ID 04f2:b015 Chicony Electronics Co., Ltd VGA 24fps UVC Webcam To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/386799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1699942] Re: network-manager fails to deprecate addresses
The bug is from 2017 without activity until now, from a desktop perspective it isn't a rls issue, tagging a notfixing ** Tags removed: rls-kk-incoming ** Tags added: rls-kk-notfixing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1699942 Title: network-manager fails to deprecate addresses Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Triaged Status in systemd package in Ubuntu: New Bug description: network manager does not properly deprecate autoconfigured temporary IP addresses when ValidLifetime for a prefix is 0 in router advertisements. This behaviour is non-compliant with RFC 4861 § 6.3.4, which reads: If the prefix is already present in the host's Prefix List as the result of a previously received advertisement, reset its invalidation timer to the Valid Lifetime value in the Prefix Information option. If the new Lifetime value is zero, time-out the prefix immediately. The hosts instead continued to use temporary addresses configured until they reached their timeout, rather than immediately dropping the addresses. It further appears that it is generating new temporary addresses when the previous ones expire, but I have not been monitoring hosts closely enough to tell for sure---I will update on this when I have further information. This problem was discovered on Ubuntu Studio 16.04.2; it is not present on Ubuntu Server (which uses Debian networking scripts). Additional Info: $ lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 $ apt-cache policy network-manager network-manager: Installed: 1.2.6-0ubuntu0.16.04.1 Candidate: 1.2.6-0ubuntu0.16.04.1 Version table: *** 1.2.6-0ubuntu0.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.2.2-0ubuntu0.16.04.4 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 1.1.93-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699942/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987870] Re: Demote to proposed LRM portions of intel-iotg
This bug report must stay open to prevent the LRM intel-iotg migrating back in again. ** Changed in: linux-restricted-signatures-intel-iotg (Ubuntu) Status: Fix Released => Triaged ** Changed in: linux-restricted-modules-intel-iotg (Ubuntu) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/1987870 Title: Demote to proposed LRM portions of intel-iotg Status in linux-restricted-modules-intel-iotg package in Ubuntu: Triaged Status in linux-restricted-signatures-intel-iotg package in Ubuntu: Triaged Bug description: v5.19 kernels are ready to migrate in kinetic. via new nvidia and LRM packages all kernels are entangled. intel-iotg kernel has not yet been upgraded to v5.19. to allow src:linux-meta migration, we need to demote to proposed LRM/LRS of intel-iotg kernel to unblock development. an updated version of intel-iotg kernel will happen a bit later. Please demote to proposed linux-restricted-modules-intel-iotg linux- restricted-signatures-intel-iotg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-intel-iotg/+bug/1987870/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984103] Re: [UBUNTU 22.04] s390/qeth: cache link_info for ethtool
I prepared a test kernel with the proposed patch (that was a clear
cherry pick for 5.15). Frank do you think you can help me validating the
test kernel?
You can find a tarball with the debian packages for the test kernel at:
https://kernel.ubuntu.com/~mhcerri/test/lp1984103/linux-unsigned-
debs-5.15.0-48.54+lp1984103.1_s390x.tgz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1984103
Title:
[UBUNTU 22.04] s390/qeth: cache link_info for ethtool
Status in Ubuntu on IBM z Systems:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
Confirmed
Status in linux source package in Kinetic:
Confirmed
Bug description:
== Comment: #0 - J?rn Siglen - 2022-08-09 07:38:27 ==
+++ This bug was initially created as a clone of Bug #199319 +++
Description: s390/qeth: cache link_info for ethtool
Symptom: lost of IP connection and log entries in journalctl:
kernel: qeth 0.0.0365: The qeth device driver failed to
recover an error on the device
Problem: Since commit e6e771b3d897
("s390/qeth: detach netdevice while card is offline")
there was a timing window during recovery, that
qeth_query_card_info could be sent to the card, even before it
was ready for it, leading to a failing card recovery. There is
evidence that this window was hit, as not all callers of
get_link_ksettings() check for netif_device_present.
Solution: Use cached values in qeth_get_link_ksettings(), instead of
calling qeth_query_card_info() and falling back to default
values in case it fails. Link info is already updated when the
card goes online, e.g. after STARTLAN (physical link up). Set
the link info to default values, when the card goes offline or
at STOPLAN (physical link down). A follow-on patch will improve
values reported for link down.
Fixes: e6e771b3d897
("s390/qeth: detach netdevice while card is offline")
Reproduction: enforce a eth device recvoery, while running ethtool multiple
times in parallel and using iperf to get load on the interface.
Upstream-ID: 7a07a29e4f6713b224f3bcde5f835e777301bdb8
https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f
applicable for most kernel > 3.14
== Comment: #3 - J?rn Siglen - 2022-08-09 07:54:41 ==
the inital update came in with kernel 5.1 upstream, but we found it
backported in many older kernel versions
== Comment: #4 - J?rn Siglen - 2022-08-09 08:03:09 ==
the acceptance info of the patch can be found here:
https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1984103/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984103] Re: [UBUNTU 22.04] s390/qeth: cache link_info for ethtool
** Patch added: "0001-s390-qeth-cache-link_info-for-ethtool.patch"
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1984103/+attachment/5612535/+files/0001-s390-qeth-cache-link_info-for-ethtool.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1984103
Title:
[UBUNTU 22.04] s390/qeth: cache link_info for ethtool
Status in Ubuntu on IBM z Systems:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
Confirmed
Status in linux source package in Kinetic:
Confirmed
Bug description:
== Comment: #0 - J?rn Siglen - 2022-08-09 07:38:27 ==
+++ This bug was initially created as a clone of Bug #199319 +++
Description: s390/qeth: cache link_info for ethtool
Symptom: lost of IP connection and log entries in journalctl:
kernel: qeth 0.0.0365: The qeth device driver failed to
recover an error on the device
Problem: Since commit e6e771b3d897
("s390/qeth: detach netdevice while card is offline")
there was a timing window during recovery, that
qeth_query_card_info could be sent to the card, even before it
was ready for it, leading to a failing card recovery. There is
evidence that this window was hit, as not all callers of
get_link_ksettings() check for netif_device_present.
Solution: Use cached values in qeth_get_link_ksettings(), instead of
calling qeth_query_card_info() and falling back to default
values in case it fails. Link info is already updated when the
card goes online, e.g. after STARTLAN (physical link up). Set
the link info to default values, when the card goes offline or
at STOPLAN (physical link down). A follow-on patch will improve
values reported for link down.
Fixes: e6e771b3d897
("s390/qeth: detach netdevice while card is offline")
Reproduction: enforce a eth device recvoery, while running ethtool multiple
times in parallel and using iperf to get load on the interface.
Upstream-ID: 7a07a29e4f6713b224f3bcde5f835e777301bdb8
https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f
applicable for most kernel > 3.14
== Comment: #3 - J?rn Siglen - 2022-08-09 07:54:41 ==
the inital update came in with kernel 5.1 upstream, but we found it
backported in many older kernel versions
== Comment: #4 - J?rn Siglen - 2022-08-09 08:03:09 ==
the acceptance info of the patch can be found here:
https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1984103/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977929] Re: Resume from suspend to ram doesn't work
I no longer see this issue with the recent kernels. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1977929 Title: Resume from suspend to ram doesn't work Status in linux package in Ubuntu: Confirmed Bug description: On Dell Latitude E7450 laptop, with Ubuntu 22.04, suspending to ram goes fine. When resuming, the disk led light is on all the time, and there are lots of SATA errors in the dmesg. Afaics, the disk (or the controller) does not work at all, and only forced power off and reboot will help. Resume worked fine on Ubuntu 20.04, and I just installed linux-image- unsigned-5.18.2-051802-generic, on which resume also works fine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-37-generic 5.15.0-37.39 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tomba 1708 F pulseaudio /dev/snd/controlC1: tomba 1708 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 8 09:59:36 2022 InstallationDate: Installed on 2022-05-28 (10 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Latitude E7450 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic root=UUID=fc8e2740-8ddd-431b-88e7-116f3d03d8d6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-37-generic N/A linux-backports-modules-5.15.0-37-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2020 dmi.bios.release: 65.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: A24 dmi.board.name: 0D8H72 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA24:bd04/11/2020:br65.24:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0D8H72:rvrA00:cvnDellInc.:ct9:cvr:sku062E: dmi.product.name: Latitude E7450 dmi.product.sku: 062E dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1977929/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971699] Re: disable Intel DMA remapping by default
> * disable Intel DMA remapping by default (LP: #1971699) Doesn't this add a massive security issue, in that you can plug a malicious thunderbolt peripheral into any Ubuntu laptop and read the entire unencrypted RAM space? The IOMMU is there for a reason... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971699 Title: disable Intel DMA remapping by default Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: [Impact] It seems that enabling Intel IOMMU can cause some weird gfx problems, see for example: https://bugs.launchpad.net/bugs/1971146 https://bugs.launchpad.net/bugs/1965882 [Test case] We don't have any specific test case, only other bug reports that tracked down the origin of the issue as being introduced when CONFIG_INTEL_IOMMU_DEFAULT_ON has been enabled by default. [Fix] Revert "UBUNTU: [Config] enable Intel DMA remapping options by default" [Regression potential] DMA remapping device not present at boot by default, users that require this feature will need to specifically add intel_iommu=on to the kernel boot parameters to enable it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988143] Re: 20.04.5 (20220829.1 build) has kernel 5.13 packages
** Description changed: + [Impact] + + * Linux-restricted-modules for the 390 drivers were disabled + temporarily back in January, however they were not re-enabled when + support for the new kernel was added. + + * Including the 390 release in the ISO causes the 5.13 packages to be + pulled in. + + [Test Plan] + + * Install the hwe-515 kernel and make sure that the NVIDIA 390 driver + can be installed with its linux-restricted-modules. + + [Where problems could occur] + + * The addition of modules for an already existing driver series would not +cause any regressions, since the whole package generation process is automated, and this is the only commit that we are going to revert: + https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-restricted-modules/+git/focal/commit/?h=hwe-5.15=0dfff8472e3e4e75e8effc5957ba6b89a9eaf020 + + [Other Info] + + * Anything else you think is useful to include + * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board + * and address these questions in advance + _ + Examining the .list file for the amd64 image it contains various kernel 5.13 .deb packages. http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop- amd64.list e.g. /pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb /pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb This is a little unexpected given that 5.15 is the default kernel. Possibly nvidia-390 doesn't have 5.15 packages? This impacts all flavours as well that include nvidia stuff in their ISO - so if the solution is to change the meta file for a revised regexp for nvidia then all flavours that include nvidia will likewise need their meta packages updated. ** Description changed: [Impact] - * Linux-restricted-modules for the 390 drivers were disabled + * Linux-restricted-modules for the 390 drivers were disabled temporarily back in January, however they were not re-enabled when support for the new kernel was added. - * Including the 390 release in the ISO causes the 5.13 packages to be + * Including the 390 release in the ISO causes the 5.13 packages to be pulled in. [Test Plan] - * Install the hwe-515 kernel and make sure that the NVIDIA 390 driver + * Install the hwe-515 kernel and make sure that the NVIDIA 390 driver can be installed with its linux-restricted-modules. [Where problems could occur] - * The addition of modules for an already existing driver series would not -cause any regressions, since the whole package generation process is automated, and this is the only commit that we are going to revert: + * The addition of modules for an already existing driver series would not + cause any regressions, since the whole package generation process is automated, and this is the only commit that we are going to revert: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-restricted-modules/+git/focal/commit/?h=hwe-5.15=0dfff8472e3e4e75e8effc5957ba6b89a9eaf020 [Other Info] - - * Anything else you think is useful to include - * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board - * and address these questions in advance + + * Other kernel releases support the 390 series. _ Examining the .list file for the amd64 image it contains various kernel 5.13 .deb packages. http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop- amd64.list e.g. /pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb /pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb This is a little unexpected given that 5.15 is the default kernel. Possibly nvidia-390 doesn't have 5.15 packages? This impacts all flavours as well that include nvidia stuff in their ISO - so if the solution is to change the meta file for a revised regexp for nvidia then all flavours that include nvidia will likewise need their meta packages updated.
[Kernel-packages] [Bug 1984103] Re: [UBUNTU 22.04] s390/qeth: cache link_info for ethtool
Yepp, it's all about kernel patches.
This bug was wrongly marked as affecting the ethtool (well, it affects the
ethtool, but not in the 'affects' send of Launchpad), which caused some
confusion.
I just changed that, pointing now to the kernel (which is "linux (Ubuntu)" in
the above affects section).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1984103
Title:
[UBUNTU 22.04] s390/qeth: cache link_info for ethtool
Status in Ubuntu on IBM z Systems:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
Confirmed
Status in linux source package in Kinetic:
Confirmed
Bug description:
== Comment: #0 - J?rn Siglen - 2022-08-09 07:38:27 ==
+++ This bug was initially created as a clone of Bug #199319 +++
Description: s390/qeth: cache link_info for ethtool
Symptom: lost of IP connection and log entries in journalctl:
kernel: qeth 0.0.0365: The qeth device driver failed to
recover an error on the device
Problem: Since commit e6e771b3d897
("s390/qeth: detach netdevice while card is offline")
there was a timing window during recovery, that
qeth_query_card_info could be sent to the card, even before it
was ready for it, leading to a failing card recovery. There is
evidence that this window was hit, as not all callers of
get_link_ksettings() check for netif_device_present.
Solution: Use cached values in qeth_get_link_ksettings(), instead of
calling qeth_query_card_info() and falling back to default
values in case it fails. Link info is already updated when the
card goes online, e.g. after STARTLAN (physical link up). Set
the link info to default values, when the card goes offline or
at STOPLAN (physical link down). A follow-on patch will improve
values reported for link down.
Fixes: e6e771b3d897
("s390/qeth: detach netdevice while card is offline")
Reproduction: enforce a eth device recvoery, while running ethtool multiple
times in parallel and using iperf to get load on the interface.
Upstream-ID: 7a07a29e4f6713b224f3bcde5f835e777301bdb8
https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f
applicable for most kernel > 3.14
== Comment: #3 - J?rn Siglen - 2022-08-09 07:54:41 ==
the inital update came in with kernel 5.1 upstream, but we found it
backported in many older kernel versions
== Comment: #4 - J?rn Siglen - 2022-08-09 08:03:09 ==
the acceptance info of the patch can be found here:
https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1984103/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984103] Comment bridged from LTC Bugzilla
--- Comment From tsta...@de.ibm.com 2022-08-30 08:13 EDT---
(In reply to comment #12)
> canonical-kernel-team does not monitor or respond to userpsace ethtool
> package bugs; this bug should have gone to the server team triage.
This is a _kernel_ patch that fixes output used by ethtool.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1984103
Title:
[UBUNTU 22.04] s390/qeth: cache link_info for ethtool
Status in Ubuntu on IBM z Systems:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
Confirmed
Status in linux source package in Kinetic:
Confirmed
Bug description:
== Comment: #0 - J?rn Siglen - 2022-08-09 07:38:27 ==
+++ This bug was initially created as a clone of Bug #199319 +++
Description: s390/qeth: cache link_info for ethtool
Symptom: lost of IP connection and log entries in journalctl:
kernel: qeth 0.0.0365: The qeth device driver failed to
recover an error on the device
Problem: Since commit e6e771b3d897
("s390/qeth: detach netdevice while card is offline")
there was a timing window during recovery, that
qeth_query_card_info could be sent to the card, even before it
was ready for it, leading to a failing card recovery. There is
evidence that this window was hit, as not all callers of
get_link_ksettings() check for netif_device_present.
Solution: Use cached values in qeth_get_link_ksettings(), instead of
calling qeth_query_card_info() and falling back to default
values in case it fails. Link info is already updated when the
card goes online, e.g. after STARTLAN (physical link up). Set
the link info to default values, when the card goes offline or
at STOPLAN (physical link down). A follow-on patch will improve
values reported for link down.
Fixes: e6e771b3d897
("s390/qeth: detach netdevice while card is offline")
Reproduction: enforce a eth device recvoery, while running ethtool multiple
times in parallel and using iperf to get load on the interface.
Upstream-ID: 7a07a29e4f6713b224f3bcde5f835e777301bdb8
https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f
applicable for most kernel > 3.14
== Comment: #3 - J?rn Siglen - 2022-08-09 07:54:41 ==
the inital update came in with kernel 5.1 upstream, but we found it
backported in many older kernel versions
== Comment: #4 - J?rn Siglen - 2022-08-09 08:03:09 ==
the acceptance info of the patch can be found here:
https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1984103/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988143] Re: 20.04.5 (20220829.1 build) has kernel 5.13 packages
...discussed this with the kernel team and it seems to be a bug in the 5.15 hwe lrm kernel packages. Apparently because of an error, the nvidia-390 packages have not been prepared for this kernel. And since we pull in 390 (and should), this causes the build infrastructure to pull in the old 5.13 kernels along with them. The kernel team is working on a lrm-only respin. ** Also affects: linux-restricted-modules-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-meta (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1988143 Title: 20.04.5 (20220829.1 build) has kernel 5.13 packages Status in linux-restricted-modules-hwe-5.15 package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Invalid Bug description: Examining the .list file for the amd64 image it contains various kernel 5.13 .deb packages. http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop- amd64.list e.g. /pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb /pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb This is a little unexpected given that 5.15 is the default kernel. Possibly nvidia-390 doesn't have 5.15 packages? This impacts all flavours as well that include nvidia stuff in their ISO - so if the solution is to change the meta file for a revised regexp for nvidia then all flavours that include nvidia will likewise need their meta packages updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.15/+bug/1988143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984103] Re: [UBUNTU 22.04] s390/qeth: cache link_info for ethtool
** Tags removed: rls-incoming-jj rls-incoming-kk
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1984103
Title:
[UBUNTU 22.04] s390/qeth: cache link_info for ethtool
Status in Ubuntu on IBM z Systems:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
Confirmed
Status in linux source package in Kinetic:
Confirmed
Bug description:
== Comment: #0 - J?rn Siglen - 2022-08-09 07:38:27 ==
+++ This bug was initially created as a clone of Bug #199319 +++
Description: s390/qeth: cache link_info for ethtool
Symptom: lost of IP connection and log entries in journalctl:
kernel: qeth 0.0.0365: The qeth device driver failed to
recover an error on the device
Problem: Since commit e6e771b3d897
("s390/qeth: detach netdevice while card is offline")
there was a timing window during recovery, that
qeth_query_card_info could be sent to the card, even before it
was ready for it, leading to a failing card recovery. There is
evidence that this window was hit, as not all callers of
get_link_ksettings() check for netif_device_present.
Solution: Use cached values in qeth_get_link_ksettings(), instead of
calling qeth_query_card_info() and falling back to default
values in case it fails. Link info is already updated when the
card goes online, e.g. after STARTLAN (physical link up). Set
the link info to default values, when the card goes offline or
at STOPLAN (physical link down). A follow-on patch will improve
values reported for link down.
Fixes: e6e771b3d897
("s390/qeth: detach netdevice while card is offline")
Reproduction: enforce a eth device recvoery, while running ethtool multiple
times in parallel and using iperf to get load on the interface.
Upstream-ID: 7a07a29e4f6713b224f3bcde5f835e777301bdb8
https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f
applicable for most kernel > 3.14
== Comment: #3 - J?rn Siglen - 2022-08-09 07:54:41 ==
the inital update came in with kernel 5.1 upstream, but we found it
backported in many older kernel versions
== Comment: #4 - J?rn Siglen - 2022-08-09 08:03:09 ==
the acceptance info of the patch can be found here:
https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1984103/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984103] Re: [UBUNTU 22.04] s390/qeth: cache link_info for ethtool
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ethtool (Ubuntu)
** Changed in: ethtool (Ubuntu Jammy)
Assignee: Ubuntu Server (ubuntu-server) => (unassigned)
** Changed in: ethtool (Ubuntu Kinetic)
Assignee: Ubuntu Server (ubuntu-server) => (unassigned)
** No longer affects: ethtool (Ubuntu Kinetic)
** No longer affects: ethtool (Ubuntu Jammy)
** Changed in: linux (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: linux (Ubuntu Kinetic)
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/1984103
Title:
[UBUNTU 22.04] s390/qeth: cache link_info for ethtool
Status in Ubuntu on IBM z Systems:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
Confirmed
Status in linux source package in Kinetic:
Confirmed
Bug description:
== Comment: #0 - J?rn Siglen - 2022-08-09 07:38:27 ==
+++ This bug was initially created as a clone of Bug #199319 +++
Description: s390/qeth: cache link_info for ethtool
Symptom: lost of IP connection and log entries in journalctl:
kernel: qeth 0.0.0365: The qeth device driver failed to
recover an error on the device
Problem: Since commit e6e771b3d897
("s390/qeth: detach netdevice while card is offline")
there was a timing window during recovery, that
qeth_query_card_info could be sent to the card, even before it
was ready for it, leading to a failing card recovery. There is
evidence that this window was hit, as not all callers of
get_link_ksettings() check for netif_device_present.
Solution: Use cached values in qeth_get_link_ksettings(), instead of
calling qeth_query_card_info() and falling back to default
values in case it fails. Link info is already updated when the
card goes online, e.g. after STARTLAN (physical link up). Set
the link info to default values, when the card goes offline or
at STOPLAN (physical link down). A follow-on patch will improve
values reported for link down.
Fixes: e6e771b3d897
("s390/qeth: detach netdevice while card is offline")
Reproduction: enforce a eth device recvoery, while running ethtool multiple
times in parallel and using iperf to get load on the interface.
Upstream-ID: 7a07a29e4f6713b224f3bcde5f835e777301bdb8
https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f
applicable for most kernel > 3.14
== Comment: #3 - J?rn Siglen - 2022-08-09 07:54:41 ==
the inital update came in with kernel 5.1 upstream, but we found it
backported in many older kernel versions
== Comment: #4 - J?rn Siglen - 2022-08-09 08:03:09 ==
the acceptance info of the patch can be found here:
https://lore.kernel.org/all/20220805184504.7f6f2...@kernel.org/T/#m2e3799a38d1d4630822db50f9a5d9b2ca018252f
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1984103/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987870] Re: Demote to proposed LRM portions of intel-iotg
Demoting packages to kinetic-proposed: linux-restricted-modules-oem-5.17 5.17.0-1003.3+1 in kinetic linux-restricted-signatures-oem-5.17 5.17.0-1003.3+1 in kinetic linux-restricted-modules-intel-iotg 5.15.0-1004.6 in kinetic linux-restricted-signatures-intel-iotg 5.15.0-1004.6 in kinetic Comment: v5.19 kernel migration LP:#1987870 and LP:#1987869 Demote [y|N]? y Remove linux-restricted-modules-oem-5.17 from release [y|N]? y Remove linux-restricted-signatures-oem-5.17 from release [y|N]? y Remove linux-restricted-modules-intel-iotg from release [y|N]? y Remove linux-restricted-signatures-intel-iotg from release [y|N]? y 4 packages successfully demoted. ** Changed in: linux-restricted-modules-intel-iotg (Ubuntu) Status: Triaged => Fix Released ** Changed in: linux-restricted-signatures-intel-iotg (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/1987870 Title: Demote to proposed LRM portions of intel-iotg Status in linux-restricted-modules-intel-iotg package in Ubuntu: Fix Released Status in linux-restricted-signatures-intel-iotg package in Ubuntu: Fix Released Bug description: v5.19 kernels are ready to migrate in kinetic. via new nvidia and LRM packages all kernels are entangled. intel-iotg kernel has not yet been upgraded to v5.19. to allow src:linux-meta migration, we need to demote to proposed LRM/LRS of intel-iotg kernel to unblock development. an updated version of intel-iotg kernel will happen a bit later. Please demote to proposed linux-restricted-modules-intel-iotg linux- restricted-signatures-intel-iotg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-intel-iotg/+bug/1987870/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987870] Re: RM: Remove linux-intel-iotg from kinetic
** Description changed: - Remove linux-intel-iotg from kinetic + v5.19 kernels are ready to migrate in kinetic. - This kernel should not exist in kinetic-release, as it is jammy-only - thing. + via new nvidia and LRM packages all kernels are entangled. - At least for the time being. + intel-iotg kernel has not yet been upgraded to v5.19. + + to allow src:linux-meta migration, we need to demote to proposed LRM/LRS + of intel-iotg kernel to unblock development. + + an updated version of intel-iotg kernel will happen a bit later. ** No longer affects: linux-intel-iotg (Ubuntu) ** No longer affects: linux-meta-intel-iotg (Ubuntu) ** No longer affects: linux-signed-intel-iotg (Ubuntu) ** Summary changed: - RM: Remove linux-intel-iotg from kinetic + Demote to proposed LRM portions of linux-restricted-modules-intel-iotg ** Summary changed: - Demote to proposed LRM portions of linux-restricted-modules-intel-iotg + Demote to proposed LRM portions of intel-iotg ** Description changed: v5.19 kernels are ready to migrate in kinetic. via new nvidia and LRM packages all kernels are entangled. intel-iotg kernel has not yet been upgraded to v5.19. to allow src:linux-meta migration, we need to demote to proposed LRM/LRS of intel-iotg kernel to unblock development. an updated version of intel-iotg kernel will happen a bit later. + + Please demote to proposed linux-restricted-modules-intel-iotg linux- + restricted-signatures-intel-iotg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/1987870 Title: Demote to proposed LRM portions of intel-iotg Status in linux-restricted-modules-intel-iotg package in Ubuntu: Triaged Status in linux-restricted-signatures-intel-iotg package in Ubuntu: Triaged Bug description: v5.19 kernels are ready to migrate in kinetic. via new nvidia and LRM packages all kernels are entangled. intel-iotg kernel has not yet been upgraded to v5.19. to allow src:linux-meta migration, we need to demote to proposed LRM/LRS of intel-iotg kernel to unblock development. an updated version of intel-iotg kernel will happen a bit later. Please demote to proposed linux-restricted-modules-intel-iotg linux- restricted-signatures-intel-iotg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-intel-iotg/+bug/1987870/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987869] Re: Demote to proposed LRM portions of linux-oem-5.17
** Summary changed: - Remove linux-oem-5.17 from kinetic + Demote to proposed LRM portions of linux-oem-5.17 ** No longer affects: linux-meta-oem-5.17 (Ubuntu) ** No longer affects: linux-oem-5.17 (Ubuntu) ** No longer affects: linux-signed-oem-5.17 (Ubuntu) ** Description changed: - Remove linux-oem-5.17 from kinetic + v5.19 kernels are ready to migrate in kinetic. - this kernel should not exist in kinetic-release, as it is jammy-only - thing + via new nvidia and LRM packages all kernels are entangled. + + oem-5.17 is an obsolete kernel, and its meta packages will be taken over + by src:linux-meta once it migrates + + to allow src:linux-meta migration, we need to demote to proposed LRM/LRS + of oem-5.17 kernel. Once src:linux-meta migrates all of the oem-5.17 + packages will be removed completely from the archive. + + Please demote to proposed linux-restricted-modules-oem-5.17 linux- + restricted-signatures-oem-5.17 -- 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/1987869 Title: Demote to proposed LRM portions of linux-oem-5.17 Status in linux-restricted-modules-oem-5.17 package in Ubuntu: Triaged Status in linux-restricted-signatures-oem-5.17 package in Ubuntu: Triaged Bug description: v5.19 kernels are ready to migrate in kinetic. via new nvidia and LRM packages all kernels are entangled. oem-5.17 is an obsolete kernel, and its meta packages will be taken over by src:linux-meta once it migrates to allow src:linux-meta migration, we need to demote to proposed LRM/LRS of oem-5.17 kernel. Once src:linux-meta migrates all of the oem-5.17 packages will be removed completely from the archive. Please demote to proposed linux-restricted-modules-oem-5.17 linux- restricted-signatures-oem-5.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-oem-5.17/+bug/1987869/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987869] Re: Remove linux-oem-5.17 from kinetic
@vorlon @apw Then we must either respin or remove linux-restricted-modules-oem-5.17 linux-restricted-signatures-oem-5.17 then linux-meta can migrate (with the oem packages transitionals) and then we can remove the rest of the oem-5.17 packages. ** Changed in: linux-oem-5.17 (Ubuntu) Status: Triaged => Incomplete ** Changed in: linux-signed-oem-5.17 (Ubuntu) Status: Triaged => Incomplete ** Tags added: block-proposed-kinetic -- 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/1987869 Title: Remove linux-oem-5.17 from kinetic Status in linux-meta-oem-5.17 package in Ubuntu: Incomplete Status in linux-oem-5.17 package in Ubuntu: Incomplete Status in linux-restricted-modules-oem-5.17 package in Ubuntu: Triaged Status in linux-restricted-signatures-oem-5.17 package in Ubuntu: Triaged Status in linux-signed-oem-5.17 package in Ubuntu: Incomplete Bug description: Remove linux-oem-5.17 from kinetic this kernel should not exist in kinetic-release, as it is jammy-only thing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-5.17/+bug/1987869/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987870] Re: RM: Remove linux-intel-iotg from kinetic
** Changed in: linux-restricted-modules-intel-iotg (Ubuntu) Status: Incomplete => Triaged ** Changed in: linux-restricted-signatures-intel-iotg (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/1987870 Title: RM: Remove linux-intel-iotg from kinetic Status in linux-intel-iotg package in Ubuntu: Incomplete Status in linux-meta-intel-iotg package in Ubuntu: Incomplete Status in linux-restricted-modules-intel-iotg package in Ubuntu: Triaged Status in linux-restricted-signatures-intel-iotg package in Ubuntu: Triaged Status in linux-signed-intel-iotg package in Ubuntu: Incomplete Bug description: Remove linux-intel-iotg from kinetic This kernel should not exist in kinetic-release, as it is jammy-only thing. At least for the time being. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/1987870/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922910] Re: Unable to deploy HWE kernel with sub-arch set to xgene-uboot
** Tags added: bug-council -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922910 Title: Unable to deploy HWE kernel with sub-arch set to xgene-uboot Status in MAAS: New Status in linux package in Ubuntu: Expired Bug description: When trying to deploy Moonshot nodes, the sub-arch must be set to xgene-uboot for it to be deployed with GA kernel. However, when trying to deploy it with the HWE kernel it will complain that: Subarchitecture(xgene-uboot) must be generic when setting hwe_kernel. [ deleted the bit about how generic/hwe fails, because that is expected. this machine requires xgene-uboot/hwe ] To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1922910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978986] Re: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average luminance
** Changed in: linux (Ubuntu Jammy) Status: Confirmed => Fix Committed ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: Fix Committed => Invalid ** Changed in: hwe-next Status: Confirmed => In Progress ** Changed in: hwe-next 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/1978986 Title: [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame- average luminance Status in HWE Next: Fix Committed Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] The brightness is not changed obviously during 200 to 255 on AMD or 400 to 512 on Intel.. [Fix] Read HDR meta to detect the max and min luminance. max_cll defines the content light luminance for individual pixel. max_fall defines frame-average level luminance. Use max_fall value instead of max_cll as a limit for brightness control. [Test] Verified on AMD Cezanne, Barcelo, Rembrandt and Intel ADL, also on LCD panel and OLED panel. The brightness is changed more obivously on OLED panel, and no affect on LCD panel. [Where problems could occur] Low risk, It may cause the max brightness can't be set. All 3 patches are in drm-misc tree. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1978986/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980829] Re: System freeze after resuming from suspend due to PCI ASPM settings
** Changed in: hwe-next 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/1980829 Title: System freeze after resuming from suspend due to PCI ASPM settings Status in HWE Next: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 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-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: In Progress Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: For Jammy/Kinetic SRU [Impact] While doing some tests such as suspend/resume or CPU stress tests the system would hang. [Fix] The 2 commits fix the issue, but still not get accepted yet. https://patchwork.ozlabs.org/project/linux-pci/patch/20220705060014.10050-1-vid...@nvidia.com/ https://patchwork.ozlabs.org/project/linux-pci/patch/20220509073639.2048236-1-kai.heng.f...@canonical.com/ So, I created a DMI quirk to make the patches only affects on listed platforms. [Test] Verified on the failed machines and ODM also verified on their side. [Where problems could occur] The patches only affects on the listed platforms, and won't affect other platforms. == [Impact] While doing some tests such as suspend/resume or CPU stress tests the system would hang. [Fix] The 2 commits fix the issue, but still not get accepted yet. https://patchwork.ozlabs.org/project/linux-pci/patch/20220705060014.10050-1-vid...@nvidia.com/ https://patchwork.ozlabs.org/project/linux-pci/patch/20220509073639.2048236-1-kai.heng.f...@canonical.com/ [Test] Verified on the failed machines and ODM also verified on their side. [Where problems could occur] The 2 patches look pretty safe to me, they try to preserve the ASPM state of devices. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1980829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988120] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1988120 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1988120 Title: Support Intel TDX guest attestation driver Status in linux package in Ubuntu: Incomplete Status in linux source package in Kinetic: Incomplete Bug description: [Impact] Intel has requested to support the TDX (trust domain extension) guest attestation driver interface. In a TDX guest "attestation" is used to verify the trustworthiness of a TD (trusted domain) before provisioning secrets to the TD (i.e, encrypted keys to mount an encrypted rootfs, etc.). During the TD boot the initial contents and configurations are recorded by the Intel TDX module in the build time measurement register (MRTD). At TD runtime, the Intel TDX module reuses the Intel SGX attestation infrastructure to provide support for attesting to these information. This driver is targeting 6.x upstream, so we need to backport the upstream patches as SAUCE patches to properly support this feature in 5.19. [Fix] Backport upstream TDX attestation driver. [Test case] Tests have been performed by IBM, a test-case is included in the patch set as a kernel selftest (called 'tdx'). TODO: consider to integrate this test in our testing infrastructure once this feature has been merged. [Regression potential] This feature is self-contained, it's only available on amd64 and it doesn't affect any other amd64 code. So we could only experience regressions on amd64 systems that are using the TDX feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988120/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988120] [NEW] Support Intel TDX guest attestation driver
Public bug reported: [Impact] Intel has requested to support the TDX (trust domain extension) guest attestation driver interface. In a TDX guest "attestation" is used to verify the trustworthiness of a TD (trusted domain) before provisioning secrets to the TD (i.e, encrypted keys to mount an encrypted rootfs, etc.). During the TD boot the initial contents and configurations are recorded by the Intel TDX module in the build time measurement register (MRTD). At TD runtime, the Intel TDX module reuses the Intel SGX attestation infrastructure to provide support for attesting to these information. This driver is targeting 6.x upstream, so we need to backport the upstream patches as SAUCE patches to properly support this feature in 5.19. [Fix] Backport upstream TDX attestation driver. [Test case] Tests have been performed by IBM, a test-case is included in the patch set as a kernel selftest (called 'tdx'). TODO: consider to integrate this test in our testing infrastructure once this feature has been merged. [Regression potential] This feature is self-contained, it's only available on amd64 and it doesn't affect any other amd64 code. So we could only experience regressions on amd64 systems that are using the TDX feature. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1988120 Title: Support Intel TDX guest attestation driver Status in linux package in Ubuntu: New Status in linux source package in Kinetic: New Bug description: [Impact] Intel has requested to support the TDX (trust domain extension) guest attestation driver interface. In a TDX guest "attestation" is used to verify the trustworthiness of a TD (trusted domain) before provisioning secrets to the TD (i.e, encrypted keys to mount an encrypted rootfs, etc.). During the TD boot the initial contents and configurations are recorded by the Intel TDX module in the build time measurement register (MRTD). At TD runtime, the Intel TDX module reuses the Intel SGX attestation infrastructure to provide support for attesting to these information. This driver is targeting 6.x upstream, so we need to backport the upstream patches as SAUCE patches to properly support this feature in 5.19. [Fix] Backport upstream TDX attestation driver. [Test case] Tests have been performed by IBM, a test-case is included in the patch set as a kernel selftest (called 'tdx'). TODO: consider to integrate this test in our testing infrastructure once this feature has been merged. [Regression potential] This feature is self-contained, it's only available on amd64 and it doesn't affect any other amd64 code. So we could only experience regressions on amd64 systems that are using the TDX feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988120/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988073] Re: package linux-firmware 20220329.git681281e4-0ubuntu1 failed to install/upgrade: no se pudieron copiar los datos extraídos de './lib/firmware/ath10k/WCN3990/hw1.0/wl
Is this reproducible? Can you rerun 'apt upgrade'? ** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete -- 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/1988073 Title: package linux-firmware 20220329.git681281e4-0ubuntu1 failed to install/upgrade: no se pudieron copiar los datos extraídos de './lib/firmware/ath10k/WCN3990/hw1.0/wlanmdsp.mbn' a '/lib/firmware/ath10k/WCN3990/hw1.0/wlanmdsp.mbn.dpkg-new': fin de fichero o de flujo inesperado Status in linux-firmware package in Ubuntu: Incomplete Bug description: no idea ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: braisoncrece 1211 F pulseaudio /dev/snd/controlC1: braisoncrece 1211 F pulseaudio /dev/snd/controlC2: braisoncrece 1211 F pulseaudio /dev/snd/controlC0: braisoncrece 1211 F pulseaudio CRDA: N/A CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: fail Date: Mon Aug 29 19:18:48 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu3 ErrorMessage: no se pudieron copiar los datos extraídos de './lib/firmware/ath10k/WCN3990/hw1.0/wlanmdsp.mbn' a '/lib/firmware/ath10k/WCN3990/hw1.0/wlanmdsp.mbn.dpkg-new': fin de fichero o de flujo inesperado InstallationDate: Installed on 2022-08-29 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO PackageArchitecture: all ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=82c4ebe7-2e57-4b67-a5f5-e1b1c5a31b63 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.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7 SourcePackage: linux-firmware Title: package linux-firmware 20220329.git681281e4-0ubuntu1 failed to install/upgrade: no se pudieron copiar los datos extraídos de './lib/firmware/ath10k/WCN3990/hw1.0/wlanmdsp.mbn' a '/lib/firmware/ath10k/WCN3990/hw1.0/wlanmdsp.mbn.dpkg-new': fin de fichero o de flujo inesperado UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F30 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS PRO dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF30:bd09/15/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPRO:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPRO:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS PRO dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1988073/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988073] Re: package linux-firmware 20220329.git681281e4-0ubuntu1 failed to install/upgrade: no se pudieron copiar los datos extraídos de './lib/firmware/ath10k/WCN3990/hw1.0/wl
Desempaquetando linux-firmware (20220329.git681281e4-0ubuntu3.4) sobre (20220329.git681281e4-0ubuntu1) ... dpkg-deb (subproceso): ZSTD_decompressStream error : Corrupted block detected -- 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/1988073 Title: package linux-firmware 20220329.git681281e4-0ubuntu1 failed to install/upgrade: no se pudieron copiar los datos extraídos de './lib/firmware/ath10k/WCN3990/hw1.0/wlanmdsp.mbn' a '/lib/firmware/ath10k/WCN3990/hw1.0/wlanmdsp.mbn.dpkg-new': fin de fichero o de flujo inesperado Status in linux-firmware package in Ubuntu: Incomplete Bug description: no idea ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: braisoncrece 1211 F pulseaudio /dev/snd/controlC1: braisoncrece 1211 F pulseaudio /dev/snd/controlC2: braisoncrece 1211 F pulseaudio /dev/snd/controlC0: braisoncrece 1211 F pulseaudio CRDA: N/A CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: fail Date: Mon Aug 29 19:18:48 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu3 ErrorMessage: no se pudieron copiar los datos extraídos de './lib/firmware/ath10k/WCN3990/hw1.0/wlanmdsp.mbn' a '/lib/firmware/ath10k/WCN3990/hw1.0/wlanmdsp.mbn.dpkg-new': fin de fichero o de flujo inesperado InstallationDate: Installed on 2022-08-29 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO PackageArchitecture: all ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=82c4ebe7-2e57-4b67-a5f5-e1b1c5a31b63 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.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu7 SourcePackage: linux-firmware Title: package linux-firmware 20220329.git681281e4-0ubuntu1 failed to install/upgrade: no se pudieron copiar los datos extraídos de './lib/firmware/ath10k/WCN3990/hw1.0/wlanmdsp.mbn' a '/lib/firmware/ath10k/WCN3990/hw1.0/wlanmdsp.mbn.dpkg-new': fin de fichero o de flujo inesperado UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F30 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS PRO dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF30:bd09/15/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPRO:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPRO:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS PRO dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1988073/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
