[Kernel-packages] [Bug 2012789] Re: blacklist: Problem blacklisting hash (-13)
[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/2012789 Title: blacklist: Problem blacklisting hash (-13) Status in linux package in Ubuntu: Expired Bug description: [0.794819] Key type blacklist registered [4.860504] blacklist: Loading compiled-in revocation X.509 certificates [4.916587] blacklist: Problem blacklisting hash (-13) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012789/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009676] Re: Add support for Raptor Lake S CPUs
Awaiting answer to Andreas' latest question. ** Changed in: thermald (Ubuntu Focal) Status: In Progress => Incomplete -- 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/2009676 Title: Add support for Raptor Lake S CPUs Status in OEM Priority Project: Fix Released Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Incomplete Status in thermald source package in Jammy: Fix Released Bug description: [Impact] * Support thermald on Raptor Lake S CPU. [Test Plan] * Use a machine with a Raptor Lake S cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Raptor Lake S in thermald, which won't impact other hardware. [Other Info] https://github.com/intel/thermal_daemon/commit/e03493dc1e972374c1686492655250f8f48a15ba To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2009676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018960] Re: linux-image-5.4.0-149-generic (focal-proposed): 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0
I have the same problem except I don't appear to be on focal-proposed. steve@xxx:/etc/apt$ apt-cache policy linux-image-5.4.0-149-generic linux-image-5.4.0-149-generic: Installed: 5.4.0-149.166 Candidate: 5.4.0-149.166 Version table: *** 5.4.0-149.166 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status steve@xxx:/etc/apt$ apt-cache policy linux-image-generic linux-image-generic: Installed: 5.4.0.149.147 Candidate: 5.4.0.149.147 Version table: *** 5.4.0.149.147 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 5.4.0.26.32 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2018960 Title: linux-image-5.4.0-149-generic (focal-proposed): 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 Status in linux-signed package in Ubuntu: Confirmed Bug description: After upgrading and rebooting this Ubuntu 20.04 LTS server (Ubuntu Focal), I noticed that it was suddenly getting a bunch of kernel log (dmesg) reports like: WARNING: CPU: 4 PID: 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 while investigating I determined that it is currently running the focal-proposed kernel (linux-image-5.4.0-149-generic), which it turns out was enabled for this server (clearly it seemed like a good idea at the time). I'm not expecting focal-proposed to be fixed as if it were a release package, but since I couldn't find any reports on Launchpad I figured I should let y'all know this focal-proposed package could do with some additional work before it's actually released :-) There have been at least 80 such reports in the last 5 hours since the server was rebooted, differing only by the CPU core and the process reported, although it seems the last one was a couple of hours ago, so I guess it's traffic dependent/timing dependent. ewen@naosr620:~$ uptime 16:27:32 up 5:19, 1 user, load average: 0.08, 0.14, 0.06 ewen@naosr620:~$ dmesg -t | grep WARNING | sed 's/CPU: [0-9]*/CPU: N/; s/PID: [0-9]*/PID: N/;' | uniq -c 88 WARNING: CPU: N PID: N at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 ewen@naosr620:~$ Ubuntu Release: ewen@naosr620:~$ lsb_release -rd Description: Ubuntu 20.04.6 LTS Release: 20.04 ewen@naosr620:~$ Kernel/package version affected: ewen@naosr620:~$ uname -a Linux naosr620 5.4.0-149-generic #166-Ubuntu SMP Tue Apr 18 16:51:45 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ewen@naosr620:~$ dpkg -l | grep linux-image | grep 149 ii linux-image-5.4.0-149-generic 5.4.0-149.166 amd64Signed kernel image generic ii linux-image-generic5.4.0.149.147 amd64Generic Linux kernel image ewen@naosr620:~$ apt-cache policy linux-image-5.4.0-149-generic linux-image-5.4.0-149-generic: Installed: 5.4.0-149.166 Candidate: 5.4.0-149.166 Version table: *** 5.4.0-149.166 500 500 https://mirror.fsmg.org.nz/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status ewen@naosr620:~$ apt-cache policy linux-image-generic linux-image-generic: Installed: 5.4.0.149.147 Candidate: 5.4.0.149.147 Version table: *** 5.4.0.149.147 500 500 https://mirror.fsmg.org.nz/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 5.4.0.148.146 500 500 https://mirror.fsmg.org.nz/ubuntu focal-updates/main amd64 Packages 500 https://mirror.fsmg.org.nz/ubuntu focal-security/main amd64 Packages 5.4.0.26.32 500 500 https://mirror.fsmg.org.nz/ubuntu focal/main amd64 Packages ewen@naosr620:~$ ewen@naosr620:~$ apt-cache show linux-image-5.4.0-149-generic | grep Source: Source: linux-signed ewen@naosr620:~$ Full example dmesg, including stack trace (they all seem to be WARNINGs, and other than filling dmesg / system logs the system "appears to be running okay", so I'm not going to rush another reboot now -- near end of business day): ewen@naosr620:~$ date Tue 09 May 2023 16:34:56 NZST ewen@naosr620:~$ dmesg -T | tail -100 | grep -B 150 "end trace" | grep -A 999 "cut here" [Tue May 9 14:21:18 2023] [ cut here ] [Tue May 9 14:21:18 2023] WARNING: CPU: 10 PID: 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0 [Tue May 9 14:21:18 2023] Modules linked in: mpt3sas raid_class scsi_transport_sas mptctl mptbase vhost_net vhost tap ip6t_REJECT
[Kernel-packages] [Bug 1798166] Re: “Mouse battery low” notification can't be disabled
echo $XDG_CURRENT_DESKTOP GNOME-Flashback:GNOME OS is Ubuntu 20.04.6 LTS I am still having this problem. -- 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/1798166 Title: “Mouse battery low” notification can't be disabled Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Bug description: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/108 --- I have a wireless mouse powered by non-rechargeable battery. The mouse works absolutely fine even with low battery level. Problem is, Ubuntu gives notifications about the battery level all the time. I have had this issue for almost two months now, and mouse is working perfectly. I had to click away the notification almost every time I moved the mouse. I was then able to make the notifications appear less frequently, but the notification still always appear after some interval, and always after I log in. Here are some specific things I have tried, they have not helped. https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery- low-notification-in-ubuntu-18-04 1) Description: Ubuntu 18.04.1 LTS Release: 18.04 2) I assume the packet in question is notify-osd, not sure. notify-osd: Installed: (none) Candidate: 0.9.35+16.04.20160415-0ubuntu2 Version table: 0.9.35+16.04.20160415-0ubuntu2 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 3) I expected that no notifications would appear when notifications are set to off 4) Mouse battery low - notification always appears --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ohto 2927 F...m pulseaudio /dev/snd/controlC0: ohto 2927 F pulseaudio /dev/snd/controlC1: ohto 2927 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-28 (79 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1 ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77X-UP5 TH-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018226] Re: autoinstall fails despite BUILD_EXCLUSIVE
This bug was fixed in the package dkms - 3.0.11-1ubuntu7
---
dkms (3.0.11-1ubuntu7) mantic; urgency=medium
* Reset test messages correctly.
dkms (3.0.11-1ubuntu6) mantic; urgency=medium
* Fix hardcoded arch in test result expectations.
dkms (3.0.11-1ubuntu5) mantic; urgency=medium
* Attempt #5 to fix autopkgtest on all arches.
dkms (3.0.11-1ubuntu4) mantic; urgency=medium
* Testsuite forces a fake mok key, on arches that do not have
update-secureboot-policy. Thus it should be possible to run the tests
on all arches without specifying no-signing-tool flag. Try this now,
again.
dkms (3.0.11-1ubuntu3) mantic; urgency=medium
* Support running tests on systems with module signing, but without
update-secureboot-policy.
* Limit dkms-test-dkms to prevent badpkg on i386 for dkms-autopkgtest
dkms (3.0.11-1ubuntu2) mantic; urgency=medium
* Fix autopkgtest for ubuntu delta.
dkms (3.0.11-1ubuntu1) mantic; urgency=medium
* Deliberate Ubuntu delta:
- Even if there is no delta with Debian, do not force-sync this
package. This package will be updated by the kernel team as part of
landing new kernels. Neither upstream, nor Debian, use dkms to the
same extend as Ubuntu Kernel Team build processes do, plus Ubuntu has
more dkms packages than Debian. Testing in Debian is insufficient for
successful upload to Ubuntu. Over the previous two cycles, there were
multiple regressions introduced in upstream and Debian revisions that
have significantly impacted Ubuntu development. Introducing more
strict upload process for the DKMS package should hopefully mitigate
this. Previous request from the Kernel to do this, was ignored close
to Lunar release, which caused Lunar to be shipped with a regressed
dkms.
* Fixup autopkgtest:
- Support systems with secure boot off
- Support systems without update-secureboot-policy
dkms (3.0.11-1) experimental; urgency=medium
* New upstream release.
- Adds BUILD_EXCLUSIVE_{CONFIG,_KERNEL_{MIN,MAX}}. (Closes: #911665)
- Fixes BUILD_EXCLUSIVE matches propagating as error. (Closes: #1031561)
* Drop patches that were applied upstream.
* Avoid unnecessary rpm comands on Debian based systems. (Closes: #741399)
dkms (3.0.10-9) experimental; urgency=medium
* Add dkms-test-dkms package with trivial kernel module for dkms tests.
* New autopkgtest: Install some-dkms after linux-headers.
* New autopkgtest: Install linux-headers after some-dkms.
* New autopkgtest: Install some-dkms after linux-image w/o linux-headers.
* New autopkgtest: Install linux-image after some-dkms w/o linux-headers.
* Upload to experimental.
dkms (3.0.10-8ubuntu1) mantic; urgency=medium
* Fix a regression that prevents a kernel installation if a BUILD_EXCLUSIVE
skips a DKMS build. LP: #2018226
dkms (3.0.10-8) unstable; urgency=medium
* Disable tests broken by fix-builtin-archive-dkms-coinstallation.patch.
(Closes: #1033396)
* Run autopkgtest for all architectures using the headers from the
linux-headers-generic (virtual) meta-package.
* Generate dh_dkms.1 at build time.
* Clean up /boot/*.old-dkms on upgrades from bullseye. (Closes: #717584)
* Clean up obsolete /etc/dkms/sign_helper.sh on upgrades. (Closes: #1019563)
* dkms-autopkgtest: Try to 'dkms install' its BUILD_DEPENDS before testing a
module. (Single level only, without recursion.) (Closes: #1034303)
* Fix fallback value for BUILD_MODULE_NAME[0]. (Closes: #651973)
* dkms.8: Clarify 'dkms add' arguments. (Closes: #704917)
* Print a warning if /proc is not mounted. (Closes: #810665, #968074)
* dkms_autoinstaller: Skip autoinstall if headers are missing (like
dkms_common.postinst). (Closes: #1030595)
* Use return code 77 if skipping due to BUILD_EXCLUSIVE_*.
* Sort kernels by version.
-- Dimitri John Ledkov Wed, 24 May 2023
10:11:33 +0100
** Changed in: dkms (Ubuntu Mantic)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/2018226
Title:
autoinstall fails despite BUILD_EXCLUSIVE
Status in dkms package in Ubuntu:
Fix Released
Status in dkms source package in Lunar:
Fix Committed
Status in dkms source package in Mantic:
Fix Released
Bug description:
[Impact]
Kernel upgrades fail if DKMS packages are currently installed that
include BUILD_EXCLUSIVE directives which skip the DKMS build. In this
case, the dkms tool incorrectly returns a non-zero exit status.
$ sudo /etc/kernel/postinst.d/dkms 6.2.0-20-generic
* dkms: running auto installation service for kernel 6.2.0-20-generic
Deprecated
feature: REMAKE_INITRD
(/var/lib/dkms/oem-ethernet-r8169-aspm-support-bionic/4/source/dkms.conf)
Deprecated feature: REMAKE_INITRD
[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
@raj Hi, did you do step-by-step from home folder? sudo apt-get install build-essential git clone https://github.com/Kvalme/uvc.git cd ./uvc/ git checkout 5ea688c make (may be you must change cam id in uvc_driver.c (2471 line) for 4033 model. If you still have an error, later I can make dockerfile for building module in docker (if you familiar with it). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giuliano 2142 F pulseaudio /dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio /dev/snd/controlC0: giuliano 2142 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-03 (66 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-55 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 Tags: jammy Uname: Linux 5.15.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 04/20/2022
[Kernel-packages] [Bug 2008745] Re: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU
Hi Keng-Yu, Here is a test kernel for lunar. I had only included the source before and not the debs. Can you please test and verify the config_numa_emu option works and provides the performance boost. https://people.canonical.com/~mreed/hpe/lp_2008745_config_numa_emu/lunar/ ** Description changed: [Impact] Currently Ubuntu kernel has this kernel config disabled. But in some cases, Intel's Sapphire Rapids High Bandwith Memory (SPR-HBM) needs this option. Memory bandwidth has been a bottleneck of increasingly memory bound workloads. Sapphire Rapids plus HBM is specifically targeted to cater to these workloads, traditionally served using overprovisioning of memory devices. Please search the keyword "fake numa" in https://community.intel.com/t5/Blogs/Products-and- Solutions/HPC/Enabling-High-Bandwidth-Memory-for-HPC-and-AI- Applications-for/post/1335100 [Fix] Enable CONFIG_NUMA_EMU in our kernel config for 5.15 and later [Test Plan] + Use "STREAM-triadd" algorithm* in Intel MLC** to benchmark 3 scenarios (no fake NUMA, 2U fake NUMA and 4U fake NUMA). + + * https://www.intel.com/content/www/us/en/developer/articles/technical/optimizing-memory-bandwidth-on-stream-triad.html + ** https://www.intel.com/content/www/us/en/download/736633/intel-memory-latency-checker-intel-mlc.html + + An improvement to performance on a Sapphire Rapids CPU with HBM should + be observed [Where problems could occur] The regression risk is low [Other Info] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008745_config_numa_emu Kinetic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008745_config_numa_emu_kinetic Lunar https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/config_numa_emu_lunar ** Description changed: [Impact] Currently Ubuntu kernel has this kernel config disabled. But in some cases, Intel's Sapphire Rapids High Bandwith Memory (SPR-HBM) needs this option. Memory bandwidth has been a bottleneck of increasingly memory bound workloads. Sapphire Rapids plus HBM is specifically targeted to cater to these workloads, traditionally served using overprovisioning of memory devices. Please search the keyword "fake numa" in https://community.intel.com/t5/Blogs/Products-and- Solutions/HPC/Enabling-High-Bandwidth-Memory-for-HPC-and-AI- Applications-for/post/1335100 [Fix] Enable CONFIG_NUMA_EMU in our kernel config for 5.15 and later [Test Plan] - Use "STREAM-triadd" algorithm* in Intel MLC** to benchmark 3 scenarios (no fake NUMA, 2U fake NUMA and 4U fake NUMA). + Use "STREAM-triadd" algorithm* in Intel MLC** to benchmark 3 scenarios (no fake NUMA, 2U fake NUMA and 4U fake NUMA). * https://www.intel.com/content/www/us/en/developer/articles/technical/optimizing-memory-bandwidth-on-stream-triad.html ** https://www.intel.com/content/www/us/en/download/736633/intel-memory-latency-checker-intel-mlc.html An improvement to performance on a Sapphire Rapids CPU with HBM should be observed [Where problems could occur] The regression risk is low [Other Info] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008745_config_numa_emu Kinetic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008745_config_numa_emu_kinetic Lunar - https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/config_numa_emu_lunar + https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/config_numa_emu_2_lunar ** Description changed: [Impact] Currently Ubuntu kernel has this kernel config disabled. But in some cases, Intel's Sapphire Rapids High Bandwith Memory (SPR-HBM) needs this option. Memory bandwidth has been a bottleneck of increasingly memory bound workloads. Sapphire Rapids plus HBM is specifically targeted to cater to these workloads, traditionally served using overprovisioning of memory devices. Please search the keyword "fake numa" in https://community.intel.com/t5/Blogs/Products-and- Solutions/HPC/Enabling-High-Bandwidth-Memory-for-HPC-and-AI- Applications-for/post/1335100 [Fix] Enable CONFIG_NUMA_EMU in our kernel config for 5.15 and later [Test Plan] Use "STREAM-triadd" algorithm* in Intel MLC** to benchmark 3 scenarios (no fake NUMA, 2U fake NUMA and 4U fake NUMA). * https://www.intel.com/content/www/us/en/developer/articles/technical/optimizing-memory-bandwidth-on-stream-triad.html ** https://www.intel.com/content/www/us/en/download/736633/intel-memory-latency-checker-intel-mlc.html An improvement to performance on a Sapphire Rapids CPU with HBM should be observed [Where problems could occur] The regression risk is low [Other Info] Jammy
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
@oshunluvr, please check whether its the same issue as described here : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012830. The described issue does not depend on the kernel. "Audio speed up, it sounds like chirps" -- 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/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Released Bug description: [Impact] For amdgpu/i915, hdmi audio output device has disappeared. [Fix] The latest fix for the non-contiguous memalloc helper changed the allocation method for a non-IOMMU system to use only the fallback allocator. This should have worked, but it caused a problem sometimes when too many non-contiguous pages are allocated that can't be treated by HD-audio controller. As a quirk workaround, go back to the original strategy: use dma_alloc_noncontiguous() at first, and apply the fallback only when it fails, but only for non-IOMMU case [Test Case] 1. boot with kernel applied the patches. 2. check the cards in /proc/asound/cards. Get the hdmi cards. 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xe232 irq 137 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xe226 irq 134 [Where problems could occur] Low, this is just workaround and may have a better solution in the future. [Misc] All patches has been landed on OEM-6.1 and lunar. ~~ CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. Currently known affected cards: * HD 7700 (comment 8) * R9 290 (comment 21) * RX 550 (LP: #2012141, and comment 27) * RX 570 (mine) * RX 580 (LP: #2009276, and comment 28) * WX 3200 (comment 29) * RX 6600 (LP: #2009542) * RX 6700 (LP: #2009275) [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
@raj Hello, If I may say, I also had this same error when I was trying to work with the instructions in #19 before Giuliano provided the Bash script. What caused the error from my experience is that I was running the wget command and compiling in the wrong directory. I think checking which are the correct directories to work in will solve the error because that is what happened in my case. I hope that helps Kind regards Samer Attrah -- 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/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giuliano 2142 F pulseaudio /dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio /dev/snd/controlC0: giuliano 2142 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-03 (66 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-55 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 Tags: jammy Uname: Linux 5.15.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd
[Kernel-packages] [Bug 2018303] Re: move sev-guest module from linux-modules-extra to linux-modules
** Changed in: linux-aws (Ubuntu Kinetic) Status: In Progress => Fix Committed ** Changed in: linux-aws (Ubuntu Lunar) Status: In Progress => Fix Committed ** Changed in: linux-aws (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2018303 Title: move sev-guest module from linux-modules-extra to linux-modules Status in linux-aws package in Ubuntu: Fix Committed Status in linux-aws source package in Kinetic: Fix Committed Status in linux-aws source package in Lunar: Fix Committed Status in linux-aws source package in Mantic: Fix Committed Bug description: AWS did recently announce AMD SEV-SNP support (see https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/sev-snp.html. To have that working in the ubuntu AWS images, the module needs to be available (linux-modules-extra is not installed by default). So please move the module to linux-modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2018303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015369] Re: Azure: Add PCI pass-thru support to Hyper-V Confidential VMs
** Changed in: linux-azure (Ubuntu Kinetic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2015369 Title: Azure: Add PCI pass-thru support to Hyper-V Confidential VMs Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Kinetic: Fix Committed Status in linux-azure source package in Lunar: Fix Released Bug description: SRU Justification [Impact] Microsoft has requested the inclusion of this patch set: https://lore.kernel.org/linux-hyperv/1679838727-87310-1-git-send- email-mikel...@microsoft.com/T/ [Regression Potential] Private memory mappings could be incorrect. [Test Plan] Microsoft tested. [Other Info] SF: #00355859 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2015369/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020647] Re: Upgrade from 22.04 to 22.10 won't boot
So, I still dont' understand how/why but I seem to have solved it by: (1) I changed /etc/default/grub: GRUB_TERMINAL=console GRUB_CMDLINE_LINUX_DEFAULT="text nosplash debug loglevel=7 apic=verbose --verbose" (the change to the line above was only adding "text" parameter) (2) I installed ubuntu-budgie-desktop (3) Purged any nvidia package (4) Installed the nouveau XOrg package. Rebooted (4) Installed nvidia drivers using the UI "Software Updater" tool (in settings) Things are booting normally in kernel 6.2.0 now, and things look normal so far. Curiously now 5.17.5 doesnt' boot, but it doesnt' matter, since I can make it work with 6.2.0. Now some stuff I need to re-install (nvidia support for dockers for instance). But I'll mark this as resolved for now. -- 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/2020647 Title: Upgrade from 22.04 to 22.10 won't boot Status in linux package in Ubuntu: Incomplete Bug description: I was actually meaning to upgrade to 23.04, but the updater offered to upgrade to 22.10 first, so I supposed this was needed. After a standard upgrade with the UI, even the recovery boot never passes the "Loading initial ramdisk ..." line -- it silently freezes. I have removed the "quiet splash" options in grub by "dis_ucode_ldr", following some random article. Anyway, nothing is displayed after "Loading initial ramdisk ..." line. I have the following kernel installed: 5.19.0-42-generic 5.17.5-051705-generic 5.15.36-051536-generic 5.15.0-27-generic (*) 5.13.0-19-generic Plus a dual-boot windows. Just the 5.15.0-27-generic boots, but it doesn't mount ethernet for some reason. My motherboard uses Realtek 8125, and it used to work just fine 10 minutes ago (in 22.04), but now I'm not able to install `r8125-dkms` module, because I dont' have the linux-headers version installed for that kernel ... I'm also not able to find it to download. I also have an old 2080ti NVidia card, in case that has any effect on this. Any suggestions ? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020647/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020656] Re: system freeze (cpu fan goes high)
New freeze No particular message in journalctl The fan did not went high this time -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2020656 Title: system freeze (cpu fan goes high) Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: More than once a day the system totally freeze. CPU fan then goes higher and higher. Does not seem to be related to system load as yesterday it happend during lunch break. Today's journalctl -b -1 last message is mai 24 11:50:06 ThinkPad-P14s kernel: watchdog: BUG: soft lockup - CPU#9 stuck for 167s! [opt ax7ixzwwoey:158586] There are many more of the same kind just before $ lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 $ apt-cache policy linux-image-5.19.0-42-generic linux-image-5.19.0-42-generic: Installé : 5.19.0-42.43~22.04.1 Candidat : 5.19.0-42.43~22.04.1 Table de version : *** 5.19.0-42.43~22.04.1 500 500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status Note this problem was present before last kernel updates ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-42-generic 5.19.0-42.43~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 24 12:00:08 2023 InstallationDate: Installed on 2023-03-25 (59 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: TERM=alacritty PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 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.19/+bug/2020656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
KDEneon provided 5.19.0-42 this morning and the audio devices reappeared. HOWEVER, system startup sound and Accessibility notifications (like Lock Key toggle sound) do not produce audio. Rebooting back to the 5.15.0 series restored normal audio feedback. -- 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/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Released Bug description: [Impact] For amdgpu/i915, hdmi audio output device has disappeared. [Fix] The latest fix for the non-contiguous memalloc helper changed the allocation method for a non-IOMMU system to use only the fallback allocator. This should have worked, but it caused a problem sometimes when too many non-contiguous pages are allocated that can't be treated by HD-audio controller. As a quirk workaround, go back to the original strategy: use dma_alloc_noncontiguous() at first, and apply the fallback only when it fails, but only for non-IOMMU case [Test Case] 1. boot with kernel applied the patches. 2. check the cards in /proc/asound/cards. Get the hdmi cards. 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xe232 irq 137 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xe226 irq 134 [Where problems could occur] Low, this is just workaround and may have a better solution in the future. [Misc] All patches has been landed on OEM-6.1 and lunar. ~~ CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. Currently known affected cards: * HD 7700 (comment 8) * R9 290 (comment 21) * RX 550 (LP: #2012141, and comment 27) * RX 570 (mine) * RX 580 (LP: #2009276, and comment 28) * WX 3200 (comment 29) * RX 6600 (LP: #2009542) * RX 6700 (LP: #2009275) [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020887] Re: Ubuntu 22.04 after last update Gnome desktop shows up after login but freezes
** 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/2020887 Title: Ubuntu 22.04 after last update Gnome desktop shows up after login but freezes Status in linux package in Ubuntu: Confirmed Bug description: Using my Ubuntu 22.04.2 LTS VM under Microsoft Hyper-V and Windows 10 for some years now. Have a snapshot from April 29 with the latest updates up to that time, and that one worked perfectly. 1) Release: Description:Ubuntu 22.04.2 LTS Release:22.04 After the last updates the kernel version in the VM is: Linux 5.19.0-42-generic (before in the snapshot version of the VM where everything worked normally, kernel version was 5.19.0-40-generic) 2) From your own "FindRightPackage" link, I am guessing the problem is in Nautilus. Nautilus package version: nautilus: Instalados: 1:42.2-0ubuntu2.1 Candidato: 1:42.2-0ubuntu2.1 Tabla de versión: *** 1:42.2-0ubuntu2.1 500 500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 1:42.0-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What I expected to happen: The VM boots apparently normally, login GUI shows up, I can login, Gnome desktop shows up completely (desktop icons included), and I should be able to start moving the mouse and clicking on things to start using the system through the Gnome desktop. 4) What happened instead: I log in through the GUI, the gnome desktop appears after the login, but incomplete. No desktop icons get shown. Also, I see the mouse cursor, but there is no mouse movement whatsoever. The desktop is effectively frozen and unresponsive, completely unusable. I can still ssh into the VM perfectly and operate on the command line, the VM itself is not frozen, just the GUI. If any journalctl outputs or logs needed from either version of the VM, I can provide them. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-04-13 (772 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. eth0 no wireless extensions. docker0 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=c7d3be02-30d6-49e4-8290-10c2678f35f9 ro video=hyperv_fb:1920x1080 ipv6.disable=1 video=hyperv_fb:1920x1080 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-42-generic N/A linux-backports-modules-5.19.0-42-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 RfKill: Tags: jammy Uname: Linux 5.19.0-42-generic x86_64 UpgradeStatus: Upgraded to jammy on 2023-02-16 (98 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 2473-5733-1385-7558-0781-8481-94 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020656] Re: system freeze (cpu fan goes high)
I decided to upgrade to ubuntu 23.03 to see if a newer version of the kernel change something -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2020656 Title: system freeze (cpu fan goes high) Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: More than once a day the system totally freeze. CPU fan then goes higher and higher. Does not seem to be related to system load as yesterday it happend during lunch break. Today's journalctl -b -1 last message is mai 24 11:50:06 ThinkPad-P14s kernel: watchdog: BUG: soft lockup - CPU#9 stuck for 167s! [opt ax7ixzwwoey:158586] There are many more of the same kind just before $ lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 $ apt-cache policy linux-image-5.19.0-42-generic linux-image-5.19.0-42-generic: Installé : 5.19.0-42.43~22.04.1 Candidat : 5.19.0-42.43~22.04.1 Table de version : *** 5.19.0-42.43~22.04.1 500 500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status Note this problem was present before last kernel updates ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-42-generic 5.19.0-42.43~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 24 12:00:08 2023 InstallationDate: Installed on 2023-03-25 (59 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: TERM=alacritty PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 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.19/+bug/2020656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020887] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2020887/+attachment/5675866/+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/2020887 Title: Ubuntu 22.04 after last update Gnome desktop shows up after login but freezes Status in linux package in Ubuntu: Incomplete Bug description: Using my Ubuntu 22.04.2 LTS VM under Microsoft Hyper-V and Windows 10 for some years now. Have a snapshot from April 29 with the latest updates up to that time, and that one worked perfectly. 1) Release: Description:Ubuntu 22.04.2 LTS Release:22.04 After the last updates the kernel version in the VM is: Linux 5.19.0-42-generic (before in the snapshot version of the VM where everything worked normally, kernel version was 5.19.0-40-generic) 2) From your own "FindRightPackage" link, I am guessing the problem is in Nautilus. Nautilus package version: nautilus: Instalados: 1:42.2-0ubuntu2.1 Candidato: 1:42.2-0ubuntu2.1 Tabla de versión: *** 1:42.2-0ubuntu2.1 500 500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 1:42.0-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What I expected to happen: The VM boots apparently normally, login GUI shows up, I can login, Gnome desktop shows up completely (desktop icons included), and I should be able to start moving the mouse and clicking on things to start using the system through the Gnome desktop. 4) What happened instead: I log in through the GUI, the gnome desktop appears after the login, but incomplete. No desktop icons get shown. Also, I see the mouse cursor, but there is no mouse movement whatsoever. The desktop is effectively frozen and unresponsive, completely unusable. I can still ssh into the VM perfectly and operate on the command line, the VM itself is not frozen, just the GUI. If any journalctl outputs or logs needed from either version of the VM, I can provide them. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-04-13 (772 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. eth0 no wireless extensions. docker0 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=c7d3be02-30d6-49e4-8290-10c2678f35f9 ro video=hyperv_fb:1920x1080 ipv6.disable=1 video=hyperv_fb:1920x1080 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-42-generic N/A linux-backports-modules-5.19.0-42-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 RfKill: Tags: jammy Uname: Linux 5.19.0-42-generic x86_64 UpgradeStatus: Upgraded to jammy on 2023-02-16 (98 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 2473-5733-1385-7558-0781-8481-94 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 2020887] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2020887/+attachment/5675863/+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/2020887 Title: Ubuntu 22.04 after last update Gnome desktop shows up after login but freezes Status in linux package in Ubuntu: Incomplete Bug description: Using my Ubuntu 22.04.2 LTS VM under Microsoft Hyper-V and Windows 10 for some years now. Have a snapshot from April 29 with the latest updates up to that time, and that one worked perfectly. 1) Release: Description:Ubuntu 22.04.2 LTS Release:22.04 After the last updates the kernel version in the VM is: Linux 5.19.0-42-generic (before in the snapshot version of the VM where everything worked normally, kernel version was 5.19.0-40-generic) 2) From your own "FindRightPackage" link, I am guessing the problem is in Nautilus. Nautilus package version: nautilus: Instalados: 1:42.2-0ubuntu2.1 Candidato: 1:42.2-0ubuntu2.1 Tabla de versión: *** 1:42.2-0ubuntu2.1 500 500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 1:42.0-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What I expected to happen: The VM boots apparently normally, login GUI shows up, I can login, Gnome desktop shows up completely (desktop icons included), and I should be able to start moving the mouse and clicking on things to start using the system through the Gnome desktop. 4) What happened instead: I log in through the GUI, the gnome desktop appears after the login, but incomplete. No desktop icons get shown. Also, I see the mouse cursor, but there is no mouse movement whatsoever. The desktop is effectively frozen and unresponsive, completely unusable. I can still ssh into the VM perfectly and operate on the command line, the VM itself is not frozen, just the GUI. If any journalctl outputs or logs needed from either version of the VM, I can provide them. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-04-13 (772 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. eth0 no wireless extensions. docker0 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=c7d3be02-30d6-49e4-8290-10c2678f35f9 ro video=hyperv_fb:1920x1080 ipv6.disable=1 video=hyperv_fb:1920x1080 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-42-generic N/A linux-backports-modules-5.19.0-42-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 RfKill: Tags: jammy Uname: Linux 5.19.0-42-generic x86_64 UpgradeStatus: Upgraded to jammy on 2023-02-16 (98 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 2473-5733-1385-7558-0781-8481-94 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 2020887] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2020887/+attachment/5675864/+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/2020887 Title: Ubuntu 22.04 after last update Gnome desktop shows up after login but freezes Status in linux package in Ubuntu: Incomplete Bug description: Using my Ubuntu 22.04.2 LTS VM under Microsoft Hyper-V and Windows 10 for some years now. Have a snapshot from April 29 with the latest updates up to that time, and that one worked perfectly. 1) Release: Description:Ubuntu 22.04.2 LTS Release:22.04 After the last updates the kernel version in the VM is: Linux 5.19.0-42-generic (before in the snapshot version of the VM where everything worked normally, kernel version was 5.19.0-40-generic) 2) From your own "FindRightPackage" link, I am guessing the problem is in Nautilus. Nautilus package version: nautilus: Instalados: 1:42.2-0ubuntu2.1 Candidato: 1:42.2-0ubuntu2.1 Tabla de versión: *** 1:42.2-0ubuntu2.1 500 500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 1:42.0-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What I expected to happen: The VM boots apparently normally, login GUI shows up, I can login, Gnome desktop shows up completely (desktop icons included), and I should be able to start moving the mouse and clicking on things to start using the system through the Gnome desktop. 4) What happened instead: I log in through the GUI, the gnome desktop appears after the login, but incomplete. No desktop icons get shown. Also, I see the mouse cursor, but there is no mouse movement whatsoever. The desktop is effectively frozen and unresponsive, completely unusable. I can still ssh into the VM perfectly and operate on the command line, the VM itself is not frozen, just the GUI. If any journalctl outputs or logs needed from either version of the VM, I can provide them. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-04-13 (772 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. eth0 no wireless extensions. docker0 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=c7d3be02-30d6-49e4-8290-10c2678f35f9 ro video=hyperv_fb:1920x1080 ipv6.disable=1 video=hyperv_fb:1920x1080 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-42-generic N/A linux-backports-modules-5.19.0-42-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 RfKill: Tags: jammy Uname: Linux 5.19.0-42-generic x86_64 UpgradeStatus: Upgraded to jammy on 2023-02-16 (98 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 2473-5733-1385-7558-0781-8481-94 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 2020887] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2020887/+attachment/5675868/+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/2020887 Title: Ubuntu 22.04 after last update Gnome desktop shows up after login but freezes Status in linux package in Ubuntu: Incomplete Bug description: Using my Ubuntu 22.04.2 LTS VM under Microsoft Hyper-V and Windows 10 for some years now. Have a snapshot from April 29 with the latest updates up to that time, and that one worked perfectly. 1) Release: Description:Ubuntu 22.04.2 LTS Release:22.04 After the last updates the kernel version in the VM is: Linux 5.19.0-42-generic (before in the snapshot version of the VM where everything worked normally, kernel version was 5.19.0-40-generic) 2) From your own "FindRightPackage" link, I am guessing the problem is in Nautilus. Nautilus package version: nautilus: Instalados: 1:42.2-0ubuntu2.1 Candidato: 1:42.2-0ubuntu2.1 Tabla de versión: *** 1:42.2-0ubuntu2.1 500 500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 1:42.0-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What I expected to happen: The VM boots apparently normally, login GUI shows up, I can login, Gnome desktop shows up completely (desktop icons included), and I should be able to start moving the mouse and clicking on things to start using the system through the Gnome desktop. 4) What happened instead: I log in through the GUI, the gnome desktop appears after the login, but incomplete. No desktop icons get shown. Also, I see the mouse cursor, but there is no mouse movement whatsoever. The desktop is effectively frozen and unresponsive, completely unusable. I can still ssh into the VM perfectly and operate on the command line, the VM itself is not frozen, just the GUI. If any journalctl outputs or logs needed from either version of the VM, I can provide them. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-04-13 (772 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. eth0 no wireless extensions. docker0 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=c7d3be02-30d6-49e4-8290-10c2678f35f9 ro video=hyperv_fb:1920x1080 ipv6.disable=1 video=hyperv_fb:1920x1080 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-42-generic N/A linux-backports-modules-5.19.0-42-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 RfKill: Tags: jammy Uname: Linux 5.19.0-42-generic x86_64 UpgradeStatus: Upgraded to jammy on 2023-02-16 (98 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 2473-5733-1385-7558-0781-8481-94 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 2020887] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/2020887/+attachment/5675865/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2020887 Title: Ubuntu 22.04 after last update Gnome desktop shows up after login but freezes Status in linux package in Ubuntu: Incomplete Bug description: Using my Ubuntu 22.04.2 LTS VM under Microsoft Hyper-V and Windows 10 for some years now. Have a snapshot from April 29 with the latest updates up to that time, and that one worked perfectly. 1) Release: Description:Ubuntu 22.04.2 LTS Release:22.04 After the last updates the kernel version in the VM is: Linux 5.19.0-42-generic (before in the snapshot version of the VM where everything worked normally, kernel version was 5.19.0-40-generic) 2) From your own "FindRightPackage" link, I am guessing the problem is in Nautilus. Nautilus package version: nautilus: Instalados: 1:42.2-0ubuntu2.1 Candidato: 1:42.2-0ubuntu2.1 Tabla de versión: *** 1:42.2-0ubuntu2.1 500 500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 1:42.0-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What I expected to happen: The VM boots apparently normally, login GUI shows up, I can login, Gnome desktop shows up completely (desktop icons included), and I should be able to start moving the mouse and clicking on things to start using the system through the Gnome desktop. 4) What happened instead: I log in through the GUI, the gnome desktop appears after the login, but incomplete. No desktop icons get shown. Also, I see the mouse cursor, but there is no mouse movement whatsoever. The desktop is effectively frozen and unresponsive, completely unusable. I can still ssh into the VM perfectly and operate on the command line, the VM itself is not frozen, just the GUI. If any journalctl outputs or logs needed from either version of the VM, I can provide them. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-04-13 (772 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. eth0 no wireless extensions. docker0 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=c7d3be02-30d6-49e4-8290-10c2678f35f9 ro video=hyperv_fb:1920x1080 ipv6.disable=1 video=hyperv_fb:1920x1080 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-42-generic N/A linux-backports-modules-5.19.0-42-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 RfKill: Tags: jammy Uname: Linux 5.19.0-42-generic x86_64 UpgradeStatus: Upgraded to jammy on 2023-02-16 (98 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 2473-5733-1385-7558-0781-8481-94 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 2020887] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2020887/+attachment/5675867/+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/2020887 Title: Ubuntu 22.04 after last update Gnome desktop shows up after login but freezes Status in linux package in Ubuntu: Incomplete Bug description: Using my Ubuntu 22.04.2 LTS VM under Microsoft Hyper-V and Windows 10 for some years now. Have a snapshot from April 29 with the latest updates up to that time, and that one worked perfectly. 1) Release: Description:Ubuntu 22.04.2 LTS Release:22.04 After the last updates the kernel version in the VM is: Linux 5.19.0-42-generic (before in the snapshot version of the VM where everything worked normally, kernel version was 5.19.0-40-generic) 2) From your own "FindRightPackage" link, I am guessing the problem is in Nautilus. Nautilus package version: nautilus: Instalados: 1:42.2-0ubuntu2.1 Candidato: 1:42.2-0ubuntu2.1 Tabla de versión: *** 1:42.2-0ubuntu2.1 500 500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 1:42.0-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What I expected to happen: The VM boots apparently normally, login GUI shows up, I can login, Gnome desktop shows up completely (desktop icons included), and I should be able to start moving the mouse and clicking on things to start using the system through the Gnome desktop. 4) What happened instead: I log in through the GUI, the gnome desktop appears after the login, but incomplete. No desktop icons get shown. Also, I see the mouse cursor, but there is no mouse movement whatsoever. The desktop is effectively frozen and unresponsive, completely unusable. I can still ssh into the VM perfectly and operate on the command line, the VM itself is not frozen, just the GUI. If any journalctl outputs or logs needed from either version of the VM, I can provide them. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-04-13 (772 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. eth0 no wireless extensions. docker0 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=c7d3be02-30d6-49e4-8290-10c2678f35f9 ro video=hyperv_fb:1920x1080 ipv6.disable=1 video=hyperv_fb:1920x1080 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-42-generic N/A linux-backports-modules-5.19.0-42-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 RfKill: Tags: jammy Uname: Linux 5.19.0-42-generic x86_64 UpgradeStatus: Upgraded to jammy on 2023-02-16 (98 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 2473-5733-1385-7558-0781-8481-94 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 2020887] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/2020887/+attachment/5675857/+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/2020887 Title: Ubuntu 22.04 after last update Gnome desktop shows up after login but freezes Status in linux package in Ubuntu: Incomplete Bug description: Using my Ubuntu 22.04.2 LTS VM under Microsoft Hyper-V and Windows 10 for some years now. Have a snapshot from April 29 with the latest updates up to that time, and that one worked perfectly. 1) Release: Description:Ubuntu 22.04.2 LTS Release:22.04 After the last updates the kernel version in the VM is: Linux 5.19.0-42-generic (before in the snapshot version of the VM where everything worked normally, kernel version was 5.19.0-40-generic) 2) From your own "FindRightPackage" link, I am guessing the problem is in Nautilus. Nautilus package version: nautilus: Instalados: 1:42.2-0ubuntu2.1 Candidato: 1:42.2-0ubuntu2.1 Tabla de versión: *** 1:42.2-0ubuntu2.1 500 500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 1:42.0-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What I expected to happen: The VM boots apparently normally, login GUI shows up, I can login, Gnome desktop shows up completely (desktop icons included), and I should be able to start moving the mouse and clicking on things to start using the system through the Gnome desktop. 4) What happened instead: I log in through the GUI, the gnome desktop appears after the login, but incomplete. No desktop icons get shown. Also, I see the mouse cursor, but there is no mouse movement whatsoever. The desktop is effectively frozen and unresponsive, completely unusable. I can still ssh into the VM perfectly and operate on the command line, the VM itself is not frozen, just the GUI. If any journalctl outputs or logs needed from either version of the VM, I can provide them. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-04-13 (772 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. eth0 no wireless extensions. docker0 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=c7d3be02-30d6-49e4-8290-10c2678f35f9 ro video=hyperv_fb:1920x1080 ipv6.disable=1 video=hyperv_fb:1920x1080 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-42-generic N/A linux-backports-modules-5.19.0-42-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 RfKill: Tags: jammy Uname: Linux 5.19.0-42-generic x86_64 UpgradeStatus: Upgraded to jammy on 2023-02-16 (98 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 2473-5733-1385-7558-0781-8481-94 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 2020887] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2020887/+attachment/5675862/+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/2020887 Title: Ubuntu 22.04 after last update Gnome desktop shows up after login but freezes Status in linux package in Ubuntu: Incomplete Bug description: Using my Ubuntu 22.04.2 LTS VM under Microsoft Hyper-V and Windows 10 for some years now. Have a snapshot from April 29 with the latest updates up to that time, and that one worked perfectly. 1) Release: Description:Ubuntu 22.04.2 LTS Release:22.04 After the last updates the kernel version in the VM is: Linux 5.19.0-42-generic (before in the snapshot version of the VM where everything worked normally, kernel version was 5.19.0-40-generic) 2) From your own "FindRightPackage" link, I am guessing the problem is in Nautilus. Nautilus package version: nautilus: Instalados: 1:42.2-0ubuntu2.1 Candidato: 1:42.2-0ubuntu2.1 Tabla de versión: *** 1:42.2-0ubuntu2.1 500 500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 1:42.0-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What I expected to happen: The VM boots apparently normally, login GUI shows up, I can login, Gnome desktop shows up completely (desktop icons included), and I should be able to start moving the mouse and clicking on things to start using the system through the Gnome desktop. 4) What happened instead: I log in through the GUI, the gnome desktop appears after the login, but incomplete. No desktop icons get shown. Also, I see the mouse cursor, but there is no mouse movement whatsoever. The desktop is effectively frozen and unresponsive, completely unusable. I can still ssh into the VM perfectly and operate on the command line, the VM itself is not frozen, just the GUI. If any journalctl outputs or logs needed from either version of the VM, I can provide them. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-04-13 (772 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. eth0 no wireless extensions. docker0 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=c7d3be02-30d6-49e4-8290-10c2678f35f9 ro video=hyperv_fb:1920x1080 ipv6.disable=1 video=hyperv_fb:1920x1080 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-42-generic N/A linux-backports-modules-5.19.0-42-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 RfKill: Tags: jammy Uname: Linux 5.19.0-42-generic x86_64 UpgradeStatus: Upgraded to jammy on 2023-02-16 (98 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 2473-5733-1385-7558-0781-8481-94 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 2020887] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2020887/+attachment/5675861/+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/2020887 Title: Ubuntu 22.04 after last update Gnome desktop shows up after login but freezes Status in linux package in Ubuntu: Incomplete Bug description: Using my Ubuntu 22.04.2 LTS VM under Microsoft Hyper-V and Windows 10 for some years now. Have a snapshot from April 29 with the latest updates up to that time, and that one worked perfectly. 1) Release: Description:Ubuntu 22.04.2 LTS Release:22.04 After the last updates the kernel version in the VM is: Linux 5.19.0-42-generic (before in the snapshot version of the VM where everything worked normally, kernel version was 5.19.0-40-generic) 2) From your own "FindRightPackage" link, I am guessing the problem is in Nautilus. Nautilus package version: nautilus: Instalados: 1:42.2-0ubuntu2.1 Candidato: 1:42.2-0ubuntu2.1 Tabla de versión: *** 1:42.2-0ubuntu2.1 500 500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 1:42.0-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What I expected to happen: The VM boots apparently normally, login GUI shows up, I can login, Gnome desktop shows up completely (desktop icons included), and I should be able to start moving the mouse and clicking on things to start using the system through the Gnome desktop. 4) What happened instead: I log in through the GUI, the gnome desktop appears after the login, but incomplete. No desktop icons get shown. Also, I see the mouse cursor, but there is no mouse movement whatsoever. The desktop is effectively frozen and unresponsive, completely unusable. I can still ssh into the VM perfectly and operate on the command line, the VM itself is not frozen, just the GUI. If any journalctl outputs or logs needed from either version of the VM, I can provide them. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-04-13 (772 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. eth0 no wireless extensions. docker0 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=c7d3be02-30d6-49e4-8290-10c2678f35f9 ro video=hyperv_fb:1920x1080 ipv6.disable=1 video=hyperv_fb:1920x1080 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-42-generic N/A linux-backports-modules-5.19.0-42-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 RfKill: Tags: jammy Uname: Linux 5.19.0-42-generic x86_64 UpgradeStatus: Upgraded to jammy on 2023-02-16 (98 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 2473-5733-1385-7558-0781-8481-94 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 2020887] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2020887/+attachment/5675858/+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/2020887 Title: Ubuntu 22.04 after last update Gnome desktop shows up after login but freezes Status in linux package in Ubuntu: Incomplete Bug description: Using my Ubuntu 22.04.2 LTS VM under Microsoft Hyper-V and Windows 10 for some years now. Have a snapshot from April 29 with the latest updates up to that time, and that one worked perfectly. 1) Release: Description:Ubuntu 22.04.2 LTS Release:22.04 After the last updates the kernel version in the VM is: Linux 5.19.0-42-generic (before in the snapshot version of the VM where everything worked normally, kernel version was 5.19.0-40-generic) 2) From your own "FindRightPackage" link, I am guessing the problem is in Nautilus. Nautilus package version: nautilus: Instalados: 1:42.2-0ubuntu2.1 Candidato: 1:42.2-0ubuntu2.1 Tabla de versión: *** 1:42.2-0ubuntu2.1 500 500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 1:42.0-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What I expected to happen: The VM boots apparently normally, login GUI shows up, I can login, Gnome desktop shows up completely (desktop icons included), and I should be able to start moving the mouse and clicking on things to start using the system through the Gnome desktop. 4) What happened instead: I log in through the GUI, the gnome desktop appears after the login, but incomplete. No desktop icons get shown. Also, I see the mouse cursor, but there is no mouse movement whatsoever. The desktop is effectively frozen and unresponsive, completely unusable. I can still ssh into the VM perfectly and operate on the command line, the VM itself is not frozen, just the GUI. If any journalctl outputs or logs needed from either version of the VM, I can provide them. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-04-13 (772 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. eth0 no wireless extensions. docker0 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=c7d3be02-30d6-49e4-8290-10c2678f35f9 ro video=hyperv_fb:1920x1080 ipv6.disable=1 video=hyperv_fb:1920x1080 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-42-generic N/A linux-backports-modules-5.19.0-42-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 RfKill: Tags: jammy Uname: Linux 5.19.0-42-generic x86_64 UpgradeStatus: Upgraded to jammy on 2023-02-16 (98 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 2473-5733-1385-7558-0781-8481-94 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 2020887] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2020887/+attachment/5675860/+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/2020887 Title: Ubuntu 22.04 after last update Gnome desktop shows up after login but freezes Status in linux package in Ubuntu: Incomplete Bug description: Using my Ubuntu 22.04.2 LTS VM under Microsoft Hyper-V and Windows 10 for some years now. Have a snapshot from April 29 with the latest updates up to that time, and that one worked perfectly. 1) Release: Description:Ubuntu 22.04.2 LTS Release:22.04 After the last updates the kernel version in the VM is: Linux 5.19.0-42-generic (before in the snapshot version of the VM where everything worked normally, kernel version was 5.19.0-40-generic) 2) From your own "FindRightPackage" link, I am guessing the problem is in Nautilus. Nautilus package version: nautilus: Instalados: 1:42.2-0ubuntu2.1 Candidato: 1:42.2-0ubuntu2.1 Tabla de versión: *** 1:42.2-0ubuntu2.1 500 500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 1:42.0-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What I expected to happen: The VM boots apparently normally, login GUI shows up, I can login, Gnome desktop shows up completely (desktop icons included), and I should be able to start moving the mouse and clicking on things to start using the system through the Gnome desktop. 4) What happened instead: I log in through the GUI, the gnome desktop appears after the login, but incomplete. No desktop icons get shown. Also, I see the mouse cursor, but there is no mouse movement whatsoever. The desktop is effectively frozen and unresponsive, completely unusable. I can still ssh into the VM perfectly and operate on the command line, the VM itself is not frozen, just the GUI. If any journalctl outputs or logs needed from either version of the VM, I can provide them. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-04-13 (772 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. eth0 no wireless extensions. docker0 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=c7d3be02-30d6-49e4-8290-10c2678f35f9 ro video=hyperv_fb:1920x1080 ipv6.disable=1 video=hyperv_fb:1920x1080 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-42-generic N/A linux-backports-modules-5.19.0-42-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 RfKill: Tags: jammy Uname: Linux 5.19.0-42-generic x86_64 UpgradeStatus: Upgraded to jammy on 2023-02-16 (98 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 2473-5733-1385-7558-0781-8481-94 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 2020887] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/2020887/+attachment/5675859/+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/2020887 Title: Ubuntu 22.04 after last update Gnome desktop shows up after login but freezes Status in linux package in Ubuntu: Incomplete Bug description: Using my Ubuntu 22.04.2 LTS VM under Microsoft Hyper-V and Windows 10 for some years now. Have a snapshot from April 29 with the latest updates up to that time, and that one worked perfectly. 1) Release: Description:Ubuntu 22.04.2 LTS Release:22.04 After the last updates the kernel version in the VM is: Linux 5.19.0-42-generic (before in the snapshot version of the VM where everything worked normally, kernel version was 5.19.0-40-generic) 2) From your own "FindRightPackage" link, I am guessing the problem is in Nautilus. Nautilus package version: nautilus: Instalados: 1:42.2-0ubuntu2.1 Candidato: 1:42.2-0ubuntu2.1 Tabla de versión: *** 1:42.2-0ubuntu2.1 500 500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 1:42.0-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What I expected to happen: The VM boots apparently normally, login GUI shows up, I can login, Gnome desktop shows up completely (desktop icons included), and I should be able to start moving the mouse and clicking on things to start using the system through the Gnome desktop. 4) What happened instead: I log in through the GUI, the gnome desktop appears after the login, but incomplete. No desktop icons get shown. Also, I see the mouse cursor, but there is no mouse movement whatsoever. The desktop is effectively frozen and unresponsive, completely unusable. I can still ssh into the VM perfectly and operate on the command line, the VM itself is not frozen, just the GUI. If any journalctl outputs or logs needed from either version of the VM, I can provide them. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-04-13 (772 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. eth0 no wireless extensions. docker0 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=c7d3be02-30d6-49e4-8290-10c2678f35f9 ro video=hyperv_fb:1920x1080 ipv6.disable=1 video=hyperv_fb:1920x1080 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-42-generic N/A linux-backports-modules-5.19.0-42-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 RfKill: Tags: jammy Uname: Linux 5.19.0-42-generic x86_64 UpgradeStatus: Upgraded to jammy on 2023-02-16 (98 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 2473-5733-1385-7558-0781-8481-94 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 2020887] Re: Ubuntu 22.04 after last update Gnome desktop shows up after login but freezes
apport information ** Tags added: apport-collected jammy ** Description changed: Using my Ubuntu 22.04.2 LTS VM under Microsoft Hyper-V and Windows 10 for some years now. Have a snapshot from April 29 with the latest updates up to that time, and that one worked perfectly. 1) Release: Description:Ubuntu 22.04.2 LTS Release:22.04 After the last updates the kernel version in the VM is: Linux 5.19.0-42-generic (before in the snapshot version of the VM where everything worked normally, kernel version was 5.19.0-40-generic) 2) From your own "FindRightPackage" link, I am guessing the problem is in Nautilus. Nautilus package version: nautilus: Instalados: 1:42.2-0ubuntu2.1 Candidato: 1:42.2-0ubuntu2.1 Tabla de versión: *** 1:42.2-0ubuntu2.1 500 500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 1:42.0-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What I expected to happen: The VM boots apparently normally, login GUI shows up, I can login, Gnome desktop shows up completely (desktop icons included), and I should be able to start moving the mouse and clicking on things to start using the system through the Gnome desktop. 4) What happened instead: I log in through the GUI, the gnome desktop appears after the login, but incomplete. No desktop icons get shown. Also, I see the mouse cursor, but there is no mouse movement whatsoever. The desktop is effectively frozen and unresponsive, completely unusable. I can still ssh into the VM perfectly and operate on the command line, the VM itself is not frozen, just the GUI. - If any journalctl outputs or logs needed from either version of the VM, - I can provide them. + If any journalctl outputs or logs needed from either version of the VM, I can provide them. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.5 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CasperMD5CheckResult: unknown + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2021-04-13 (772 days ago) + InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) + IwConfig: + lono wireless extensions. + + eth0 no wireless extensions. + + docker0 no wireless extensions. + Lspci: + + Lspci-vt: -[:00]- + Lsusb: Error: command ['lsusb'] failed with exit code 1: + Lsusb-t: + + Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: + MachineType: Microsoft Corporation Virtual Machine + Package: linux (not installed) + ProcFB: 0 hyperv_fb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic root=UUID=c7d3be02-30d6-49e4-8290-10c2678f35f9 ro video=hyperv_fb:1920x1080 ipv6.disable=1 video=hyperv_fb:1920x1080 + ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 + RelatedPackageVersions: + linux-restricted-modules-5.19.0-42-generic N/A + linux-backports-modules-5.19.0-42-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.13 + RfKill: + + Tags: jammy + Uname: Linux 5.19.0-42-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2023-02-16 (98 days ago) + UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 11/01/2019 + dmi.bios.release: 4.0 + dmi.bios.vendor: Microsoft Corporation + dmi.bios.version: Hyper-V UEFI Release v4.0 + dmi.board.asset.tag: None + dmi.board.name: Virtual Machine + dmi.board.vendor: Microsoft Corporation + dmi.board.version: Hyper-V UEFI Release v4.0 + dmi.chassis.asset.tag: 2473-5733-1385-7558-0781-8481-94 + dmi.chassis.type: 3 + dmi.chassis.vendor: Microsoft Corporation + dmi.chassis.version: Hyper-V UEFI Release v4.0 + dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone: + dmi.product.family: Virtual Machine + dmi.product.name: Virtual Machine + dmi.product.sku: None + dmi.product.version: Hyper-V UEFI Release v4.0 + dmi.sys.vendor: Microsoft Corporation ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2020887/+attachment/5675856/+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/2020887 Title: Ubuntu 22.04 after last update Gnome desktop shows up after login but freezes Status in linux package in Ubuntu: Incomplete Bug description: Using my Ubuntu 22.04.2 LTS VM under Microsoft Hyper-V and Windows 10 for some years now. Have a
[Kernel-packages] [Bug 2020887] 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 2020887 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/2020887 Title: Ubuntu 22.04 after last update Gnome desktop shows up after login but freezes Status in linux package in Ubuntu: Incomplete Bug description: Using my Ubuntu 22.04.2 LTS VM under Microsoft Hyper-V and Windows 10 for some years now. Have a snapshot from April 29 with the latest updates up to that time, and that one worked perfectly. 1) Release: Description:Ubuntu 22.04.2 LTS Release:22.04 After the last updates the kernel version in the VM is: Linux 5.19.0-42-generic (before in the snapshot version of the VM where everything worked normally, kernel version was 5.19.0-40-generic) 2) From your own "FindRightPackage" link, I am guessing the problem is in Nautilus. Nautilus package version: nautilus: Instalados: 1:42.2-0ubuntu2.1 Candidato: 1:42.2-0ubuntu2.1 Tabla de versión: *** 1:42.2-0ubuntu2.1 500 500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 1:42.0-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What I expected to happen: The VM boots apparently normally, login GUI shows up, I can login, Gnome desktop shows up completely (desktop icons included), and I should be able to start moving the mouse and clicking on things to start using the system through the Gnome desktop. 4) What happened instead: I log in through the GUI, the gnome desktop appears after the login, but incomplete. No desktop icons get shown. Also, I see the mouse cursor, but there is no mouse movement whatsoever. The desktop is effectively frozen and unresponsive, completely unusable. I can still ssh into the VM perfectly and operate on the command line, the VM itself is not frozen, just the GUI. If any journalctl outputs or logs needed from either version of the VM, I can provide them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020887] [NEW] Ubuntu 22.04 after last update Gnome desktop shows up after login but freezes
Public bug reported: Using my Ubuntu 22.04.2 LTS VM under Microsoft Hyper-V and Windows 10 for some years now. Have a snapshot from April 29 with the latest updates up to that time, and that one worked perfectly. 1) Release: Description:Ubuntu 22.04.2 LTS Release:22.04 After the last updates the kernel version in the VM is: Linux 5.19.0-42-generic (before in the snapshot version of the VM where everything worked normally, kernel version was 5.19.0-40-generic) 2) From your own "FindRightPackage" link, I am guessing the problem is in Nautilus. Nautilus package version: nautilus: Instalados: 1:42.2-0ubuntu2.1 Candidato: 1:42.2-0ubuntu2.1 Tabla de versión: *** 1:42.2-0ubuntu2.1 500 500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 1:42.0-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What I expected to happen: The VM boots apparently normally, login GUI shows up, I can login, Gnome desktop shows up completely (desktop icons included), and I should be able to start moving the mouse and clicking on things to start using the system through the Gnome desktop. 4) What happened instead: I log in through the GUI, the gnome desktop appears after the login, but incomplete. No desktop icons get shown. Also, I see the mouse cursor, but there is no mouse movement whatsoever. The desktop is effectively frozen and unresponsive, completely unusable. I can still ssh into the VM perfectly and operate on the command line, the VM itself is not frozen, just the GUI. If any journalctl outputs or logs needed from either version of the VM, I can provide them. ** 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/2020887 Title: Ubuntu 22.04 after last update Gnome desktop shows up after login but freezes Status in linux package in Ubuntu: New Bug description: Using my Ubuntu 22.04.2 LTS VM under Microsoft Hyper-V and Windows 10 for some years now. Have a snapshot from April 29 with the latest updates up to that time, and that one worked perfectly. 1) Release: Description:Ubuntu 22.04.2 LTS Release:22.04 After the last updates the kernel version in the VM is: Linux 5.19.0-42-generic (before in the snapshot version of the VM where everything worked normally, kernel version was 5.19.0-40-generic) 2) From your own "FindRightPackage" link, I am guessing the problem is in Nautilus. Nautilus package version: nautilus: Instalados: 1:42.2-0ubuntu2.1 Candidato: 1:42.2-0ubuntu2.1 Tabla de versión: *** 1:42.2-0ubuntu2.1 500 500 http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 1:42.0-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What I expected to happen: The VM boots apparently normally, login GUI shows up, I can login, Gnome desktop shows up completely (desktop icons included), and I should be able to start moving the mouse and clicking on things to start using the system through the Gnome desktop. 4) What happened instead: I log in through the GUI, the gnome desktop appears after the login, but incomplete. No desktop icons get shown. Also, I see the mouse cursor, but there is no mouse movement whatsoever. The desktop is effectively frozen and unresponsive, completely unusable. I can still ssh into the VM perfectly and operate on the command line, the VM itself is not frozen, just the GUI. If any journalctl outputs or logs needed from either version of the VM, I can provide them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
@BlindBO I have same problem my kernel is 6.2.0-20-generic and ubuntu version is 23.04 for same camera Mode No is - 0408:4033 Quanta Computer, Inc. ACER HD User Facing I have issues webcam not working can you provide better solutions with clear instructions I follow your instructions and give me error showing me error The kernel was built by: x86_64-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0 You are using: gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0 CC [M] /home/raj/uvc/uvc_driver.o /home/raj/uvc/uvc_driver.c:17:10: fatal error: linux/usb/uvc.h: No such file or directory 17 | #include | ^ compilation terminated. -- 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/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giuliano 2142 F pulseaudio /dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio /dev/snd/controlC0: giuliano 2142 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-03 (66 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-55 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware
[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
@raj better ask BlindBO some help, as only you two have 04033 version and kernel 6.x BuildBO ask to install build-essential from ubuntu repo) Did you install it ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giuliano 2142 F pulseaudio /dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio /dev/snd/controlC0: giuliano 2142 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-03 (66 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-55 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 Tags: jammy Uname: Linux 5.15.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 04/20/2022 dmi.bios.release: 1.6 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ignis_ADH dmi.board.vendor: ADL
[Kernel-packages] [Bug 2020656] Re: system freeze (cpu fan goes high)
new freeze after about 18h of uptime last messages from journalctl -f (around 2 to 3 min before the freeze) mai 26 10:38:46 jf-ThinkPad-P14s kernel: perf: interrupt took too long (3199 > 3165), lowering kernel.perf_event_max_sample_rate to 62500 mai 26 10:39:30 jf-ThinkPad-P14s gnome-keyring-daemon[15315]: asked to register item /org/freedesktop/secrets/collection/login/2, but it's already registered mai 26 10:39:30 jf-ThinkPad-P14s gnome-keyring-d[15315]: asked to register item /org/freedesktop/secrets/collection/login/2, but it's already registered apt dist-upgrade done this morning system load was low, reading a file in vscode through ssh… I don't really know what to do, I wish I can be sure it's not a hardware problem? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2020656 Title: system freeze (cpu fan goes high) Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: More than once a day the system totally freeze. CPU fan then goes higher and higher. Does not seem to be related to system load as yesterday it happend during lunch break. Today's journalctl -b -1 last message is mai 24 11:50:06 ThinkPad-P14s kernel: watchdog: BUG: soft lockup - CPU#9 stuck for 167s! [opt ax7ixzwwoey:158586] There are many more of the same kind just before $ lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 $ apt-cache policy linux-image-5.19.0-42-generic linux-image-5.19.0-42-generic: Installé : 5.19.0-42.43~22.04.1 Candidat : 5.19.0-42.43~22.04.1 Table de version : *** 5.19.0-42.43~22.04.1 500 500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status Note this problem was present before last kernel updates ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-42-generic 5.19.0-42.43~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 24 12:00:08 2023 InstallationDate: Installed on 2023-03-25 (59 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: TERM=alacritty PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 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.19/+bug/2020656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
showing me error The kernel was built by: x86_64-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0 You are using: gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0 CC [M] /home/raj/uvc/uvc_driver.o /home/raj/uvc/uvc_driver.c:17:10: fatal error: linux/usb/uvc.h: No such file or directory 17 | #include | ^ compilation terminated. -- 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/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giuliano 2142 F pulseaudio /dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio /dev/snd/controlC0: giuliano 2142 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-03 (66 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-55 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 Tags: jammy Uname: Linux 5.15.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True
[Kernel-packages] [Bug 2020757] Re: Kernel BUG (null ptr dereference) with linux-image-5.19.0-42-generic (HWE kernel on 22.04)
The same issue with VirtualBox running on Windows (stupid corporate requirements). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2020757 Title: Kernel BUG (null ptr dereference) with linux-image-5.19.0-42-generic (HWE kernel on 22.04) Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: I use Ubuntu 22.04 in VMWare Player 17.0.2 (Windows host, due to corporate IT...). I installed the HWE kernel since I have an Intel CPU with P/E-cores. 3D acceleration is enabled in VMWare. With linux-image-5.19.0-41-generic it is rock solid. With linux- image-5.19.0-42-generic it invariably crashes after anything between a minute and an hour. In the journalctl after rebooting it showed that X.Org had crashed followed by a Kernel BUG/Oops due to NULL pointer dereference in drm_gem_object_release_handle. A journalctl log from the Xorg crash up until the kernel OOPS has been attached to this case. This issue happened twice with this kernel. In addition, after trying to reproduce it with kdump tools installed, I got a different issue: refcount_t: saturated; leaking memory. in the log, leading to the OOM killing everything on the system, including (based on what was printed on the terminal), systemd-udevd and journald. That OOM killing never made it into the journal however, as can be expected. I have attached what I could get from the journal for this case as well. One thing that helped trigger this bug (but not every time) was launching Firefox, but once it didn't crash from that and only crashed much much later. Unfortunately I could not get ubuntu-bug to work for this case. I tried "ubuntu-bug --package linux-image-5.19.0-42-generic" but it did absolutely nothing. I'm happy to provide any additional information you require however. $ lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 $ apt-cache policy linux-generic-hwe-22.04 linux-generic-hwe-22.04: Installed: 5.19.0.42.43~22.04.15 Candidate: 5.19.0.42.43~22.04.15 Version table: *** 5.19.0.42.43~22.04.15 500 500 http://se.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.25.27 500 500 http://se.archive.ubuntu.com/ubuntu jammy/main amd64 Packages $ apt-cache policy linux-image-5.19.0-42-generic linux-image-5.19.0-42-generic: Installed: 5.19.0-42.43~22.04.1 Candidate: 5.19.0-42.43~22.04.1 Version table: *** 5.19.0-42.43~22.04.1 500 500 http://se.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: No crash. What happened instead: The crash in the attached log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2020757/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
@raj As you are using kernel version 6.x, consider using solution at #45 fron @BlindBo My kernel version is 5.x follow @blindBo instructions at #45 Also change camera to 4033 model in the source of uvc_driver.c. Let us know if it work. Giuliano -- 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/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giuliano 2142 F pulseaudio /dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio /dev/snd/controlC0: giuliano 2142 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-03 (66 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-55 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 Tags: jammy Uname: Linux 5.15.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 04/20/2022 dmi.bios.release: 1.6 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag:
