[Kernel-packages] [Bug 2040524] Re: openvswitch fails on raspberry pi 4
** Also affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2040524 Title: openvswitch fails on raspberry pi 4 Status in microovn: New Status in linux-raspi package in Ubuntu: New Bug description: I have a homelab and I'm experimenting with adding arm nodes to my existing cluster. MicroOVN works fine on my x86_64 nodes but fails on my arm nodes (raspberry pi 4). I am using microovn 22.03/stable (rev 295). When I run "microovn init" on the arm nodes, I get the error Error: Post "http://control.socket/cluster/control": context deadline exceeded The output from "snap services microovn" is: Service Startup Current Notes microovn.central disabled inactive - microovn.chassis enabled active- microovn.daemon enabled active- microovn.ovn-northd disabled inactive - microovn.ovn-ovsdb-server-nb disabled inactive - microovn.ovn-ovsdb-server-sb disabled inactive - microovn.refresh-expiring-certs enabled inactive timer-activated microovn.switch enabled inactive - The output from "systemctl | grep ovn" is: run-snapd-ns-microovn.mnt.mount loaded active mounted /run/snapd/ns/microovn.mnt snap-microovn-301.mount loaded active mounted Mount unit for microovn, revision 301 snap.microovn.chassis.service loaded active running Service for snap application microovn.chassis snap.microovn.daemon.service loaded active running Service for snap application microovn.daemon ● snap.microovn.switch.service loaded failed failedService for snap application microovn.switch snap.microovn.refresh-expiring-certs.timer loaded active waiting Timer refresh-expiring-certs for snap application microovn.refresh-expiring-certs The output from "journalctl -b -u snap.microovn.switch.service" is (in relevant part): Oct 25 10:55:27 pi01 systemd[1]: Started Service for snap application microovn.switch. Oct 25 10:55:28 pi01 microovn.switch[7315]: * /var/snap/microovn/common/data/switch/db/conf.db does not exist Oct 25 10:55:28 pi01 microovn.switch[7315]: * Creating empty database /var/snap/microovn/common/data/switch/db/conf.db Oct 25 10:55:28 pi01 microovn.switch[7315]: * Starting ovsdb-server Oct 25 10:55:28 pi01 ovs-vsctl[7338]: ovs|1|vsctl|INFO|Called as ovs-vsctl --no-wait -- init -- set Open_vSwitch . db-version=8.3.0 Oct 25 10:55:28 pi01 ovs-vsctl[7348]: ovs|1|vsctl|INFO|Called as ovs-vsctl --no-wait set Open_vSwitch . ovs-version=2.17.7 "external-ids:system-id=\"pi01\"" "external-ids:rundir=\"/var/snap/microovn/> Oct 25 10:55:28 pi01 microovn.switch[7315]: * Configuring Open vSwitch system IDs Oct 25 10:55:28 pi01 microovn.switch[7380]: /snap/microovn/301/share/openvswitch/scripts/ovs-kmod-ctl: 112: modprobe: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/microovn/+bug/2040524/+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 2040280] Re: CVE-2022-40982 on Ubuntu Mantic Linux Kernel still not fixed
The kernel mitigations for this vulnerability were provided back in August, when Mantic was still the development released. So, though the Mantic target kernel had not been in the release pocket yet, the fixes were there, so it was marked as pending for the development release. When Mantic got released, the status was not updated fast enough. So thank you for bringing this up, this has been fixed in our CVE tracker and CVE web pages now. Cascardo. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: intel-microcode (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu Mantic) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2040280 Title: CVE-2022-40982 on Ubuntu Mantic Linux Kernel still not fixed Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in intel-microcode source package in Mantic: New Status in linux source package in Mantic: Fix Released Bug description: An pro fix CVE-2022-40982 gives me an ✘ CVE-2022-40982 is not resolved. Strangely without a specific description of the affected package: "1 package is still affected: linux" But, when i look up the CVW here: https://ubuntu.com/security/CVE-2022-40982 it is mentioned that the fix is contained with the new version of intel-microcode: mantic Released (3.20230808.1) And that's the version i seem to have installed: apt show intel-microcode: "Package: intel-microcode Version: 3.20230808.1" Any Ideas on that? ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: intel-microcode 3.20230808.1 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Oct 24 16:05:24 2023 InstallationDate: Installed on 2022-08-05 (445 days ago) InstallationMedia: Ubuntu Unity 22.04 SourcePackage: intel-microcode UpgradeStatus: Upgraded to mantic on 2023-10-12 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/2040280/+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 2015670] Re: [r8169] Kernel loop PCIe Bus Error on RTL810xE
still same problem on Noble installed from Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231118) -- 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/2015670 Title: [r8169] Kernel loop PCIe Bus Error on RTL810xE Status in linux package in Ubuntu: Confirmed Bug description: Kernel loop after login This happens with both kernels 6.2.0-18 and 6.2.0-19 on 2 different partitions of same PC: Partition installed from beta and partition from ISO dated 04/02. No problem on same PC different partitions of same disk with Ubuntu Focal, Jammy and Kinetic Problem does not occur with kernel 5.19.17-051917-generic installed from https://kernel.ubuntu.com/~kernel-ppa/mainline/ Adding journalctl -b related to the problem note: I opened another bug for this problem blaming gnome-shell but it's wrong https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015540 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-19-generic 6.2.0-19.19 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: corrado1511 F wireplumber /dev/snd/seq:corrado1508 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 9 09:33:06 2023 InstallationDate: Installed on 2023-04-07 (1 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230402) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 002: ID 145f:02b5 Trust Trust Wireless Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3793 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-19-generic root=UUID=78239576-b8af-4c66-bf15-8d5ee9a63d35 ro quiet splash RelatedPackageVersions: linux-restricted-modules-6.2.0-19-generic N/A linux-backports-modules-6.2.0-19-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2019 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0C1PF2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd12/17/2019:br1.5:svnDellInc.:pnInspiron3793:pvr:rvnDellInc.:rn0C1PF2:rvrA00:cvnDellInc.:ct10:cvr:sku097A: dmi.product.family: Inspiron dmi.product.name: Inspiron 3793 dmi.product.sku: 097A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015670/+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 2043884] [NEW] package linux-intel-iotg-tools-common 5.15.0-1040.46 [modified: usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf-archive.1.gz usr/share/man/man1/perf
Public bug reported: paula@paula-pc:~/Downloads$ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages have been kept back: gjs libgjs0g ubuntu-advantage-tools The following packages will be upgraded: apt apt-utils firmware-sof-signed intel-microcode libapt-pkg6.0 libprocps8 linux-firmware linux-intel-iotg-tools-common procps ubuntu-drivers-common 10 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. 4 standard LTS security updates Need to get 268 MB/268 MB of archives. After this operation, 9.895 kB of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://es.archive.ubuntu.com/ubuntu jammy-updates/main amd64 libapt-pkg6.0 amd64 2.4.11 [912 kB] Get:2 http://es.archive.ubuntu.com/ubuntu jammy-updates/main amd64 apt amd64 2.4.11 [1.363 kB] Get:3 http://es.archive.ubuntu.com/ubuntu jammy-updates/main amd64 apt-utils amd64 2.4.11 [211 kB] Get:4 http://es.archive.ubuntu.com/ubuntu jammy-updates/main amd64 ubuntu-drivers-common amd64 1:0.9.6.2~0.22.04.6 [58,7 kB] Get:5 http://es.archive.ubuntu.com/ubuntu jammy-updates/main amd64 libprocps8 amd64 2:3.3.17-6ubuntu2.1 [36,2 kB] Get:6 http://es.archive.ubuntu.com/ubuntu jammy-updates/main amd64 procps amd64 2:3.3.17-6ubuntu2.1 [378 kB] Get:7 http://es.archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 firmware-sof-signed all 2.0-1ubuntu4.2 [821 kB] Get:8 http://es.archive.ubuntu.com/ubuntu jammy-updates/main amd64 linux-firmware all 20220329.git681281e4-0ubuntu3.22 [258 MB] Get:9 http://es.archive.ubuntu.com/ubuntu jammy-updates/main amd64 intel-microcode amd64 3.20231114.0ubuntu0.22.04.1 [6.047 kB] Fetched 268 MB in 49s (5.460 kB/s) Preconfiguring packages ... (Reading database ... 204747 files and directories currently installed.) Preparing to unpack .../libapt-pkg6.0_2.4.11_amd64.deb ... Unpacking libapt-pkg6.0:amd64 (2.4.11) over (2.4.10) ... Setting up libapt-pkg6.0:amd64 (2.4.11) ... (Reading database ... 204747 files and directories currently installed.) Preparing to unpack .../archives/apt_2.4.11_amd64.deb ... Unpacking apt (2.4.11) over (2.4.10) ... Setting up apt (2.4.11) ... (Reading database ... 204745 files and directories currently installed.) Preparing to unpack .../0-apt-utils_2.4.11_amd64.deb ... Unpacking apt-utils (2.4.11) over (2.4.10) ... Preparing to unpack .../1-ubuntu-drivers-common_1%3a0.9.6.2~0.22.04.6_amd64.deb ... Unpacking ubuntu-drivers-common (1:0.9.6.2~0.22.04.6) over (1:0.9.6.2~0.22.04.4) ... Preparing to unpack .../2-libprocps8_2%3a3.3.17-6ubuntu2.1_amd64.deb ... Unpacking libprocps8:amd64 (2:3.3.17-6ubuntu2.1) over (2:3.3.17-6ubuntu2) ... Preparing to unpack .../3-procps_2%3a3.3.17-6ubuntu2.1_amd64.deb ... Unpacking procps (2:3.3.17-6ubuntu2.1) over (2:3.3.17-6ubuntu2) ... Preparing to unpack .../4-firmware-sof-signed_2.0-1ubuntu4.2_all.deb ... Unpacking firmware-sof-signed (2.0-1ubuntu4.2) over (2.0-1ubuntu4.1) ... Preparing to unpack .../5-linux-firmware_20220329.git681281e4-0ubuntu3.22_all.de b ... Unpacking linux-firmware (20220329.git681281e4-0ubuntu3.22) over (20220329.git68 1281e4-0ubuntu3.21) ... Preparing to unpack .../6-linux-intel-iotg-tools-common_5.15.0-1043.49_all.deb . .. Unpacking linux-intel-iotg-tools-common (5.15.0-1043.49) over (5.15.0-1040.46) . .. dpkg: error processing archive /tmp/apt-dpkg-install-UXSDLH/6-linux-intel-iotg-t ools-common_5.15.0-1043.49_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-co mmon 5.15.0-88.98 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../7-intel-microcode_3.20231114.0ubuntu0.22.04.1_amd64.deb ... Unpacking intel-microcode (3.20231114.0ubuntu0.22.04.1) over (3.20230808.0ubuntu 0.22.04.1) ... Errors were encountered while processing: /tmp/apt-dpkg-install-UXSDLH/6-linux-intel-iotg-tools-common_5.15.0-1043.49_all .deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Nov 18 12:47:51 2023 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-88.98 InstallationDate: Installed on 2023-09-27 (51 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all Python3Details: /usr/local/bin/python3.11, Python 3.11.5, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: linux-intel-iotg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-intel-iotg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You r
[Kernel-packages] [Bug 2040106] Re: firmware broken after upgrade to Ubuntu 23.10
On my Dell XPS 13 I installed the new kernel 6.5 because I still was on
5.14. With that new kernel I don't have wifi and even no wired internet.
This didn't help at all.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2040106
Title:
firmware broken after upgrade to Ubuntu 23.10
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-meta package in Ubuntu:
Confirmed
Bug description:
[ Impact ]
* Focal preinstalled systems with OEM kernel, if force upgraded to
interim releases, before transitional packages have been made
available resulted in systems having been stuck on focal oem kernel
and not getting any kernel updates.
* Reintroduce all focal oem kernel transitionals to trigger upgrade
to hwe kernel in all stable releases for the oem-20.04* kernels
[ Test Plan ]
* Starting with focal, install linux-image-oem-20.04*
linux-headers-oem-20.04* metapackages
* Force upgrade to mantic
* Observe that all oem-20.04 meta packages got upgraded and rolled to
generic hwe kernel (of appropriate version for jammy & mantic)
[ Where problems could occur ]
* This may trigger dkms package recompilation, and nvidia driver missmatches
* Likely users will have to rerun `ubuntu-drivers` or use additional drivers
GUI to reinstall nvidia drivers
* Users may experience jump from v5.10 kernel to v6.5 kernel
[ Other Info ]
* Original bug report
After upgrading from Ubuntu 23.04 to 23.10 on a Dell Precision 5560, wifi and
bluetooth did not work anymore.
Looking at the dmesg output I saw this:
Direct firmware load for iwlwifi-QuZ-a0-hr-b0-59.ucode failed with error -2
..
Direct firmware load for iwlwifi-QuZ-a0-hr-b0-39.ucode failed with error -2
no suitable firmware found!
minimum version required: iwlwifi-QuZ-a0-hr-b0-39
minimum version required: iwlwifi-QuZ-a0-hr-b0-59
These files did seem to exist in /lib/firmware.
I did sudo apt install linux-firmware/mantic --reinstall
Which did not fix it.
I manually overwrote the iwlwifi... files with the corresponding files from
linux-firmware-20230804.tar.gz and this did fix the issue.
I did the same for ibt-19-0-4.sfi and that fixed the bluetooth issue.
So my best guess is that something is wrong in the latest firmware
package.
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 23.10
Release: 23.10
Codename: mantic
apt-cache policy linux-firmware
linux-firmware:
Installed: 20230919.git3672ccab-0ubuntu2.1
Candidate: 20230919.git3672ccab-0ubuntu2.1
Version table:
*** 20230919.git3672ccab-0ubuntu2.1 500
500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
ProcVersionSignature: Ubuntu 5.10.0-1053.55-oem 5.10.83
Uname: Linux 5.10.0-1053-oem x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: joep 2545 F wireplumber
/dev/snd/controlC0: joep 2545 F wireplumber
/dev/snd/seq:joep 2537 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 22 15:19:18 2023
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85
InstallationDate: Installed on 2021-10-16 (736 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1053-oem
root=UUID=482b1305-d8fa-4fb1-be20-ae911e6a4def ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.10.0-1053-oem N/A
linux-backports-modules-5.10.0-1053-oem N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux-firmware
UpgradeStatus: Upgraded to mantic on 2023-10-22 (0 days ago)
dmi.bios.date: 07/13/2023
dmi.bios.release: 1.22
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.22.0
dmi.board.name: 0NG7N9
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.22.0:bd07/13/2023:br1.22:svnDellInc.:pnPrecision5560:pvr:sku0A62:rvnDellInc.:rn0NG7N9:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 5560
dmi.product.sku: 0A62
dmi.sys.vendor: Dell Inc.
To manage notificatio
[Kernel-packages] [Bug 1953554] Re: NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out
Just my two cents. I have the same issue with to different usb ethernet adapters on a rasppi 4b with ubuntu 5.15.0-1042-raspi #45-Ubuntu SMP PREEMPT Thu Oct 12 09:20:16 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux 22.04.3 LTS (Jammy Jellyfish)" Nov 17 16:33:07 ids kernel: [ cut here ] Nov 17 16:33:07 ids kernel: NETDEV WATCHDOG: eth1 (ax88179_178a): transmit queue 0 timed out Nov 17 16:33:07 ids kernel: WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:477 dev_watchdog+0x3b4/0x3d0 Nov 17 16:33:07 ids kernel: Modules linked in: bnep bridge stp llc binfmt_misc btsdio snd_bcm2835(CE) bluetooth ecdh_generic ecc snd_pcm brcmfmac snd_seq_midi brcmutil snd_seq_midi_event bcm2835_isp(CE) bcm2835_co> Nov 17 16:33:07 ids kernel: CPU: 0 PID: 0 Comm: swapper/0 Tainted: G C E 5.15.0-1042-raspi #45-Ubuntu Nov 17 16:33:07 ids kernel: Hardware name: Raspberry Pi 4 Model B Rev 1.2 (DT) Nov 17 16:33:07 ids kernel: pstate: 6045 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) Nov 17 16:33:07 ids kernel: pc : dev_watchdog+0x3b4/0x3d0 Nov 17 16:33:07 ids kernel: lr : dev_watchdog+0x3b4/0x3d0 Nov 17 16:33:07 ids kernel: sp : 88003d20 Nov 17 16:33:07 ids kernel: x29: 88003d20 x28: 0001 x27: 0004 Nov 17 16:33:07 ids kernel: x26: dde19e51a000 x25: 5984084364c0 x24: Nov 17 16:33:07 ids kernel: x23: 59840843641c x22: dde19e2d6000 x21: Nov 17 16:33:07 ids kernel: x20: 598408436000 x19: dde19e4f5ac0 x18: Nov 17 16:33:07 ids kernel: x17: 7ba31d93 x16: 8800 x15: 3d08f6ba57c0 Nov 17 16:33:07 ids kernel: x14: 0001 x13: 74756f2064656d69 x12: 7420302065756575 Nov 17 16:33:07 ids kernel: x11: 712074696d736e61 x10: 7274203a29613837 x9 : dde19cb35654 Nov 17 16:33:07 ids kernel: x8 : 6128203168746520 x7 : 0003 x6 : Nov 17 16:33:07 ids kernel: x5 : x4 : x3 : 0100 Nov 17 16:33:07 ids kernel: x2 : x1 : x0 : dde19e2e79c0 Nov 17 16:33:07 ids kernel: Call trace: Nov 17 16:33:07 ids kernel: dev_watchdog+0x3b4/0x3d0 Nov 17 16:33:07 ids kernel: call_timer_fn+0x3c/0x1f0 Nov 17 16:33:07 ids kernel: __run_timers.part.0+0x230/0x330 Nov 17 16:33:07 ids kernel: run_timer_softirq+0x44/0x80 Nov 17 16:33:07 ids kernel: __do_softirq+0x1a4/0x56c Nov 17 16:33:07 ids kernel: __irq_exit_rcu+0xac/0xec Nov 17 16:33:07 ids kernel: irq_exit+0x18/0x44 Nov 17 16:33:07 ids kernel: handle_domain_irq+0x6c/0xa0 Nov 17 16:33:07 ids kernel: gic_handle_irq+0x54/0xe0 Nov 17 16:33:07 ids kernel: call_on_irq_stack+0x20/0x48 Nov 17 16:33:07 ids kernel: do_interrupt_handler+0x5c/0x70 Nov 17 16:33:07 ids kernel: el1_interrupt+0x30/0xa0 Nov 17 16:33:07 ids kernel: el1h_64_irq_handler+0x18/0x24 Nov 17 16:33:07 ids kernel: el1h_64_irq+0x7c/0x80 Nov 17 16:33:07 ids kernel: arch_cpu_idle+0x18/0x3c Nov 17 16:33:07 ids kernel: default_idle_call+0x4c/0x1c8 Nov 17 16:33:07 ids kernel: cpuidle_idle_call+0x164/0x1d4 Nov 17 16:33:07 ids kernel: do_idle+0xdc/0x11c Nov 17 16:33:07 ids kernel: cpu_startup_entry+0x30/0x7c Nov 17 16:33:07 ids kernel: rest_init+0x100/0x130 Nov 17 16:33:07 ids kernel: arch_call_rest_init+0x18/0x24 Nov 17 16:33:07 ids kernel: start_kernel+0x4cc/0x504 Nov 17 16:33:07 ids kernel: __primary_switched+0xbc/0xc4 Nov 17 16:33:07 ids kernel: ---[ end trace 2b3e5d867458aad0 ]--- Nov 17 16:33:07 ids kernel: xhci_hcd :01:00.0: WARN Successful completion on short TX Nov 17 16:33:08 ids kernel: xhci_hcd :01:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 5 comp_code 1 Nov 17 16:33:08 ids kernel: xhci_hcd :01:00.0: Looking for event-dma 000449d88d00 trb-start 000449c3c330 trb-end 000449c3c340 seg-start 000449c3c000 seg-end 000449c3cff0 Nov 17 16:33:08 ids kernel: xhci_hcd :01:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 5 comp_code 1 Nov 17 16:33:08 ids kernel: xhci_hcd :01:00.0: Looking for event-dma 000449d88d20 trb-start 000449c3c330 trb-end 000449c3c340 seg-start 000449c3c000 seg-end 000449c3cff0 Nov 17 16:33:08 ids kernel: xhci_hcd :01:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 5 comp_code 1 -- 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/1953554 Title: NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out Status in linux package in Ubuntu: Confirmed Bug description: Hi, I am facing this problem in Focal with the USB 3.0 Ethernet Gigabit adapter "ASIX Electronics Corp. AX88179 Gigabit Ethernet" (waneth is the name I assigned to this ethernet connected to the cable modem/router): [ cut here ] [94104.121581] NETDEV WATCHDOG: wanet
[Kernel-packages] [Bug 1878279]
I am having the same issue. Will enable "efi=boot" hopefully to capture more logs. root@r-laptop ~]# uname -a Linux r-laptop 6.5.9-arch2-1 #1 SMP PREEMPT_DYNAMIC Thu, 26 Oct 2023 00:52:20 + x86_64 GNU/Linux Nov 17 18:11:24 r-laptop kernel: i2c_designware AMDI0010:00: controller timed out Nov 17 18:11:24 r-laptop systemd[1]: Using hardware watchdog 'SP5100 TCO timer', version 0, device /dev/watchdog0 Nov 17 18:11:24 r-laptop systemd[1]: Watchdog running with a timeout of 10min. Nov 17 18:11:24 r-laptop kernel: watchdog: watchdog0: watchdog did not stop! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1878279 Title: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot Status in Linux: Confirmed Status in Ubuntu: Confirmed Status in linux-signed-hwe package in Ubuntu: In Progress Status in linux-signed-hwe package in Fedora: New Bug description: Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5 14IIL05 81YH' from first system start on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tilman 1607 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 21:22:22 2020 InstallationDate: Installed on 2020-05-12 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=bb961a96-8855-4e50-814d-7994235377c3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DSCN23WW(V1.09) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 14IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05: dmi.product.family: IdeaPad 5 14IIL05 dmi.product.name: 81YH dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05 dmi.product.version: IdeaPad 5 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1878279/+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 1878279]
radupantiru@: could you also capture the "acpidump" output, please?
We have a couple other reports like
https://bugzilla.kernel.org/show_bug.cgi?id=218050 that seem related to
07eab0901ede ("efi/x86: Remove EfiMemoryMappedIO from E820 map").
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe in Ubuntu.
https://bugs.launchpad.net/bugs/1878279
Title:
MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized
from any given boot
Status in Linux:
Confirmed
Status in Ubuntu:
Confirmed
Status in linux-signed-hwe package in Ubuntu:
In Progress
Status in linux-signed-hwe package in Fedora:
New
Bug description:
Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work
at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5
14IIL05 81YH' from first system start on.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-29-generic 5.4.0-29.33
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: tilman 1607 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue May 12 21:22:22 2020
InstallationDate: Installed on 2020-05-12 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 81YH
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic
root=UUID=bb961a96-8855-4e50-814d-7994235377c3 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.4.0-29-generic N/A
linux-backports-modules-5.4.0-29-generic N/A
linux-firmware1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/25/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: DSCN23WW(V1.09)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: No DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad 5 14IIL05
dmi.modalias:
dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05:
dmi.product.family: IdeaPad 5 14IIL05
dmi.product.name: 81YH
dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05
dmi.product.version: IdeaPad 5 14IIL05
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1878279/+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 1878279]
Created attachment 305416
acpidump.txt
There you are and thanks for looking into this!
On Fri, Nov 17, 2023 at 7:02 PM wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208171
>
> Bjorn Helgaas (bj...@helgaas.com) changed:
>
>What|Removed |Added
>
>
> Status|RESOLVED|REOPENED
> Resolution|CODE_FIX|---
>
> --- Comment #18 from Bjorn Helgaas (bj...@helgaas.com) ---
> radupantiru@: could you also capture the "acpidump" output, please?
>
> We have a couple other reports like
> https://bugzilla.kernel.org/show_bug.cgi?id=218050 that seem related to
> 07eab0901ede ("efi/x86: Remove EfiMemoryMappedIO from E820 map").
>
> --
> You may reply to this email to add a comment.
>
> You are receiving this mail because:
> You are on the CC list for the bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe in Ubuntu.
https://bugs.launchpad.net/bugs/1878279
Title:
MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized
from any given boot
Status in Linux:
Confirmed
Status in Ubuntu:
Confirmed
Status in linux-signed-hwe package in Ubuntu:
In Progress
Status in linux-signed-hwe package in Fedora:
New
Bug description:
Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work
at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5
14IIL05 81YH' from first system start on.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-29-generic 5.4.0-29.33
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: tilman 1607 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue May 12 21:22:22 2020
InstallationDate: Installed on 2020-05-12 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 81YH
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic
root=UUID=bb961a96-8855-4e50-814d-7994235377c3 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.4.0-29-generic N/A
linux-backports-modules-5.4.0-29-generic N/A
linux-firmware1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/25/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: DSCN23WW(V1.09)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: No DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad 5 14IIL05
dmi.modalias:
dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05:
dmi.product.family: IdeaPad 5 14IIL05
dmi.product.name: 81YH
dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05
dmi.product.version: IdeaPad 5 14IIL05
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1878279/+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 1878279] Re: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot
** Changed in: linux Status: Fix Released => Confirmed ** Bug watch added: Linux Kernel Bug Tracker #218050 https://bugzilla.kernel.org/show_bug.cgi?id=218050 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1878279 Title: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot Status in Linux: Confirmed Status in Ubuntu: Confirmed Status in linux-signed-hwe package in Ubuntu: In Progress Status in linux-signed-hwe package in Fedora: New Bug description: Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5 14IIL05 81YH' from first system start on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tilman 1607 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 21:22:22 2020 InstallationDate: Installed on 2020-05-12 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YH ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=bb961a96-8855-4e50-814d-7994235377c3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DSCN23WW(V1.09) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 14IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05: dmi.product.family: IdeaPad 5 14IIL05 dmi.product.name: 81YH dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05 dmi.product.version: IdeaPad 5 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1878279/+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 787738]
(In reply to Przemek from comment #36) > Similar problem here. Machine is the t440p with changed touchpad from t450 > (it fits and was working fine), some logs: > > [7.853125] rmi4_smbus 9-002c: registering SMbus-connected sensor > [7.904417] rmi4_f01 rmi4-00.fn01: found RMI device, manufacturer: > Synaptics, product: TM3053-008, fw id: 2491654 > [7.960935] input: Synaptics TM3053-008 as > /devices/pci:00/:00:1f.3/i2c-9/9-002c/rmi4-00/input/input20 > [7.966394] serio: RMI4 PS/2 pass-through port at rmi4-00.fn03 > [8.373257] input: TPPS/2 IBM TrackPoint as > /devices/pci:00/:00:1f.3/i2c-9/9-002c/rmi4-00/rmi4-00.fn03/serio3/ > input/input21 > [81220.734879] psmouse serio3: TrackPoint at rmi4-00.fn03/serio0/input0 lost > synchronization, throwing 1 bytes away. > > Gentoo/ SuSe Tumbleweed. > After resume from suspend trackpoint and touchpad doesn't work anymore. I also have a T440p with the touchpad from the T450. My dmesg log does not show my TrackPoint throwing bytes away; however, I found that reloading the psmouse driver using modprobe temporarily fixes the issue... for a minute. -- 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/787738 Title: [Thinkpad X220/E220s/E420s] trackpoint/trackpoint displays odd behaviour Status in Linux: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Natty: Invalid Status in linux source package in Oneiric: Invalid Status in Fedora: New Bug description: Using the touchpad does not result in expected behavior. The touchpad has three "mouse" buttons on top, and none of these buttons currently function. Using xev does not show any output from these buttons. The touchpad itself works fine. There are two bottom buttons integrated with the touchpad, which do not work consistantly. The left button will sometimes act like a left-click and sometime like a right click, making it hard to move applications on the screen. The right button acts like a left click and only sometimes bring up menus. Trying to change from a left hand to a right hand mouse in mouse options does not change the behavior. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: linux-image-2.6.38-8-generic 2.6.38-8.42 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1235 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xd252 irq 44' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:14f1506e,17aa21da,0010 HDA:80862805,80860101,0010' Controls : 20 Simple ctrls : 8 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw unknown' Mixer name : 'ThinkPad EC (unknown)' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Tue May 24 14:44:59 2011 HibernationDevice: RESUME=UUID=dd9d30b2-4950-42af-87e2-b304fc01e83d InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) MachineType: LENOVO 428623U ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=4985f74f-9e44-411f-8d41-73f9f68c057d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-2.6.38-8-generic N/A linux-backports-modules-2.6.38-8-generic N/A linux-firmware1.52 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET28WW (1.00 ) dmi.board.asset.tag: Not Available dmi.board.name: 428623U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET28WW(1.00):bd01/25/2011:svnLENOVO:pn428623U:pvrThinkPadX220:rvnLENOVO:rn428623U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 428623U dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/787738/+subscriptions -- Mailing list: https://launchpad.net/~kernel
[Kernel-packages] [Bug 787738]
(In reply to Przemek from comment #36) > Similar problem here. Machine is the t440p with changed touchpad from t450 > (it fits and was working fine), some logs: > > [7.853125] rmi4_smbus 9-002c: registering SMbus-connected sensor > [7.904417] rmi4_f01 rmi4-00.fn01: found RMI device, manufacturer: > Synaptics, product: TM3053-008, fw id: 2491654 > [7.960935] input: Synaptics TM3053-008 as > /devices/pci:00/:00:1f.3/i2c-9/9-002c/rmi4-00/input/input20 > [7.966394] serio: RMI4 PS/2 pass-through port at rmi4-00.fn03 > [8.373257] input: TPPS/2 IBM TrackPoint as > /devices/pci:00/:00:1f.3/i2c-9/9-002c/rmi4-00/rmi4-00.fn03/serio3/ > input/input21 > [81220.734879] psmouse serio3: TrackPoint at rmi4-00.fn03/serio0/input0 lost > synchronization, throwing 1 bytes away. > > Gentoo/ SuSe Tumbleweed. > After resume from suspend trackpoint and touchpad doesn't work anymore. I also have a T440p with the touchpad from the T450. My dmesg log does not show my TrackPoint throwing bytes away; however, I found that reloading the psmouse driver using modprobe temporarily fixes the issue... for a minute. -- 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/787738 Title: [Thinkpad X220/E220s/E420s] trackpoint/trackpoint displays odd behaviour Status in Linux: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Natty: Invalid Status in linux source package in Oneiric: Invalid Status in Fedora: New Bug description: Using the touchpad does not result in expected behavior. The touchpad has three "mouse" buttons on top, and none of these buttons currently function. Using xev does not show any output from these buttons. The touchpad itself works fine. There are two bottom buttons integrated with the touchpad, which do not work consistantly. The left button will sometimes act like a left-click and sometime like a right click, making it hard to move applications on the screen. The right button acts like a left click and only sometimes bring up menus. Trying to change from a left hand to a right hand mouse in mouse options does not change the behavior. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: linux-image-2.6.38-8-generic 2.6.38-8.42 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1235 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xd252 irq 44' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:14f1506e,17aa21da,0010 HDA:80862805,80860101,0010' Controls : 20 Simple ctrls : 8 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw unknown' Mixer name : 'ThinkPad EC (unknown)' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Tue May 24 14:44:59 2011 HibernationDevice: RESUME=UUID=dd9d30b2-4950-42af-87e2-b304fc01e83d InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) MachineType: LENOVO 428623U ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=4985f74f-9e44-411f-8d41-73f9f68c057d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-2.6.38-8-generic N/A linux-backports-modules-2.6.38-8-generic N/A linux-firmware1.52 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET28WW (1.00 ) dmi.board.asset.tag: Not Available dmi.board.name: 428623U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET28WW(1.00):bd01/25/2011:svnLENOVO:pn428623U:pvrThinkPadX220:rvnLENOVO:rn428623U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 428623U dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/787738/+subscriptions -- Mailing list: https://launchpad.net/~kernel
[Kernel-packages] [Bug 2040280] Re: CVE-2022-40982 on Ubuntu Mantic Linux Kernel still not fixed
Hello Cascardo, thank you and anybody involved for your work! I can confirm that on my end, with: Linux pro 6.5.0-10-generic #10-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 13 13:49:38 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux, mantic and ubuntu-advantage-tools (30~23.10), an: pro fix CVE-2022-40982 generates: CVE-2022-40982: Linux kernel (BlueField) vulnerabilities - https://ubuntu.com/security/CVE-2022-40982 1 affected source package is installed: intel-microcode (1/1) intel-microcode: A fix is available in Ubuntu standard updates. The update is already installed. ✔ CVE-2022-40982 is resolved. Interestingly, t only the microcode-package is listed, not as before the microcode package and the "linux kernel". But, the output is pretty satisfying. Have a great weekend, and thanks for working on on of the best things this world has to offer: Linux/GNU -- 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/2040280 Title: CVE-2022-40982 on Ubuntu Mantic Linux Kernel still not fixed Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in intel-microcode source package in Mantic: New Status in linux source package in Mantic: Fix Released Bug description: An pro fix CVE-2022-40982 gives me an ✘ CVE-2022-40982 is not resolved. Strangely without a specific description of the affected package: "1 package is still affected: linux" But, when i look up the CVW here: https://ubuntu.com/security/CVE-2022-40982 it is mentioned that the fix is contained with the new version of intel-microcode: mantic Released (3.20230808.1) And that's the version i seem to have installed: apt show intel-microcode: "Package: intel-microcode Version: 3.20230808.1" Any Ideas on that? ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: intel-microcode 3.20230808.1 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Oct 24 16:05:24 2023 InstallationDate: Installed on 2022-08-05 (445 days ago) InstallationMedia: Ubuntu Unity 22.04 SourcePackage: intel-microcode UpgradeStatus: Upgraded to mantic on 2023-10-12 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/2040280/+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 2039191] Re: Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization
Verified to boot successfully. 32-bit machines otherwise not used on GCP, anyway. ** Tags removed: verification-needed-lunar-linux-gcp ** Tags added: verification-done-lunar-linux-gcp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2039191 Title: Kernel oops on 32-0bit kernels due to x86_cache_alignment initialization Status in linux-aws package in Ubuntu: In Progress Status in linux-gcp package in Ubuntu: Fix Committed Status in linux-aws source package in Lunar: Triaged Status in linux-gcp source package in Lunar: Fix Committed Status in linux-aws source package in Mantic: In Progress Status in linux-gcp source package in Mantic: Fix Released Bug description: [Impact] * Kernel OOPS encountered on 32-bit kernels due to commit cd0e9ab from git://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-gcp/+git/lunar [Fix] * Clean cherry pick from linux-next, commit 3e3255265291 [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression, isolated fix slightly modifying when value becomes available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2039191/+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 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
Hi people, I guess it would be a good idea to let you know that the problem on Lenovo V14 G2 ALC is now fixed, didn't do anything, it just worked after an update. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in ideapad-laptop: New Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: Confirmed Status in linux source package in Mantic: Confirmed Status in linux source package in Noble: Confirmed Status in Fedora: New Bug description: [Impact] Keyboard and touchpad doesn't work on some recent systems, and also s2idle is broken. [Fix] Two upstream commits. 128b0c9781c9f26 x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility 3bde7ec13c97144 platform/x86: Add s2idle quirk for more Lenovo laptops [Test case] boot a fixed kernel and test that input and s2idle works. [Where problems could occur] A buggy bios could maybe advertise a system being PCAT compatible when it's not, though in such a case it might have been already caught before. -- Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
I had a working system despite this bug with the MUTTER_DEBUG_KMS_THREAD_TYPE=user workaround, after upgrading to get this fix I can no longer use the laptop. It prints "[ OK ] Starting gdm.service" during boot and then hangs. No GUI comes up. I can get into vterms with ctrl-alt-fn-fkey but ofc I need a GUI. Persists across reboots. Removing the `MUTTER_DEBUG_KMS_THREAD_TYPE=user` workaround did not fix things. This happened at an inconvenient time and has caused big problems. Will file another bug I guess -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: Fix Released Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released Status in linux source package in Mantic: Triaged Status in mutter source package in Mantic: Fix Released Bug description: [ Impact ] gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, sometimes when the screen locks, sometimes when launching particular apps. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Test Plan ] Not all Ryzen systems (including one I just purchased) are able to reproduce the bug. We have no choice but to leave final verification to the community. Anyone affected should try locking their screen and verify they are not instantly returned to the login screen. [ Where problems could occur ] Anywhere in frame scheduling and particularly for mouse cursor movement since that's what the real-time thread exists to optimize. [ Original Description ] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+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 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
For all Linux beginners that don't want to compile their own kernel: It seems that it's already possible to download and install a pre- compiled kernel via GUI: Simply follow these instructions: https://9to5linux.com/you-can-now- install-linux-kernel-6-5-on-ubuntu-heres-how You'll need to enter the following commands into your terminal: sudo add-apt-repository ppa:cappelikan/ppa sudo apt update && sudo apt full-upgrade sudo apt install -y mainline After that is done you will find an application called "Mainline Kernels" in your desktop-environment. Start that application and install a new Kernel (I installed kernel 6.5.11). After you installed that kernel, enter this line in your terminal: sudo apt --fix-broken install Restart your notebook and enjoy your built-in keyboard and trackpad. PLEASE NOTE: Like yourself I'm a linux-noob. I can only confirm that this works on my configuration: Ubuntu 22.04/Gnome 42/Kernel 6.5.11 But in my case it works like a charm. Good luck! theageman -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in ideapad-laptop: New Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Lunar: Confirmed Status in linux source package in Mantic: Confirmed Status in linux source package in Noble: Confirmed Status in Fedora: New Bug description: [Impact] Keyboard and touchpad doesn't work on some recent systems, and also s2idle is broken. [Fix] Two upstream commits. 128b0c9781c9f26 x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility 3bde7ec13c97144 platform/x86: Add s2idle quirk for more Lenovo laptops [Test case] boot a fixed kernel and test that input and s2idle works. [Where problems could occur] A buggy bios could maybe advertise a system being PCAT compatible when it's not, though in such a case it might have been already caught before. -- Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+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 2043640] Re: amdgpu: GPU Recovery fails, frequent hangs
** Changed in: mesa
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2043640
Title:
amdgpu: GPU Recovery fails, frequent hangs
Status in Mesa:
Fix Released
Status in linux package in Ubuntu:
Won't Fix
Status in mesa package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Won't Fix
Status in mesa source package in Jammy:
New
Status in linux source package in Lunar:
Won't Fix
Status in mesa source package in Lunar:
New
Bug description:
I've been using 23.04 for a few months, and experienced a total system
hang occasionally when sharing my screen over Zoom or Google Meet
(running on Google Chrome).
At first it hangs and then it periodically flashes like it's trying
(unsuccessfully) to recover; I've got 3 screens (including the
laptop's internal one) and each attempt shows something different (at
first it tries to recover the contents of all 3 screens, then it shows
only one of them, and then it shows the same content on all 3, but it
never gets responsive).
I've recently upgraded to 23.10, hoping a new kernel would help the
situation. It's only gotten considerably worse now; it hangs sometimes
just when opening Zoom; it's somehow easier to reproduce with Google
Chrome. Interestingly, it fails quickly and reliably now when enabling
my webcam (with special effects). It started hanging badly when using
Google Maps as well.
For all these behaviors, I suspect amdgpu is to blame (I'm running on
Renoir, 4750U Pro); `dmesg` and `journalctl` didn't seem to show
anything interesting.
Any tips about debugging this further?
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-generic 6.5.0.10.12
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Thu Nov 16 02:27:45 2023
InstallationDate: Installed on 2023-07-02 (137 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-14 (2 days ago)
dmi.bios.date: 06/13/2023
dmi.bios.release: 1.44
dmi.bios.vendor: LENOVO
dmi.bios.version: R1BET75W(1.44 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20UD000GUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.44
dmi.modalias:
dmi:bvnLENOVO:bvrR1BET75W(1.44):bd06/13/2023:br1.44:efr1.44:svnLENOVO:pn20UD000GUS:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD000GUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UD_BU_Think_FM_ThinkPadT14Gen1:
dmi.product.family: ThinkPad T14 Gen 1
dmi.product.name: 20UD000GUS
dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
dmi.product.version: ThinkPad T14 Gen 1
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2043640/+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 2037493] Re: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD
** Description changed: [Impact] System can't enter suspend on AHCI mode, the CPU FAN and System FAN is running, PSU LED is on. When fail to enter suspend, remove ODD, the system can successfully enter suspend again. [Fix] Enable LPM on Alder Lake-P AHCI. [Test Cases] 1. enabled AHCI on target machine. 2. boot with kernel applied fix. 3. suspend then check slp_s0_residency_usec&package_cstate_show ~~~ u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 4951200 Package C2 : 63571033 Package C3 : 6212 Package C6 : 5633477 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 5255561 u@ubuntu:~$ sudo rtcwake -m mem -s 10 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 12965280 Package C2 : 75052691 Package C3 : 46989 Package C6 : 8108332 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 13628111 ~~~ [where the issue could happen] Medium, Intel promise there's no issue of ADL AHCI and they will take responsibility after regression. Intel also take LPM as POR so they will fix any issues. + + [Misc] + For generic J/M, passed the all arch compilations on cbd, + Jammy, + ~~~ + $ git push j_cbd + Total 0 (delta 0), reused 0 (delta 0), pack-reused 0 + remote: *** kernel-cbd * + remote: * Queueing builds (your 'ubuntu_jammy_next'); ok to interrupt + remote: * For results: ssh cbd ls kobako-jammy-f5146c67dd2d-XWAJ + remote: * 0/1 workers busy, 0 builds queued + remote: 2023-11-17 19:50:25 kobako-jammy-f5146c67dd2d-XWAJ/amd64/BUILD-OK + remote: 2023-11-17 20:18:29 kobako-jammy-f5146c67dd2d-XWAJ/arm64/BUILD-OK + remote: 2023-11-17 20:01:41 kobako-jammy-f5146c67dd2d-XWAJ/armhf/BUILD-OK + remote: 2023-11-17 20:31:51 kobako-jammy-f5146c67dd2d-XWAJ/ppc64el/BUILD-OK + remote: 2023-11-17 20:37:25 kobako-jammy-f5146c67dd2d-XWAJ/s390x/BUILD-OK + remote: + To cbd.kernel:jammy.git + * [new branch]ubuntu_jammy_next -> ubuntu_jammy_next + ~~~ + Mantic, + ~~~ + $ git push m_cbd + Enumerating objects: 102, done. + Counting objects: 100% (102/102), done. + Delta compression using up to 8 threads + Compressing objects: 100% (17/17), done. + Writing objects: 100% (61/61), 252.10 KiB | 2.23 MiB/s, done. + Total 61 (delta 46), reused 54 (delta 41), pack-reused 0 + remote: *** kernel-cbd * + remote: * Queueing builds (your 'ubuntu_mantic_next'); ok to interrupt + remote: * For results: ssh cbd ls kobako-mantic-e489d3bb608c-9LiJ + remote: * 0/1 workers busy, 0 builds queued + remote: 2023-11-17 20:58:33 kobako-mantic-e489d3bb608c-9LiJ/amd64/BUILD-OK + remote: 2023-11-17 21:30:32 kobako-mantic-e489d3bb608c-9LiJ/arm64/BUILD-OK + remote: 2023-11-17 21:09:18 kobako-mantic-e489d3bb608c-9LiJ/armhf/BUILD-OK + remote: 2023-11-17 21:45:50 kobako-mantic-e489d3bb608c-9LiJ/ppc64el/BUILD-OK + remote: 2023-11-17 21:54:30 kobako-mantic-e489d3bb608c-9LiJ/s390x/BUILD-OK + remote: + To cbd.kernel:mantic.git + * [new branch]ubuntu_mantic_next -> ubuntu_mantic_next + ~~~ + + For Unstable, successfully compiled with the Mantic configuration and without dkms. + ~~~ + Total 0 (delta 0), reused 0 (delta 0), pack-reused 0 + remote: *** kernel-cbd * + remote: * Queueing builds (your 'ubuntu_unstable_next'); ok to interrupt + remote: * For results: ssh cbd ls kobako-mantic-dc0405f4bd4c-VZvy + remote: * 0/1 workers busy, 0 builds queued + remote: 2023-11-18 22:35:41 kobako-mantic-dc0405f4bd4c-VZvy/amd64/BUILD-OK + remote: 2023-11-18 23:03:15 kobako-mantic-dc0405f4bd4c-VZvy/arm64/BUILD-OK + remote: 2023-11-18 22:46:15 kobako-mantic-dc0405f4bd4c-VZvy/armhf/BUILD-OK + remote: 2023-11-18 23:16:02 kobako-mantic-dc0405f4bd4c-VZvy/ppc64el/BUILD-OK + remote: 2023-11-18 23:22:02 kobako-mantic-dc0405f4bd4c-VZvy/s390x/BUILD-OK + remote: + To cbd.kernel:mantic.git + * [new branch]ubuntu_unstable_next -> ubuntu_unstable_next + ~~~ ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: In Progress ** Also affects: linux-oem-6.1 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Lunar) Status: In Progress => Invalid ** Changed in: linux (Ubuntu Lunar)
[Kernel-packages] [Bug 2037493] Re: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD
SRUed for generic J/M/U, https://lists.ubuntu.com/archives/kernel-team/2023-November/147011.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2037493 Title: Fix ADL: System enabled AHCI can't get into s0ix when attached ODD Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] System can't enter suspend on AHCI mode, the CPU FAN and System FAN is running, PSU LED is on. When fail to enter suspend, remove ODD, the system can successfully enter suspend again. [Fix] Enable LPM on Alder Lake-P AHCI. [Test Cases] 1. enabled AHCI on target machine. 2. boot with kernel applied fix. 3. suspend then check slp_s0_residency_usec&package_cstate_show ~~~ u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 4951200 Package C2 : 63571033 Package C3 : 6212 Package C6 : 5633477 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 5255561 u@ubuntu:~$ sudo rtcwake -m mem -s 10 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 u@ubuntu:~$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec;sudo cat /sys/kernel/debug/pmc_core/package_cstate_show 12965280 Package C2 : 75052691 Package C3 : 46989 Package C6 : 8108332 Package C7 : 0 Package C8 : 0 Package C9 : 0 Package C10 : 13628111 ~~~ [where the issue could happen] Medium, Intel promise there's no issue of ADL AHCI and they will take responsibility after regression. Intel also take LPM as POR so they will fix any issues. [Misc] Because the board_ahci_mobile is still not modified to board_ahci_low_power on Jammy, provide a single patch for Jammy. For generic J/M, passed the all arch compilations on cbd, Jammy, ~~~ $ git push j_cbd Total 0 (delta 0), reused 0 (delta 0), pack-reused 0 remote: *** kernel-cbd * remote: * Queueing builds (your 'ubuntu_jammy_next'); ok to interrupt remote: * For results: ssh cbd ls kobako-jammy-f5146c67dd2d-XWAJ remote: * 0/1 workers busy, 0 builds queued remote: 2023-11-17 19:50:25 kobako-jammy-f5146c67dd2d-XWAJ/amd64/BUILD-OK remote: 2023-11-17 20:18:29 kobako-jammy-f5146c67dd2d-XWAJ/arm64/BUILD-OK remote: 2023-11-17 20:01:41 kobako-jammy-f5146c67dd2d-XWAJ/armhf/BUILD-OK remote: 2023-11-17 20:31:51 kobako-jammy-f5146c67dd2d-XWAJ/ppc64el/BUILD-OK remote: 2023-11-17 20:37:25 kobako-jammy-f5146c67dd2d-XWAJ/s390x/BUILD-OK remote: To cbd.kernel:jammy.git * [new branch]ubuntu_jammy_next -> ubuntu_jammy_next ~~~ Mantic, ~~~ $ git push m_cbd Enumerating objects: 102, done. Counting objects: 100% (102/102), done. Delta compression using up to 8 threads Compressing objects: 100% (17/17), done. Writing objects: 100% (61/61), 252.10 KiB | 2.23 MiB/s, done. Total 61 (delta 46), reused 54 (delta 41), pack-reused 0 remote: *** kernel-cbd * remote: * Queueing builds (your 'ubuntu_mantic_next'); ok to interrupt remote: * For results: ssh cbd ls kobako-mantic-e489d3bb608c-9LiJ remote: * 0/1 workers busy, 0 builds queued remote: 2023-11-17 20:58:33 kobako-mantic-e489d3bb608c-9LiJ/amd64/BUILD-OK remote: 2023-11-17 21:30:32 kobako-mantic-e489d3bb608c-9LiJ/arm64/BUILD-OK remote: 2023-11-17 21:09:18 kobako-mantic-e489d3bb608c-9LiJ/armhf/BUILD-OK remote: 2023-11-17 21:45:50 kobako-mantic-e489d3bb608c-9LiJ/ppc64el/BUILD-OK remote: 2023-11-17 21:54:30 kobako-mantic-e489d3bb608c-9LiJ/s390x/BUILD-OK remote: To cbd.kernel:mantic.git * [new branch]ubuntu_mantic_next -> ubuntu_mantic_next ~~~ For Unstable, successfully compiled with the Mantic configuration and without dkms. ~~~ Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
[Kernel-packages] [Bug 2043905] [NEW] Mantic reboot loop before splash screen is displayed
Public bug reported: used the live USB for Kubuntu and UbuntuStudio 23.10 as well as upgraded to Mantic 6.5.0-10-generic from a Lunar 6.2.0-36 that works... all of the 6.5.0 64 bit kernel versions do a reboot loop prior to the splash screen display. Processor is an AMD Ryzen 5600X, MSI MPG B550 GAMING PLUS Motherboard with 64 gig 3200 ddr4 ram. AMD Radeon RX6600 graphics... latest BIOS firmware is installed, "fwupdmrg refresh --force && fwupdmrg update" in root terminal reports no available updates. in the advanced options of grub I can boot into mantic with the lunar 6.2.0-36 kernel. Cell phone video capture of the bad boot included... Further testing found that a Mantic beta July 3rd build will boot (6.3 kernel) booting to the current live Kubuntu USB with the 6.5.0-9 kernel and removing hardware 1 piece at a time then replacing if the loop occurred found that as soon as a VT6307 PCIe card is removed the 6.5.0-9 and 6.5.0-10 kernels will boot properly. as soon as the card is reinstalled the panic reboot loop starts up again... If there was a log generated from the loop I have been unable to find one in the /var/log directory... I have been unable to get kdump to work... ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: mantic -- 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/2043905 Title: Mantic reboot loop before splash screen is displayed Status in linux package in Ubuntu: New Bug description: used the live USB for Kubuntu and UbuntuStudio 23.10 as well as upgraded to Mantic 6.5.0-10-generic from a Lunar 6.2.0-36 that works... all of the 6.5.0 64 bit kernel versions do a reboot loop prior to the splash screen display. Processor is an AMD Ryzen 5600X, MSI MPG B550 GAMING PLUS Motherboard with 64 gig 3200 ddr4 ram. AMD Radeon RX6600 graphics... latest BIOS firmware is installed, "fwupdmrg refresh --force && fwupdmrg update" in root terminal reports no available updates. in the advanced options of grub I can boot into mantic with the lunar 6.2.0-36 kernel. Cell phone video capture of the bad boot included... Further testing found that a Mantic beta July 3rd build will boot (6.3 kernel) booting to the current live Kubuntu USB with the 6.5.0-9 kernel and removing hardware 1 piece at a time then replacing if the loop occurred found that as soon as a VT6307 PCIe card is removed the 6.5.0-9 and 6.5.0-10 kernels will boot properly. as soon as the card is reinstalled the panic reboot loop starts up again... If there was a log generated from the loop I have been unable to find one in the /var/log directory... I have been unable to get kdump to work... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043905/+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 1964916] Re: [HP Omni 120-2110il AIO] Flickering white lines on screen
@Camilo QS, Could you please show me how to fix? I'm suffering from the same problem? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1964916 Title: [HP Omni 120-2110il AIO] Flickering white lines on screen Status in linux-hwe-5.11 package in Ubuntu: Confirmed Bug description: https://www.youtube.com/watch?v=GcAXAicoZqY this is the video of my error i am having this issue on all versions of ubuntu-- i have tried installing versions 20.04, 18.04.06, 12.04.. i have intel pentium g630 processor with intel graphics 2000 (Vram-256M). I used Windows 10 on my PC but i thought of switching to ubuntu when this problem arose.. The glitch shows up on ubuntu splash screen and remains there until i restart my pc with nomodeset parameter...i have reinstalled windows 10 but i want this issue to get fixed.. i need to use ubuntu ...pls ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 14:59:57 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:2ac5] InstallationDate: Installed on 2022-03-05 (9 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Hewlett-Packard 120-2110il ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=54d1c05e-a544-4510-8da7-87e1a7242e0f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/17/2011 dmi.bios.release: 4.6 dmi.bios.vendor: AMI dmi.bios.version: LEO_707 dmi.board.name: 2AC5 dmi.board.vendor: Quanta dmi.board.version: 101 dmi.chassis.asset.tag: 4CS2040B0F dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvrLEO_707:bd11/17/2011:br4.6:svnHewlett-Packard:pn120-2110il:pvr:rvnQuanta:rn2AC5:rvr101:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: 120-2110il dmi.product.sku: QF135AA#ACJ dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1964916/+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
