[Kernel-packages] [Bug 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
I seem to have the same error booting. Using anything above Linux verston
5.13.0-35-genertc
Ubuntu get stuck with the error below. Reading what has been said, my driver
for ToughArmor MB992SKR-B would be the cause of the error and my inability to
use the latest kernel.
1.7517151
=
158855
1.7517261 UBSAN: array-index-out-of-bounds in /build/linux-hue-5.15-69LdMO/
linux-hwe-5.15-5.15.0/drivers/ata/libahci.c:968:41
1.7517311 index 15 is out of range for
type
'ahci em priu [8]'
1.7518821
ass=222s==5
SI
sasssa===
34.2160741 ata2.00: exception Emask 0x100 SAct Ox0 SErr Ox0 action Ox6 frozen
34.2161171 ata2.00: failed command: READ DMA
34.2161391 ata2.00: cm c8/00:08:00:00:00/00:00:00:00:00/e0 tag 22 dma 4096 in
34.2161391
res 40/00:00:00:00:00/00:00:00:00:00/00 mask 0x4
(timeout)
34.2162121 ata2.00: status:
{ DRDY }
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1970074
Title:
UBSAN: array-index-out-of-bounds in
/build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
Status in linux package in Ubuntu:
Confirmed
Bug description:
Something wrong with ata driver in dmesg found:
[1.980693] kernel:
[1.980699] kernel: fbcon: Taking over console
[1.980703] kernel: UBSAN: array-index-out-of-bounds in
/build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
[1.980709] kernel: index 15 is out of range for type 'ahci_em_priv [8]'
[1.980713] kernel: CPU: 0 PID: 209 Comm: scsi_eh_8 Not tainted
5.15.0-25-generic #25-Ubuntu
[1.980716] kernel: Hardware name: System manufacturer System Product
Name/P5Q3, BIOS 110206/11/2010
[1.980718] kernel: Call Trace:
[1.980721] kernel:
[1.980723] kernel: show_stack+0x52/0x58
[1.980729] kernel: dump_stack_lvl+0x4a/0x5f
[1.980734] kernel: dump_stack+0x10/0x12
[1.980736] kernel: ubsan_epilogue+0x9/0x45
[1.980739] kernel: __ubsan_handle_out_of_bounds.cold+0x44/0x49
[1.980742] kernel: ahci_qc_issue+0x166/0x170 [libahci]
[1.980748] kernel: ata_qc_issue+0x135/0x240
[1.980752] kernel: ata_exec_internal_sg+0x2c4/0x580
[1.980754] kernel: ? vprintk_default+0x1d/0x20
[1.980759] kernel: ata_exec_internal+0x67/0xa0
[1.980762] kernel: sata_pmp_read+0x8d/0xc0
[1.980765] kernel: sata_pmp_read_gscr+0x3c/0x90
[1.980768] kernel: sata_pmp_attach+0x8b/0x310
[1.980771] kernel: ata_eh_revalidate_and_attach+0x28c/0x4b0
[1.980775] kernel: ata_eh_recover+0x6b6/0xb30
[1.980778] kernel: ? ahci_do_hardreset+0x180/0x180 [libahci]
[1.980783] kernel: ? ahci_stop_engine+0xb0/0xb0 [libahci]
[1.980787] kernel: ? ahci_do_softreset+0x290/0x290 [libahci]
[1.980792] kernel: ?
trace_event_raw_event_ata_eh_link_autopsy_qc+0xe0/0xe0
[1.980795] kernel: sata_pmp_eh_recover.isra.0+0x214/0x560
[1.980799] kernel: sata_pmp_error_handler+0x23/0x40
[1.980802] kernel: ahci_error_handler+0x43/0x80 [libahci]
[1.980806] kernel: ata_scsi_port_error_handler+0x2b1/0x600
[1.980810] kernel: ata_scsi_error+0x9c/0xd0
[1.980813] kernel: scsi_error_handler+0xa1/0x180
[1.980817] kernel: ? scsi_unjam_host+0x1c0/0x1c0
[1.980820] kernel: kthread+0x12a/0x150
[1.980823] kernel: ? set_kthread_struct+0x50/0x50
[1.980826] kernel: ret_from_fork+0x22/0x30
[1.980831] kernel:
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-25-generic 5.15.0-25.25
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: eugene16798 F pulseaudio
/dev/snd/pcmC0D0p: eugene16798 F...m pulseaudio
/dev/snd/controlC1: eugene16798 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Apr 24 05:13:34 2022
HibernationDevice: RESUME=UUID=7e115b53-56a4-444f-bd93-6ad4f15c4a61
InstallationDate: Installed on 2019-04-13 (1106 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1)
IwConfig:
lono wireless extensions.
enp2s0no wireless extensions.
virbr0no wireless extensions.
MachineType: System manufacturer System Product Name
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=uk_UA.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-25-generic
root=UUID=d87288b4-dbdd-4448-8088-4ebb6ed6cf33 ro rootflags=subvol=@ quiet
splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.15.0-25-generic N/A
linux-backports-modules-5.15.0-25-generic N/A
linux-firmware
[Kernel-packages] [Bug 1941808] Re: AMD desktop fails to suspend
[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/1941808 Title: AMD desktop fails to suspend Status in linux package in Ubuntu: Expired Bug description: Since upgrading to 5.11.0-31-generic from 5.11.0-25-generic my system is no longer able to enter deep sleep when I choose "Suspend" from the Gnome power menu. The display goes blank for about 3 seconds and then comes back to the login screen. Machine setup: Desktop PC Ubuntu 21.04 Linux version 5.11.0-17-generic AMD Ryzen 3900X Asus X590 PRIME PRO motherboard NVIDIA P400 GPU The following appears in dmesg: [ 193.035190] PM: suspend entry (deep) [ 193.043644] Filesystems sync: 0.008 seconds [ 193.221385] rfkill: input handler enabled [ 193.223342] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 193.225169] OOM killer disabled. [ 193.225170] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 193.226377] printk: Suspending console(s) (use no_console_suspend to debug) [ 193.227086] serial 00:04: disabled [ 193.236938] PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16 [ 193.236948] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x170 returns -16 [ 193.236955] PM: Device :0b:00.3 failed to suspend async: error -16 [ 193.433850] PM: Some devices failed to suspend, or early wake event detected [ 193.434781] serial 00:04: activated [ 193.439638] nvme nvme1: Shutdown timeout set to 8 seconds [ 193.441267] nvme nvme0: 32/0/0 default/read/poll queues [ 193.467431] nvme nvme1: 32/0/0 default/read/poll queues [ 193.729944] usb 5-2.3: reset high-speed USB device number 3 using xhci_hcd [ 193.746614] ata1: SATA link down (SStatus 0 SControl 300) [ 193.746619] ata2: SATA link down (SStatus 0 SControl 300) [ 193.864008] OOM killer enabled. [ 193.864009] Restarting tasks ... done. [ 193.865012] PM: suspend exit [ 193.865069] PM: suspend entry (s2idle) [ 193.869519] Filesystems sync: 0.004 seconds [ 193.907792] Freezing user space processes ... (elapsed 0.007 seconds) done. [ 193.915352] OOM killer disabled. [ 193.915353] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 193.916464] printk: Suspending console(s) (use no_console_suspend to debug) [ 193.917046] serial 00:04: disabled [ 193.925345] PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16 [ 193.925355] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x170 returns -16 [ 193.925362] PM: Device :0b:00.3 failed to suspend async: error -16 [ 194.118212] PM: Some devices failed to suspend, or early wake event detected [ 194.119120] serial 00:04: activated [ 194.123827] nvme nvme1: Shutdown timeout set to 8 seconds [ 194.126322] nvme nvme0: 32/0/0 default/read/poll queues [ 194.150499] nvme nvme1: 32/0/0 default/read/poll queues [ 194.413459] usb 5-2.3: reset high-speed USB device number 3 using xhci_hcd [ 194.434238] ata2: SATA link down (SStatus 0 SControl 300) [ 194.434256] ata1: SATA link down (SStatus 0 SControl 300) [ 194.547373] OOM killer enabled. [ 194.547374] Restarting tasks ... done. [ 194.548195] PM: suspend exit [ 194.694550] rfkill: input handler disabled I see pci device mentioned is: 0b:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-31-generic 5.11.0-31.33 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jacob 2034 F pulseaudio /dev/snd/controlC0: jacob 2034 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Aug 26 16:57:09 2021 InstallationDate: Installed on 2020-10-28 (302 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp5s0no wireless extensions. docker0 no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-31-generic root=UUID=f721d5df-ceec-434a-919a-0680ee380996 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware 1.197.3
[Kernel-packages] [Bug 1986921] Re: lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51
This issue can be found on F-5.15 as well. ** Tags added: focal ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: lttng-modules (Ubuntu Focal) 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/1986921 Title: lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Won't Fix Status in lttng-modules package in Ubuntu: Invalid Status in linux source package in Focal: New Status in lttng-modules source package in Focal: New Status in linux source package in Jammy: Won't Fix Status in lttng-modules source package in Jammy: In Progress Bug description: SRU Justification: Impact: The kernel upstream changed in v5.18 and dropped tracepoints for random. This change was backported to 5.15/jammy in upstream stable 5.15.44. With that the build of lttng-modules-dkms fails. Fix: Backport of an upstream change which checks for the kernel header file which got removed in the process. Additionally the DKMS spec file has to do the same check to be aware of the missing probe module. Testcase: Installing lttng-modules-dkms for a kernel < 5.15.0-47 and -47 or later. Currently -47 and later will fail. With the change both should complete. Regression Potential: This changes whether lttng-probe-random.ko is available or not (if it is available the code is unchanged). User- space might be affected if this module is always expected. --- This is a scripted bug report about ADT failures while running lttng- modules tests for linux/5.15.0-47.51 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/lttng-modules/20220817_074711_55044@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/l/lttng-modules/20220817_075639_1a4d1@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/l/lttng-modules/20220817_074544_d2849@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/l/lttng-modules/20220817_075106_d2849@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1986921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986429] Re: do-release-upgrade fails
I managed to figure this out. I'm gonna say the bug here is poor
logging.
In the output I posted, in the "Original exception was" section, the
original error is:
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xec in position
8200: invalid continuation byte
Go back up a couple lines and you'll see this:
File "/tmp/ubuntu-release-
upgrader-l3yamuwr/DistUpgrade/DistUpgradeQuirks.py", line 395, in
_test_and_fail_on_pam_tally
This is the upgrader script that was running when the error was thrown.
Edit that file (as root) and go to line 395 and see that you're in a
"for" loop:
for f in os.listdir('/etc/pam.d'):
if f in ('common-account', 'common-auth', 'common-password',
'common-session', 'common-session-noninteractive'):
# managed by pam-auth-updates, and any references to
# pam_tally* will be handled by libpam-modules on upgrade
# without breaking
continue
with open(os.path.join('/etc/pam.d', f)) as f:
content = f.read()
if re.search('^[^#]*pam_tally', content, re.MULTILINE):
<--- line 395
The script is looping through files in /etc/pam.d. You can go look
there for the trouble, or you can edit the script to find which file is
being processed when the error is thrown. Like this:
for f in os.listdir('/etc/pam.d'):
print ("Rob says: " + f)
Now run the upgrader again from this temporary directory, which includes
the edits made above. Like this:
sudo /tmp/ubuntu-release-upgrader-l3yamuwr/DistUpgrade/jammy
We run the "jammy" script because that's what we're trying to upgrade
to. If in doubt, do 'ls -l' on that directory and look for an
executable script that is named after an ubuntu release.
After you run the above command, you'll still get an error but if you
search the output for "Rob says", you'll see the list of files that are
being processed in the "for" loop. The last one in the list before the
error is the likely culprit. In my case it was:
.common-auth.swp
This is a vi swap file. Several months ago I apparently edited common-
auth and didn't save it before the computer was shut down. I deleted
that file and then ran:
sudo do-release-upgrade
and the upgrade is now running.
So the problem was that the upgrader tried to process a file but it
could not (because it was not an ascii file). The upgrader should have,
at the very least, output the name of the problematic file.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1986429
Title:
do-release-upgrade fails
Status in linux-hwe-5.13 package in Ubuntu:
New
Bug description:
Running a completely up to date Ubuntu 20.04, I run:
sudo do-release-upgrade
and get the following output:
Building dependency tree
Reading state information... Done
Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-l3yamuwr/jammy", line 8, in
sys.exit(main())
File
"/tmp/ubuntu-release-upgrader-l3yamuwr/DistUpgrade/DistUpgradeMain.py", line
241, in main
if app.run():
File
"/tmp/ubuntu-release-upgrader-l3yamuwr/DistUpgrade/DistUpgradeController.py",
line 2042, in run
return self.fullUpgrade()
File
"/tmp/ubuntu-release-upgrader-l3yamuwr/DistUpgrade/DistUpgradeController.py",
line 1873, in fullUpgrade
if not self.doPostInitialUpdate():
File
"/tmp/ubuntu-release-upgrader-l3yamuwr/DistUpgrade/DistUpgradeController.py",
line 906, in doPostInitialUpdate
self.quirks.run("PostInitialUpdate")
File
"/tmp/ubuntu-release-upgrader-l3yamuwr/DistUpgrade/DistUpgradeQuirks.py", line
99, in run
func()
File
"/tmp/ubuntu-release-upgrader-l3yamuwr/DistUpgrade/DistUpgradeQuirks.py", line
122, in jammyPostInitialUpdate
self._test_and_fail_on_pam_tally()
File
"/tmp/ubuntu-release-upgrader-l3yamuwr/DistUpgrade/DistUpgradeQuirks.py", line
395, in _test_and_fail_on_pam_tally
content = f.read()
File "/usr/lib/python3.8/codecs.py", line 322, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xec in position 8200:
invalid continuation byte
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/problem_report.py", line 477, in
add_to_existing
self.write(f)
File "/usr/lib/python3/dist-packages/problem_report.py", line 430, in write
block = f.read(1048576)
File "/usr/lib/python3.8/codecs.py", line 322, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1:
invalid start byte
Original exception was:
Traceback (most recent call last):
File
[Kernel-packages] [Bug 1981087] Re: thermald prematurely throttling GPU
@Colette, Could you please help me to bisect the thermald between 2.4.9~2.5.0, it would be a several tries -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1981087 Title: thermald prematurely throttling GPU Status in thermald package in Ubuntu: In Progress Bug description: I got a new game and started playing it It would run at over 100 FPS solidly some of the time and then cyclically dip down to below 20 FPS for a few minutes I determined that it was thermald trying to keep my GPU below 70°C to determine this I sudo systemctl stop thermald The game ran solidly and consistently with the GPU at 75°C This is well below the specs set by the manufacturer and perhaps unreasonably low for a laptop But more importantly I was given no indication this was happening. I had to sleuth it out myself. Perhaps it is impossible to determine good defaults for all hardware, I don't know. However without an indication that this is happening there will be a lot of people with a mysteriously broken experience. This was extremely difficult for me to find and I had several friend who are experts on linux gaming and video drivers trying to track this down. I discovered it by luck and perseverance. This absolutely needs some sort of indication and hopefully a way to remedy it from the GUI. ideally it would set thermal limits that are more in line with what the device is designed for and not a conservative default if at all possible. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thermald 2.4.9-1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Fri Jul 8 16:08:55 2022 InstallationDate: Installed on 2020-10-19 (626 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: thermald UpgradeStatus: Upgraded to jammy on 2022-06-17 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1981087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947618] Re: [i915] CPU locks up on Ubuntu 21.10 boot when 2 displays are connected
Ivan: Ubuntu 21.10 is no longer supported. Please install Ubuntu 22.04 instead. Colin: Please open your own bug by running: ubuntu-bug linux ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947618 Title: [i915] CPU locks up on Ubuntu 21.10 boot when 2 displays are connected Status in linux package in Ubuntu: Won't Fix Bug description: I've updated from 21.04 to 21.10 and that bug has appeared in kernel 5.13.0-19. When 2 displays are connected simulateneously (DP and HDMI) before graphics server is started the kernel hangs up and reports that cpu is locked up. Boot with 5.11 kernel doesn't produce that problem. PC is based on i7-11700 CPU. Here is part of kernel log with call trace: кас 18 19:36:24 MWU-2197 kernel: fb0: switching to inteldrmfb from EFI VGA кас 18 19:36:24 MWU-2197 kernel: Console: switching to colour dummy device 80x25 кас 18 19:36:24 MWU-2197 kernel: i915 :00:02.0: vgaarb: deactivate vga console кас 18 19:36:24 MWU-2197 kernel: snd_hda_intel :00:1f.3: enabling device ( -> 0002) кас 18 19:36:24 MWU-2197 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem кас 18 19:36:24 MWU-2197 kernel: mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops i915_hdcp_component_ops [i915]) кас 18 19:36:24 MWU-2197 kernel: i915 :00:02.0: [drm] Finished loading DMC firmware i915/rkl_dmc_ver2_02.bin (v2.2) кас 18 19:36:25 MWU-2197 kernel: Bluetooth: hci0: BCM: chip id 63 кас 18 19:36:25 MWU-2197 kernel: Bluetooth: hci0: BCM: features 0x07 кас 18 19:36:25 MWU-2197 kernel: Bluetooth: hci0: Broadcom Bluetooth Device кас 18 19:36:25 MWU-2197 kernel: Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 кас 18 19:36:25 MWU-2197 kernel: Bluetooth: hci0: BCM20702A1 'brcm/BCM20702A1-0b05-17cb.hcd' Patch кас 18 19:36:25 MWU-2197 kernel: Bluetooth: hci0: Broadcom Bluetooth Device кас 18 19:36:25 MWU-2197 kernel: Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 кас 18 19:36:51 MWU-2197 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [systemd-udevd:461] кас 18 19:36:51 MWU-2197 kernel: Modules linked in: 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_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus ledtrig_audio snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec nls_iso8859_1 snd_hda_core fjes(-) mei_hdcp intel_rapl_msr i915(+) snd_hwdep snd_pcm intel_rapl_common snd_seq_midi snd_seq_midi_event btusb x86_pkg_temp_thermal snd_rawmidi intel_powerclamp btrtl drm_kms_helper btbcm snd_seq coretemp btintel crct10dif_pclmul snd_seq_device ghash_clmulni_intel cec snd_timer bluetooth rc_core aesni_intel snd crypto_simd i2c_algo_bit joydev cryptd fb_sys_fops mei_me ecdh_generic syscopyarea input_leds ecc sysfillrect intel_cstate eeepc_wmi wmi_bmof efi_pstore ee1004 soundcore sysimgblt mei sch_fq_codel mac_hid acpi_pad acpi_tad msr parport_pc ppdev кас 18 19:36:51 MWU-2197 kernel: lp parport drm ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid mfd_aaeon asus_wmi sparse_keymap intel_lpss_pci crc32_pclmul nvme xhci_pci i2c_i801 ahci intel_lpss e1000e nvme_core i2c_smbus libahci idma64 xhci_pci_renesas wmi video pinctrl_tigerlake кас 18 19:36:51 MWU-2197 kernel: CPU: 0 PID: 461 Comm: systemd-udevd Not tainted 5.13.0-19-generic #19-Ubuntu кас 18 19:36:51 MWU-2197 kernel: Hardware name: ASUS System Product Name/PRIME B560M-A, BIOS 1017 07/12/2021 кас 18 19:36:51 MWU-2197 kernel: RIP: 0010:skl_commit_modeset_enables+0x1b1/0x540 [i915] кас 18 19:36:51 MWU-2197 kernel: Code: 39 d8 7e 5d 49 8b 75 20 83 c3 01 8d 43 ff 48 98 48 8d 0c c5 00 00 00 00 48 29 c1 48 8d 04 ce 4c 8b 20 4c 8b 50 10 4c 8b 40 18 <4d> 85 e4 74 1a 41 8b 8c 24 f0 03 00 00 41 0f b6 c7 4c 89 55 b8 48 кас 18 19:36:51 MWU-2197 kernel: RSP: 0018:b89600d6b7b8 EFLAGS: 0202 кас 18 19:36:51 MWU-2197 kernel: RAX: 97474f0867b8 RBX: 0002 RCX: 0007 кас 18 19:36:51 MWU-2197 kernel: RDX: 97474434 RSI: 97474f086780 RDI: 974748c5ef3c кас 18 19:36:51 MWU-2197 kernel: RBP: b89600d6b828 R08: 974749b72000 R09: 0800 кас 18 19:36:51 MWU-2197 kernel: R10: 974741e22000 R11: 97474f086828 R12: 974752d1e000 кас 18 19:36:51 MWU-2197 kernel: R13: 97474fe5e800 R14: 0003 R15: 0003 кас 18 19:36:51 MWU-2197 kernel: FS: 7fe5dbb858c0() GS:974e7f40() knlGS: кас 18 19:36:51 MWU-2197 kernel: CS: 0010 DS:
[Kernel-packages] [Bug 1987040] Re: [i915] Max resolution for FullHD monitor is 1024x768
Yes my concern about VGA is the same if it's still VGA at either end. I don't know if EDID retrieval is meant to work on analog VGA connections, but in recent years there has been a slow trickle of bug reports about this. I think either: (a) Windows has a "driver" (.inf file) for the monitor already that defines the graphics modes for the monitor without the OS having to auto-detect it; or (b) The Linux kernel is not as good at auto-detecting over analog VGA as Windows is. ** Summary changed: - [i915] Max resolution for FullHD monitor is 1024x768 + [i915] Max resolution for FullHD monitor over VGA is 1024x768 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987040 Title: [i915] Max resolution for FullHD monitor over VGA is 1024x768 Status in linux package in Ubuntu: Confirmed Bug description: I have 1 external monitor, and the max resolution for this FullHD monitor which I can configure is 1024x768 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 19 08:40:15 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3] InstallationDate: Installed on 2022-06-04 (75 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 2349AV6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b8deb0ab-b1f3-469e-85fe-3cf4a56dc624 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/21/2016 dmi.bios.release: 2.70 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB0WW (2.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349AV6 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: BB70374050 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG1ETB0WW(2.70):bd01/21/2016:br2.70:efr1.13:svnLENOVO:pn2349AV6:pvrThinkPadT430:rvnLENOVO:rn2349AV6:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2349: dmi.product.family: ThinkPad T430 dmi.product.name: 2349AV6 dmi.product.sku: LENOVO_MT_2349 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986976] Re: At all startup time with recently installed 22.04.1 LTS screen flashing occurs, only close of the laptop screen stops tyhe flashing and allows to correctly login.
Please try adding these kernel parameters: i915.enable_dc=0 intel_idle.max_cstate=2 (from bug 1958191) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1986976 Title: At all startup time with recently installed 22.04.1 LTS screen flashing occurs, only close of the laptop screen stops tyhe flashing and allows to correctly login. Status in linux package in Ubuntu: Incomplete Bug description: I do remember such BIOS related issues back in 2019 for now I do have the list of the kernel error messages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: labdom 3949 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-07-15 (1130 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0029 Intel Corp. AX200 Bluetooth Bus 001 Device 003: ID 04d9:0499 Holtek Semiconductor, Inc. Optical Mouse Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=ea604268-2faf-42c2-abf5-69e0de92b334 ro quiet splash acpi=force vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 Tags: jammy wayland-session Uname: Linux 5.15.0-46-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-17 (2 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/06/2018 dmi.bios.release: 7.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.12 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.13 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.12:bd09/06/2018:br7.12:efr7.13:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986976/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987232] 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 1987232 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/1987232 Title: WARN in trace_event_dyn_put_ref Status in linux package in Ubuntu: Incomplete Bug description: I have systems that are regularly hitting a WARN in trace_event_dyn_put_ref. The exact message is: WARNING: CPU: 1 PID: 30309 at kernel/trace/trace_dynevent.c:46 +trace_event_dyn_put_ref+0x15/0x20 With the following stacktrace: perf_trace_init+0x8f/0xd0 perf_tp_event_init+0x1f/0x40 perf_try_init_event+0x4a/0x130 perf_event_alloc+0x497/0xf40 __do_sys_perf_event_open+0x1d4/0xf70 __x64_sys_perf_event_open+0x20/0x30 do_syscall_64+0x5c/0xc0 entry_SYSCALL_64_after_hwframe+0x44/0xae I've debugged this and worked with upstream to get a fix into Linux. It was recently merged in 6.0-rc2. See here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.0-rc2=7249921d94ff64f67b733eca0b68853a62032b3d The problem started appearing as soon as our systems picked up the linux-aws-5.15 branch for Focal. (That was 5.15.0-1015-aws, if memory serves). Could you please cherry pick this fix and pull it back to the the linux and linux-aws kernels for Focal? There's test here: https://lore.kernel.org/all/cover.1660347763.git.k...@templeofstupid.com/ that reproduces the problem very reliably for me. With the patch applied, I no longer get the WARNs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973676] Re: flickering and black screen from boot time, no more display after 22.04 upgrade
This bug is closed. Please open a new bug of your own by running: ubuntu-bug linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973676 Title: flickering and black screen from boot time, no more display after 22.04 upgrade Status in linux package in Ubuntu: Fix Released Bug description: On an HP x360 Spectre (i7-8565U WhiskeyLake-U GT2 [UHD Graphics 620]), after upgrading to 22.04 from 21.10, the display goes to some flickering lines in black and grey or colors (remember the artifacts on Amstrad CPC or C64 when loading from a tape? Same here...). After the initial grub menu, the kernel loads and boots. There are a few lines of log when the screen is in text mode. As soon as the plymouth screen comes in, the screen starts flickering massively. Nothing appeared on the screen except horizontal lines. I have an encrypted partition, so I type in the password and then the screen goes to flickering lines in color when Wayland starts. I tried different kernels: - 5.17.8: failed - 5.15.x: all failed (from Ubuntu 22.04) - 5.13.19: works and back to normal I found the following errors in the logs: * i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=43426 end=43427) time 300 us, min 2146, max 2159, scanline start 2131, end 2171 * i915 :00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) * i915 :00:02.0: [drm] [ENCODER:102:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it * i915 :00:02.0: [drm] [ENCODER:113:DDI C/PHY C] is disabled/in DSI mode with an ungated DDI clock, gate it * i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun So the problem is > 5.13.x series I temporarily solved it by downgrading to 5.13.19 from ubuntu mainline on a newly updated ubuntu 22.04! But it seems the bug affects all the kernels. It might be related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191 Info: Description: Ubuntu 22.04 LTS Release: 22.04 linux-image-5.15.0-30-generic: Installed: 5.15.0-30.31 Candidate: 5.15.0-30.31 Version table: *** 5.15.0-30.31 500 500 http://au.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978038] Re: test_brk_collision in ubuntu_qrt_kernel_aslr_collisions failed on T
** Tags added: sru-20220711 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1978038 Title: test_brk_collision in ubuntu_qrt_kernel_aslr_collisions failed on T Status in QA Regression Testing: New Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Trusty: Incomplete Bug description: Issue found on 3.13.0-190.241 lowlatency kernel with node gonzo (passed with generic kernel on another node onibi) Manually tested with: * node "onibi" + 3.13.0-190 lowlatency kernel: passed * node "onibi" + 3.13.0-170 generic kernel: passed * node "gonzo" + 3.13.0-190 generic kernel: failed * node "gonzo" + 3.13.0-189 generic kernel: failed * node "gonzo" + 3.13.0-170 generic kernel: failed Looks like this is not a regression but rather a hardware-specific issue. Test fail rate 5 out of 5 attempts. Test log: test_brk_collision (__main__.KernelASLRCollisionsTest) Check if brk crashes into mmap in 10,000 execs (i386, nx-emu only) (LP: #452175) ... FAIL test_stack_collision (__main__.KernelASLRCollisionsTest) Check if stack crashes into mmap in 100,000 execs (amd64 only?) (LP: #504164) ... ok == FAIL: test_brk_collision (__main__.KernelASLRCollisionsTest) Check if brk crashes into mmap in 10,000 execs (i386, nx-emu only) (LP: #452175) -- Traceback (most recent call last): File "./test-kernel-aslr-collisions.py", line 95, in test_brk_collision self.assertShellExitEquals(0, ['./explode-brk']) File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_aslr_collisions/src/qa-regression-testing/scripts/testlib.py", line 1203, in assertShellExitEquals self.assertEqual(expected, rc, msg + result + report) AssertionError: Got exit code 1, expected 0 Command: './explode-brk' Output: 7f59c8fd8000-7f59c9196000 r-xp 08:01 3281122 /lib/x86_64-linux-gnu/libc-2.19.so 7f59c9196000-7f59c9396000 ---p 001be000 08:01 3281122 /lib/x86_64-linux-gnu/libc-2.19.so 7f59c9396000-7f59c939a000 r--p 001be000 08:01 3281122 /lib/x86_64-linux-gnu/libc-2.19.so 7f59c939a000-7f59c939c000 rw-p 001c2000 08:01 3281122 /lib/x86_64-linux-gnu/libc-2.19.so 7f59c939c000-7f59c93a1000 rw-p 00:00 0 7f59c93a8000-7f59c93cb000 r-xp 08:01 328 /lib/x86_64-linux-gnu/ld-2.19.so 7f59c95ca000-7f59c95cb000 r--p 00022000 08:01 328 /lib/x86_64-linux-gnu/ld-2.19.so 7f59c95cb000-7f59c95cc000 rw-p 00023000 08:01 328 /lib/x86_64-linux-gnu/ld-2.19.so 7f59c95cc000-7f59c95cd000 rw-p 00:00 0 7f59c95d-7f59c95d1000 r-xp 08:01 15470803 /home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_aslr_collisions/src/qa-regression-testing/scripts/kernel-aslr-collisions/explode-brk 7f59c97d-7f59c97d1000 r--p 08:01 15470803 /home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_aslr_collisions/src/qa-regression-testing/scripts/kernel-aslr-collisions/explode-brk 7f59c97d1000-7f59c97d2000 rw-p 1000 08:01 15470803 /home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_aslr_collisions/src/qa-regression-testing/scripts/kernel-aslr-collisions/explode-brk 7f59c97d4000-7f59c97d8000 rw-p 00:00 0 [heap] 7fffd59ff000-7fffd5a2 rw-p 00:00 0 [stack] 7fffd5a2-7fffd5a22000 r-xp 00:00 0 [vdso] ff60-ff601000 r-xp 00:00 0 [vsyscall] FAIL: unable to use brk area at 0x7f59c97d4000 - 0x7f59c97dc000 -- Ran 5 tests in 467.450s FAILED (failures=1) No output printed in /var/log/syslog To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1978038/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987232] [NEW] WARN in trace_event_dyn_put_ref
Public bug reported: I have systems that are regularly hitting a WARN in trace_event_dyn_put_ref. The exact message is: WARNING: CPU: 1 PID: 30309 at kernel/trace/trace_dynevent.c:46 +trace_event_dyn_put_ref+0x15/0x20 With the following stacktrace: perf_trace_init+0x8f/0xd0 perf_tp_event_init+0x1f/0x40 perf_try_init_event+0x4a/0x130 perf_event_alloc+0x497/0xf40 __do_sys_perf_event_open+0x1d4/0xf70 __x64_sys_perf_event_open+0x20/0x30 do_syscall_64+0x5c/0xc0 entry_SYSCALL_64_after_hwframe+0x44/0xae I've debugged this and worked with upstream to get a fix into Linux. It was recently merged in 6.0-rc2. See here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.0-rc2=7249921d94ff64f67b733eca0b68853a62032b3d The problem started appearing as soon as our systems picked up the linux-aws-5.15 branch for Focal. (That was 5.15.0-1015-aws, if memory serves). Could you please cherry pick this fix and pull it back to the the linux and linux-aws kernels for Focal? There's test here: https://lore.kernel.org/all/cover.1660347763.git.k...@templeofstupid.com/ that reproduces the problem very reliably for me. With the patch applied, I no longer get the WARNs. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987232 Title: WARN in trace_event_dyn_put_ref Status in linux package in Ubuntu: New Bug description: I have systems that are regularly hitting a WARN in trace_event_dyn_put_ref. The exact message is: WARNING: CPU: 1 PID: 30309 at kernel/trace/trace_dynevent.c:46 +trace_event_dyn_put_ref+0x15/0x20 With the following stacktrace: perf_trace_init+0x8f/0xd0 perf_tp_event_init+0x1f/0x40 perf_try_init_event+0x4a/0x130 perf_event_alloc+0x497/0xf40 __do_sys_perf_event_open+0x1d4/0xf70 __x64_sys_perf_event_open+0x20/0x30 do_syscall_64+0x5c/0xc0 entry_SYSCALL_64_after_hwframe+0x44/0xae I've debugged this and worked with upstream to get a fix into Linux. It was recently merged in 6.0-rc2. See here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.0-rc2=7249921d94ff64f67b733eca0b68853a62032b3d The problem started appearing as soon as our systems picked up the linux-aws-5.15 branch for Focal. (That was 5.15.0-1015-aws, if memory serves). Could you please cherry pick this fix and pull it back to the the linux and linux-aws kernels for Focal? There's test here: https://lore.kernel.org/all/cover.1660347763.git.k...@templeofstupid.com/ that reproduces the problem very reliably for me. With the patch applied, I no longer get the WARNs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951772] Re: post upgrade, no video after suspend
Tried some web solutions: * adding "amd_iommu=off" to grub - nope! * switching to lightdm - already was using - nope! * not enough swap space - but have 3x memory - nope! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951772 Title: post upgrade, no video after suspend Status in linux package in Ubuntu: Confirmed Bug description: Suspend on desktop worked fine before upgrade to impish. Post upgrade, coming up after suspend leaves monitors with no signal from nvidia graphics card. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-release-upgrader-core 1:21.10.8 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: XFCE Date: Sun Nov 21 20:47:15 2021 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/tcsh SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to impish on 2021-11-21 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951772/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951772] Re: post upgrade, no video after suspend
Persists on upgrade to 22.04 Jammy. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951772 Title: post upgrade, no video after suspend Status in linux package in Ubuntu: Confirmed Bug description: Suspend on desktop worked fine before upgrade to impish. Post upgrade, coming up after suspend leaves monitors with no signal from nvidia graphics card. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-release-upgrader-core 1:21.10.8 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: XFCE Date: Sun Nov 21 20:47:15 2021 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/tcsh SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to impish on 2021-11-21 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951772/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987158] Re: touchpad does not work after distupgrade to 22.04
** Package changed: linux (Ubuntu) => mate-desktop (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987158 Title: touchpad does not work after distupgrade to 22.04 Status in mate-desktop package in Ubuntu: Confirmed Bug description: I upgraded my dual boot XPS 9870 to Ubuntu 22.04 and after a day or so the toucpad is not recognized. I looked up the dmesg errors online, it seems a common problem that Ubuntu had regularly over past years that a touchpad is recognized as generic mouse and cannot be activiated. interestingly it works in the login screen, but when the GUI starts, the touchpad cannot be actiavted again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matthias 2327 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Sat Aug 20 07:30:52 2022 InstallationDate: Installed on 2019-04-04 (1233 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 004: ID 27c6:5385 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=9b991c55-5313-4aa3-97a2-032ff0701df3 ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-08-13 (6 days ago) dmi.bios.date: 12/09/2021 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.0 dmi.board.name: 0H0VG3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.0:bd12/09/2021:br1.18:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0H0VG3:rvrA00:cvnDellInc.:ct10:cvr:sku07E6: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-desktop/+bug/1987158/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986429] Re: do-release-upgrade fails
On Feb 26 I opened this bug, which has not had any activity since I opened it:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1962373
I was hoping that maybe an upgrade to 22.04 would make the above
irrelevant, but now I'm not able to 'do-release-upgrade' due to this
bug. Can anybody give me some assurance that this bug won't end up like
the last bug I filed?
I can be patient if this bug is going to be worked on, but if it's not
then I should probably start making plans to move to another distro that
will work with my hardware.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1986429
Title:
do-release-upgrade fails
Status in linux-hwe-5.13 package in Ubuntu:
New
Bug description:
Running a completely up to date Ubuntu 20.04, I run:
sudo do-release-upgrade
and get the following output:
Building dependency tree
Reading state information... Done
Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-l3yamuwr/jammy", line 8, in
sys.exit(main())
File
"/tmp/ubuntu-release-upgrader-l3yamuwr/DistUpgrade/DistUpgradeMain.py", line
241, in main
if app.run():
File
"/tmp/ubuntu-release-upgrader-l3yamuwr/DistUpgrade/DistUpgradeController.py",
line 2042, in run
return self.fullUpgrade()
File
"/tmp/ubuntu-release-upgrader-l3yamuwr/DistUpgrade/DistUpgradeController.py",
line 1873, in fullUpgrade
if not self.doPostInitialUpdate():
File
"/tmp/ubuntu-release-upgrader-l3yamuwr/DistUpgrade/DistUpgradeController.py",
line 906, in doPostInitialUpdate
self.quirks.run("PostInitialUpdate")
File
"/tmp/ubuntu-release-upgrader-l3yamuwr/DistUpgrade/DistUpgradeQuirks.py", line
99, in run
func()
File
"/tmp/ubuntu-release-upgrader-l3yamuwr/DistUpgrade/DistUpgradeQuirks.py", line
122, in jammyPostInitialUpdate
self._test_and_fail_on_pam_tally()
File
"/tmp/ubuntu-release-upgrader-l3yamuwr/DistUpgrade/DistUpgradeQuirks.py", line
395, in _test_and_fail_on_pam_tally
content = f.read()
File "/usr/lib/python3.8/codecs.py", line 322, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xec in position 8200:
invalid continuation byte
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/problem_report.py", line 477, in
add_to_existing
self.write(f)
File "/usr/lib/python3/dist-packages/problem_report.py", line 430, in write
block = f.read(1048576)
File "/usr/lib/python3.8/codecs.py", line 322, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1:
invalid start byte
Original exception was:
Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-l3yamuwr/jammy", line 8, in
sys.exit(main())
File
"/tmp/ubuntu-release-upgrader-l3yamuwr/DistUpgrade/DistUpgradeMain.py", line
241, in main
if app.run():
File
"/tmp/ubuntu-release-upgrader-l3yamuwr/DistUpgrade/DistUpgradeController.py",
line 2042, in run
return self.fullUpgrade()
File
"/tmp/ubuntu-release-upgrader-l3yamuwr/DistUpgrade/DistUpgradeController.py",
line 1873, in fullUpgrade
if not self.doPostInitialUpdate():
File
"/tmp/ubuntu-release-upgrader-l3yamuwr/DistUpgrade/DistUpgradeController.py",
line 906, in doPostInitialUpdate
self.quirks.run("PostInitialUpdate")
File
"/tmp/ubuntu-release-upgrader-l3yamuwr/DistUpgrade/DistUpgradeQuirks.py", line
99, in run
func()
File
"/tmp/ubuntu-release-upgrader-l3yamuwr/DistUpgrade/DistUpgradeQuirks.py", line
122, in jammyPostInitialUpdate
self._test_and_fail_on_pam_tally()
File
"/tmp/ubuntu-release-upgrader-l3yamuwr/DistUpgrade/DistUpgradeQuirks.py", line
395, in _test_and_fail_on_pam_tally
content = f.read()
File "/usr/lib/python3.8/codecs.py", line 322, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xec in position 8200:
invalid continuation byte
Press x to destroy or r to resurrect window t Aug 13 10:07:11 2022) ===
$ lsb_release -rd
Description: Ubuntu 20.04.4 LTS
Release: 20.04
$ apt-cache policy python3.8
python3.8:
Installed: 3.8.10-0ubuntu1~20.04.5
Candidate: 3.8.10-0ubuntu1~20.04.5
Version table:
*** 3.8.10-0ubuntu1~20.04.5 500
500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu focal-security/main amd64
Packages
100 /var/lib/dpkg/status
3.8.2-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
The only thing unusual about my
[Kernel-packages] [Bug 1987223] Re: Touchpad and Touchscreen not showing up in devices on Dell after Kubuntu 22.04 upgrade
Following this: https://www.dell.com/support/kbdoc/fr- ch/000150104/precision-xps-ubuntu-general-touchpad-mouse-issue- fix?lang=en I ran the following and rebooted: sudo apt install --install-recommends linux-generic-hwe-22.04 xserver-xorg-hwe-18.04 Now the devices exist, see devices2 attachment ** Attachment added: "devices2" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987223/+attachment/5610586/+files/devices2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987223 Title: Touchpad and Touchscreen not showing up in devices on Dell after Kubuntu 22.04 upgrade Status in linux package in Ubuntu: Confirmed Bug description: The touchpad and touch screen worked ok on 20.04. After installing 22.04 they no longer work. Investigation shows no devices, output from below attached in "devices": cat /proc/bus/input/devices ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: david 1396 F pulseaudio /dev/snd/controlC1: david 1396 F pulseaudio /dev/snd/pcmC1D0p: david 1396 F...m pulseaudio /dev/snd/controlC0: david 1396 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Aug 21 22:24:24 2022 InstallationDate: Installed on 2022-04-20 (123 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: Dell Inc. Inspiron 7786 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=9c986618-4ee9-4eb8-bc36-dbdfc9a61cd1 ro acpi_osi=! "acpi_osi=Windows 2009" quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/28/2022 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0C6KN0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd03/28/2022:br1.14:svnDellInc.:pnInspiron7786:pvr:rvnDellInc.:rn0C6KN0:rvrA00:cvnDellInc.:ct31:cvr:sku0896: dmi.product.family: Inspiron dmi.product.name: Inspiron 7786 dmi.product.sku: 0896 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987223/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987223] 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/1987223 Title: Touchpad and Touchscreen not showing up in devices on Dell after Kubuntu 22.04 upgrade Status in linux package in Ubuntu: Confirmed Bug description: The touchpad and touch screen worked ok on 20.04. After installing 22.04 they no longer work. Investigation shows no devices, output from below attached in "devices": cat /proc/bus/input/devices ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: david 1396 F pulseaudio /dev/snd/controlC1: david 1396 F pulseaudio /dev/snd/pcmC1D0p: david 1396 F...m pulseaudio /dev/snd/controlC0: david 1396 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Aug 21 22:24:24 2022 InstallationDate: Installed on 2022-04-20 (123 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: Dell Inc. Inspiron 7786 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=9c986618-4ee9-4eb8-bc36-dbdfc9a61cd1 ro acpi_osi=! "acpi_osi=Windows 2009" quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/28/2022 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0C6KN0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd03/28/2022:br1.14:svnDellInc.:pnInspiron7786:pvr:rvnDellInc.:rn0C6KN0:rvrA00:cvnDellInc.:ct31:cvr:sku0896: dmi.product.family: Inspiron dmi.product.name: Inspiron 7786 dmi.product.sku: 0896 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987223/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987223] [NEW] Touchpad and Touchscreen not showing up in devices on Dell after Kubuntu 22.04 upgrade
Public bug reported: The touchpad and touch screen worked ok on 20.04. After installing 22.04 they no longer work. Investigation shows no devices, output from below attached in "devices": cat /proc/bus/input/devices ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: david 1396 F pulseaudio /dev/snd/controlC1: david 1396 F pulseaudio /dev/snd/pcmC1D0p: david 1396 F...m pulseaudio /dev/snd/controlC0: david 1396 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Aug 21 22:24:24 2022 InstallationDate: Installed on 2022-04-20 (123 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: Dell Inc. Inspiron 7786 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=9c986618-4ee9-4eb8-bc36-dbdfc9a61cd1 ro acpi_osi=! "acpi_osi=Windows 2009" quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/28/2022 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0C6KN0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd03/28/2022:br1.14:svnDellInc.:pnInspiron7786:pvr:rvnDellInc.:rn0C6KN0:rvrA00:cvnDellInc.:ct31:cvr:sku0896: dmi.product.family: Inspiron dmi.product.name: Inspiron 7786 dmi.product.sku: 0896 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "cat /proc/bus/input/devices" https://bugs.launchpad.net/bugs/1987223/+attachment/5610550/+files/devices ** Summary changed: - radeTouchpad and Touchscreen not showing up in devices on Dell after Kubuntu 22.04 upg + Touchpad and Touchscreen not showing up in devices on Dell after Kubuntu 22.04 upgrade -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987223 Title: Touchpad and Touchscreen not showing up in devices on Dell after Kubuntu 22.04 upgrade Status in linux package in Ubuntu: New Bug description: The touchpad and touch screen worked ok on 20.04. After installing 22.04 they no longer work. Investigation shows no devices, output from below attached in "devices": cat /proc/bus/input/devices ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: david 1396 F pulseaudio /dev/snd/controlC1: david 1396 F pulseaudio /dev/snd/pcmC1D0p: david 1396 F...m pulseaudio /dev/snd/controlC0: david 1396 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Aug 21 22:24:24 2022 InstallationDate: Installed on 2022-04-20 (123 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: Dell Inc. Inspiron 7786 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=9c986618-4ee9-4eb8-bc36-dbdfc9a61cd1 ro acpi_osi=! "acpi_osi=Windows 2009" quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/28/2022 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.name: 0C6KN0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd03/28/2022:br1.14:svnDellInc.:pnInspiron7786:pvr:rvnDellInc.:rn0C6KN0:rvrA00:cvnDellInc.:ct31:cvr:sku0896: dmi.product.family: Inspiron dmi.product.name: Inspiron 7786 dmi.product.sku: 0896 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987223/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1987190] Re: ZFS unrecoverable error after upgrading from 20.04 to 22.04.1
I saw that downgrading the module was not a very realistic option so I decided to follow a different route. It seems that the problem is the same as the one described here https://github.com/openzfs/zfs/issues/13709. The solution that worked for me is described here: https://github.com/openzfs/zfs/issues/13709#issuecomment-1200430509. It took a while to recover all the data because of the need for send / receive but it seems it is all back. I would suggest that you would consider to include some wording about this in the release notes or that you would even stop the upgrade for users that are using native ZFS encryption until this is solved. Thanks ** Bug watch added: github.com/openzfs/zfs/issues #13709 https://github.com/openzfs/zfs/issues/13709 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1987190 Title: ZFS unrecoverable error after upgrading from 20.04 to 22.04.1 Status in zfs-linux package in Ubuntu: New Bug description: I have a server that has been running its data volume using ZFS in 20.04 without any problem. The volume is using ZFS encryption and a raidz1-0 configuration. I performed a scrub operations before the upgrade and it did not find any problem. After the reboot for the upgrade, I was welcomed with the following message: status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-8A The volumes still do not have any checksum error but there are 5 zvols that are not accessible. zpool status displays a line similar to the below for each of the five: errors: Permanent errors have been detected in the following files: tank/data/data:<0x0> I run a scrub and it has not identified any problem but the error messages are not there and the data is still not available. There are 10+ other zvols in the zpool that do not have any kind of problem. I have been unable to identify any correlation between the zvols that are failing. I have seen people reporting similar problems in github after the 20.04 to the 22.04 upgrade (see https://github.com/openzfs/zfs/issues/13763). I wonder how widespread the problem will be as more people upgrades to 22.04. I will try to downgrade the version of zfs in the system and report back ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfsutils-linux 2.1.4-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat Aug 20 22:24:54 2022 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: Upgraded to jammy on 2022-08-20 (0 days ago) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/zfs'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1987190/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970957] Re: suspend problem
Can confirm on Lenovo ThinkPad L13Yoga. Kernel 5.15.0-46. Deactivating the security chip in BIOS and other proposed solutions in different forum and here to no avail. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1970957 Title: suspend problem Status in linux package in Ubuntu: Confirmed Bug description: I've installed Ubuntu 22.04 on the ThinkPad E480. Suspend functions ok intermittently. Some times it works fine, other times the computer does not enter the suspend mode (the screen gets blank, but the machine is still running and the ThinPad led is on, and there is no way out... no response from keyboard or mouse... the only solution is to switch off manually hitting and holding the power button), other times the machine does not wakes up from suspension mode. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 10:53:59 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leoca 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20KQ000EBR Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=1e7d6212-699d-4319-b137-8a7059545433 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/14/2018 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R0PET42W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KQ000EBR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR0PET42W(1.19):bd06/14/2018:br1.19:efr1.19:svnLENOVO:pn20KQ000EBR:pvrThinkPadE480:rvnLENOVO:rn20KQ000EBR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KQ_BU_Think_FM_ThinkPadE480: dmi.product.family: ThinkPad E480 dmi.product.name: 20KQ000EBR dmi.product.sku: LENOVO_MT_20KQ_BU_Think_FM_ThinkPad E480 dmi.product.version: ThinkPad E480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987200] 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/1987200 Title: 22.04 is unstabile Status in linux package in Ubuntu: Confirmed Bug description: I upgraded yesterday from 20.04 to 22.05. System came very unstabile, especially when I', using a lots of communication application. Typically I have Telegram, Skype, Thunderbird and Chromium on all of the time. Especially Thunderbird seems to create issues, Communicaton apps will give "no reponse from... Force quit or wait" message. Ocationally GUI will freeze. I have seen two o/s crashes as well, one when Impress presentation on. (crash when writing this report) I upgraded yesterday from 20.04 to 22.05. System came very unstabile, especially when I', using a lots of communication application. Typically I have Telegram, Skype, Thunderbird and Chromium on all of the time. Especially Thunderbird seems to create issues, Communicaton apps will give "no reponse from... Force quit or wait" message. Ocationally GUI will freeze. I have seen two o/s crashes as well, one when Impress presentation on. (crash when writing this report) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: timo 2219 F pulseaudio /dev/snd/controlC0: timo 2219 F pulseaudio /dev/snd/controlC1: timo 2219 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Aug 21 13:01:46 2022 HibernationDevice: RESUME=UUID=21e5e306-bb15-4ad7-904f-e7d2f5d39861 MachineType: HP HP Notebook ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=7da986a5-81ea-4ede-83aa-5c5798c46c56 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-08-20 (0 days ago) dmi.bios.date: 05/18/2016 dmi.bios.release: 15.16 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81DF dmi.board.vendor: HP dmi.board.version: KBC Version 70.12 dmi.chassis.asset.tag: 5CG6294Q15 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 70.12 dmi.modalias: dmi:bvnInsyde:bvrF.10:bd05/18/2016:br15.16:efr70.12:svnHP:pnHPNotebook:pvrCNB1:rvnHP:rn81DF:rvrKBCVersion70.12:cvnHP:ct10:cvrChassisVersion:skuY0B49EA#UUW: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: Y0B49EA#UUW dmi.product.version: CNB1 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987200/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987200] [NEW] 22.04 is unstabile
Public bug reported: I upgraded yesterday from 20.04 to 22.05. System came very unstabile, especially when I', using a lots of communication application. Typically I have Telegram, Skype, Thunderbird and Chromium on all of the time. Especially Thunderbird seems to create issues, Communicaton apps will give "no reponse from... Force quit or wait" message. Ocationally GUI will freeze. I have seen two o/s crashes as well, one when Impress presentation on. (crash when writing this report) I upgraded yesterday from 20.04 to 22.05. System came very unstabile, especially when I', using a lots of communication application. Typically I have Telegram, Skype, Thunderbird and Chromium on all of the time. Especially Thunderbird seems to create issues, Communicaton apps will give "no reponse from... Force quit or wait" message. Ocationally GUI will freeze. I have seen two o/s crashes as well, one when Impress presentation on. (crash when writing this report) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: timo 2219 F pulseaudio /dev/snd/controlC0: timo 2219 F pulseaudio /dev/snd/controlC1: timo 2219 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Aug 21 13:01:46 2022 HibernationDevice: RESUME=UUID=21e5e306-bb15-4ad7-904f-e7d2f5d39861 MachineType: HP HP Notebook ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=7da986a5-81ea-4ede-83aa-5c5798c46c56 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A linux-backports-modules-5.15.0-46-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.4 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-08-20 (0 days ago) dmi.bios.date: 05/18/2016 dmi.bios.release: 15.16 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81DF dmi.board.vendor: HP dmi.board.version: KBC Version 70.12 dmi.chassis.asset.tag: 5CG6294Q15 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 70.12 dmi.modalias: dmi:bvnInsyde:bvrF.10:bd05/18/2016:br15.16:efr70.12:svnHP:pnHPNotebook:pvrCNB1:rvnHP:rn81DF:rvrKBCVersion70.12:cvnHP:ct10:cvrChassisVersion:skuY0B49EA#UUW: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: Y0B49EA#UUW dmi.product.version: CNB1 dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1987200 Title: 22.04 is unstabile Status in linux package in Ubuntu: New Bug description: I upgraded yesterday from 20.04 to 22.05. System came very unstabile, especially when I', using a lots of communication application. Typically I have Telegram, Skype, Thunderbird and Chromium on all of the time. Especially Thunderbird seems to create issues, Communicaton apps will give "no reponse from... Force quit or wait" message. Ocationally GUI will freeze. I have seen two o/s crashes as well, one when Impress presentation on. (crash when writing this report) I upgraded yesterday from 20.04 to 22.05. System came very unstabile, especially when I', using a lots of communication application. Typically I have Telegram, Skype, Thunderbird and Chromium on all of the time. Especially Thunderbird seems to create issues, Communicaton apps will give "no reponse from... Force quit or wait" message. Ocationally GUI will freeze. I have seen two o/s crashes as well, one when Impress presentation on. (crash when writing this report) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: timo 2219 F pulseaudio /dev/snd/controlC0: timo 2219 F pulseaudio /dev/snd/controlC1: timo 2219 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Aug 21 13:01:46 2022 HibernationDevice: RESUME=UUID=21e5e306-bb15-4ad7-904f-e7d2f5d39861 MachineType: HP HP Notebook ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=7da986a5-81ea-4ede-83aa-5c5798c46c56 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.15.0-46-generic N/A
