[Kernel-packages] [Bug 1979899] Re: Dell Inspiron 17 7000 series 32-512 doesn't start after standby
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1979899 Title: Dell Inspiron 17 7000 series 32-512 doesn't start after standby Status in linux package in Ubuntu: Expired Bug description: Hi, seems there is a bug for dell devices, My laptop doesn't resume after a standby, even short. My trick is to shut it off and then restart. It seems to be a nvidia driver problem I tried things but it doesn't work and also, it seems to be diffrent for each device, even for the same brand like dell. So I post one report for this laptop. I run ubuntu 20.04, this problem occured after 3 updates. My laptop is a dell inspiron 17 7000 series intel I7. I tried updates, upgrades, and it's worth, my laptop doesn't start, so I start using esc, and reboot it. Now I don't want to do any updates until this problem will be solve. If you guys have an idea? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1979899/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981589] Re: dell latitude 3400 touchpad not detected
[Expired for linux-signed-hwe-5.4 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-signed-hwe-5.4 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1981589 Title: dell latitude 3400 touchpad not detected Status in linux-signed-hwe-5.4 package in Ubuntu: Expired Bug description: touchpad not detected and work only after connecting usb mouse, touchpad features don't work at all. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-121-generic 5.4.0-121.137~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-121.137~18.04.1-generic 5.4.189 Uname: Linux 5.4.0-121-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 13 19:13:11 2022 InstallationDate: Installed on 2020-12-06 (584 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1981589/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982008] Re: Brightness Bar Not Working
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982008 Title: Brightness Bar Not Working Status in linux package in Ubuntu: Expired Bug description: The Brightness Bar broke after an update from kernel 5.13 to 5.15. The issue couldn't be located. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884232] Re: touchpad and touchscreen doesn't work at all on ACER Spin 5 (SP513-54N)
This bug is awaiting verification that the linux-nvidia/5.15.0-1006.6
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1884232
Title:
touchpad and touchscreen doesn't work at all on ACER Spin 5
(SP513-54N)
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Focal:
Won't Fix
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
E820 reserved retire memory window, and make other hot-added devices unable
to get the required memory window.
[Fix]
It only can be fixed by a list of quirk to mark those machines out, and
requires below commits from v5.19-rc1 and v5.19-rc3
a2b36ffbf5b6 x86/PCI: Revert "x86/PCI: Clip only host bridge windows for E820
regions"
d341838d776a x86/PCI: Disable E820 reserved region clipping via quirks
fa6dae5d8208 x86/PCI: Add kernel cmdline options to use/ignore E820 reserved
regions
4c5e242d3e93 x86/PCI: Clip only host bridge windows for E820 regions
31bf0f433325 x86: Log resource clipping for E820 regions
93d256cd3c1e x86/PCI: Eliminate remove_e820_regions() common subexpressions
[Test]
Verified by the bug reporter.
[Where problems could occur]
The 6 commits are all clean cherry-picked, and the sixth commit reverts the
third commit which are the 2 commits that do real functional changes.
a2b36ffbf5b6 ("x86/PCI: Revert \"x86/PCI: Clip only host bridge windows for
E820 regions\"")
4c5e242d3e93 ("x86/PCI: Clip only host bridge windows for E820 regions")
The fourth and and fifth commits introduce a new quirk to ignore E820
reserved regions and the quirk only affects the listed machines.
Drivers that operates E820 table may fail if we ignore the E820 regions, but
it should have no impact on the listed consumer PCs.
===
Touchpad is not working at all on ACER Spin 5 SP513-54N.
According to
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29
I am creating this kernel bug issue.
There are more issues, too, like touchscreen not working and Ubuntu
not installable - see here if interrested
https://askubuntu.com/questions/1251719/
I would like to run Ubuntu on this machine and I am willing to help
with any debug or kernel tweaking... Please let me know.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-26-generic 5.4.0-26.30
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 4195 F pulseaudio
CasperMD5CheckResult: skip
CasperVersion: 1.445
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 19 10:44:58 2020
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Acer Spin SP513-54N
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
RelatedPackageVersions:
linux-restricted-modules-5.4.0-26-generic N/A
linux-backports-modules-5.4.0-26-generic N/A
linux-firmware1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/21/2020
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.00
dmi.board.name: Caboom_IL
dmi.board.vendor: IL
dmi.board.version: V1.00
dmi.chassis.type: 31
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.00
dmi.modalias:
dmi:bvnInsydeCorp.:bvrV1.00:bd02/21/2020:svnAcer:pnSpinSP513-54N:pvrV1.00:rvnIL:rnCaboom_IL:rvrV1.00:cvnAcer:ct31:cvrV1.00:
dmi.product.family: Spin 5
dmi.product.name: Spin SP513-54N
dmi.product.sku:
dmi.product.version: V1.00
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe :
[Kernel-packages] [Bug 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes
This bug is awaiting verification that the linux-nvidia/5.15.0-1006.6 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1957026 Title: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On AMD Yellow Carp B0 platforms, S0i3 is still not working. [Fix] This denpends on a few fixes for kernel driver that are all either in v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed dmcub firmware. [Test Case] On AMD RMT CRB board, 1. apply both kernel and firmware fixes 2. module blacklist amd_sfh as it's still under development, 3. trigger system suspend. Use power button to wake up the device. 4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero On without any of above, the board may not cut device power during suspend, and/or fail to resume and leaving a blank screen, and/or s0ix stats remain all zeros. [Where problems could occur] On AMD RMT CRB board, Sensor Fusion Hub (amd_sfh) still doesn't support S0ix and has to be disabled. For the kernel side, the driver fixes addressed a few procedure errors that should be unlikely to introduce regressions; for the firmware side, also tested loading new firmware on unpatched kernels and there is no difference found yet. [Other Info] For kernel driver fixes, patches for both oem-5.14 and jammy are necessary; for firmware, that has been available in jammy branch but not yet released, so only Focal will be nominated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1957026/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1966680] Re: Fix drm/amd/pm: enable ASPM by default
This bug is awaiting verification that the linux-nvidia/5.15.0-1006.6
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1966680
Title:
Fix drm/amd/pm: enable ASPM by default
Status in HWE Next:
Fix Released
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 Released
Status in linux-oem-5.14 source package in Jammy:
Invalid
Status in linux-oem-5.17 source package in Jammy:
Fix Released
Bug description:
[Impact]
With WX3200 and 20.04d kernel the unit freezes on resume
[Fix]
commit 0064b0ce85bb ("drm/amd/pm: enable ASPM by default") enabled ASPM
by default but a variety of hardware configurations it turns out that this
caused a regression.
Multiple SKUs with wx3200 gpus encounter the resume issue.
Before the real fix is landed, revert commit 0064b0ce85bb first.
[Test Case]
1. plug wx3200 on the adl machine and make it as a output.
2. suspend machine
3. check if machine could resume successfully
[Where problems could occur]
Low, don't make AMDGPU ASPM by default.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1966680/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1966010] Re: Fix audio on Zbook Studio G9
This bug is awaiting verification that the linux-nvidia/5.15.0-1006.6 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1966010 Title: Fix audio on Zbook Studio G9 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Cirrus Logic AMP still doesn't work on Zbook Studio G9. Moreoever, The audio mute LEDs stop working after the said SRU. [Fix] Correcly interpret the debounce time from ACPI to gpiolib, and apply the correct quirk for the audio mute LEDs. [Where problems could occur] It's possible that some hardwares rely on the "wrong" debounce time to work, however the fix is to increase the debounce time, so it's more forgiving than decreasing. The LED fix is only applied to one system, so it's specifi and won't cause too much trouble. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1966010/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980087] Re: Fix PSR flickers on Intel TGL laptops + AUO panel
This bug is awaiting verification that the linux-nvidia/5.15.0-1006.6 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1980087 Title: Fix PSR flickers on Intel TGL laptops + AUO panel Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Screen flickers on certain Intel TGL laptops + AUO panel. [Fix] Enable PSR2 selective fetch only for the specific case to minimize the regression risk. [Test] Screen flickers can no longer be observed on affected laptops. [Where problems could occur] The fix becomes very specific, so any other combination won't be affected at all. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1980087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978915] Re: alsa/hda: mute led can't work on the lenovo machine with cs35l41 s-codec
This bug is awaiting verification that the linux-nvidia/5.15.0-1006.6 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1978915 Title: alsa/hda: mute led can't work on the lenovo machine with cs35l41 s-codec Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: The fix is already in the upstream kernel stable-v5.17, no need to send this patch to oem-5.17 and unstable kernels. [Impact] After we apply the cs35l41 s-codec patchset to the oem-5.14 and jammy kernels, the mute led can't work anymore. [Fix] Backport a patch from mainline kernel to fix this regression [Test] boot the patched kernel, press mute hotkey, the speaker is muted and the mute led is on, press the mute hotkey again, the speaker is unmuted and the mute led is off. [Where problems could occur] After merging this patch, it is possible to affect the machines which apply the ALC287_FIXUP_CS35L41_I2C_2, but the regression possibility is very low since hda_fixup_thinkpad_acpi() could check if the quirk is suitable for the running machine. And we did test, all machines could work well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1978915/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980060] Re: Fix AMDGPU blank screen when Type-C DP alt is in use
This bug is awaiting verification that the linux-nvidia/5.15.0-1006.6 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1980060 Title: Fix AMDGPU blank screen when Type-C DP alt is in use Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] When Type-C DP/HDMI is in use, s0ix resume renders both eDP and DP outputs blank. [Fix] Query the firmware to ensure the DP alt status. [Test] Suspend and resume the system, both eDP and Type-C DP/HDMI are working. [Where problems could occur] This fix only applies to certain AMD GFX with certain firmware version, so the scope is very limited. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1980060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942999] Re: Fix invalid MAC address after hotplug tbt dock
This bug is awaiting verification that the linux-nvidia/5.15.0-1006.6 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1942999 Title: Fix invalid MAC address after hotplug tbt dock Status in HWE Next: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid 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.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Won't Fix Status in linux source package in Impish: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: SRU justification: [Impact] igc driver can not connect to network after re-plugin thunderbolt dock when MAC passthrough enabled in BIOS. [Fix] Wait for the MAC copy of BIOS when enabled MAC passthrough. Intel engineer wants a different solution and promise to discuss with firmware engineer. Due to the schedule, made this as a short term solution to fix the issue, and wait for the other fix from Intel. [Test] Verified on hardware, after hotplug the thunderbolt cable, Ethernet works fine. [Where problems could occur] It may break the igc driver. Intel still doesn't provide any solution about their approach. In the meantime, this patch is still the only fix. Re-submit it to Jammy, oem-5.17 and Unstable kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953613] Re: GPIO character device v1 API not enabled in kernel
This bug is awaiting verification that the linux-nvidia/5.15.0-1006.6 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-allwinner-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1953613 Title: GPIO character device v1 API not enabled in kernel Status in linux package in Ubuntu: Fix Released Status in linux-allwinner-5.17 package in Ubuntu: Invalid Status in linux-hwe-5.17 package in Ubuntu: Invalid Status in linux-starfive-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-allwinner-5.17 source package in Jammy: Fix Released Status in linux-hwe-5.17 source package in Jammy: Fix Committed Status in linux-starfive-5.17 source package in Jammy: Fix Released Bug description: [Impact] * The libgpiod2 library and gpiod tools shipped in Jammy don't work. * These tools are meant to replace the old sysfs interface and be a better and more efficient way to manipulate GPIOs from userspace. Unfortunately the latest release is still using v1 of the character device kernel API which is not enabled in Ubuntu kernels. * This is Kent Gibsons reply on the linux-gpio mailing list: On Tue, Jul 12, 2022 at 09:48:45AM +0200, Alexandre Ghiti wrote: > Hi, > > Ubuntu kernels do not enable GPIO_CDEV_V1 as it is deprecated, but the > libgpiod package that we ship is still based on the latest version > 1.6.3 which does not implement the API v2. So I'd like to update > libgpiod, do you have any recommendations about what branch/sha1 I > should use? Do you plan to make a release that implements the API v2? > Firstly, libgpiod is Bart's library so he is the authority, but this is my understanding... TLDR: You should keep GPIO_CDEV_V1 enabled. v1 is deprecated from a development perspective, so all new feature development will occur on v2, and new applications should target v2. Existing apps targetting v1, be that directly or via libgpiod v1.6.3, will require GPIO_CDEV_V1 until they migrate to v2. The mainline kernel will continue to support v1 while userspace transitions. libgpiod v2 is in active development, and should reach its first release shortly. Note that it is NOT a plugin replacement for v1. It has a different API, for similar reasons to why we had to switch in the kernel, so apps will need to be actively migrated. I wouldn't suggest making any effort to package libgpiod v2 until Bart makes an official release. Cheers, Kent. [Test Plan] * Run gpioinfo on a machine with exposed GPIOs and check that it lists the GPIOs and doesn't error with gpioinfo: error creating line iterator: Invalid argument [Where problems could occur] * There may be code and scripts that hasn't been tested with a working libgpiod2/gpiod tools and uncover latent bugs. [Other Info] Original bug text: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. Thanks to Marek Szuba, who reported the same bug for Gentoo (https://bugs.gentoo.org/807334), pointing me in the right direction. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1
[Kernel-packages] [Bug 1980925] Re: [SRU] bcache deadlock during read IO in writeback mode
This bug is awaiting verification that the linux-nvidia/5.15.0-1006.6 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1980925 Title: [SRU] bcache deadlock during read IO in writeback mode Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: [Impact] When Random Read I/O is started with a test like - fio --name=read_iops --directory=/home/ubuntu/bcache_mount/ --size=16G --ioengine=libaio --direct=1 --verify=0 --bs=4K --iodepth=128 --rw=randread --randrepeat=0 or random read-writes with a test like, fio --filename=/home/ubuntu/bcache_mount/cachedfile --size=15GB --direct=1 --rw=randrw --bs=4k --ioengine=libaio --iodepth=128 --name=iops-test-job --randrepeat=0 traces are seen in the kernel log, [ 4473.699902] INFO: task bcache_writebac:1835 blocked for more than 120 seconds. [ 4474.050921] Not tainted 5.15.50-051550-generic #202206251445 [ 4474.350883] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 4474.731391] task:bcache_writebac state:D stack:0 pid: 1835 ppid: 2 flags:0x4000 [ 4474.731408] Call Trace: [ 4474.731411] [ 4474.731413] __schedule+0x23d/0x5a0 [ 4474.731433] schedule+0x4e/0xb0 [ 4474.731436] rwsem_down_write_slowpath+0x220/0x3d0 [ 4474.731441] down_write+0x43/0x50 [ 4474.731446] bch_writeback_thread+0x78/0x320 [bcache] [ 4474.731471] ? read_dirty_submit+0x70/0x70 [bcache] [ 4474.731487] kthread+0x12a/0x150 [ 4474.731491] ? set_kthread_struct+0x50/0x50 [ 4474.731494] ret_from_fork+0x22/0x30 [ 4474.731499] The bug exists till kernel 5.15.50-051550-generic The reproducer is pasted below: # uname -a Linux bronzor 5.15.50-051550-generic #202206251445 SMP Sat Jun 25 14:51:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sdd 8:48 0 279.4G 0 disk └─sdd18:49 060G 0 part └─bcache0 252:0060G 0 disk /home/ubuntu/bcache_mount nvme0n1 259:00 372.6G 0 disk └─nvme0n1p1 259:2015G 0 part └─bcache0 252:0060G 0 disk /home/ubuntu/bcache_mount fio --name=read_iops --directory=/home/ubuntu/bcache_mount --size=12G --ioengine=libaio --direct=1 --verify=0 --bs=4K --iodepth=128 --rw=randread --group_reporting=1 read_iops: (g=0): rw=randread, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=128 fio-3.28 Starting 1 process read_iops: Laying out IO file (1 file / 12288MiB) The test does not progress beyond a few minutes, and this trace is then seen in the kernel log, [ 4473.699902] INFO: task bcache_writebac:1835 blocked for more than 120 seconds. [ 4474.050921] Not tainted 5.15.50-051550-generic #202206251445 [ 4474.350883] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 4474.731391] task:bcache_writebac state:D stack:0 pid: 1835 ppid: 2 flags:0x4000 [ 4474.731408] Call Trace: [ 4474.731411] [ 4474.731413] __schedule+0x23d/0x5a0 [ 4474.731433] schedule+0x4e/0xb0 [ 4474.731436] rwsem_down_write_slowpath+0x220/0x3d0 [ 4474.731441] down_write+0x43/0x50 [ 4474.731446] bch_writeback_thread+0x78/0x320 [bcache] [ 4474.731471] ? read_dirty_submit+0x70/0x70 [bcache] [ 4474.731487] kthread+0x12a/0x150 [ 4474.731491] ? set_kthread_struct+0x50/0x50 [ 4474.731494] ret_from_fork+0x22/0x30 [ 4474.731499] [Fix] These 3 fixes are needed for the SRU. dea3560e5f31965165bcf34ecf0b47af28bfd155, 6445ec3df23f24677064a327dce437ef3e02dc6, dc60301fb408e06e0b718c0980cdd31d2b238bee I have built these fixes into kernel 5.15.0-39-generic (jammy) and tested to verify the problem is fixed. [Regression Potential] Regression potential should be minimal. I have not seen any potential drawbacks or harmful effects of this fix in my testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1981390] Re: Mass Storage Gadget driver truncates device >2TB
This bug is awaiting verification that the linux-nvidia/5.15.0-1006.6
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1981390
Title:
Mass Storage Gadget driver truncates device >2TB
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
I tried to use f_mass_storage to expose a 16TB hard drive attached to
Raspberry Pi to another computer.
On the remote computer the recognised drive has incorrect capacity and the
data is truncated.
After some debugging I noted the problem is caused by a bug in the
read capacity function of f_mass_storage in kernel version prior to
5.15, which had already been fixed upstream in mainline kernel since
v5.16
https://lore.kernel.org/all/20210914052728.23369-1-nikita.yo...@cogentembedded.com/
I tried the kernel from https://github.com/raspberrypi/linux version
rpi-5.16.y and confirmed that the problem is fixed at v5.16.
I wonder if the fix can be backported to the Ubuntu kernel.
Thank you very much!
Current kernel package version: linux-raspi (5.15.0-1011.13) jammy
Hardware: Raspberry Pi 4B
[Fix]
Backport commit bedbac5f66bf ("usb: gadget: storage: add support for
media larger than 2T")
[Test case]
See above.
[Where problems could occur]
Modifications are limited to the USB gadget mass storage driver, so
problems should only be seen on a client that uses this driver to
expose a USB drive to an attached USB host.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981390/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982930] Re: ioam6.sh in net from ubuntu_kernel_selftests fails with 5.15 kernels in Focal
This bug is awaiting verification that the linux-nvidia/5.15.0-1006.6 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982930 Title: ioam6.sh in net from ubuntu_kernel_selftests fails with 5.15 kernels in Focal Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Released Bug description: [Impact] Testcase ubuntu_kernel_selftests.net:ioam6.sh fails in Focal with the 5.15 kernels with the following errors: 17:19:35 DEBUG| [stdout] make: Entering directory '/tmp/autopkgtest.WSxPqj/build.GQs/src/autotest/cl ient/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' 17:19:35 DEBUG| [stdout] make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install 17:19:35 DEBUG| [stdout] make[1]: Entering directory '/tmp/autopkgtest.WSxPqj/build.GQs/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' 17:19:35 DEBUG| [stdout] INSTALL ./usr/include 17:19:35 DEBUG| [stdout] make[1]: Leaving directory '/tmp/autopkgtest.WSxPqj/build.GQs/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' 17:19:35 DEBUG| [stdout] TAP version 13 17:19:35 DEBUG| [stdout] 1..1 17:19:35 DEBUG| [stdout] # selftests: net: ioam6.sh 17:19:35 DEBUG| [stdout] # SKIP: iproute2 too old, missing ioam command 17:19:35 DEBUG| [stdout] not ok 1 selftests: net: ioam6.sh # exit=1 This is caused by an older version of iproute2 in Focal. The package has been updated in Jammy via bug 1951390 and the bug report says it should be updated in Focal as well. Even if the package is eventually updated, the testcase shouldn't throw a fatal error in this case and really return "SKIP" as the log message says. [Fix] The proper fix would be to make tools/testing/selftests/net/ioam6.sh return the Kselftest framework proper skip code instead of failing. [Testcase] Run the selftest script in Focal with a 5.15 kernel. [Where problems could occur] If the skip code is added to places where it shouldn't be added it could introduce false positives and not fail where it should. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1982930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982716] Re: Audio mute key (f5) LED and Mic mute key (f8) LED are no function on HP 440/450/640/650 G9
This bug is awaiting verification that the linux-nvidia/5.15.0-1006.6 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1982716 Title: Audio mute key (f5) LED and Mic mute key (f8) LED are no function on HP 440/450/640/650 G9 Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.17 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-hwe-5.17 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 Bug description: [Impact] The audio mute key (F5) and mic-mute LED (F8) don't work on some HP 440/450/640/650 G9 laptops. [Fix] The HP ProBook 440/450 G9 and EliteBook 640/650 G9 have multiple motherboard design and they are using different subsystem ID of audio codec. Add the same quirk for other MBs. [Test] After applying the fix, the mute LEDs are working. [Where problems could occur] It's low risk as it's specific ID for HP new machines. If the HP ships other machines using same SSID, then the LED may not work on those machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1982716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983143] Re: AMD Rembrandt: DP tunneling fails with Thunderbolt monitors
This bug is awaiting verification that the linux-nvidia/5.15.0-1006.6 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1983143 Title: AMD Rembrandt: DP tunneling fails with Thunderbolt monitors Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released 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 Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Summary] No video output on Thunderbolt monitor. 1. Connect monitor to DUT directly 2. Connect monitor to DUT via Docking System can detect the monitor and able to change display mode but no output on the monitor [Steps to reproduce] 1. Boot to OS 2. Plug an external monitor via thunderbolt port [Expected result] Display on external monitor normally [Actual result] No vidoe ouput on external monitor [Failure rate] 3/3 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1983143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983297] Re: Additional fix for TGL + AUO panel flickering
This bug is awaiting verification that the linux-nvidia/5.15.0-1006.6 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1983297 Title: Additional fix for TGL + AUO panel flickering Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] "UBUNTU: SAUCE: drm/i915/display/psr: Fix flicker on TGL + AUO panel" alone used to fix the issue on the AUO panel. But the panel starts to flicker like crazy on top of the new stable commits. [Fix] Backport full fix for PSR2 selective fetch, but only enable it on TGL + specific AUO panel. The last three patches which enable PSR2 on ADL-P are dropped. [Test] Originally the backport regressed ADL + BOE panel, so this time we put extra effort to ensure those system are unaffected, while TGL + AUO panel is still fixed. [Where problems could occur] Most code changes only have functional impact when PSR2 selective fetch is enabled. Some of changes are under more general call path for hardware cursor rendering. Notes are added to describe the functional impact for each patch, so if regression really occurrs it's easier to spot the offending commit. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1983297/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983640] Re: refactoring of overlayfs fix to properly support shiftfs
This bug is awaiting verification that the linux-nvidia/5.15.0-1006.6
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1983640
Title:
refactoring of overlayfs fix to properly support shiftfs
Status in linux package in Ubuntu:
Fix Committed
Status in linux-hwe-5.17 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux-hwe-5.17 source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Committed
Status in linux-hwe-5.17 source package in Kinetic:
Invalid
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
However, we made this patch dependent on AUFS, starting with Jammy
we're not enabling AUFS anymore, so this fix becomes a no-op.
So we need to re-introduce this fix with a bit of refactoring to not
depend on AUFS.
[Test case]
The following script can be used to trigger the issue:
#!/bin/bash
cat > test.py << EOF
import sys
f = open("/proc/self/maps")
for l in f.readlines():
if "python" not in l:
continue
print(l)
s = l.split()
start, end = s[0].split("-")
fname = s[-1]
print(start, end, fname)
break
else:
sys.exit(1)
test_file1 = open(fname)
test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
if fdinfo1 != fdinfo2:
print("FAIL")
print(test_file1)
print(fdinfo1)
print(test_file2)
print(fdinfo2)
sys.exit(1)
print("PASS")
EOF
sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
[Fix]
Import the right pieces from AUFS to properly support the fix and get
rid of the AUFS dependency across all our kernels and re-apply the
overlayfs fix without the AUFS dependency.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs, especially when containers are used.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983640/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983498] Re: Jammy: Add OVS Internal Port HW Offload to mlx5 driver
This bug is awaiting verification that the linux-nvidia/5.15.0-1006.6 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1983498 Title: Jammy: Add OVS Internal Port HW Offload to mlx5 driver Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] A request has been made, originating from https://bugs.launchpad.net/bugs/1980730, to add support for OVS internal port offload for the mlx5 driver. This feature takes care of certain traffic workloads that are not currently being offloaded to the hardware. [Test Case] Tested by the requester. [Where things could go wrong] These changes could potentially introduce regressions in behavior of the mlx5 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983498/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986798] Re: Remove unused variable from i915 psr
This bug is awaiting verification that the linux-nvidia/5.15.0-1006.6
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1986798
Title:
Remove unused variable from i915 psr
Status in linux package in Ubuntu:
Won't Fix
Status in linux source package in Jammy:
Fix Committed
Bug description:
[Impact]
Compiler warns unused variable after commit 0c1d6921b07c ("UBUNTU:
SAUCE: drm/i915/display/psr: Reinstate fix for TGL + AUO panel flicker")
[Fix]
The variable is unused, remove it.
[Test]
Compiler no longer warns about it.
[Where problems could occur]
Nothing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986798/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884232] Re: touchpad and touchscreen doesn't work at all on ACER Spin 5 (SP513-54N)
This bug is awaiting verification that the linux-
hwe-5.15/5.15.0-48.54~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem still exists, change the tag
'verification-needed-focal' to 'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1884232
Title:
touchpad and touchscreen doesn't work at all on ACER Spin 5
(SP513-54N)
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Focal:
Won't Fix
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
E820 reserved retire memory window, and make other hot-added devices unable
to get the required memory window.
[Fix]
It only can be fixed by a list of quirk to mark those machines out, and
requires below commits from v5.19-rc1 and v5.19-rc3
a2b36ffbf5b6 x86/PCI: Revert "x86/PCI: Clip only host bridge windows for E820
regions"
d341838d776a x86/PCI: Disable E820 reserved region clipping via quirks
fa6dae5d8208 x86/PCI: Add kernel cmdline options to use/ignore E820 reserved
regions
4c5e242d3e93 x86/PCI: Clip only host bridge windows for E820 regions
31bf0f433325 x86: Log resource clipping for E820 regions
93d256cd3c1e x86/PCI: Eliminate remove_e820_regions() common subexpressions
[Test]
Verified by the bug reporter.
[Where problems could occur]
The 6 commits are all clean cherry-picked, and the sixth commit reverts the
third commit which are the 2 commits that do real functional changes.
a2b36ffbf5b6 ("x86/PCI: Revert \"x86/PCI: Clip only host bridge windows for
E820 regions\"")
4c5e242d3e93 ("x86/PCI: Clip only host bridge windows for E820 regions")
The fourth and and fifth commits introduce a new quirk to ignore E820
reserved regions and the quirk only affects the listed machines.
Drivers that operates E820 table may fail if we ignore the E820 regions, but
it should have no impact on the listed consumer PCs.
===
Touchpad is not working at all on ACER Spin 5 SP513-54N.
According to
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29
I am creating this kernel bug issue.
There are more issues, too, like touchscreen not working and Ubuntu
not installable - see here if interrested
https://askubuntu.com/questions/1251719/
I would like to run Ubuntu on this machine and I am willing to help
with any debug or kernel tweaking... Please let me know.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-26-generic 5.4.0-26.30
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 4195 F pulseaudio
CasperMD5CheckResult: skip
CasperVersion: 1.445
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 19 10:44:58 2020
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Acer Spin SP513-54N
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
RelatedPackageVersions:
linux-restricted-modules-5.4.0-26-generic N/A
linux-backports-modules-5.4.0-26-generic N/A
linux-firmware1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/21/2020
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.00
dmi.board.name: Caboom_IL
dmi.board.vendor: IL
dmi.board.version: V1.00
dmi.chassis.type: 31
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.00
dmi.modalias:
dmi:bvnInsydeCorp.:bvrV1.00:bd02/21/2020:svnAcer:pnSpinSP513-54N:pvrV1.00:rvnIL:rnCaboom_IL:rvrV1.00:cvnAcer:ct31:cvrV1.00:
dmi.product.family: Spin 5
dmi.product.name: Spin SP513-54N
dmi.product.sku:
dmi.product.version: V1.00
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe :
[Kernel-packages] [Bug 1980925] Re: [SRU] bcache deadlock during read IO in writeback mode
This bug is awaiting verification that the linux- hwe-5.15/5.15.0-48.54~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1980925 Title: [SRU] bcache deadlock during read IO in writeback mode Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: [Impact] When Random Read I/O is started with a test like - fio --name=read_iops --directory=/home/ubuntu/bcache_mount/ --size=16G --ioengine=libaio --direct=1 --verify=0 --bs=4K --iodepth=128 --rw=randread --randrepeat=0 or random read-writes with a test like, fio --filename=/home/ubuntu/bcache_mount/cachedfile --size=15GB --direct=1 --rw=randrw --bs=4k --ioengine=libaio --iodepth=128 --name=iops-test-job --randrepeat=0 traces are seen in the kernel log, [ 4473.699902] INFO: task bcache_writebac:1835 blocked for more than 120 seconds. [ 4474.050921] Not tainted 5.15.50-051550-generic #202206251445 [ 4474.350883] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 4474.731391] task:bcache_writebac state:D stack:0 pid: 1835 ppid: 2 flags:0x4000 [ 4474.731408] Call Trace: [ 4474.731411] [ 4474.731413] __schedule+0x23d/0x5a0 [ 4474.731433] schedule+0x4e/0xb0 [ 4474.731436] rwsem_down_write_slowpath+0x220/0x3d0 [ 4474.731441] down_write+0x43/0x50 [ 4474.731446] bch_writeback_thread+0x78/0x320 [bcache] [ 4474.731471] ? read_dirty_submit+0x70/0x70 [bcache] [ 4474.731487] kthread+0x12a/0x150 [ 4474.731491] ? set_kthread_struct+0x50/0x50 [ 4474.731494] ret_from_fork+0x22/0x30 [ 4474.731499] The bug exists till kernel 5.15.50-051550-generic The reproducer is pasted below: # uname -a Linux bronzor 5.15.50-051550-generic #202206251445 SMP Sat Jun 25 14:51:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sdd 8:48 0 279.4G 0 disk └─sdd18:49 060G 0 part └─bcache0 252:0060G 0 disk /home/ubuntu/bcache_mount nvme0n1 259:00 372.6G 0 disk └─nvme0n1p1 259:2015G 0 part └─bcache0 252:0060G 0 disk /home/ubuntu/bcache_mount fio --name=read_iops --directory=/home/ubuntu/bcache_mount --size=12G --ioengine=libaio --direct=1 --verify=0 --bs=4K --iodepth=128 --rw=randread --group_reporting=1 read_iops: (g=0): rw=randread, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=128 fio-3.28 Starting 1 process read_iops: Laying out IO file (1 file / 12288MiB) The test does not progress beyond a few minutes, and this trace is then seen in the kernel log, [ 4473.699902] INFO: task bcache_writebac:1835 blocked for more than 120 seconds. [ 4474.050921] Not tainted 5.15.50-051550-generic #202206251445 [ 4474.350883] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 4474.731391] task:bcache_writebac state:D stack:0 pid: 1835 ppid: 2 flags:0x4000 [ 4474.731408] Call Trace: [ 4474.731411] [ 4474.731413] __schedule+0x23d/0x5a0 [ 4474.731433] schedule+0x4e/0xb0 [ 4474.731436] rwsem_down_write_slowpath+0x220/0x3d0 [ 4474.731441] down_write+0x43/0x50 [ 4474.731446] bch_writeback_thread+0x78/0x320 [bcache] [ 4474.731471] ? read_dirty_submit+0x70/0x70 [bcache] [ 4474.731487] kthread+0x12a/0x150 [ 4474.731491] ? set_kthread_struct+0x50/0x50 [ 4474.731494] ret_from_fork+0x22/0x30 [ 4474.731499] [Fix] These 3 fixes are needed for the SRU. dea3560e5f31965165bcf34ecf0b47af28bfd155, 6445ec3df23f24677064a327dce437ef3e02dc6, dc60301fb408e06e0b718c0980cdd31d2b238bee I have built these fixes into kernel 5.15.0-39-generic (jammy) and tested to verify the problem is fixed. [Regression Potential] Regression potential should be minimal. I have not seen any potential drawbacks or harmful effects of this fix in my testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1973104] Re: e1000e report hardware hang
This bug is awaiting verification that the linux- hwe-5.15/5.15.0-48.54~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1973104 Title: e1000e report hardware hang Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] e1000e hardware unit hang after s2idle May 06 15:34:49 ubuntu kernel: e1000e :00:1f.6 enp0s31f6: Detected Hardware Unit Hang: TDH <1> TDT <5> next_to_use <5> next_to_clean <1> buffer_info[next_to_clean]: time_stamp <1000587f0> next_to_watch <1> jiffies <1000589c0> next_to_watch.status <0> MAC Status <40080283> PHY Status <796d> PHY 1000BASE-T Status <3800> PHY Extended Status <3000> PCI Status <10> [Fix] Below commits fix this issue which have been included in v5.19-rc8 https://patchwork.ozlabs.org/project/intel-wired-lan/patch/20220508070905.1878172-1-sasha.nef...@intel.com/ 6cfa45361d3e Revert "e1000e: Fix possible HW unit hang after an s0ix exit" b49feacbeffc e1000e: Enable GPT clock before sending message to CSME [Test] Verified on the target machine, and confirmed the issue is gone. [Where problems could occur] The impact is low, it keeps the GPT clock enabled for CSME when e1000e_pm_resume() is called. With the new fix, the old workaround could be removed. I can't see this may introduce any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1973104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981390] Re: Mass Storage Gadget driver truncates device >2TB
This bug is awaiting verification that the linux-
hwe-5.15/5.15.0-48.54~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem still exists, change the tag
'verification-needed-focal' to 'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1981390
Title:
Mass Storage Gadget driver truncates device >2TB
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
I tried to use f_mass_storage to expose a 16TB hard drive attached to
Raspberry Pi to another computer.
On the remote computer the recognised drive has incorrect capacity and the
data is truncated.
After some debugging I noted the problem is caused by a bug in the
read capacity function of f_mass_storage in kernel version prior to
5.15, which had already been fixed upstream in mainline kernel since
v5.16
https://lore.kernel.org/all/20210914052728.23369-1-nikita.yo...@cogentembedded.com/
I tried the kernel from https://github.com/raspberrypi/linux version
rpi-5.16.y and confirmed that the problem is fixed at v5.16.
I wonder if the fix can be backported to the Ubuntu kernel.
Thank you very much!
Current kernel package version: linux-raspi (5.15.0-1011.13) jammy
Hardware: Raspberry Pi 4B
[Fix]
Backport commit bedbac5f66bf ("usb: gadget: storage: add support for
media larger than 2T")
[Test case]
See above.
[Where problems could occur]
Modifications are limited to the USB gadget mass storage driver, so
problems should only be seen on a client that uses this driver to
expose a USB drive to an attached USB host.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981390/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953613] Re: GPIO character device v1 API not enabled in kernel
This bug is awaiting verification that the linux- hwe-5.15/5.15.0-48.54~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-allwinner-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1953613 Title: GPIO character device v1 API not enabled in kernel Status in linux package in Ubuntu: Fix Released Status in linux-allwinner-5.17 package in Ubuntu: Invalid Status in linux-hwe-5.17 package in Ubuntu: Invalid Status in linux-starfive-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-allwinner-5.17 source package in Jammy: Fix Released Status in linux-hwe-5.17 source package in Jammy: Fix Committed Status in linux-starfive-5.17 source package in Jammy: Fix Released Bug description: [Impact] * The libgpiod2 library and gpiod tools shipped in Jammy don't work. * These tools are meant to replace the old sysfs interface and be a better and more efficient way to manipulate GPIOs from userspace. Unfortunately the latest release is still using v1 of the character device kernel API which is not enabled in Ubuntu kernels. * This is Kent Gibsons reply on the linux-gpio mailing list: On Tue, Jul 12, 2022 at 09:48:45AM +0200, Alexandre Ghiti wrote: > Hi, > > Ubuntu kernels do not enable GPIO_CDEV_V1 as it is deprecated, but the > libgpiod package that we ship is still based on the latest version > 1.6.3 which does not implement the API v2. So I'd like to update > libgpiod, do you have any recommendations about what branch/sha1 I > should use? Do you plan to make a release that implements the API v2? > Firstly, libgpiod is Bart's library so he is the authority, but this is my understanding... TLDR: You should keep GPIO_CDEV_V1 enabled. v1 is deprecated from a development perspective, so all new feature development will occur on v2, and new applications should target v2. Existing apps targetting v1, be that directly or via libgpiod v1.6.3, will require GPIO_CDEV_V1 until they migrate to v2. The mainline kernel will continue to support v1 while userspace transitions. libgpiod v2 is in active development, and should reach its first release shortly. Note that it is NOT a plugin replacement for v1. It has a different API, for similar reasons to why we had to switch in the kernel, so apps will need to be actively migrated. I wouldn't suggest making any effort to package libgpiod v2 until Bart makes an official release. Cheers, Kent. [Test Plan] * Run gpioinfo on a machine with exposed GPIOs and check that it lists the GPIOs and doesn't error with gpioinfo: error creating line iterator: Invalid argument [Where problems could occur] * There may be code and scripts that hasn't been tested with a working libgpiod2/gpiod tools and uncover latent bugs. [Other Info] Original bug text: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. Thanks to Marek Szuba, who reported the same bug for Gentoo (https://bugs.gentoo.org/807334), pointing me in the right direction. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1
[Kernel-packages] [Bug 1982930] Re: ioam6.sh in net from ubuntu_kernel_selftests fails with 5.15 kernels in Focal
This bug is awaiting verification that the linux- hwe-5.15/5.15.0-48.54~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982930 Title: ioam6.sh in net from ubuntu_kernel_selftests fails with 5.15 kernels in Focal Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Released Bug description: [Impact] Testcase ubuntu_kernel_selftests.net:ioam6.sh fails in Focal with the 5.15 kernels with the following errors: 17:19:35 DEBUG| [stdout] make: Entering directory '/tmp/autopkgtest.WSxPqj/build.GQs/src/autotest/cl ient/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' 17:19:35 DEBUG| [stdout] make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install 17:19:35 DEBUG| [stdout] make[1]: Entering directory '/tmp/autopkgtest.WSxPqj/build.GQs/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' 17:19:35 DEBUG| [stdout] INSTALL ./usr/include 17:19:35 DEBUG| [stdout] make[1]: Leaving directory '/tmp/autopkgtest.WSxPqj/build.GQs/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' 17:19:35 DEBUG| [stdout] TAP version 13 17:19:35 DEBUG| [stdout] 1..1 17:19:35 DEBUG| [stdout] # selftests: net: ioam6.sh 17:19:35 DEBUG| [stdout] # SKIP: iproute2 too old, missing ioam command 17:19:35 DEBUG| [stdout] not ok 1 selftests: net: ioam6.sh # exit=1 This is caused by an older version of iproute2 in Focal. The package has been updated in Jammy via bug 1951390 and the bug report says it should be updated in Focal as well. Even if the package is eventually updated, the testcase shouldn't throw a fatal error in this case and really return "SKIP" as the log message says. [Fix] The proper fix would be to make tools/testing/selftests/net/ioam6.sh return the Kselftest framework proper skip code instead of failing. [Testcase] Run the selftest script in Focal with a 5.15 kernel. [Where problems could occur] If the skip code is added to places where it shouldn't be added it could introduce false positives and not fail where it should. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1982930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983143] Re: AMD Rembrandt: DP tunneling fails with Thunderbolt monitors
This bug is awaiting verification that the linux- hwe-5.15/5.15.0-48.54~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1983143 Title: AMD Rembrandt: DP tunneling fails with Thunderbolt monitors Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released 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 Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Summary] No video output on Thunderbolt monitor. 1. Connect monitor to DUT directly 2. Connect monitor to DUT via Docking System can detect the monitor and able to change display mode but no output on the monitor [Steps to reproduce] 1. Boot to OS 2. Plug an external monitor via thunderbolt port [Expected result] Display on external monitor normally [Actual result] No vidoe ouput on external monitor [Failure rate] 3/3 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1983143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983297] Re: Additional fix for TGL + AUO panel flickering
This bug is awaiting verification that the linux- hwe-5.15/5.15.0-48.54~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1983297 Title: Additional fix for TGL + AUO panel flickering Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] "UBUNTU: SAUCE: drm/i915/display/psr: Fix flicker on TGL + AUO panel" alone used to fix the issue on the AUO panel. But the panel starts to flicker like crazy on top of the new stable commits. [Fix] Backport full fix for PSR2 selective fetch, but only enable it on TGL + specific AUO panel. The last three patches which enable PSR2 on ADL-P are dropped. [Test] Originally the backport regressed ADL + BOE panel, so this time we put extra effort to ensure those system are unaffected, while TGL + AUO panel is still fixed. [Where problems could occur] Most code changes only have functional impact when PSR2 selective fetch is enabled. Some of changes are under more general call path for hardware cursor rendering. Notes are added to describe the functional impact for each patch, so if regression really occurrs it's easier to spot the offending commit. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1983297/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983640] Re: refactoring of overlayfs fix to properly support shiftfs
This bug is awaiting verification that the linux/5.15.0-48.54 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-jammy' to 'verification-done-jammy'. If the problem
still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1983640
Title:
refactoring of overlayfs fix to properly support shiftfs
Status in linux package in Ubuntu:
Fix Committed
Status in linux-hwe-5.17 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux-hwe-5.17 source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Committed
Status in linux-hwe-5.17 source package in Kinetic:
Invalid
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
However, we made this patch dependent on AUFS, starting with Jammy
we're not enabling AUFS anymore, so this fix becomes a no-op.
So we need to re-introduce this fix with a bit of refactoring to not
depend on AUFS.
[Test case]
The following script can be used to trigger the issue:
#!/bin/bash
cat > test.py << EOF
import sys
f = open("/proc/self/maps")
for l in f.readlines():
if "python" not in l:
continue
print(l)
s = l.split()
start, end = s[0].split("-")
fname = s[-1]
print(start, end, fname)
break
else:
sys.exit(1)
test_file1 = open(fname)
test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
if fdinfo1 != fdinfo2:
print("FAIL")
print(test_file1)
print(fdinfo1)
print(test_file2)
print(fdinfo2)
sys.exit(1)
print("PASS")
EOF
sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
[Fix]
Import the right pieces from AUFS to properly support the fix and get
rid of the AUFS dependency across all our kernels and re-apply the
overlayfs fix without the AUFS dependency.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs, especially when containers are used.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983640/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983498] Re: Jammy: Add OVS Internal Port HW Offload to mlx5 driver
This bug is awaiting verification that the linux/5.15.0-48.54 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1983498 Title: Jammy: Add OVS Internal Port HW Offload to mlx5 driver Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] A request has been made, originating from https://bugs.launchpad.net/bugs/1980730, to add support for OVS internal port offload for the mlx5 driver. This feature takes care of certain traffic workloads that are not currently being offloaded to the hardware. [Test Case] Tested by the requester. [Where things could go wrong] These changes could potentially introduce regressions in behavior of the mlx5 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983498/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986798] Re: Remove unused variable from i915 psr
This bug is awaiting verification that the linux/5.15.0-48.54 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-jammy' to 'verification-done-jammy'. If the problem
still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1986798
Title:
Remove unused variable from i915 psr
Status in linux package in Ubuntu:
Won't Fix
Status in linux source package in Jammy:
Fix Committed
Bug description:
[Impact]
Compiler warns unused variable after commit 0c1d6921b07c ("UBUNTU:
SAUCE: drm/i915/display/psr: Reinstate fix for TGL + AUO panel flicker")
[Fix]
The variable is unused, remove it.
[Test]
Compiler no longer warns about it.
[Where problems could occur]
Nothing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986798/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988966] Re: kiwi: kiwi-dracut-oem-dump/riscv64 has unsatisfiable dependency
This bug was fixed in the package kiwi - 9.24.45-1ubuntu1 --- kiwi (9.24.45-1ubuntu1) kinetic; urgency=medium * Drop riscv64 as an architecture for kiwi-dracut-oem-dump, until kexec-tools are appropriately available on that architecture (LP: #1988966) -- Dan Bungert Fri, 16 Sep 2022 14:08:43 -0600 ** Changed in: kiwi (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1988966 Title: kiwi: kiwi-dracut-oem-dump/riscv64 has unsatisfiable dependency Status in kexec-tools package in Ubuntu: New Status in kiwi package in Ubuntu: Fix Released Status in kexec-tools package in Debian: New Bug description: kiwi-dracut-oem-dump has a dependency on kexec-tools which is not built for riscv64. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019254 contains a patch from openSUSE https://build.opensuse.org/package/view_file/openSUSE:Factory:RISCV/kexec- tools/riscv.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1988966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983297] Re: Additional fix for TGL + AUO panel flickering
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1052.59 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1983297 Title: Additional fix for TGL + AUO panel flickering Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] "UBUNTU: SAUCE: drm/i915/display/psr: Fix flicker on TGL + AUO panel" alone used to fix the issue on the AUO panel. But the panel starts to flicker like crazy on top of the new stable commits. [Fix] Backport full fix for PSR2 selective fetch, but only enable it on TGL + specific AUO panel. The last three patches which enable PSR2 on ADL-P are dropped. [Test] Originally the backport regressed ADL + BOE panel, so this time we put extra effort to ensure those system are unaffected, while TGL + AUO panel is still fixed. [Where problems could occur] Most code changes only have functional impact when PSR2 selective fetch is enabled. Some of changes are under more general call path for hardware cursor rendering. Notes are added to describe the functional impact for each patch, so if regression really occurrs it's easier to spot the offending commit. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1983297/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1984011] Re: [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal
This bug is awaiting verification that the linux/5.4.0-126.142 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1984011 Title: [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: [Impact] fNIC driver controls print messages based on the flag fnic_log_level. shost_printk is not controlled via this flag. This issue is resolved by using some of the print macros that have been defined in fnic. This has negligible impact. The resid was being set irrespective of whether we saw an underflow or not. It needs to be set only when we see an underflow. The impact here is negligible. When we don't receive link events, we could go into a loop before sending fw reset. The patch for the issue resolves this, and we break out of the loop. Prior to checking the remote port, fnic driver must check if the io_req is valid. If not, there could be a crash. The patch resolves this issue. [Fix] The following patches need to be pulled from upstream to update the fnic driver to 1.6.0.53: https://marc.info/?l=linux-scsi=160591061813369=2 https://marc.info/?l=linux-scsi=160592183315837=2 https://marc.info/?l=linux-scsi=160592283315997=2 https://marc.info/?l=linux-scsi=160592363016122=2 https://marc.info/?l=linux-scsi=160592616516616=2 Here's a description of each issue: 1. https://marc.info/?l=linux-scsi=160591061813369=2 FNIC_FCS_DBG print is controlled by fnic_log_level flag. Replace shost_printk in fnic_fip_handler_timer with this print so that it can be controlled. 2. https://marc.info/?l=linux-scsi=160592183315837=2 When fnic is in TRANS ETH state, and when there are no link events, we must not loop before sending fw reset. 3. https://marc.info/?l=linux-scsi=160592283315997=2 FNIC_MAIN_DBG print is controlled by fnic_log_level flag. Replace shost_printk in fnic_handle_link with this print so that it can be controlled. 4. https://marc.info/?l=linux-scsi=160592363016122=2 Fix to set scsi_set_resid() only if FCPIO_ICMND_CMPL_RESID_UNDER is set. 5. https://marc.info/?l=linux-scsi=160592616516616=2 Check for a valid io_req before we check other data. [Test Plan] Runnings IOs with multiple link flaps would be a good test case to validate all the patches above. It is suggested to run these IOs with a data integrity check. We do this as a standard practice. [Where problems could occur] The print messages are innocuous. It is not expected to run into any issues. Problems could occur with storage arrays that have a non-standard response. If the sanity test fails, there could be issues in the scsi midlayer or fnic driver. All the patches present low regression risk. [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/fnic_cisco_ver3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986713] Re: azure: Replace hyperv_fb with hyperv_drm
This bug is awaiting verification that the linux-azure/5.15.0-1020.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1986713 Title: azure: Replace hyperv_fb with hyperv_drm Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: SRU Justification [Impact] Microsoft has asked to replace hyperv_fb with hyperv_drm in linux- modules-azure. [Test Plan] Extract linux-modules and ensure hyperv_drm.ko exists and hyperv_fb.ko does not. [Where things could go wrong] According to Microsoft, hyperv_drm is a direct replacement for hyperv_fb, yet there could be cases where hyperv_fb is being explicitly installed by customized images. [Other Info] SF: #00342707 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988434] Re: azure: Set arm64 CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=n
This bug is awaiting verification that the linux-azure/5.15.0-1020.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1988434 Title: azure: Set arm64 CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=n Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: Fix Committed Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Kinetic: Fix Released Bug description: SRU Justification [Impact] This request for all the ARM images Kernel have config updated . There is performance issues due to these config setting and after troubleshooting MSFT team found below two settings to update . Recommended CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS=n CONFIG_TRANSPARENT_HUGEPAGE_MADVISE=y [Test Case] Microsoft tested [Where things could go wrong] Performance could decrease for some workloads. [Other Info] SF: #00343662 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1988434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980925] Re: [SRU] bcache deadlock during read IO in writeback mode
This bug is awaiting verification that the linux-lowlatency- hwe-5.15/5.15.0-48.54~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1980925 Title: [SRU] bcache deadlock during read IO in writeback mode Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: [Impact] When Random Read I/O is started with a test like - fio --name=read_iops --directory=/home/ubuntu/bcache_mount/ --size=16G --ioengine=libaio --direct=1 --verify=0 --bs=4K --iodepth=128 --rw=randread --randrepeat=0 or random read-writes with a test like, fio --filename=/home/ubuntu/bcache_mount/cachedfile --size=15GB --direct=1 --rw=randrw --bs=4k --ioengine=libaio --iodepth=128 --name=iops-test-job --randrepeat=0 traces are seen in the kernel log, [ 4473.699902] INFO: task bcache_writebac:1835 blocked for more than 120 seconds. [ 4474.050921] Not tainted 5.15.50-051550-generic #202206251445 [ 4474.350883] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 4474.731391] task:bcache_writebac state:D stack:0 pid: 1835 ppid: 2 flags:0x4000 [ 4474.731408] Call Trace: [ 4474.731411] [ 4474.731413] __schedule+0x23d/0x5a0 [ 4474.731433] schedule+0x4e/0xb0 [ 4474.731436] rwsem_down_write_slowpath+0x220/0x3d0 [ 4474.731441] down_write+0x43/0x50 [ 4474.731446] bch_writeback_thread+0x78/0x320 [bcache] [ 4474.731471] ? read_dirty_submit+0x70/0x70 [bcache] [ 4474.731487] kthread+0x12a/0x150 [ 4474.731491] ? set_kthread_struct+0x50/0x50 [ 4474.731494] ret_from_fork+0x22/0x30 [ 4474.731499] The bug exists till kernel 5.15.50-051550-generic The reproducer is pasted below: # uname -a Linux bronzor 5.15.50-051550-generic #202206251445 SMP Sat Jun 25 14:51:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sdd 8:48 0 279.4G 0 disk └─sdd18:49 060G 0 part └─bcache0 252:0060G 0 disk /home/ubuntu/bcache_mount nvme0n1 259:00 372.6G 0 disk └─nvme0n1p1 259:2015G 0 part └─bcache0 252:0060G 0 disk /home/ubuntu/bcache_mount fio --name=read_iops --directory=/home/ubuntu/bcache_mount --size=12G --ioengine=libaio --direct=1 --verify=0 --bs=4K --iodepth=128 --rw=randread --group_reporting=1 read_iops: (g=0): rw=randread, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=128 fio-3.28 Starting 1 process read_iops: Laying out IO file (1 file / 12288MiB) The test does not progress beyond a few minutes, and this trace is then seen in the kernel log, [ 4473.699902] INFO: task bcache_writebac:1835 blocked for more than 120 seconds. [ 4474.050921] Not tainted 5.15.50-051550-generic #202206251445 [ 4474.350883] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 4474.731391] task:bcache_writebac state:D stack:0 pid: 1835 ppid: 2 flags:0x4000 [ 4474.731408] Call Trace: [ 4474.731411] [ 4474.731413] __schedule+0x23d/0x5a0 [ 4474.731433] schedule+0x4e/0xb0 [ 4474.731436] rwsem_down_write_slowpath+0x220/0x3d0 [ 4474.731441] down_write+0x43/0x50 [ 4474.731446] bch_writeback_thread+0x78/0x320 [bcache] [ 4474.731471] ? read_dirty_submit+0x70/0x70 [bcache] [ 4474.731487] kthread+0x12a/0x150 [ 4474.731491] ? set_kthread_struct+0x50/0x50 [ 4474.731494] ret_from_fork+0x22/0x30 [ 4474.731499] [Fix] These 3 fixes are needed for the SRU. dea3560e5f31965165bcf34ecf0b47af28bfd155, 6445ec3df23f24677064a327dce437ef3e02dc6, dc60301fb408e06e0b718c0980cdd31d2b238bee I have built these fixes into kernel 5.15.0-39-generic (jammy) and tested to verify the problem is fixed. [Regression Potential] Regression potential should be minimal. I have not seen any potential drawbacks or harmful effects of this fix in my testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More
[Kernel-packages] [Bug 1884232] Re: touchpad and touchscreen doesn't work at all on ACER Spin 5 (SP513-54N)
This bug is awaiting verification that the linux-lowlatency-
hwe-5.15/5.15.0-48.54~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem still exists, change the tag
'verification-needed-focal' to 'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1884232
Title:
touchpad and touchscreen doesn't work at all on ACER Spin 5
(SP513-54N)
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Focal:
Won't Fix
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
E820 reserved retire memory window, and make other hot-added devices unable
to get the required memory window.
[Fix]
It only can be fixed by a list of quirk to mark those machines out, and
requires below commits from v5.19-rc1 and v5.19-rc3
a2b36ffbf5b6 x86/PCI: Revert "x86/PCI: Clip only host bridge windows for E820
regions"
d341838d776a x86/PCI: Disable E820 reserved region clipping via quirks
fa6dae5d8208 x86/PCI: Add kernel cmdline options to use/ignore E820 reserved
regions
4c5e242d3e93 x86/PCI: Clip only host bridge windows for E820 regions
31bf0f433325 x86: Log resource clipping for E820 regions
93d256cd3c1e x86/PCI: Eliminate remove_e820_regions() common subexpressions
[Test]
Verified by the bug reporter.
[Where problems could occur]
The 6 commits are all clean cherry-picked, and the sixth commit reverts the
third commit which are the 2 commits that do real functional changes.
a2b36ffbf5b6 ("x86/PCI: Revert \"x86/PCI: Clip only host bridge windows for
E820 regions\"")
4c5e242d3e93 ("x86/PCI: Clip only host bridge windows for E820 regions")
The fourth and and fifth commits introduce a new quirk to ignore E820
reserved regions and the quirk only affects the listed machines.
Drivers that operates E820 table may fail if we ignore the E820 regions, but
it should have no impact on the listed consumer PCs.
===
Touchpad is not working at all on ACER Spin 5 SP513-54N.
According to
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29
I am creating this kernel bug issue.
There are more issues, too, like touchscreen not working and Ubuntu
not installable - see here if interrested
https://askubuntu.com/questions/1251719/
I would like to run Ubuntu on this machine and I am willing to help
with any debug or kernel tweaking... Please let me know.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-26-generic 5.4.0-26.30
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 4195 F pulseaudio
CasperMD5CheckResult: skip
CasperVersion: 1.445
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 19 10:44:58 2020
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Acer Spin SP513-54N
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
RelatedPackageVersions:
linux-restricted-modules-5.4.0-26-generic N/A
linux-backports-modules-5.4.0-26-generic N/A
linux-firmware1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/21/2020
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.00
dmi.board.name: Caboom_IL
dmi.board.vendor: IL
dmi.board.version: V1.00
dmi.chassis.type: 31
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.00
dmi.modalias:
dmi:bvnInsydeCorp.:bvrV1.00:bd02/21/2020:svnAcer:pnSpinSP513-54N:pvrV1.00:rvnIL:rnCaboom_IL:rvrV1.00:cvnAcer:ct31:cvrV1.00:
dmi.product.family: Spin 5
dmi.product.name: Spin SP513-54N
dmi.product.sku:
dmi.product.version: V1.00
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 1953613] Re: GPIO character device v1 API not enabled in kernel
This bug is awaiting verification that the linux-lowlatency- hwe-5.15/5.15.0-48.54~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-allwinner-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1953613 Title: GPIO character device v1 API not enabled in kernel Status in linux package in Ubuntu: Fix Released Status in linux-allwinner-5.17 package in Ubuntu: Invalid Status in linux-hwe-5.17 package in Ubuntu: Invalid Status in linux-starfive-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-allwinner-5.17 source package in Jammy: Fix Released Status in linux-hwe-5.17 source package in Jammy: Fix Committed Status in linux-starfive-5.17 source package in Jammy: Fix Released Bug description: [Impact] * The libgpiod2 library and gpiod tools shipped in Jammy don't work. * These tools are meant to replace the old sysfs interface and be a better and more efficient way to manipulate GPIOs from userspace. Unfortunately the latest release is still using v1 of the character device kernel API which is not enabled in Ubuntu kernels. * This is Kent Gibsons reply on the linux-gpio mailing list: On Tue, Jul 12, 2022 at 09:48:45AM +0200, Alexandre Ghiti wrote: > Hi, > > Ubuntu kernels do not enable GPIO_CDEV_V1 as it is deprecated, but the > libgpiod package that we ship is still based on the latest version > 1.6.3 which does not implement the API v2. So I'd like to update > libgpiod, do you have any recommendations about what branch/sha1 I > should use? Do you plan to make a release that implements the API v2? > Firstly, libgpiod is Bart's library so he is the authority, but this is my understanding... TLDR: You should keep GPIO_CDEV_V1 enabled. v1 is deprecated from a development perspective, so all new feature development will occur on v2, and new applications should target v2. Existing apps targetting v1, be that directly or via libgpiod v1.6.3, will require GPIO_CDEV_V1 until they migrate to v2. The mainline kernel will continue to support v1 while userspace transitions. libgpiod v2 is in active development, and should reach its first release shortly. Note that it is NOT a plugin replacement for v1. It has a different API, for similar reasons to why we had to switch in the kernel, so apps will need to be actively migrated. I wouldn't suggest making any effort to package libgpiod v2 until Bart makes an official release. Cheers, Kent. [Test Plan] * Run gpioinfo on a machine with exposed GPIOs and check that it lists the GPIOs and doesn't error with gpioinfo: error creating line iterator: Invalid argument [Where problems could occur] * There may be code and scripts that hasn't been tested with a working libgpiod2/gpiod tools and uncover latent bugs. [Other Info] Original bug text: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. Thanks to Marek Szuba, who reported the same bug for Gentoo (https://bugs.gentoo.org/807334), pointing me in the right direction. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1
[Kernel-packages] [Bug 1973104] Re: e1000e report hardware hang
This bug is awaiting verification that the linux-lowlatency- hwe-5.15/5.15.0-48.54~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1973104 Title: e1000e report hardware hang Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] e1000e hardware unit hang after s2idle May 06 15:34:49 ubuntu kernel: e1000e :00:1f.6 enp0s31f6: Detected Hardware Unit Hang: TDH <1> TDT <5> next_to_use <5> next_to_clean <1> buffer_info[next_to_clean]: time_stamp <1000587f0> next_to_watch <1> jiffies <1000589c0> next_to_watch.status <0> MAC Status <40080283> PHY Status <796d> PHY 1000BASE-T Status <3800> PHY Extended Status <3000> PCI Status <10> [Fix] Below commits fix this issue which have been included in v5.19-rc8 https://patchwork.ozlabs.org/project/intel-wired-lan/patch/20220508070905.1878172-1-sasha.nef...@intel.com/ 6cfa45361d3e Revert "e1000e: Fix possible HW unit hang after an s0ix exit" b49feacbeffc e1000e: Enable GPT clock before sending message to CSME [Test] Verified on the target machine, and confirmed the issue is gone. [Where problems could occur] The impact is low, it keeps the GPT clock enabled for CSME when e1000e_pm_resume() is called. With the new fix, the old workaround could be removed. I can't see this may introduce any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1973104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981390] Re: Mass Storage Gadget driver truncates device >2TB
This bug is awaiting verification that the linux-lowlatency-
hwe-5.15/5.15.0-48.54~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem still exists, change the tag
'verification-needed-focal' to 'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1981390
Title:
Mass Storage Gadget driver truncates device >2TB
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
I tried to use f_mass_storage to expose a 16TB hard drive attached to
Raspberry Pi to another computer.
On the remote computer the recognised drive has incorrect capacity and the
data is truncated.
After some debugging I noted the problem is caused by a bug in the
read capacity function of f_mass_storage in kernel version prior to
5.15, which had already been fixed upstream in mainline kernel since
v5.16
https://lore.kernel.org/all/20210914052728.23369-1-nikita.yo...@cogentembedded.com/
I tried the kernel from https://github.com/raspberrypi/linux version
rpi-5.16.y and confirmed that the problem is fixed at v5.16.
I wonder if the fix can be backported to the Ubuntu kernel.
Thank you very much!
Current kernel package version: linux-raspi (5.15.0-1011.13) jammy
Hardware: Raspberry Pi 4B
[Fix]
Backport commit bedbac5f66bf ("usb: gadget: storage: add support for
media larger than 2T")
[Test case]
See above.
[Where problems could occur]
Modifications are limited to the USB gadget mass storage driver, so
problems should only be seen on a client that uses this driver to
expose a USB drive to an attached USB host.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981390/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982930] Re: ioam6.sh in net from ubuntu_kernel_selftests fails with 5.15 kernels in Focal
This bug is awaiting verification that the linux-lowlatency- hwe-5.15/5.15.0-48.54~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982930 Title: ioam6.sh in net from ubuntu_kernel_selftests fails with 5.15 kernels in Focal Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Released Bug description: [Impact] Testcase ubuntu_kernel_selftests.net:ioam6.sh fails in Focal with the 5.15 kernels with the following errors: 17:19:35 DEBUG| [stdout] make: Entering directory '/tmp/autopkgtest.WSxPqj/build.GQs/src/autotest/cl ient/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' 17:19:35 DEBUG| [stdout] make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install 17:19:35 DEBUG| [stdout] make[1]: Entering directory '/tmp/autopkgtest.WSxPqj/build.GQs/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' 17:19:35 DEBUG| [stdout] INSTALL ./usr/include 17:19:35 DEBUG| [stdout] make[1]: Leaving directory '/tmp/autopkgtest.WSxPqj/build.GQs/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' 17:19:35 DEBUG| [stdout] TAP version 13 17:19:35 DEBUG| [stdout] 1..1 17:19:35 DEBUG| [stdout] # selftests: net: ioam6.sh 17:19:35 DEBUG| [stdout] # SKIP: iproute2 too old, missing ioam command 17:19:35 DEBUG| [stdout] not ok 1 selftests: net: ioam6.sh # exit=1 This is caused by an older version of iproute2 in Focal. The package has been updated in Jammy via bug 1951390 and the bug report says it should be updated in Focal as well. Even if the package is eventually updated, the testcase shouldn't throw a fatal error in this case and really return "SKIP" as the log message says. [Fix] The proper fix would be to make tools/testing/selftests/net/ioam6.sh return the Kselftest framework proper skip code instead of failing. [Testcase] Run the selftest script in Focal with a 5.15 kernel. [Where problems could occur] If the skip code is added to places where it shouldn't be added it could introduce false positives and not fail where it should. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1982930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983143] Re: AMD Rembrandt: DP tunneling fails with Thunderbolt monitors
This bug is awaiting verification that the linux-lowlatency- hwe-5.15/5.15.0-48.54~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1983143 Title: AMD Rembrandt: DP tunneling fails with Thunderbolt monitors Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released 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 Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Summary] No video output on Thunderbolt monitor. 1. Connect monitor to DUT directly 2. Connect monitor to DUT via Docking System can detect the monitor and able to change display mode but no output on the monitor [Steps to reproduce] 1. Boot to OS 2. Plug an external monitor via thunderbolt port [Expected result] Display on external monitor normally [Actual result] No vidoe ouput on external monitor [Failure rate] 3/3 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1983143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983297] Re: Additional fix for TGL + AUO panel flickering
This bug is awaiting verification that the linux-lowlatency- hwe-5.15/5.15.0-48.54~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1983297 Title: Additional fix for TGL + AUO panel flickering Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] "UBUNTU: SAUCE: drm/i915/display/psr: Fix flicker on TGL + AUO panel" alone used to fix the issue on the AUO panel. But the panel starts to flicker like crazy on top of the new stable commits. [Fix] Backport full fix for PSR2 selective fetch, but only enable it on TGL + specific AUO panel. The last three patches which enable PSR2 on ADL-P are dropped. [Test] Originally the backport regressed ADL + BOE panel, so this time we put extra effort to ensure those system are unaffected, while TGL + AUO panel is still fixed. [Where problems could occur] Most code changes only have functional impact when PSR2 selective fetch is enabled. Some of changes are under more general call path for hardware cursor rendering. Notes are added to describe the functional impact for each patch, so if regression really occurrs it's easier to spot the offending commit. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1983297/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1966436] Re: Bluetooth fails to connect "br-connection-profile-unavailable"
Thanks for this - I couldn't pair a simple Bluetooth speaker on 22.04 upgraded from 22.04. I didn't even know that pipewire was a thing nor that it crept in. Now it's working well, hopefully my JACK configuration will continue to work well as well... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1966436 Title: Bluetooth fails to connect "br-connection-profile-unavailable" Status in bluez package in Ubuntu: Invalid Status in pipewire package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: How to reproduce: > bluetoothctl scan on Discovery started ... > bluetoothctl connect 94:DB:56:8E:0B:96 Attempting to connect to 94:DB:56:8E:0B:96 Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable > systemctl status bluetooth bluetooth.service - Bluetooth service Loaded: loaded ... mars 25 12:39:08 ncelrnd2375 bluetoothd[1282]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 94:DB:56:8E:0B:96: Protocol not available Notes: kernel-5.15, bluez-5.64 Bus 003 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth Dell Precision 3560 Unfortunately I did not test before upgrade to 22.04. Tried installing pipewire-pulse, blueman, but this is lower-level. There are reports of similar errors popping up in Arch and Manjaro recently: https://bbs.archlinux.org/viewtopic.php?id=270465 https://forum.manjaro.org/t/bluetooth-ko-with-kernel-5-16/99913 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Mar 25 12:56:34 2022 InstallationDate: Installed on 2022-03-04 (21 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Precision 3560 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/AmadeUbuntu20-root ro audit=1 acpi_rev_override load_nvme=YES nouveau.modeset=0 dis_ucode_ldr quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-03-22 (3 days ago) dmi.bios.date: 09/13/2021 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.2 dmi.board.name: 095HH7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.2:bd09/13/2021:br1.12:svnDellInc.:pnPrecision3560:pvr:rvnDellInc.:rn095HH7:rvrA00:cvnDellInc.:ct10:cvr:sku0A22: dmi.product.family: Precision dmi.product.name: Precision 3560 dmi.product.sku: 0A22 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 44:E5:17:BC:00:DD ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:24189 acl:41 sco:0 events:519 errors:0 TX bytes:8252 acl:33 sco:0 commands:239 errors:0 modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1966436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988966] Re: kiwi: kiwi-dracut-oem-dump/riscv64 has unsatisfiable dependency
The origin of that patch appears to be: https://github.com/riscv-collab/kexec-tools/compare/master...riscv There seems to be some ongoing conversation about that patch: http://lists.infradead.org/pipermail/kexec/2022-August/025697.html Given that it's been around for a year and not merged yet and still under discussion with fundamental-looking changes needed, I though it best to not apply the patch. I have elected to remove the risc-v build from kiwi-dracut-oem-dump until the above is resolved. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1988966 Title: kiwi: kiwi-dracut-oem-dump/riscv64 has unsatisfiable dependency Status in kexec-tools package in Ubuntu: New Status in kiwi package in Ubuntu: New Status in kexec-tools package in Debian: New Bug description: kiwi-dracut-oem-dump has a dependency on kexec-tools which is not built for riscv64. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019254 contains a patch from openSUSE https://build.opensuse.org/package/view_file/openSUSE:Factory:RISCV/kexec- tools/riscv.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1988966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947464] Re: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse
Thanks to the original reporter. I have re-opened essentially the same bug. See bug 1989991 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947464 Title: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse Status in linux package in Ubuntu: Expired Bug description: Hi The following problem has existed for years on Linux or Ubuntu. As the title of the bug report suggests, the touchpad of a Logitech K400 Plus Wireless Touch Keyboard [1] is wrongly recognized as a mouse. Touchpad features like scrolling, tapping, etc. do not work at all. As requested in the DebuggingTouchpadDetection [2] guidelines, I have gathered and attached the required hardware information. I hope this helps to fix this annoying problem that has been going on for years. Best regards, Ettore Atalan [1] Logitech product page: https://www.logitech.com/en-us/products/keyboards/k400-plus-touchpad-keyboard.920-007119.html [2] https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_Touchpad_features_like_scrolling.2C_tapping.2C_etc._do_not_work_at_all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947464/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989992] Re: i915 traceback when connecting display via USB-C
Following the suggestion on https://forums.lenovo.com/t5/Other-Linux- Discussions/Thinkpad-T14-Gen-3-has-no-available-HDMI-ports-under- Linux/m-p/5147202?page=8#5745003 I've tried setting i915.enable_psr2_sel_fetch=0, which does seem to avoid the traceback. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989992 Title: i915 traceback when connecting display via USB-C Status in linux package in Ubuntu: Confirmed Bug description: When connecting display via USB-C, I get the following traceback in dmesg. The display still work, though. [ 62.598637] usb 3-5: new full-speed USB device number 11 using xhci_hcd [ 62.761540] usb 3-5: not running at top speed; connect to a high speed hub [ 62.766478] usb 3-5: New USB device found, idVendor=2109, idProduct=0103, bcdDevice= 3.c3 [ 62.766487] usb 3-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 62.766490] usb 3-5: Product: USB 2.0 BILLBOARD [ 62.766493] usb 3-5: Manufacturer: VLI Inc. [ 62.766494] usb 3-5: SerialNumber: 0001 [ 62.927194] ucsi_acpi USBC000:00: ucsi_handle_connector_change: GET_CONNECTOR_STATUS failed (-110) [ 63.100051] ucsi_acpi USBC000:00: UCSI_GET_PDOS returned 0 bytes [ 63.463027] Registered IR keymap rc-cec [ 63.463092] rc rc0: DP-1 as /devices/pci:00/:00:02.0/rc/rc0 [ 63.463127] input: DP-1 as /devices/pci:00/:00:02.0/rc/rc0/input27 [ 65.013853] i915 :00:02.0: [drm] *ERROR* [CRTC:80:pipe A] mismatch in has_psr (expected yes, found no) [ 65.013859] i915 :00:02.0: [drm] *ERROR* [CRTC:80:pipe A] mismatch in has_psr2 (expected yes, found no) [ 65.013860] i915 :00:02.0: [drm] *ERROR* [CRTC:80:pipe A] mismatch in enable_psr2_sel_fetch (expected yes, found no) [ 65.013862] [ cut here ] [ 65.013862] pipe state doesn't match! [ 65.013913] WARNING: CPU: 4 PID: 3728 at drivers/gpu/drm/i915/display/intel_display.c:6682 verify_crtc_state+0x47d/0x540 [i915] [ 65.014021] Modules linked in: typec_displayport binfmt_misc veth nft_masq zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) ccm vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xfrm_user xfrm_algo xt_addrtype iptable_nat bpfilter rfcomm cmac algif_hash algif_skcipher af_alg xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables snd_seq_dummy snd_hrtimer nfnetlink bnep nls_iso8859_1 snd_ctl_led snd_soc_skl_hda_dsp snd_soc_intel_hda_dsp_common snd_soc_hdac_hdmi snd_sof_probes snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_soc_dmic snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core [ 65.014049] snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel iwlmvm snd_intel_dspcfg snd_intel_sdw_acpi snd_usb_audio snd_hda_codec intel_tcc_cooling snd_usbmidi_lib snd_hda_core mac80211 snd_hwdep snd_pcm x86_pkg_temp_thermal intel_powerclamp snd_seq_midi libarc4 snd_seq_midi_event coretemp uvcvideo snd_rawmidi btusb btrtl videobuf2_vmalloc btbcm videobuf2_memops kvm_intel thinkpad_acpi snd_seq btintel videobuf2_v4l2 mei_pxp mei_hdcp btmtk videobuf2_common snd_seq_device nvram kvm iwlwifi rapl bluetooth videodev ledtrig_audio snd_timer pmt_telemetry spi_nor
[Kernel-packages] [Bug 1990009] Re: Azure: Focal 5.4 kernel eBPF opensnoop does not display PATH
Git repository at 'git://git.launchpad.net/~timg- tpi/ubuntu/+source/linux/+git/focal focal-azure-opensnoop'. The kernel built using these sources worked correctly. ** Description changed: SRU Justification [Impact] The actual kernel used on AKS arm64 (i.e. 5.4.1089) suffers from a known problem [1]. As a consequence, opensnoop does not display PATH: # Run the following from Canonical:UbuntuServer:18_04-daily-lts-arm64:18.04.202208290 $ uname -a Linux francis-vm-arm64-ubuntu18vm 5.4.0-1089-azure #94~18.04.1-Ubuntu SMP Fri Aug 5 12:36:48 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux $ lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 $ git clone --recurse-submodules https://github.com/iovisor/bcc Linux francis-vm-arm64-ubuntu18vm 5.4.0-1089-azure #94~18.04.1-Ubuntu SMP Fri Aug 5 12:36:48 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux $ sudo sh -c 'apt update && apt install -qy clang-10 llvm-10 make gcc pkg-config libelf-dev libz-dev' ... $ cd bcc/libbpf-tools $ CLANG=clang-10 LLVM_STRIP=llvm-strip-10 make -j opensnoop ... BINARY opensnoop $ sudo ./opensnoop PID COMM FD ERR PATH 1672 python3 3 0 9746 opensnoop 20 0 1672 python3 3 0 1672 python3 3 0 1672 python3 -1 2 1672 python3 3 0 1 systemd 18 0 1672 python3 6 0 1672 python3 3 0 1672 python3 3 0 1672 python3 3 0 1672 python3 3 0 1672 python3 3 0 ^C As you can see, nothing is printed for the PATH while normal behavior prints the path of the opened file: $ uname -a Linux pwmachine 5.15.0-46-generic #49~20.04.1-Ubuntu SMP Thu Aug 4 19:15:44 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ sudo ./opensnoop PID COMM FD ERR PATH 2704 systemd 23 0 virtual 2704 systemd 22 0 misc 2704 systemd 23 0 fuse 2704 systemd 22 0 /sys/devices/virtual/misc/fuse/uevent 2704 systemd 22 0 /run/udev/data/c10:229 2704 systemd 22 0 /proc/2704/status 2704 systemd 22 0 /proc/2704/status 2704 systemd 22 0 /proc/2704/status ^C This bug was fixed in upstream patch [2] Sadly, this patch was not back ported, so it is not present in stable kernels. [Test plan] Follow the above instructions [Where things could go wrong] Unknown + + [Other Info] + + Original RFC at https://lists.ubuntu.com/archives/kernel- + team/2022-September/133038.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1990009 Title: Azure: Focal 5.4 kernel eBPF opensnoop does not display PATH Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: In Progress Bug description: SRU Justification [Impact] The actual kernel used on AKS arm64 (i.e. 5.4.1089) suffers from a known problem [1]. As a consequence, opensnoop does not display PATH: # Run the following from Canonical:UbuntuServer:18_04-daily-lts-arm64:18.04.202208290 $ uname -a Linux francis-vm-arm64-ubuntu18vm 5.4.0-1089-azure #94~18.04.1-Ubuntu SMP Fri Aug 5 12:36:48 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux $ lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 $ git clone --recurse-submodules https://github.com/iovisor/bcc Linux francis-vm-arm64-ubuntu18vm 5.4.0-1089-azure #94~18.04.1-Ubuntu SMP Fri Aug 5 12:36:48 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux $ sudo sh -c 'apt update && apt install -qy clang-10 llvm-10 make gcc pkg-config libelf-dev libz-dev' ... $ cd bcc/libbpf-tools $ CLANG=clang-10 LLVM_STRIP=llvm-strip-10 make -j opensnoop ... BINARY opensnoop $ sudo ./opensnoop PID COMM FD ERR PATH 1672 python3 3 0 9746 opensnoop 20 0 1672 python3 3 0 1672 python3 3 0 1672 python3 -1 2 1672 python3 3 0 1 systemd 18 0 1672 python3 6 0 1672 python3 3 0 1672 python3 3 0 1672 python3 3 0 1672 python3 3 0 1672 python3 3 0 ^C As you can see, nothing is printed for the PATH while normal behavior prints the path of the opened file: $ uname -a Linux pwmachine 5.15.0-46-generic #49~20.04.1-Ubuntu SMP Thu Aug 4 19:15:44 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ sudo ./opensnoop PID COMM FD ERR PATH 2704 systemd 23 0 virtual 2704 systemd 22 0 misc 2704 systemd 23 0 fuse 2704 systemd 22 0 /sys/devices/virtual/misc/fuse/uevent 2704 systemd 22 0 /run/udev/data/c10:229 2704 systemd 22 0 /proc/2704/status 2704 systemd 22 0 /proc/2704/status 2704 systemd 22 0 /proc/2704/status ^C This bug was fixed in upstream patch [2] Sadly, this patch was not back ported, so it is not present in stable kernels. [Test plan] Follow the above instructions [Where things could go wrong] Unknown [Other Info] Original RFC at https://lists.ubuntu.com/archives/kernel- team/2022-September/133038.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1990009/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all
Same here, I tried almost everything possible searching through the web. No sound, might be issue with Cirrus amps driver issue? A quick work around or fix would be appreciated. :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1981433 Title: [Asus Zenbook UX3402ZA] Sound doesn't work at all Status in linux package in Ubuntu: Confirmed Bug description: Sound/speakers don't work at all on Asus Zenbook 14 OLED and other similar models with Realtek ALC294. No solution works. Audio is not muted, tried adding snd-hda arguments - no dice. This has been reported numerous times, when will a fix finally be rolled out?! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1730 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jul 12 13:57:05 2022 InstallationDate: Installed on 2022-07-12 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=40c924aa-99ad-4770-a66d-33d3359f6053 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3402ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3402ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UX3402ZA_UX3402ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990009] [NEW] Azure: Focal 5.4 kernel eBPF opensnoop does not display PATH
Public bug reported: SRU Justification [Impact] The actual kernel used on AKS arm64 (i.e. 5.4.1089) suffers from a known problem [1]. As a consequence, opensnoop does not display PATH: # Run the following from Canonical:UbuntuServer:18_04-daily-lts-arm64:18.04.202208290 $ uname -a Linux francis-vm-arm64-ubuntu18vm 5.4.0-1089-azure #94~18.04.1-Ubuntu SMP Fri Aug 5 12:36:48 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux $ lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 $ git clone --recurse-submodules https://github.com/iovisor/bcc Linux francis-vm-arm64-ubuntu18vm 5.4.0-1089-azure #94~18.04.1-Ubuntu SMP Fri Aug 5 12:36:48 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux $ sudo sh -c 'apt update && apt install -qy clang-10 llvm-10 make gcc pkg-config libelf-dev libz-dev' ... $ cd bcc/libbpf-tools $ CLANG=clang-10 LLVM_STRIP=llvm-strip-10 make -j opensnoop ... BINARY opensnoop $ sudo ./opensnoop PID COMM FD ERR PATH 1672 python3 3 0 9746 opensnoop 20 0 1672 python3 3 0 1672 python3 3 0 1672 python3 -1 2 1672 python3 3 0 1 systemd 18 0 1672 python3 6 0 1672 python3 3 0 1672 python3 3 0 1672 python3 3 0 1672 python3 3 0 1672 python3 3 0 ^C As you can see, nothing is printed for the PATH while normal behavior prints the path of the opened file: $ uname -a Linux pwmachine 5.15.0-46-generic #49~20.04.1-Ubuntu SMP Thu Aug 4 19:15:44 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ sudo ./opensnoop PID COMM FD ERR PATH 2704 systemd 23 0 virtual 2704 systemd 22 0 misc 2704 systemd 23 0 fuse 2704 systemd 22 0 /sys/devices/virtual/misc/fuse/uevent 2704 systemd 22 0 /run/udev/data/c10:229 2704 systemd 22 0 /proc/2704/status 2704 systemd 22 0 /proc/2704/status 2704 systemd 22 0 /proc/2704/status ^C This bug was fixed in upstream patch [2] Sadly, this patch was not back ported, so it is not present in stable kernels. [Test plan] Follow the above instructions [Where things could go wrong] Unknown ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux-azure (Ubuntu Focal) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Also affects: linux-azure (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu) Status: New => Fix Released ** Changed in: linux-azure (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1990009 Title: Azure: Focal 5.4 kernel eBPF opensnoop does not display PATH Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: In Progress Bug description: SRU Justification [Impact] The actual kernel used on AKS arm64 (i.e. 5.4.1089) suffers from a known problem [1]. As a consequence, opensnoop does not display PATH: # Run the following from Canonical:UbuntuServer:18_04-daily-lts-arm64:18.04.202208290 $ uname -a Linux francis-vm-arm64-ubuntu18vm 5.4.0-1089-azure #94~18.04.1-Ubuntu SMP Fri Aug 5 12:36:48 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux $ lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 $ git clone --recurse-submodules https://github.com/iovisor/bcc Linux francis-vm-arm64-ubuntu18vm 5.4.0-1089-azure #94~18.04.1-Ubuntu SMP Fri Aug 5 12:36:48 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux $ sudo sh -c 'apt update && apt install -qy clang-10 llvm-10 make gcc pkg-config libelf-dev libz-dev' ... $ cd bcc/libbpf-tools $ CLANG=clang-10 LLVM_STRIP=llvm-strip-10 make -j opensnoop ... BINARY opensnoop $ sudo ./opensnoop PID COMM FD ERR PATH 1672 python3 3 0 9746 opensnoop 20 0 1672 python3 3 0 1672 python3 3 0 1672 python3 -1 2 1672 python3 3 0 1 systemd 18 0 1672 python3 6 0 1672 python3 3 0 1672 python3 3 0 1672 python3 3 0 1672 python3 3 0 1672 python3 3 0 ^C As you can see, nothing is printed for the PATH while normal behavior prints the path of the opened file: $ uname -a Linux pwmachine 5.15.0-46-generic #49~20.04.1-Ubuntu SMP Thu Aug 4 19:15:44 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ sudo ./opensnoop PID COMM FD ERR PATH 2704 systemd 23 0 virtual 2704 systemd 22 0 misc 2704 systemd 23 0 fuse 2704 systemd 22 0 /sys/devices/virtual/misc/fuse/uevent 2704 systemd 22 0 /run/udev/data/c10:229 2704 systemd 22 0 /proc/2704/status 2704 systemd 22 0 /proc/2704/status 2704 systemd 22 0 /proc/2704/status ^C This bug was fixed in upstream patch [2] Sadly, this patch was not back ported, so it is not present in stable kernels. [Test plan] Follow the above instructions [Where things could go wrong] Unknown To manage notifications about this bug go
[Kernel-packages] [Bug 1989991] Re: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse
I marked this bug as confirmed because it was also reported in bug 1947464. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989991 Title: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.1 LTS Same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947464 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 Package: linux (not installed) Tags: jammy Uname: Linux 5.18.10-76051810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joshua 4264 F wireplumber /dev/snd/controlC2: joshua 4264 F wireplumber /dev/snd/controlC0: joshua 4264 F wireplumber /dev/snd/seq:joshua 4261 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: System76 Thelio Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/tvg-jammy ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: System76 dmi.bios.version: F61a Z5 dmi.board.asset.tag: Default string dmi.board.name: Thelio dmi.board.vendor: System76 dmi.board.version: thelio-r1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: System76 dmi.chassis.version: thelio-r1 dmi.modalias: dmi:bvnSystem76:bvrF61aZ5:bd04/12/2021:br5.17:svnSystem76:pnThelio:pvrthelio-r1:rvnSystem76:rnThelio:rvrthelio-r1:cvnSystem76:ct3:cvrthelio-r1:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Thelio dmi.product.sku: Default string dmi.product.version: thelio-r1 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989991] Re: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse
/proc/bus/input/devices output is the same for both 5.15.0-47 and 5.18.10 ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989991 Title: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.1 LTS Same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947464 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 Package: linux (not installed) Tags: jammy Uname: Linux 5.18.10-76051810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joshua 4264 F wireplumber /dev/snd/controlC2: joshua 4264 F wireplumber /dev/snd/controlC0: joshua 4264 F wireplumber /dev/snd/seq:joshua 4261 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: System76 Thelio Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/tvg-jammy ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: System76 dmi.bios.version: F61a Z5 dmi.board.asset.tag: Default string dmi.board.name: Thelio dmi.board.vendor: System76 dmi.board.version: thelio-r1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: System76 dmi.chassis.version: thelio-r1 dmi.modalias: dmi:bvnSystem76:bvrF61aZ5:bd04/12/2021:br5.17:svnSystem76:pnThelio:pvrthelio-r1:rvnSystem76:rnThelio:rvrthelio-r1:cvnSystem76:ct3:cvrthelio-r1:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Thelio dmi.product.sku: Default string dmi.product.version: thelio-r1 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989991] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1989991/+attachment/5616589/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989991 Title: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.1 LTS Same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947464 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 Package: linux (not installed) Tags: jammy Uname: Linux 5.18.10-76051810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joshua 4264 F wireplumber /dev/snd/controlC2: joshua 4264 F wireplumber /dev/snd/controlC0: joshua 4264 F wireplumber /dev/snd/seq:joshua 4261 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: System76 Thelio Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/tvg-jammy ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: System76 dmi.bios.version: F61a Z5 dmi.board.asset.tag: Default string dmi.board.name: Thelio dmi.board.vendor: System76 dmi.board.version: thelio-r1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: System76 dmi.chassis.version: thelio-r1 dmi.modalias: dmi:bvnSystem76:bvrF61aZ5:bd04/12/2021:br5.17:svnSystem76:pnThelio:pvrthelio-r1:rvnSystem76:rnThelio:rvrthelio-r1:cvnSystem76:ct3:cvrthelio-r1:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Thelio dmi.product.sku: Default string dmi.product.version: thelio-r1 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989991] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1989991/+attachment/5616590/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989991 Title: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.1 LTS Same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947464 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 Package: linux (not installed) Tags: jammy Uname: Linux 5.18.10-76051810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joshua 4264 F wireplumber /dev/snd/controlC2: joshua 4264 F wireplumber /dev/snd/controlC0: joshua 4264 F wireplumber /dev/snd/seq:joshua 4261 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: System76 Thelio Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/tvg-jammy ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: System76 dmi.bios.version: F61a Z5 dmi.board.asset.tag: Default string dmi.board.name: Thelio dmi.board.vendor: System76 dmi.board.version: thelio-r1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: System76 dmi.chassis.version: thelio-r1 dmi.modalias: dmi:bvnSystem76:bvrF61aZ5:bd04/12/2021:br5.17:svnSystem76:pnThelio:pvrthelio-r1:rvnSystem76:rnThelio:rvrthelio-r1:cvnSystem76:ct3:cvrthelio-r1:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Thelio dmi.product.sku: Default string dmi.product.version: thelio-r1 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989991] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1989991/+attachment/5616591/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989991 Title: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.1 LTS Same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947464 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 Package: linux (not installed) Tags: jammy Uname: Linux 5.18.10-76051810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joshua 4264 F wireplumber /dev/snd/controlC2: joshua 4264 F wireplumber /dev/snd/controlC0: joshua 4264 F wireplumber /dev/snd/seq:joshua 4261 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: System76 Thelio Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/tvg-jammy ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: System76 dmi.bios.version: F61a Z5 dmi.board.asset.tag: Default string dmi.board.name: Thelio dmi.board.vendor: System76 dmi.board.version: thelio-r1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: System76 dmi.chassis.version: thelio-r1 dmi.modalias: dmi:bvnSystem76:bvrF61aZ5:bd04/12/2021:br5.17:svnSystem76:pnThelio:pvrthelio-r1:rvnSystem76:rnThelio:rvrthelio-r1:cvnSystem76:ct3:cvrthelio-r1:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Thelio dmi.product.sku: Default string dmi.product.version: thelio-r1 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989991] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1989991/+attachment/5616588/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989991 Title: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.1 LTS Same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947464 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 Package: linux (not installed) Tags: jammy Uname: Linux 5.18.10-76051810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joshua 4264 F wireplumber /dev/snd/controlC2: joshua 4264 F wireplumber /dev/snd/controlC0: joshua 4264 F wireplumber /dev/snd/seq:joshua 4261 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: System76 Thelio Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/tvg-jammy ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: System76 dmi.bios.version: F61a Z5 dmi.board.asset.tag: Default string dmi.board.name: Thelio dmi.board.vendor: System76 dmi.board.version: thelio-r1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: System76 dmi.chassis.version: thelio-r1 dmi.modalias: dmi:bvnSystem76:bvrF61aZ5:bd04/12/2021:br5.17:svnSystem76:pnThelio:pvrthelio-r1:rvnSystem76:rnThelio:rvrthelio-r1:cvnSystem76:ct3:cvrthelio-r1:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Thelio dmi.product.sku: Default string dmi.product.version: thelio-r1 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989991] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1989991/+attachment/5616597/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989991 Title: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.1 LTS Same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947464 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 Package: linux (not installed) Tags: jammy Uname: Linux 5.18.10-76051810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joshua 4264 F wireplumber /dev/snd/controlC2: joshua 4264 F wireplumber /dev/snd/controlC0: joshua 4264 F wireplumber /dev/snd/seq:joshua 4261 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: System76 Thelio Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/tvg-jammy ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: System76 dmi.bios.version: F61a Z5 dmi.board.asset.tag: Default string dmi.board.name: Thelio dmi.board.vendor: System76 dmi.board.version: thelio-r1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: System76 dmi.chassis.version: thelio-r1 dmi.modalias: dmi:bvnSystem76:bvrF61aZ5:bd04/12/2021:br5.17:svnSystem76:pnThelio:pvrthelio-r1:rvnSystem76:rnThelio:rvrthelio-r1:cvnSystem76:ct3:cvrthelio-r1:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Thelio dmi.product.sku: Default string dmi.product.version: thelio-r1 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989991] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1989991/+attachment/5616598/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989991 Title: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.1 LTS Same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947464 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 Package: linux (not installed) Tags: jammy Uname: Linux 5.18.10-76051810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joshua 4264 F wireplumber /dev/snd/controlC2: joshua 4264 F wireplumber /dev/snd/controlC0: joshua 4264 F wireplumber /dev/snd/seq:joshua 4261 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: System76 Thelio Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/tvg-jammy ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: System76 dmi.bios.version: F61a Z5 dmi.board.asset.tag: Default string dmi.board.name: Thelio dmi.board.vendor: System76 dmi.board.version: thelio-r1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: System76 dmi.chassis.version: thelio-r1 dmi.modalias: dmi:bvnSystem76:bvrF61aZ5:bd04/12/2021:br5.17:svnSystem76:pnThelio:pvrthelio-r1:rvnSystem76:rnThelio:rvrthelio-r1:cvnSystem76:ct3:cvrthelio-r1:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Thelio dmi.product.sku: Default string dmi.product.version: thelio-r1 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989991] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1989991/+attachment/5616595/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989991 Title: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.1 LTS Same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947464 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 Package: linux (not installed) Tags: jammy Uname: Linux 5.18.10-76051810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joshua 4264 F wireplumber /dev/snd/controlC2: joshua 4264 F wireplumber /dev/snd/controlC0: joshua 4264 F wireplumber /dev/snd/seq:joshua 4261 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: System76 Thelio Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/tvg-jammy ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: System76 dmi.bios.version: F61a Z5 dmi.board.asset.tag: Default string dmi.board.name: Thelio dmi.board.vendor: System76 dmi.board.version: thelio-r1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: System76 dmi.chassis.version: thelio-r1 dmi.modalias: dmi:bvnSystem76:bvrF61aZ5:bd04/12/2021:br5.17:svnSystem76:pnThelio:pvrthelio-r1:rvnSystem76:rnThelio:rvrthelio-r1:cvnSystem76:ct3:cvrthelio-r1:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Thelio dmi.product.sku: Default string dmi.product.version: thelio-r1 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989991] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1989991/+attachment/5616596/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989991 Title: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.1 LTS Same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947464 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 Package: linux (not installed) Tags: jammy Uname: Linux 5.18.10-76051810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joshua 4264 F wireplumber /dev/snd/controlC2: joshua 4264 F wireplumber /dev/snd/controlC0: joshua 4264 F wireplumber /dev/snd/seq:joshua 4261 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: System76 Thelio Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/tvg-jammy ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: System76 dmi.bios.version: F61a Z5 dmi.board.asset.tag: Default string dmi.board.name: Thelio dmi.board.vendor: System76 dmi.board.version: thelio-r1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: System76 dmi.chassis.version: thelio-r1 dmi.modalias: dmi:bvnSystem76:bvrF61aZ5:bd04/12/2021:br5.17:svnSystem76:pnThelio:pvrthelio-r1:rvnSystem76:rnThelio:rvrthelio-r1:cvnSystem76:ct3:cvrthelio-r1:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Thelio dmi.product.sku: Default string dmi.product.version: thelio-r1 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989991] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1989991/+attachment/5616593/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989991 Title: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.1 LTS Same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947464 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 Package: linux (not installed) Tags: jammy Uname: Linux 5.18.10-76051810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joshua 4264 F wireplumber /dev/snd/controlC2: joshua 4264 F wireplumber /dev/snd/controlC0: joshua 4264 F wireplumber /dev/snd/seq:joshua 4261 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: System76 Thelio Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/tvg-jammy ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: System76 dmi.bios.version: F61a Z5 dmi.board.asset.tag: Default string dmi.board.name: Thelio dmi.board.vendor: System76 dmi.board.version: thelio-r1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: System76 dmi.chassis.version: thelio-r1 dmi.modalias: dmi:bvnSystem76:bvrF61aZ5:bd04/12/2021:br5.17:svnSystem76:pnThelio:pvrthelio-r1:rvnSystem76:rnThelio:rvrthelio-r1:cvnSystem76:ct3:cvrthelio-r1:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Thelio dmi.product.sku: Default string dmi.product.version: thelio-r1 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989991] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1989991/+attachment/5616592/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989991 Title: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.1 LTS Same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947464 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 Package: linux (not installed) Tags: jammy Uname: Linux 5.18.10-76051810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joshua 4264 F wireplumber /dev/snd/controlC2: joshua 4264 F wireplumber /dev/snd/controlC0: joshua 4264 F wireplumber /dev/snd/seq:joshua 4261 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: System76 Thelio Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/tvg-jammy ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: System76 dmi.bios.version: F61a Z5 dmi.board.asset.tag: Default string dmi.board.name: Thelio dmi.board.vendor: System76 dmi.board.version: thelio-r1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: System76 dmi.chassis.version: thelio-r1 dmi.modalias: dmi:bvnSystem76:bvrF61aZ5:bd04/12/2021:br5.17:svnSystem76:pnThelio:pvrthelio-r1:rvnSystem76:rnThelio:rvrthelio-r1:cvnSystem76:ct3:cvrthelio-r1:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Thelio dmi.product.sku: Default string dmi.product.version: thelio-r1 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989991] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1989991/+attachment/5616594/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989991 Title: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.1 LTS Same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947464 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 Package: linux (not installed) Tags: jammy Uname: Linux 5.18.10-76051810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joshua 4264 F wireplumber /dev/snd/controlC2: joshua 4264 F wireplumber /dev/snd/controlC0: joshua 4264 F wireplumber /dev/snd/seq:joshua 4261 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: System76 Thelio Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/tvg-jammy ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: System76 dmi.bios.version: F61a Z5 dmi.board.asset.tag: Default string dmi.board.name: Thelio dmi.board.vendor: System76 dmi.board.version: thelio-r1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: System76 dmi.chassis.version: thelio-r1 dmi.modalias: dmi:bvnSystem76:bvrF61aZ5:bd04/12/2021:br5.17:svnSystem76:pnThelio:pvrthelio-r1:rvnSystem76:rnThelio:rvrthelio-r1:cvnSystem76:ct3:cvrthelio-r1:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Thelio dmi.product.sku: Default string dmi.product.version: thelio-r1 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989991] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1989991/+attachment/5616585/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989991 Title: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.1 LTS Same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947464 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 Package: linux (not installed) Tags: jammy Uname: Linux 5.18.10-76051810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joshua 4264 F wireplumber /dev/snd/controlC2: joshua 4264 F wireplumber /dev/snd/controlC0: joshua 4264 F wireplumber /dev/snd/seq:joshua 4261 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: System76 Thelio Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/tvg-jammy ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: System76 dmi.bios.version: F61a Z5 dmi.board.asset.tag: Default string dmi.board.name: Thelio dmi.board.vendor: System76 dmi.board.version: thelio-r1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: System76 dmi.chassis.version: thelio-r1 dmi.modalias: dmi:bvnSystem76:bvrF61aZ5:bd04/12/2021:br5.17:svnSystem76:pnThelio:pvrthelio-r1:rvnSystem76:rnThelio:rvrthelio-r1:cvnSystem76:ct3:cvrthelio-r1:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Thelio dmi.product.sku: Default string dmi.product.version: thelio-r1 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989991] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1989991/+attachment/5616587/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989991 Title: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.1 LTS Same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947464 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 Package: linux (not installed) Tags: jammy Uname: Linux 5.18.10-76051810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joshua 4264 F wireplumber /dev/snd/controlC2: joshua 4264 F wireplumber /dev/snd/controlC0: joshua 4264 F wireplumber /dev/snd/seq:joshua 4261 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: System76 Thelio Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/tvg-jammy ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: System76 dmi.bios.version: F61a Z5 dmi.board.asset.tag: Default string dmi.board.name: Thelio dmi.board.vendor: System76 dmi.board.version: thelio-r1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: System76 dmi.chassis.version: thelio-r1 dmi.modalias: dmi:bvnSystem76:bvrF61aZ5:bd04/12/2021:br5.17:svnSystem76:pnThelio:pvrthelio-r1:rvnSystem76:rnThelio:rvrthelio-r1:cvnSystem76:ct3:cvrthelio-r1:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Thelio dmi.product.sku: Default string dmi.product.version: thelio-r1 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989991] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1989991/+attachment/5616586/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989991 Title: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.1 LTS Same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947464 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 Package: linux (not installed) Tags: jammy Uname: Linux 5.18.10-76051810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joshua 4264 F wireplumber /dev/snd/controlC2: joshua 4264 F wireplumber /dev/snd/controlC0: joshua 4264 F wireplumber /dev/snd/seq:joshua 4261 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: System76 Thelio Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/tvg-jammy ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: System76 dmi.bios.version: F61a Z5 dmi.board.asset.tag: Default string dmi.board.name: Thelio dmi.board.vendor: System76 dmi.board.version: thelio-r1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: System76 dmi.chassis.version: thelio-r1 dmi.modalias: dmi:bvnSystem76:bvrF61aZ5:bd04/12/2021:br5.17:svnSystem76:pnThelio:pvrthelio-r1:rvnSystem76:rnThelio:rvrthelio-r1:cvnSystem76:ct3:cvrthelio-r1:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Thelio dmi.product.sku: Default string dmi.product.version: thelio-r1 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989991] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1989991/+attachment/5616584/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989991 Title: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.1 LTS Same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947464 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 Package: linux (not installed) Tags: jammy Uname: Linux 5.18.10-76051810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joshua 4264 F wireplumber /dev/snd/controlC2: joshua 4264 F wireplumber /dev/snd/controlC0: joshua 4264 F wireplumber /dev/snd/seq:joshua 4261 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: System76 Thelio Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/tvg-jammy ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: System76 dmi.bios.version: F61a Z5 dmi.board.asset.tag: Default string dmi.board.name: Thelio dmi.board.vendor: System76 dmi.board.version: thelio-r1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: System76 dmi.chassis.version: thelio-r1 dmi.modalias: dmi:bvnSystem76:bvrF61aZ5:bd04/12/2021:br5.17:svnSystem76:pnThelio:pvrthelio-r1:rvnSystem76:rnThelio:rvrthelio-r1:cvnSystem76:ct3:cvrthelio-r1:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Thelio dmi.product.sku: Default string dmi.product.version: thelio-r1 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989991] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1989991/+attachment/5616583/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989991 Title: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.1 LTS Same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947464 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 Package: linux (not installed) Tags: jammy Uname: Linux 5.18.10-76051810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joshua 4264 F wireplumber /dev/snd/controlC2: joshua 4264 F wireplumber /dev/snd/controlC0: joshua 4264 F wireplumber /dev/snd/seq:joshua 4261 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: System76 Thelio Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/tvg-jammy ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: System76 dmi.bios.version: F61a Z5 dmi.board.asset.tag: Default string dmi.board.name: Thelio dmi.board.vendor: System76 dmi.board.version: thelio-r1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: System76 dmi.chassis.version: thelio-r1 dmi.modalias: dmi:bvnSystem76:bvrF61aZ5:bd04/12/2021:br5.17:svnSystem76:pnThelio:pvrthelio-r1:rvnSystem76:rnThelio:rvrthelio-r1:cvnSystem76:ct3:cvrthelio-r1:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Thelio dmi.product.sku: Default string dmi.product.version: thelio-r1 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989991] Re: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse
apport information ** Description changed: Ubuntu 22.04.1 LTS Same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947464 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 Package: linux (not installed) Tags: jammy Uname: Linux 5.18.10-76051810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: joshua 4264 F wireplumber + /dev/snd/controlC2: joshua 4264 F wireplumber + /dev/snd/controlC0: joshua 4264 F wireplumber + /dev/snd/seq:joshua 4261 F pipewire + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + MachineType: System76 Thelio + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/tvg-jammy ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-5.15.0-47-generic N/A + linux-backports-modules-5.15.0-47-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.5 + Tags: jammy + Uname: Linux 5.15.0-47-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 04/12/2021 + dmi.bios.release: 5.17 + dmi.bios.vendor: System76 + dmi.bios.version: F61a Z5 + dmi.board.asset.tag: Default string + dmi.board.name: Thelio + dmi.board.vendor: System76 + dmi.board.version: thelio-r1 + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 3 + dmi.chassis.vendor: System76 + dmi.chassis.version: thelio-r1 + dmi.modalias: dmi:bvnSystem76:bvrF61aZ5:bd04/12/2021:br5.17:svnSystem76:pnThelio:pvrthelio-r1:rvnSystem76:rnThelio:rvrthelio-r1:cvnSystem76:ct3:cvrthelio-r1:skuDefaultstring: + dmi.product.family: Default string + dmi.product.name: Thelio + dmi.product.sku: Default string + dmi.product.version: thelio-r1 + dmi.sys.vendor: System76 ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1989991/+attachment/5616580/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989991 Title: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.1 LTS Same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947464 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 Package: linux (not installed) Tags: jammy Uname: Linux 5.18.10-76051810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joshua 4264 F wireplumber /dev/snd/controlC2: joshua 4264 F wireplumber /dev/snd/controlC0: joshua 4264 F wireplumber /dev/snd/seq:joshua 4261 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: System76 Thelio Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/tvg-jammy ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: System76
[Kernel-packages] [Bug 1989991] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1989991/+attachment/5616581/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989991 Title: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.1 LTS Same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947464 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 Package: linux (not installed) Tags: jammy Uname: Linux 5.18.10-76051810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joshua 4264 F wireplumber /dev/snd/controlC2: joshua 4264 F wireplumber /dev/snd/controlC0: joshua 4264 F wireplumber /dev/snd/seq:joshua 4261 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: System76 Thelio Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/tvg-jammy ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: System76 dmi.bios.version: F61a Z5 dmi.board.asset.tag: Default string dmi.board.name: Thelio dmi.board.vendor: System76 dmi.board.version: thelio-r1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: System76 dmi.chassis.version: thelio-r1 dmi.modalias: dmi:bvnSystem76:bvrF61aZ5:bd04/12/2021:br5.17:svnSystem76:pnThelio:pvrthelio-r1:rvnSystem76:rnThelio:rvrthelio-r1:cvnSystem76:ct3:cvrthelio-r1:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Thelio dmi.product.sku: Default string dmi.product.version: thelio-r1 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989991] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1989991/+attachment/5616582/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989991 Title: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.04.1 LTS Same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947464 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 Package: linux (not installed) Tags: jammy Uname: Linux 5.18.10-76051810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joshua 4264 F wireplumber /dev/snd/controlC2: joshua 4264 F wireplumber /dev/snd/controlC0: joshua 4264 F wireplumber /dev/snd/seq:joshua 4261 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 MachineType: System76 Thelio Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=/dev/mapper/tvg-jammy ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-47-generic N/A linux-backports-modules-5.15.0-47-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-47-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: System76 dmi.bios.version: F61a Z5 dmi.board.asset.tag: Default string dmi.board.name: Thelio dmi.board.vendor: System76 dmi.board.version: thelio-r1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: System76 dmi.chassis.version: thelio-r1 dmi.modalias: dmi:bvnSystem76:bvrF61aZ5:bd04/12/2021:br5.17:svnSystem76:pnThelio:pvrthelio-r1:rvnSystem76:rnThelio:rvrthelio-r1:cvnSystem76:ct3:cvrthelio-r1:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Thelio dmi.product.sku: Default string dmi.product.version: thelio-r1 dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989991] Re: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse
** Attachment added: "xinput" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989991/+attachment/5616544/+files/xinput -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989991 Title: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 22.04.1 LTS Same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947464 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 Package: linux (not installed) Tags: jammy Uname: Linux 5.18.10-76051810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989991] Re: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse
** Attachment added: "xorg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989991/+attachment/5616545/+files/xorg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989991 Title: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 22.04.1 LTS Same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947464 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 Package: linux (not installed) Tags: jammy Uname: Linux 5.18.10-76051810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989991] Re: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse
** Attachment added: "devices" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989991/+attachment/5616543/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989991 Title: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 22.04.1 LTS Same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947464 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 Package: linux (not installed) Tags: jammy Uname: Linux 5.18.10-76051810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989991] 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 1989991 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/1989991 Title: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 22.04.1 LTS Same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947464 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 Package: linux (not installed) Tags: jammy Uname: Linux 5.18.10-76051810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989992] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989992 Title: i915 traceback when connecting display via USB-C Status in linux package in Ubuntu: Confirmed Bug description: When connecting display via USB-C, I get the following traceback in dmesg. The display still work, though. [ 62.598637] usb 3-5: new full-speed USB device number 11 using xhci_hcd [ 62.761540] usb 3-5: not running at top speed; connect to a high speed hub [ 62.766478] usb 3-5: New USB device found, idVendor=2109, idProduct=0103, bcdDevice= 3.c3 [ 62.766487] usb 3-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 62.766490] usb 3-5: Product: USB 2.0 BILLBOARD [ 62.766493] usb 3-5: Manufacturer: VLI Inc. [ 62.766494] usb 3-5: SerialNumber: 0001 [ 62.927194] ucsi_acpi USBC000:00: ucsi_handle_connector_change: GET_CONNECTOR_STATUS failed (-110) [ 63.100051] ucsi_acpi USBC000:00: UCSI_GET_PDOS returned 0 bytes [ 63.463027] Registered IR keymap rc-cec [ 63.463092] rc rc0: DP-1 as /devices/pci:00/:00:02.0/rc/rc0 [ 63.463127] input: DP-1 as /devices/pci:00/:00:02.0/rc/rc0/input27 [ 65.013853] i915 :00:02.0: [drm] *ERROR* [CRTC:80:pipe A] mismatch in has_psr (expected yes, found no) [ 65.013859] i915 :00:02.0: [drm] *ERROR* [CRTC:80:pipe A] mismatch in has_psr2 (expected yes, found no) [ 65.013860] i915 :00:02.0: [drm] *ERROR* [CRTC:80:pipe A] mismatch in enable_psr2_sel_fetch (expected yes, found no) [ 65.013862] [ cut here ] [ 65.013862] pipe state doesn't match! [ 65.013913] WARNING: CPU: 4 PID: 3728 at drivers/gpu/drm/i915/display/intel_display.c:6682 verify_crtc_state+0x47d/0x540 [i915] [ 65.014021] Modules linked in: typec_displayport binfmt_misc veth nft_masq zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) ccm vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xfrm_user xfrm_algo xt_addrtype iptable_nat bpfilter rfcomm cmac algif_hash algif_skcipher af_alg xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables snd_seq_dummy snd_hrtimer nfnetlink bnep nls_iso8859_1 snd_ctl_led snd_soc_skl_hda_dsp snd_soc_intel_hda_dsp_common snd_soc_hdac_hdmi snd_sof_probes snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_soc_dmic snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core [ 65.014049] snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel iwlmvm snd_intel_dspcfg snd_intel_sdw_acpi snd_usb_audio snd_hda_codec intel_tcc_cooling snd_usbmidi_lib snd_hda_core mac80211 snd_hwdep snd_pcm x86_pkg_temp_thermal intel_powerclamp snd_seq_midi libarc4 snd_seq_midi_event coretemp uvcvideo snd_rawmidi btusb btrtl videobuf2_vmalloc btbcm videobuf2_memops kvm_intel thinkpad_acpi snd_seq btintel videobuf2_v4l2 mei_pxp mei_hdcp btmtk videobuf2_common snd_seq_device nvram kvm iwlwifi rapl bluetooth videodev ledtrig_audio snd_timer pmt_telemetry spi_nor iwlmei think_lmi intel_cstate serio_raw pmt_class intel_rapl_msr platform_profile input_leds int3403_thermal ecdh_generic snd firmware_attributes_class wmi_bmof mc
[Kernel-packages] [Bug 1989992] [NEW] i915 traceback when connecting display via USB-C
Public bug reported: When connecting display via USB-C, I get the following traceback in dmesg. The display still work, though. [ 62.598637] usb 3-5: new full-speed USB device number 11 using xhci_hcd [ 62.761540] usb 3-5: not running at top speed; connect to a high speed hub [ 62.766478] usb 3-5: New USB device found, idVendor=2109, idProduct=0103, bcdDevice= 3.c3 [ 62.766487] usb 3-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 62.766490] usb 3-5: Product: USB 2.0 BILLBOARD [ 62.766493] usb 3-5: Manufacturer: VLI Inc. [ 62.766494] usb 3-5: SerialNumber: 0001 [ 62.927194] ucsi_acpi USBC000:00: ucsi_handle_connector_change: GET_CONNECTOR_STATUS failed (-110) [ 63.100051] ucsi_acpi USBC000:00: UCSI_GET_PDOS returned 0 bytes [ 63.463027] Registered IR keymap rc-cec [ 63.463092] rc rc0: DP-1 as /devices/pci:00/:00:02.0/rc/rc0 [ 63.463127] input: DP-1 as /devices/pci:00/:00:02.0/rc/rc0/input27 [ 65.013853] i915 :00:02.0: [drm] *ERROR* [CRTC:80:pipe A] mismatch in has_psr (expected yes, found no) [ 65.013859] i915 :00:02.0: [drm] *ERROR* [CRTC:80:pipe A] mismatch in has_psr2 (expected yes, found no) [ 65.013860] i915 :00:02.0: [drm] *ERROR* [CRTC:80:pipe A] mismatch in enable_psr2_sel_fetch (expected yes, found no) [ 65.013862] [ cut here ] [ 65.013862] pipe state doesn't match! [ 65.013913] WARNING: CPU: 4 PID: 3728 at drivers/gpu/drm/i915/display/intel_display.c:6682 verify_crtc_state+0x47d/0x540 [i915] [ 65.014021] Modules linked in: typec_displayport binfmt_misc veth nft_masq zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) ccm vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xfrm_user xfrm_algo xt_addrtype iptable_nat bpfilter rfcomm cmac algif_hash algif_skcipher af_alg xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables snd_seq_dummy snd_hrtimer nfnetlink bnep nls_iso8859_1 snd_ctl_led snd_soc_skl_hda_dsp snd_soc_intel_hda_dsp_common snd_soc_hdac_hdmi snd_sof_probes snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_soc_dmic snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core [ 65.014049] snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel iwlmvm snd_intel_dspcfg snd_intel_sdw_acpi snd_usb_audio snd_hda_codec intel_tcc_cooling snd_usbmidi_lib snd_hda_core mac80211 snd_hwdep snd_pcm x86_pkg_temp_thermal intel_powerclamp snd_seq_midi libarc4 snd_seq_midi_event coretemp uvcvideo snd_rawmidi btusb btrtl videobuf2_vmalloc btbcm videobuf2_memops kvm_intel thinkpad_acpi snd_seq btintel videobuf2_v4l2 mei_pxp mei_hdcp btmtk videobuf2_common snd_seq_device nvram kvm iwlwifi rapl bluetooth videodev ledtrig_audio snd_timer pmt_telemetry spi_nor iwlmei think_lmi intel_cstate serio_raw pmt_class intel_rapl_msr platform_profile input_leds int3403_thermal ecdh_generic snd firmware_attributes_class wmi_bmof mc mtd joydev ecc hid_multitouch cfg80211 soundcore mei_me mei nxp_nci_i2c nxp_nci nci nfc intel_hid mac_hid sparse_keymap processor_thermal_device_pci acpi_pad ucsi_acpi typec_ucsi processor_thermal_device int3400_thermal processor_thermal_rfim typec acpi_thermal_rel [ 65.014079] processor_thermal_mbox acpi_tad processor_thermal_rapl intel_vsec intel_rapl_common int340x_thermal_zone igen6_edac
[Kernel-packages] [Bug 1989991] [NEW] Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse
Public bug reported: Ubuntu 22.04.1 LTS Same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947464 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 Package: linux (not installed) Tags: jammy Uname: Linux 5.18.10-76051810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected jammy ** Tags added: apport-collected jammy ** Description changed: Ubuntu 22.04.1 LTS Same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947464 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + Package: linux (not installed) + Tags: jammy + Uname: Linux 5.18.10-76051810-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989991 Title: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse Status in linux package in Ubuntu: New Bug description: Ubuntu 22.04.1 LTS Same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947464 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 Package: linux (not installed) Tags: jammy Uname: Linux 5.18.10-76051810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to jammy on 2022-04-23 (145 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989991/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989990] [NEW] Ubuntu 22.04 - NVMe TCP - Host fails to reconnect to target after link down/link up sequence
Private bug reported: Ubuntu 22.04 host fails to reconnect successfully to the NVMe TCP target after link down event if the number of queues have changed post link down. Following upstream patch set helps address the issue. 1. nvmet: Expose max queues to configfs https://git.infradead.org/nvme.git/commit/2c4282742d049e2a5ab874e2b359a2421b9377c2 2. nvme-tcp: Handle number of queue changes https://git.infradead.org/nvme.git/commit/516204e486a19d03962c2757ef49782e6c1cacf4 3. nvme-rdma: Handle number of queue changes https://git.infradead.org/nvme.git/commit/e800278c1dc97518eab1970f8f58a5aad52b0f86 The patch in Point 2 above helps address the failure to reconnect in NVMe TCP scenario. Also, following patch addresses error code parsing issue in the reconnect sequence. nvme-fabrics: parse nvme connect Linux error codes https://git.infradead.org/nvme.git/commit/ec9e96b5230148294c7abcaf3a4c592d3720b62d ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989990 Title: Ubuntu 22.04 - NVMe TCP - Host fails to reconnect to target after link down/link up sequence Status in linux package in Ubuntu: New Bug description: Ubuntu 22.04 host fails to reconnect successfully to the NVMe TCP target after link down event if the number of queues have changed post link down. Following upstream patch set helps address the issue. 1. nvmet: Expose max queues to configfs https://git.infradead.org/nvme.git/commit/2c4282742d049e2a5ab874e2b359a2421b9377c2 2. nvme-tcp: Handle number of queue changes https://git.infradead.org/nvme.git/commit/516204e486a19d03962c2757ef49782e6c1cacf4 3. nvme-rdma: Handle number of queue changes https://git.infradead.org/nvme.git/commit/e800278c1dc97518eab1970f8f58a5aad52b0f86 The patch in Point 2 above helps address the failure to reconnect in NVMe TCP scenario. Also, following patch addresses error code parsing issue in the reconnect sequence. nvme-fabrics: parse nvme connect Linux error codes https://git.infradead.org/nvme.git/commit/ec9e96b5230148294c7abcaf3a4c592d3720b62d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989990/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989983] 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 1989983 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/1989983 Title: kinetic: apply new apparmor and LSM stacking patch set Status in linux package in Ubuntu: Incomplete Status in linux source package in Kinetic: Incomplete Bug description: [Impact] Align with the latest apparmor and LSM stacking versions. To do so we need to: - revert sauce to get back to upstream apparmor, and drop old LSM stacking - pull in needed patches from upstream 6.0 - pull in needed patches from apparmor-next 6.1 This is required to properly support apparmor in Ubuntu. [Test case] We test apparmor in our RT suite. [Regression potential] We may see breakage in the apparmor tests after applying this patch set. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989983] [NEW] kinetic: apply new apparmor and LSM stacking patch set
Public bug reported: [Impact] Align with the latest apparmor and LSM stacking versions. To do so we need to: - revert sauce to get back to upstream apparmor, and drop old LSM stacking - pull in needed patches from upstream 6.0 - pull in needed patches from apparmor-next 6.1 This is required to properly support apparmor in Ubuntu. [Test case] We test apparmor in our RT suite. [Regression potential] We may see breakage in the apparmor tests after applying this patch set. ** 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/1989983 Title: kinetic: apply new apparmor and LSM stacking patch set Status in linux package in Ubuntu: New Status in linux source package in Kinetic: New Bug description: [Impact] Align with the latest apparmor and LSM stacking versions. To do so we need to: - revert sauce to get back to upstream apparmor, and drop old LSM stacking - pull in needed patches from upstream 6.0 - pull in needed patches from apparmor-next 6.1 This is required to properly support apparmor in Ubuntu. [Test case] We test apparmor in our RT suite. [Regression potential] We may see breakage in the apparmor tests after applying this patch set. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960186] Re: [22.04 FEAT] [KRN2006] BEAR enhancement support for new IBM Z Hardware
** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Summary changed: - [22.04 FEAT] [KRN2006] BEAR enhancement support for new IBM Z Hardware + [22.10 FEAT] [KRN2006] BEAR enhancement support for new IBM Z Hardware ** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: linux (Ubuntu Kinetic) Status: New => Fix Released ** Changed in: ubuntu-z-systems Status: New => Fix Released ** Changed in: linux (Ubuntu Kinetic) Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned) ** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960186 Title: [22.10 FEAT] [KRN2006] BEAR enhancement support for new IBM Z Hardware Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: Implement BEAR enhancement support for new IBM Z Hardware to make sure that no breaking events are lost anymore for userspace. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1960186/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989958] [NEW] kinetic/linux-raspi: Update to upstream raspberrypi rpi-5.19.y (2022-09-14)
Public bug reported: Upstream raspberrypi patchset 2022-09-14 Ported from the following raspberrypi branch: rpi-5.19.y from https://github.com/raspberrypi/linux.git usb: xhci: expand mitigations for VLI_SS_BULK_OUT_BUG quirk configs: Add NET_XFRM=m drm/vc4: v3d: Switch to devm_pm_runtime_enable drm/vc4: v3d: Rework the runtime_pm setup drm/vc4: v3d: Stop disabling interrupts drm/vc4: perfmon: Add missing mutex_destroy drm/vc4: Switch to drmm_mutex_init drm/vc4: hvs: Skip DebugFS Registration for FKMS drm/vc4: debugfs: Simplify debugfs registration drm/vc4: debugfs: Return an error on failure drm/vc4: debugfs: Protect device resources drm/vc4: vec: Switch to devm_pm_runtime_enable drm/vc4: vec: Protect device resources after removal drm/vc4: vec: Switch to DRM-managed connector initialization drm/vc4: vec: Switch to DRM-managed encoder initialization drm/vc4: vec: Remove call to drm_connector_unregister() drm/vc4: vec: Switch to drmm_kzalloc drm/vc4: vec: Embed DRM structures into the private structure drm/vc4: vec: Remove vc4_dev vec pointer drm/vc4: txp: Protect device resources drm/vc4: txp: Remove call to drm_connector_unregister() drm/vc4: txp: Switch to drmm_kzalloc drm/vc4: txp: Remove duplicate regset drm/vc4: txp: Remove vc4_dev txp pointer drm/vc4: hdmi: Switch to devm_pm_runtime_enable drm/vc4: hdmi: Protect device resources after removal drm/vc4: hdmi: Move audio structure offset checks drm/vc4: hdmi: Use devm to register hotplug interrupts drm/vc4: hdmi: Switch to DRM-managed kfree to build regsets drm/vc4: hdmi: Use a device-managed action for DDC drm/vc4: hdmi: Switch to device-managed CEC initialization drm/vc4: hdmi: Switch to device-managed ALSA initialization drm/vc4: hdmi: Switch to DRM-managed connector initialization drm/vc4: hdmi: Switch to DRM-managed encoder initialization drm/vc4: hdmi: Remove call to drm_connector_unregister() drm/vc4: hdmi: Switch to drmm_kzalloc drm/vc4: dsi: Switch to devm_pm_runtime_enable drm/vc4: dsi: Fix the driver structure lifetime drm/vc4: dsi: Switch to drmm_of_get_bridge drm/vc4: dsi: Switch to DRM-managed encoder initialization drm/vc4: dsi: Embed DRM structures into the private structure drm/vc4: dpi: Protect device resources drm/vc4: dpi: Switch to drmm_of_get_bridge drm/vc4: dpi: Switch to DRM-managed encoder initialization drm/vc4: dpi: Add action to disable the clock drm/vc4: dpi: Remove unnecessary drm_of_panel_bridge_remove call drm/vc4: dpi: Return an error if we can't enable our clock drm/vc4: dpi: Switch to drmm_kzalloc drm/vc4: dpi: Embed DRM structures into the private structure drm/vc4: dpi: Remove vc4_dev dpi pointer drm/vc4: crtc: Switch to DRM-managed CRTC initialization drm/vc4: crtc: Switch to drmm_kzalloc drm/vc4: crtc: Move debugfs_name to crtc_data drm/vc4: plane: Switch to drmm_universal_plane_alloc() drm/vc4: crtc: Remove manual plane removal on error drm/vc4: plane: Take possible_crtcs as an argument drm/vc4: hvs: Remove planes currently allocated before taking down drm/vc4: hvs: Protect device resources after removal drm/vc4: crtc: Create vblank reporting function drm/vc4: drv: Use drm_dev_unplug drm/vc4: drv: Call component_unbind_all() drm/vc4: Add module dependency on hdmi-codec drm/bridge: panel: Introduce drmm_of_get_bridge drm/bridge: panel: Introduce drmm_panel_bridge_add drm/connector: Introduce drmm_connector_init drm/connector: Check for destroy implementation drm/connector: Consolidate Connector Initialization drm/connector: Clarify when drm_connector_unregister is needed drm/connector: Mention the cleanup after drm_connector_init drm/connector: Reorder headers drm/encoder: Introduce drmm_encoder_init drm/crtc: Introduce drmm_crtc_init_with_planes drm/mipi-dsi: Detach devices when removing the host overlays: Rename unofficial "rpi-" overlays overlays: Add the Raspberry Pi sound cards media: i2c: imx290: Do not reset exposure time from set_fmt media: i2c: imx290: Drop incorrect comment about pixelrate Revert "media: i2c: imx290: Explicitly set v blank on mode change" media: i2c: imx290: Updating VBLANK should update exposure in all states ASoC:ma120x0p: Extend the volume range to -144dB (mute) media: bcm2835-unicam: Fix for possible dummy buffer overrun drm/vc4: Correct interrupt masking bit assignment for HVS5 drm/vc4: SCALER_DISPBKGND_AUTOHS is only valid on HVS4 drm/vc4: Set AXI panic modes for the HVS drm/vc4: Configure the HVS COB allocations overlays: Add a pull (up/down) parameter to pps-gpio configs: Add LAN7430 driver on BCM2711 media: i2c: arducam-pivariety: Add custom controls defconfigs: Add CONFIG_MUX_GPIO. media: video-mux: Read CSI2 config from FW, and pass to receiver drm/vc4: Add async update support for cursor planes rpi-simple-soundcard: limits sample rate of Merus Amp board overlays: merus-amp: Set GPIO 8 as input np configs: Enable DACBERRY400 overlays: Add dacberry400 sound: soc: bcm: Added Sound card driver for Dacberry400 Audio card for Raspberry Pi 400 overlays: gpio-fan:
[Kernel-packages] [Bug 1989957] [NEW] `man ip-address` fails to document subcommands "change" and "replace"
Public bug reported:
$ man ip-address
...
SYNOPSIS
...
ip address { add | change | replace } ...
However, the subcommands "change" and "replace" are not documented
anywhere. As these may be used in scripts, there should be clear
definition of these features or nobody can know if a script using these
features is actually correctly implemented.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: iproute2 5.5.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-125.141-lowlatency 5.4.195
Uname: Linux 5.4.0-125-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Fri Sep 16 14:40:10 2022
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-01-05 (1349 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: iproute2
UpgradeStatus: Upgraded to focal on 2022-09-13 (2 days ago)
modified.conffile..etc.init.d.apport: [modified]
mtime.conffile..etc.init.d.apport: 2022-05-19T12:50:20.029158
** Affects: iproute2 (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 iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/1989957
Title:
`man ip-address` fails to document subcommands "change" and "replace"
Status in iproute2 package in Ubuntu:
New
Bug description:
$ man ip-address
...
SYNOPSIS
...
ip address { add | change | replace } ...
However, the subcommands "change" and "replace" are not documented
anywhere. As these may be used in scripts, there should be clear
definition of these features or nobody can know if a script using
these features is actually correctly implemented.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: iproute2 5.5.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-125.141-lowlatency 5.4.195
Uname: Linux 5.4.0-125-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Fri Sep 16 14:40:10 2022
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-01-05 (1349 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: iproute2
UpgradeStatus: Upgraded to focal on 2022-09-13 (2 days ago)
modified.conffile..etc.init.d.apport: [modified]
mtime.conffile..etc.init.d.apport: 2022-05-19T12:50:20.029158
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1989957/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988836] Re: Enable the open NVIDIA kernel modules
Kernel rework is proposed at: https://lists.ubuntu.com/archives/kernel- team/2022-September/133205.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: In Progress Status in ubuntu-drivers-common source package in Focal: In Progress Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: In Progress Status in ubuntu-drivers-common source package in Jammy: In Progress Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs
** Also affects: nvidia-graphics-drivers-515 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1846374 Title: Having a video playing/paused when switched to another user generates gigabytes of error logs Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: New Bug description: To replicate: 1. Start a video playing, for example in vlc. 'avcodec decoder: Using NVIDIA VDPAU Driver Shared Library 418.56 Fri Mar 15 12:31:51 CDT 2019 for hardware decoding' 2. Optionally pause it. 3. Switch to another user. The original user's ~/.xsession-errors will rapidly fill up with errors along the lines of "vdpau_chroma filter error". At the same time, errors are put in /var/log/syslog as well: [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. (repeat ad nauseum) At least one of the two will rapidly fill up its partition and problems will arise. With AMD video hardware and driver, the video continues playing - you can hear the sound despite being in the other user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1846374/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989944] [NEW] [22.04/Jammy] Replace SAUCE AMD DP tunneling patch by upstream version
Public bug reported: We applied a set of patches early as the upstreaming got delayed. The patch now is in linux-next on its way into upstream linux. When that happens we want to replace the SAUCE patch by its upstream version (for example to get security checks right). “UBUNTU: SAUCE: thunderbolt: Add DP out resource when DP tunnel is discovered.” to be replaced by: commit b60e31bf18a7064032dbcb73dcb5b58f8a00a110 linux-next “thunderbolt: Add DP OUT resource when DP tunnel is discovered” By now it is confirmed that the patch in linux-next is somehow different from the one we carry. But to be on the safe side we should wait until it is really upstream and maybe give a little time to settle before actually changing things. ** Affects: linux (Ubuntu) Importance: Medium Assignee: Stefan Bader (smb) Status: Triaged ** Affects: linux (Ubuntu Jammy) Importance: Medium Status: Confirmed ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) 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/1989944 Title: [22.04/Jammy] Replace SAUCE AMD DP tunneling patch by upstream version Status in linux package in Ubuntu: Triaged Status in linux source package in Jammy: Confirmed Bug description: We applied a set of patches early as the upstreaming got delayed. The patch now is in linux-next on its way into upstream linux. When that happens we want to replace the SAUCE patch by its upstream version (for example to get security checks right). “UBUNTU: SAUCE: thunderbolt: Add DP out resource when DP tunnel is discovered.” to be replaced by: commit b60e31bf18a7064032dbcb73dcb5b58f8a00a110 linux-next “thunderbolt: Add DP OUT resource when DP tunnel is discovered” By now it is confirmed that the patch in linux-next is somehow different from the one we carry. But to be on the safe side we should wait until it is really upstream and maybe give a little time to settle before actually changing things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989944/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989941] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1989941/+attachment/5616378/+files/ProcInterrupts.txt -- 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/1989941 Title: Ubuntu 22.04: linux-firmware iwlwifi-9260-th-b0-jf-b0-46.ucode 5.15.0-47-generic - Wifi broken again Status in kernel-package package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: Hi same bug as https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/1967842 reappeared with the latest Kernel update 5.15.0-47-generic on same machine. Previous Kernel 5.15.0-46-generic is working. md5sum broken firmware from linux-firmware (Jammy Repo) dcf642fd7412614e19d1d54f57147539 /usr/lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode Here again, if I copy the firmware from an Ubuntu 20.04 machine, Wifi is working again. md5sum from Ubuntu 20.04 firmware: 0668e93b8766bf95d6adffdb33ec7bdb /usr/lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode The older firmware was already a workaround for the older bugreport. Should maybe the newer firmware reverted for jammy? dmesg with not working configuration: - Kernel 5.15.0-47-generic - linux-firmware 20220329.git681281e4-0ubuntu3.5 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: enabling device ( -> 0002) [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 0 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 1 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 2 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 3 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 4 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 6 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 8 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 9 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 10 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 11 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 15 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 16 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 18 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 19 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 20 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 21 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 28 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: loaded firmware version 46.fae53a8b.0 9260-th-b0-jf-b0-46.ucode op_mode iwlmvm [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: base HW address: 58:a0:23:cf:1e:8f [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: RF_KILL bit toggled to disable radio. [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: reporting RF_KILL (radio disabled) [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Error: Response NULL in 'MCC_UPDATE_CMD' [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Failed to run INIT ucode: -5 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: retry init count 0 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: base HW address: 58:a0:23:cf:1e:8f [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Failed to run INIT calibrations: -110 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Start IWL Error Log Dump: [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Transport status: 0x007A, valid: 6 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Loaded firmware version: 46.fae53a8b.0 9260-th-b0-jf-b0-46.ucode [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x22F0 | trm_hw_status0 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x | trm_hw_status1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x000221F8 | branchlink2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x00023CD2 | interruptlink1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0001A2F8 | interruptlink2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0xD322 | data1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0100 | data2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0xF008 | data3 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x
[Kernel-packages] [Bug 1989941] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1989941/+attachment/5616377/+files/ProcEnviron.txt -- 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/1989941 Title: Ubuntu 22.04: linux-firmware iwlwifi-9260-th-b0-jf-b0-46.ucode 5.15.0-47-generic - Wifi broken again Status in kernel-package package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: Hi same bug as https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/1967842 reappeared with the latest Kernel update 5.15.0-47-generic on same machine. Previous Kernel 5.15.0-46-generic is working. md5sum broken firmware from linux-firmware (Jammy Repo) dcf642fd7412614e19d1d54f57147539 /usr/lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode Here again, if I copy the firmware from an Ubuntu 20.04 machine, Wifi is working again. md5sum from Ubuntu 20.04 firmware: 0668e93b8766bf95d6adffdb33ec7bdb /usr/lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode The older firmware was already a workaround for the older bugreport. Should maybe the newer firmware reverted for jammy? dmesg with not working configuration: - Kernel 5.15.0-47-generic - linux-firmware 20220329.git681281e4-0ubuntu3.5 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: enabling device ( -> 0002) [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 0 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 1 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 2 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 3 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 4 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 6 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 8 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 9 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 10 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 11 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 15 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 16 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 18 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 19 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 20 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 21 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 28 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: loaded firmware version 46.fae53a8b.0 9260-th-b0-jf-b0-46.ucode op_mode iwlmvm [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: base HW address: 58:a0:23:cf:1e:8f [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: RF_KILL bit toggled to disable radio. [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: reporting RF_KILL (radio disabled) [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Error: Response NULL in 'MCC_UPDATE_CMD' [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Failed to run INIT ucode: -5 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: retry init count 0 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: base HW address: 58:a0:23:cf:1e:8f [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Failed to run INIT calibrations: -110 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Start IWL Error Log Dump: [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Transport status: 0x007A, valid: 6 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Loaded firmware version: 46.fae53a8b.0 9260-th-b0-jf-b0-46.ucode [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x22F0 | trm_hw_status0 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x | trm_hw_status1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x000221F8 | branchlink2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x00023CD2 | interruptlink1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0001A2F8 | interruptlink2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0xD322 | data1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0100 | data2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0xF008 | data3 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x |
[Kernel-packages] [Bug 1989941] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1989941/+attachment/5616382/+files/WifiSyslog.txt -- 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/1989941 Title: Ubuntu 22.04: linux-firmware iwlwifi-9260-th-b0-jf-b0-46.ucode 5.15.0-47-generic - Wifi broken again Status in kernel-package package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: Hi same bug as https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/1967842 reappeared with the latest Kernel update 5.15.0-47-generic on same machine. Previous Kernel 5.15.0-46-generic is working. md5sum broken firmware from linux-firmware (Jammy Repo) dcf642fd7412614e19d1d54f57147539 /usr/lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode Here again, if I copy the firmware from an Ubuntu 20.04 machine, Wifi is working again. md5sum from Ubuntu 20.04 firmware: 0668e93b8766bf95d6adffdb33ec7bdb /usr/lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode The older firmware was already a workaround for the older bugreport. Should maybe the newer firmware reverted for jammy? dmesg with not working configuration: - Kernel 5.15.0-47-generic - linux-firmware 20220329.git681281e4-0ubuntu3.5 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: enabling device ( -> 0002) [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 0 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 1 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 2 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 3 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 4 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 6 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 8 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 9 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 10 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 11 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 15 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 16 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 18 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 19 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 20 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 21 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 28 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: loaded firmware version 46.fae53a8b.0 9260-th-b0-jf-b0-46.ucode op_mode iwlmvm [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: base HW address: 58:a0:23:cf:1e:8f [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: RF_KILL bit toggled to disable radio. [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: reporting RF_KILL (radio disabled) [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Error: Response NULL in 'MCC_UPDATE_CMD' [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Failed to run INIT ucode: -5 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: retry init count 0 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: base HW address: 58:a0:23:cf:1e:8f [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Failed to run INIT calibrations: -110 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Start IWL Error Log Dump: [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Transport status: 0x007A, valid: 6 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Loaded firmware version: 46.fae53a8b.0 9260-th-b0-jf-b0-46.ucode [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x22F0 | trm_hw_status0 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x | trm_hw_status1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x000221F8 | branchlink2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x00023CD2 | interruptlink1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0001A2F8 | interruptlink2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0xD322 | data1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0100 | data2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0xF008 | data3 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x |
[Kernel-packages] [Bug 1989941] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1989941/+attachment/5616383/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1989941 Title: Ubuntu 22.04: linux-firmware iwlwifi-9260-th-b0-jf-b0-46.ucode 5.15.0-47-generic - Wifi broken again Status in kernel-package package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: Hi same bug as https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/1967842 reappeared with the latest Kernel update 5.15.0-47-generic on same machine. Previous Kernel 5.15.0-46-generic is working. md5sum broken firmware from linux-firmware (Jammy Repo) dcf642fd7412614e19d1d54f57147539 /usr/lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode Here again, if I copy the firmware from an Ubuntu 20.04 machine, Wifi is working again. md5sum from Ubuntu 20.04 firmware: 0668e93b8766bf95d6adffdb33ec7bdb /usr/lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode The older firmware was already a workaround for the older bugreport. Should maybe the newer firmware reverted for jammy? dmesg with not working configuration: - Kernel 5.15.0-47-generic - linux-firmware 20220329.git681281e4-0ubuntu3.5 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: enabling device ( -> 0002) [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 0 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 1 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 2 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 3 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 4 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 6 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 8 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 9 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 10 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 11 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 15 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 16 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 18 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 19 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 20 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 21 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 28 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: loaded firmware version 46.fae53a8b.0 9260-th-b0-jf-b0-46.ucode op_mode iwlmvm [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: base HW address: 58:a0:23:cf:1e:8f [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: RF_KILL bit toggled to disable radio. [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: reporting RF_KILL (radio disabled) [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Error: Response NULL in 'MCC_UPDATE_CMD' [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Failed to run INIT ucode: -5 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: retry init count 0 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: base HW address: 58:a0:23:cf:1e:8f [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Failed to run INIT calibrations: -110 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Start IWL Error Log Dump: [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Transport status: 0x007A, valid: 6 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Loaded firmware version: 46.fae53a8b.0 9260-th-b0-jf-b0-46.ucode [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x22F0 | trm_hw_status0 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x | trm_hw_status1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x000221F8 | branchlink2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x00023CD2 | interruptlink1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0001A2F8 | interruptlink2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0xD322 | data1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0100 | data2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0xF008 | data3
[Kernel-packages] [Bug 1989941] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1989941/+attachment/5616381/+files/UdevDb.txt -- 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/1989941 Title: Ubuntu 22.04: linux-firmware iwlwifi-9260-th-b0-jf-b0-46.ucode 5.15.0-47-generic - Wifi broken again Status in kernel-package package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: Hi same bug as https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/1967842 reappeared with the latest Kernel update 5.15.0-47-generic on same machine. Previous Kernel 5.15.0-46-generic is working. md5sum broken firmware from linux-firmware (Jammy Repo) dcf642fd7412614e19d1d54f57147539 /usr/lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode Here again, if I copy the firmware from an Ubuntu 20.04 machine, Wifi is working again. md5sum from Ubuntu 20.04 firmware: 0668e93b8766bf95d6adffdb33ec7bdb /usr/lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode The older firmware was already a workaround for the older bugreport. Should maybe the newer firmware reverted for jammy? dmesg with not working configuration: - Kernel 5.15.0-47-generic - linux-firmware 20220329.git681281e4-0ubuntu3.5 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: enabling device ( -> 0002) [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 0 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 1 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 2 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 3 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 4 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 6 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 8 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 9 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 10 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 11 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 15 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 16 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 18 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 19 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 20 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 21 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 28 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: loaded firmware version 46.fae53a8b.0 9260-th-b0-jf-b0-46.ucode op_mode iwlmvm [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: base HW address: 58:a0:23:cf:1e:8f [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: RF_KILL bit toggled to disable radio. [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: reporting RF_KILL (radio disabled) [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Error: Response NULL in 'MCC_UPDATE_CMD' [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Failed to run INIT ucode: -5 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: retry init count 0 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: base HW address: 58:a0:23:cf:1e:8f [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Failed to run INIT calibrations: -110 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Start IWL Error Log Dump: [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Transport status: 0x007A, valid: 6 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Loaded firmware version: 46.fae53a8b.0 9260-th-b0-jf-b0-46.ucode [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x22F0 | trm_hw_status0 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x | trm_hw_status1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x000221F8 | branchlink2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x00023CD2 | interruptlink1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0001A2F8 | interruptlink2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0xD322 | data1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0100 | data2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0xF008 | data3 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x | beacon time
[Kernel-packages] [Bug 1989941] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1989941/+attachment/5616380/+files/RfKill.txt -- 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/1989941 Title: Ubuntu 22.04: linux-firmware iwlwifi-9260-th-b0-jf-b0-46.ucode 5.15.0-47-generic - Wifi broken again Status in kernel-package package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: Hi same bug as https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/1967842 reappeared with the latest Kernel update 5.15.0-47-generic on same machine. Previous Kernel 5.15.0-46-generic is working. md5sum broken firmware from linux-firmware (Jammy Repo) dcf642fd7412614e19d1d54f57147539 /usr/lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode Here again, if I copy the firmware from an Ubuntu 20.04 machine, Wifi is working again. md5sum from Ubuntu 20.04 firmware: 0668e93b8766bf95d6adffdb33ec7bdb /usr/lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode The older firmware was already a workaround for the older bugreport. Should maybe the newer firmware reverted for jammy? dmesg with not working configuration: - Kernel 5.15.0-47-generic - linux-firmware 20220329.git681281e4-0ubuntu3.5 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: enabling device ( -> 0002) [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 0 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 1 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 2 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 3 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 4 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 6 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 8 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 9 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 10 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 11 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 15 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 16 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 18 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 19 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 20 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 21 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 28 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: loaded firmware version 46.fae53a8b.0 9260-th-b0-jf-b0-46.ucode op_mode iwlmvm [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: base HW address: 58:a0:23:cf:1e:8f [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: RF_KILL bit toggled to disable radio. [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: reporting RF_KILL (radio disabled) [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Error: Response NULL in 'MCC_UPDATE_CMD' [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Failed to run INIT ucode: -5 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: retry init count 0 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: base HW address: 58:a0:23:cf:1e:8f [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Failed to run INIT calibrations: -110 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Start IWL Error Log Dump: [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Transport status: 0x007A, valid: 6 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Loaded firmware version: 46.fae53a8b.0 9260-th-b0-jf-b0-46.ucode [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x22F0 | trm_hw_status0 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x | trm_hw_status1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x000221F8 | branchlink2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x00023CD2 | interruptlink1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0001A2F8 | interruptlink2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0xD322 | data1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0100 | data2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0xF008 | data3 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x | beacon time
[Kernel-packages] [Bug 1989941] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1989941/+attachment/5616379/+files/ProcModules.txt -- 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/1989941 Title: Ubuntu 22.04: linux-firmware iwlwifi-9260-th-b0-jf-b0-46.ucode 5.15.0-47-generic - Wifi broken again Status in kernel-package package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: Hi same bug as https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/1967842 reappeared with the latest Kernel update 5.15.0-47-generic on same machine. Previous Kernel 5.15.0-46-generic is working. md5sum broken firmware from linux-firmware (Jammy Repo) dcf642fd7412614e19d1d54f57147539 /usr/lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode Here again, if I copy the firmware from an Ubuntu 20.04 machine, Wifi is working again. md5sum from Ubuntu 20.04 firmware: 0668e93b8766bf95d6adffdb33ec7bdb /usr/lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode The older firmware was already a workaround for the older bugreport. Should maybe the newer firmware reverted for jammy? dmesg with not working configuration: - Kernel 5.15.0-47-generic - linux-firmware 20220329.git681281e4-0ubuntu3.5 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: enabling device ( -> 0002) [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 0 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 1 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 2 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 3 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 4 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 6 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 8 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 9 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 10 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 11 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 15 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 16 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 18 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 19 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 20 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 21 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 28 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: loaded firmware version 46.fae53a8b.0 9260-th-b0-jf-b0-46.ucode op_mode iwlmvm [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: base HW address: 58:a0:23:cf:1e:8f [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: RF_KILL bit toggled to disable radio. [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: reporting RF_KILL (radio disabled) [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Error: Response NULL in 'MCC_UPDATE_CMD' [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Failed to run INIT ucode: -5 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: retry init count 0 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: base HW address: 58:a0:23:cf:1e:8f [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Failed to run INIT calibrations: -110 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Start IWL Error Log Dump: [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Transport status: 0x007A, valid: 6 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Loaded firmware version: 46.fae53a8b.0 9260-th-b0-jf-b0-46.ucode [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x22F0 | trm_hw_status0 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x | trm_hw_status1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x000221F8 | branchlink2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x00023CD2 | interruptlink1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0001A2F8 | interruptlink2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0xD322 | data1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0100 | data2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0xF008 | data3 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x |
[Kernel-packages] [Bug 1989941] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1989941/+attachment/5616376/+files/ProcCpuinfoMinimal.txt -- 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/1989941 Title: Ubuntu 22.04: linux-firmware iwlwifi-9260-th-b0-jf-b0-46.ucode 5.15.0-47-generic - Wifi broken again Status in kernel-package package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: Hi same bug as https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/1967842 reappeared with the latest Kernel update 5.15.0-47-generic on same machine. Previous Kernel 5.15.0-46-generic is working. md5sum broken firmware from linux-firmware (Jammy Repo) dcf642fd7412614e19d1d54f57147539 /usr/lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode Here again, if I copy the firmware from an Ubuntu 20.04 machine, Wifi is working again. md5sum from Ubuntu 20.04 firmware: 0668e93b8766bf95d6adffdb33ec7bdb /usr/lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode The older firmware was already a workaround for the older bugreport. Should maybe the newer firmware reverted for jammy? dmesg with not working configuration: - Kernel 5.15.0-47-generic - linux-firmware 20220329.git681281e4-0ubuntu3.5 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: enabling device ( -> 0002) [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 0 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 1 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 2 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 3 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 4 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 6 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 8 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 9 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 10 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 11 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 15 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 16 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 18 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 19 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 20 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 21 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 28 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: loaded firmware version 46.fae53a8b.0 9260-th-b0-jf-b0-46.ucode op_mode iwlmvm [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: base HW address: 58:a0:23:cf:1e:8f [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: RF_KILL bit toggled to disable radio. [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: reporting RF_KILL (radio disabled) [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Error: Response NULL in 'MCC_UPDATE_CMD' [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Failed to run INIT ucode: -5 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: retry init count 0 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: base HW address: 58:a0:23:cf:1e:8f [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Failed to run INIT calibrations: -110 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Start IWL Error Log Dump: [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Transport status: 0x007A, valid: 6 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Loaded firmware version: 46.fae53a8b.0 9260-th-b0-jf-b0-46.ucode [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x22F0 | trm_hw_status0 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x | trm_hw_status1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x000221F8 | branchlink2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x00023CD2 | interruptlink1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0001A2F8 | interruptlink2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0xD322 | data1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0100 | data2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0xF008 | data3 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0:
[Kernel-packages] [Bug 1989941] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1989941/+attachment/5616374/+files/PaInfo.txt -- 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/1989941 Title: Ubuntu 22.04: linux-firmware iwlwifi-9260-th-b0-jf-b0-46.ucode 5.15.0-47-generic - Wifi broken again Status in kernel-package package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: Hi same bug as https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/1967842 reappeared with the latest Kernel update 5.15.0-47-generic on same machine. Previous Kernel 5.15.0-46-generic is working. md5sum broken firmware from linux-firmware (Jammy Repo) dcf642fd7412614e19d1d54f57147539 /usr/lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode Here again, if I copy the firmware from an Ubuntu 20.04 machine, Wifi is working again. md5sum from Ubuntu 20.04 firmware: 0668e93b8766bf95d6adffdb33ec7bdb /usr/lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode The older firmware was already a workaround for the older bugreport. Should maybe the newer firmware reverted for jammy? dmesg with not working configuration: - Kernel 5.15.0-47-generic - linux-firmware 20220329.git681281e4-0ubuntu3.5 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: enabling device ( -> 0002) [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 0 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 1 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 2 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 3 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 4 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 6 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 8 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 9 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 10 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 11 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 15 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 16 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 18 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 19 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 20 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 21 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 28 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: loaded firmware version 46.fae53a8b.0 9260-th-b0-jf-b0-46.ucode op_mode iwlmvm [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: base HW address: 58:a0:23:cf:1e:8f [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: RF_KILL bit toggled to disable radio. [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: reporting RF_KILL (radio disabled) [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Error: Response NULL in 'MCC_UPDATE_CMD' [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Failed to run INIT ucode: -5 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: retry init count 0 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: base HW address: 58:a0:23:cf:1e:8f [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Failed to run INIT calibrations: -110 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Start IWL Error Log Dump: [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Transport status: 0x007A, valid: 6 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Loaded firmware version: 46.fae53a8b.0 9260-th-b0-jf-b0-46.ucode [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x22F0 | trm_hw_status0 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x | trm_hw_status1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x000221F8 | branchlink2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x00023CD2 | interruptlink1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0001A2F8 | interruptlink2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0xD322 | data1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0100 | data2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0xF008 | data3 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x | beacon time
[Kernel-packages] [Bug 1989941] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1989941/+attachment/5616375/+files/ProcCpuinfo.txt -- 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/1989941 Title: Ubuntu 22.04: linux-firmware iwlwifi-9260-th-b0-jf-b0-46.ucode 5.15.0-47-generic - Wifi broken again Status in kernel-package package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: Hi same bug as https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/1967842 reappeared with the latest Kernel update 5.15.0-47-generic on same machine. Previous Kernel 5.15.0-46-generic is working. md5sum broken firmware from linux-firmware (Jammy Repo) dcf642fd7412614e19d1d54f57147539 /usr/lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode Here again, if I copy the firmware from an Ubuntu 20.04 machine, Wifi is working again. md5sum from Ubuntu 20.04 firmware: 0668e93b8766bf95d6adffdb33ec7bdb /usr/lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode The older firmware was already a workaround for the older bugreport. Should maybe the newer firmware reverted for jammy? dmesg with not working configuration: - Kernel 5.15.0-47-generic - linux-firmware 20220329.git681281e4-0ubuntu3.5 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: enabling device ( -> 0002) [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 0 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 1 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 2 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 3 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 4 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 6 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 8 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 9 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 10 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 11 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 15 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 16 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 18 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 19 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 20 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 21 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 28 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: loaded firmware version 46.fae53a8b.0 9260-th-b0-jf-b0-46.ucode op_mode iwlmvm [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: base HW address: 58:a0:23:cf:1e:8f [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: RF_KILL bit toggled to disable radio. [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: reporting RF_KILL (radio disabled) [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Error: Response NULL in 'MCC_UPDATE_CMD' [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Failed to run INIT ucode: -5 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: retry init count 0 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: base HW address: 58:a0:23:cf:1e:8f [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Failed to run INIT calibrations: -110 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Start IWL Error Log Dump: [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Transport status: 0x007A, valid: 6 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Loaded firmware version: 46.fae53a8b.0 9260-th-b0-jf-b0-46.ucode [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x22F0 | trm_hw_status0 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x | trm_hw_status1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x000221F8 | branchlink2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x00023CD2 | interruptlink1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0001A2F8 | interruptlink2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0xD322 | data1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0100 | data2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0xF008 | data3 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x |
[Kernel-packages] [Bug 1989941] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1989941/+attachment/5616372/+files/Lsusb-t.txt -- 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/1989941 Title: Ubuntu 22.04: linux-firmware iwlwifi-9260-th-b0-jf-b0-46.ucode 5.15.0-47-generic - Wifi broken again Status in kernel-package package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: Hi same bug as https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/1967842 reappeared with the latest Kernel update 5.15.0-47-generic on same machine. Previous Kernel 5.15.0-46-generic is working. md5sum broken firmware from linux-firmware (Jammy Repo) dcf642fd7412614e19d1d54f57147539 /usr/lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode Here again, if I copy the firmware from an Ubuntu 20.04 machine, Wifi is working again. md5sum from Ubuntu 20.04 firmware: 0668e93b8766bf95d6adffdb33ec7bdb /usr/lib/firmware/iwlwifi-9260-th-b0-jf-b0-46.ucode The older firmware was already a workaround for the older bugreport. Should maybe the newer firmware reverted for jammy? dmesg with not working configuration: - Kernel 5.15.0-47-generic - linux-firmware 20220329.git681281e4-0ubuntu3.5 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: enabling device ( -> 0002) [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 0 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 1 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 2 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 3 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 4 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 6 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 8 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 9 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 10 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 11 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 15 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 16 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 18 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 19 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 20 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 21 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: WRT: Overriding region id 28 [Fr Sep 16 09:00:42 2022] iwlwifi :6e:00.0: loaded firmware version 46.fae53a8b.0 9260-th-b0-jf-b0-46.ucode op_mode iwlmvm [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: base HW address: 58:a0:23:cf:1e:8f [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: RF_KILL bit toggled to disable radio. [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: reporting RF_KILL (radio disabled) [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Error: Response NULL in 'MCC_UPDATE_CMD' [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Failed to run INIT ucode: -5 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: retry init count 0 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324 [Fr Sep 16 09:00:43 2022] iwlwifi :6e:00.0: base HW address: 58:a0:23:cf:1e:8f [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Failed to run INIT calibrations: -110 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Start IWL Error Log Dump: [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Transport status: 0x007A, valid: 6 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: Loaded firmware version: 46.fae53a8b.0 9260-th-b0-jf-b0-46.ucode [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x22F0 | trm_hw_status0 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x | trm_hw_status1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x000221F8 | branchlink2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x00023CD2 | interruptlink1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0001A2F8 | interruptlink2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0xD322 | data1 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x0100 | data2 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0xF008 | data3 [Fr Sep 16 09:00:45 2022] iwlwifi :6e:00.0: 0x | beacon time
