[Kernel-packages] [Bug 2062386] Re: Maxlinear Ethernet GPY115B report gpy_config_aneg failed: -110 and Link UP is not visible
** Description changed: Hello Ubuntu Team, I notice issue today with Maxlinear Ethernet GPY115B controller. This controller report issue in dmesg and port not have link up. My target is: OnLogic HX310 with two Ethernet Ports. > Official page: https://www.onlogic.com/computers/industrial/fanless/helix-300/ + Error: Maxlinear Ethernet GPY115B stmmac-3:01: gpy_config_aneg failed: + -110 - Error: Maxlinear Ethernet GPY115B stmmac-3:01: gpy_config_aneg failed: -110 + + https://billauer.co.il/blog/2014/01/networkmanager-carrier-detect/ + (stmmaceth: NetworkManager fails to bring up a wired Ethernet NIC) OS: Ubuntu 24.04 LTS Kernel: 6.8.0-22.22-generic 6.8.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/2062386 Title: Maxlinear Ethernet GPY115B report gpy_config_aneg failed: -110 and Link UP is not visible Status in linux package in Ubuntu: New Bug description: Hello Ubuntu Team, I notice issue today with Maxlinear Ethernet GPY115B controller. This controller report issue in dmesg and port not have link up. My target is: OnLogic HX310 with two Ethernet Ports. > Official page: https://www.onlogic.com/computers/industrial/fanless/helix-300/ Error: Maxlinear Ethernet GPY115B stmmac-3:01: gpy_config_aneg failed: -110 https://billauer.co.il/blog/2014/01/networkmanager-carrier-detect/ (stmmaceth: NetworkManager fails to bring up a wired Ethernet NIC) OS: Ubuntu 24.04 LTS Kernel: 6.8.0-22.22-generic 6.8.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062386/+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 2062386] Re: Maxlinear Ethernet GPY115B report gpy_config_aneg failed: -110 and Link UP is not visible
** Attachment added: "inxi - 6.8.0 - generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062386/+attachment/5767539/+files/inxi-6.8.0-22-generic.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/2062386 Title: Maxlinear Ethernet GPY115B report gpy_config_aneg failed: -110 and Link UP is not visible Status in linux package in Ubuntu: New Bug description: Hello Ubuntu Team, I notice issue today with Maxlinear Ethernet GPY115B controller. This controller report issue in dmesg and port not have link up. My target is: OnLogic HX310 with two Ethernet Ports. > Official page: https://www.onlogic.com/computers/industrial/fanless/helix-300/ Error: Maxlinear Ethernet GPY115B stmmac-3:01: gpy_config_aneg failed: -110 OS: Ubuntu 24.04 LTS Kernel: 6.8.0-22.22-generic 6.8.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062386/+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 2062386] Re: Maxlinear Ethernet GPY115B report gpy_config_aneg failed: -110 and Link UP is not visible
** Attachment added: "lspci - 6.8.0 - generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062386/+attachment/5767538/+files/lspci-6.8.0-22-generic.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/2062386 Title: Maxlinear Ethernet GPY115B report gpy_config_aneg failed: -110 and Link UP is not visible Status in linux package in Ubuntu: New Bug description: Hello Ubuntu Team, I notice issue today with Maxlinear Ethernet GPY115B controller. This controller report issue in dmesg and port not have link up. My target is: OnLogic HX310 with two Ethernet Ports. > Official page: https://www.onlogic.com/computers/industrial/fanless/helix-300/ Error: Maxlinear Ethernet GPY115B stmmac-3:01: gpy_config_aneg failed: -110 OS: Ubuntu 24.04 LTS Kernel: 6.8.0-22.22-generic 6.8.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062386/+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 2062386] Re: Maxlinear Ethernet GPY115B report gpy_config_aneg failed: -110 and Link UP is not visible
** Attachment added: "lshw - 6.8.0 - generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062386/+attachment/5767537/+files/lshw-6.8.0-22-generic.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/2062386 Title: Maxlinear Ethernet GPY115B report gpy_config_aneg failed: -110 and Link UP is not visible Status in linux package in Ubuntu: New Bug description: Hello Ubuntu Team, I notice issue today with Maxlinear Ethernet GPY115B controller. This controller report issue in dmesg and port not have link up. My target is: OnLogic HX310 with two Ethernet Ports. > Official page: https://www.onlogic.com/computers/industrial/fanless/helix-300/ Error: Maxlinear Ethernet GPY115B stmmac-3:01: gpy_config_aneg failed: -110 OS: Ubuntu 24.04 LTS Kernel: 6.8.0-22.22-generic 6.8.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062386/+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 2062386] [NEW] Maxlinear Ethernet GPY115B report gpy_config_aneg failed: -110 and Link UP is not visible
Public bug reported: Hello Ubuntu Team, I notice issue today with Maxlinear Ethernet GPY115B controller. This controller report issue in dmesg and port not have link up. My target is: OnLogic HX310 with two Ethernet Ports. > Official page: https://www.onlogic.com/computers/industrial/fanless/helix-300/ Error: Maxlinear Ethernet GPY115B stmmac-3:01: gpy_config_aneg failed: -110 OS: Ubuntu 24.04 LTS Kernel: 6.8.0-22.22-generic 6.8.1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Package changed: irqbalance (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2062386 Title: Maxlinear Ethernet GPY115B report gpy_config_aneg failed: -110 and Link UP is not visible Status in linux package in Ubuntu: New Bug description: Hello Ubuntu Team, I notice issue today with Maxlinear Ethernet GPY115B controller. This controller report issue in dmesg and port not have link up. My target is: OnLogic HX310 with two Ethernet Ports. > Official page: https://www.onlogic.com/computers/industrial/fanless/helix-300/ Error: Maxlinear Ethernet GPY115B stmmac-3:01: gpy_config_aneg failed: -110 OS: Ubuntu 24.04 LTS Kernel: 6.8.0-22.22-generic 6.8.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062386/+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 2062386] Re: Maxlinear Ethernet GPY115B report gpy_config_aneg failed: -110 and Link UP is not visible
** Attachment added: "dmesg - 6.8.0 - generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062386/+attachment/5767536/+files/dmesg-6.8.0-22-generic.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/2062386 Title: Maxlinear Ethernet GPY115B report gpy_config_aneg failed: -110 and Link UP is not visible Status in linux package in Ubuntu: New Bug description: Hello Ubuntu Team, I notice issue today with Maxlinear Ethernet GPY115B controller. This controller report issue in dmesg and port not have link up. My target is: OnLogic HX310 with two Ethernet Ports. > Official page: https://www.onlogic.com/computers/industrial/fanless/helix-300/ Error: Maxlinear Ethernet GPY115B stmmac-3:01: gpy_config_aneg failed: -110 OS: Ubuntu 24.04 LTS Kernel: 6.8.0-22.22-generic 6.8.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062386/+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 2060189] Re: "apt-get dist-upgrade" command causes the graphic display to stop working - OS is broken
Hi @juozaspo, This is fixed now. I use latest image: https://cdimage.ubuntu.com/daily-live/20240412/noble-desktop-amd64.iso Ticket is verifed. ** Changed in: linux (Ubuntu) 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/2060189 Title: "apt-get dist-upgrade" command causes the graphic display to stop working - OS is broken Status in linux package in Ubuntu: Fix Released Bug description: "apt-get dist-upgrade" command causes the display to stop working - OS is broken OS: Ubuntu Noble 24.04 LTS Kernel: 6.8.0 Canonical Command: apt-get dist-upgrade Status: First installation and execute dist-upgrade command to have latest packages. OS image: https://cdimage.ubuntu.com/daily-live/20240328.1/noble- desktop-amd64.iso To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060189/+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 2060189] [NEW] "apt-get dist-upgrade" command causes the graphic display to stop working - OS is broken
Public bug reported: "apt-get dist-upgrade" command causes the display to stop working - OS is broken OS: Ubuntu Noble 24.04 LTS Kernel: 6.8.0 Canonical Command: apt-get dist-upgrade Status: First installation and execute dist-upgrade command to have latest packages. OS image: https://cdimage.ubuntu.com/daily-live/20240328.1/noble- desktop-amd64.iso ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - apt-get dist-upgrade break graphics display from Ubuntu Noble + "apt-get dist-upgrade" command causes the display to stop working - OS is broken ** Summary changed: - "apt-get dist-upgrade" command causes the display to stop working - OS is broken + "apt-get dist-upgrade" command causes the graphic display to stop working - OS is broken ** Package changed: irqbalance (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2060189 Title: "apt-get dist-upgrade" command causes the graphic display to stop working - OS is broken Status in linux package in Ubuntu: New Bug description: "apt-get dist-upgrade" command causes the display to stop working - OS is broken OS: Ubuntu Noble 24.04 LTS Kernel: 6.8.0 Canonical Command: apt-get dist-upgrade Status: First installation and execute dist-upgrade command to have latest packages. OS image: https://cdimage.ubuntu.com/daily-live/20240328.1/noble- desktop-amd64.iso To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060189/+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 2052420] Re: nvidia-dkms-* FTBS with linux 6.8
** Patch added: "nvidia-drm-take-modeset-ownership-earlier.patch" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2052420/+attachment/5761484/+files/nvidia-drm-take-modeset-ownership-earlier.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/2052420 Title: nvidia-dkms-* FTBS with linux 6.8 Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-535 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-535-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-545 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470 source package in Noble: Fix Released Bug description: [Impact] ... In file included from /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:60: /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:748:40: error: ‘DRM_UNLOCKED’ undeclared here (not in a function); did you mean ‘VM_LOCKED’? 748 | DRM_RENDER_ALLOW|DRM_UNLOCKED), |^~~~ ... [Fix] Apply the attached debdiff. [How to test] Install (and rebuild) the patched package. [Regression potential] Two patches, none originating from NVidia and both touching locking: there's definitely regression potential here, hence i'm proposing this upload *only* for Noble and as a way to move forward (and not stall) until NVidia drops a new version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2052420/+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 2052420] Re: nvidia-dkms-* FTBS with linux 6.8
Hi, I have question, Is possible to add this patches: PATCH[0]="disable_fstack-clash-protection_fcf-protection.patch" PATCH[1]="buildfix_kernel_6.8-nv_drm_ioctls-DRM_UNLOCKED-is-now-the-default-behavi.patch" PATCH[2]="buildfix_kernel_6.8-gpl-pfn_valid.patch" PATCH[3]="nvidia-drm-hotplug-workqueue.patch" PATCH[4]="nvidia-drm-take-modeset-ownership-earlier.patch" At 0 to 2 exist now, but 3 and 4 not in 545. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/2052420 Title: nvidia-dkms-* FTBS with linux 6.8 Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-535 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-535-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-545 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470 source package in Noble: Fix Released Bug description: [Impact] ... In file included from /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:60: /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:748:40: error: ‘DRM_UNLOCKED’ undeclared here (not in a function); did you mean ‘VM_LOCKED’? 748 | DRM_RENDER_ALLOW|DRM_UNLOCKED), |^~~~ ... [Fix] Apply the attached debdiff. [How to test] Install (and rebuild) the patched package. [Regression potential] Two patches, none originating from NVidia and both touching locking: there's definitely regression potential here, hence i'm proposing this upload *only* for Noble and as a way to move forward (and not stall) until NVidia drops a new version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2052420/+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 2052420] Re: nvidia-dkms-* FTBS with linux 6.8
** Patch added: "nvidia-drm-hotplug-workqueue.patch" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2052420/+attachment/5761485/+files/nvidia-drm-hotplug-workqueue.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/2052420 Title: nvidia-dkms-* FTBS with linux 6.8 Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-535 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-535-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-545 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470 source package in Noble: Fix Released Bug description: [Impact] ... In file included from /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:60: /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:748:40: error: ‘DRM_UNLOCKED’ undeclared here (not in a function); did you mean ‘VM_LOCKED’? 748 | DRM_RENDER_ALLOW|DRM_UNLOCKED), |^~~~ ... [Fix] Apply the attached debdiff. [How to test] Install (and rebuild) the patched package. [Regression potential] Two patches, none originating from NVidia and both touching locking: there's definitely regression potential here, hence i'm proposing this upload *only* for Noble and as a way to move forward (and not stall) until NVidia drops a new version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2052420/+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 2058710] [NEW] CONFIG_IRQ_TIME_ACCOUNTING option is not enabled in kernel-generic - 6.8 kernel - ubuntu noble version
Public bug reported: Hi Ubuntu Kernel Team, I notice this today. This option CONFIG_IRQ_TIME_ACCOUNTING is not enabled in Ubuntu Noble 6.8 Kernel. Is possible to add this at built-in? # CONFIG_IRQ_TIME_ACCOUNTING is not set It would help me for profiling in the future, when testing applications in the performance area. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Package changed: irqbalance (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2058710 Title: CONFIG_IRQ_TIME_ACCOUNTING option is not enabled in kernel-generic - 6.8 kernel - ubuntu noble version Status in linux package in Ubuntu: New Bug description: Hi Ubuntu Kernel Team, I notice this today. This option CONFIG_IRQ_TIME_ACCOUNTING is not enabled in Ubuntu Noble 6.8 Kernel. Is possible to add this at built-in? # CONFIG_IRQ_TIME_ACCOUNTING is not set It would help me for profiling in the future, when testing applications in the performance area. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058710/+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 2057783] Re: hwmon-aaeon: probe of hwmon-aaeon.0 failed with error -22 - kernel 6.8 version
** Attachment added: "devices 2 6.8.0 noble - master-next - today" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057783/+attachment/5755595/+files/devices2.txt ** Description changed: hwmon-aaeon: probe of hwmon-aaeon.0 failed with error -22 - kernel 6.8 version device is not recognized when using 6.8 kernel version + + + /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/expensive + /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/guid + /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/instance_count + /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/modalias + /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/object_id + /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/uevent + + /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/driver: + 97845ED0-4E6D-11DE-8A39-0800200C9A66 + bind + module + uevent + unbind + + /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/gpio-aaeon.0: + driver + driver_override + gpio + gpiochip1 + modalias + power + subsystem + uevent + + /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/hwmon-aaeon.0: + driver_override + modalias + power + subsystem + uevent + + /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/leds-aaeon.0: + driver + driver_override + leds + modalias + power + subsystem + uevent + + /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/power: + async + autosuspend_delay_ms + control + runtime_active_kids + runtime_active_time + runtime_enabled + runtime_status + runtime_suspended_time + runtime_usage + + /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/subsystem: + devices + drivers + drivers_autoprobe + drivers_probe + uevent + + /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/wdt-aaeon.0: + driver_override + modalias + power + subsystem + uevent -- 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/2057783 Title: hwmon-aaeon: probe of hwmon-aaeon.0 failed with error -22 - kernel 6.8 version Status in linux package in Ubuntu: New Bug description: hwmon-aaeon: probe of hwmon-aaeon.0 failed with error -22 - kernel 6.8 version device is not recognized when using 6.8 kernel version /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/expensive /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/guid /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/instance_count /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/modalias /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/object_id /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/uevent /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/driver: 97845ED0-4E6D-11DE-8A39-0800200C9A66 bind module uevent unbind /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/gpio-aaeon.0: driver driver_override gpio gpiochip1 modalias power subsystem uevent /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/hwmon-aaeon.0: driver_override modalias power subsystem uevent /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/leds-aaeon.0: driver driver_override leds modalias power subsystem uevent /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/power: async autosuspend_delay_ms control runtime_active_kids runtime_active_time runtime_enabled runtime_status runtime_suspended_time runtime_usage /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/subsystem: devices drivers drivers_autoprobe drivers_probe uevent /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/wdt-aaeon.0: driver_override modalias power subsystem uevent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057783/+subscriptions -- Mailing
[Kernel-packages] [Bug 2057783] Re: hwmon-aaeon: probe of hwmon-aaeon.0 failed with error -22 - kernel 6.8 version
** Attachment added: "devices 1 6.8.0 noble - master-next - today" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057783/+attachment/5755594/+files/devices.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/2057783 Title: hwmon-aaeon: probe of hwmon-aaeon.0 failed with error -22 - kernel 6.8 version Status in linux package in Ubuntu: New Bug description: hwmon-aaeon: probe of hwmon-aaeon.0 failed with error -22 - kernel 6.8 version device is not recognized when using 6.8 kernel version /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/expensive /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/guid /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/instance_count /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/modalias /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/object_id /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/uevent /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/driver: 97845ED0-4E6D-11DE-8A39-0800200C9A66 bind module uevent unbind /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/gpio-aaeon.0: driver driver_override gpio gpiochip1 modalias power subsystem uevent /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/hwmon-aaeon.0: driver_override modalias power subsystem uevent /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/leds-aaeon.0: driver driver_override leds modalias power subsystem uevent /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/power: async autosuspend_delay_ms control runtime_active_kids runtime_active_time runtime_enabled runtime_status runtime_suspended_time runtime_usage /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/subsystem: devices drivers drivers_autoprobe drivers_probe uevent /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/wdt-aaeon.0: driver_override modalias power subsystem uevent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057783/+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 2057783] Re: hwmon-aaeon: probe of hwmon-aaeon.0 failed with error -22 - kernel 6.8 version
** Attachment added: "journalctl 6.8.0 noble - master-next - today" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057783/+attachment/5755593/+files/journalctl-6.8.0-ubuntu-noble-lowlatency1.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/2057783 Title: hwmon-aaeon: probe of hwmon-aaeon.0 failed with error -22 - kernel 6.8 version Status in linux package in Ubuntu: New Bug description: hwmon-aaeon: probe of hwmon-aaeon.0 failed with error -22 - kernel 6.8 version device is not recognized when using 6.8 kernel version /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/expensive /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/guid /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/instance_count /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/modalias /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/object_id /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/uevent /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/driver: 97845ED0-4E6D-11DE-8A39-0800200C9A66 bind module uevent unbind /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/gpio-aaeon.0: driver driver_override gpio gpiochip1 modalias power subsystem uevent /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/hwmon-aaeon.0: driver_override modalias power subsystem uevent /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/leds-aaeon.0: driver driver_override leds modalias power subsystem uevent /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/power: async autosuspend_delay_ms control runtime_active_kids runtime_active_time runtime_enabled runtime_status runtime_suspended_time runtime_usage /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/subsystem: devices drivers drivers_autoprobe drivers_probe uevent /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/wdt-aaeon.0: driver_override modalias power subsystem uevent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057783/+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 2057783] Re: hwmon-aaeon: probe of hwmon-aaeon.0 failed with error -22 - kernel 6.8 version
** Attachment added: "dmesg 6.8.0 noble - master-next - today" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057783/+attachment/5755592/+files/dmesg-6.8.0-ubuntu-noble-lowlatency1.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/2057783 Title: hwmon-aaeon: probe of hwmon-aaeon.0 failed with error -22 - kernel 6.8 version Status in linux package in Ubuntu: New Bug description: hwmon-aaeon: probe of hwmon-aaeon.0 failed with error -22 - kernel 6.8 version device is not recognized when using 6.8 kernel version /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/expensive /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/guid /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/instance_count /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/modalias /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/object_id /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/uevent /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/driver: 97845ED0-4E6D-11DE-8A39-0800200C9A66 bind module uevent unbind /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/gpio-aaeon.0: driver driver_override gpio gpiochip1 modalias power subsystem uevent /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/hwmon-aaeon.0: driver_override modalias power subsystem uevent /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/leds-aaeon.0: driver driver_override leds modalias power subsystem uevent /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/power: async autosuspend_delay_ms control runtime_active_kids runtime_active_time runtime_enabled runtime_status runtime_suspended_time runtime_usage /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/subsystem: devices drivers drivers_autoprobe drivers_probe uevent /sys/devices/platform/PNP0C14:03/wmi_bus/wmi_bus-PNP0C14:03/97845ED0-4E6D-11DE-8A39-0800200C9A66/wdt-aaeon.0: driver_override modalias power subsystem uevent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057783/+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 2057783] [NEW] hwmon-aaeon: probe of hwmon-aaeon.0 failed with error -22 - kernel 6.8 version
Public bug reported: hwmon-aaeon: probe of hwmon-aaeon.0 failed with error -22 - kernel 6.8 version device is not recognized when using 6.8 kernel version ** 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/2057783 Title: hwmon-aaeon: probe of hwmon-aaeon.0 failed with error -22 - kernel 6.8 version Status in linux package in Ubuntu: New Bug description: hwmon-aaeon: probe of hwmon-aaeon.0 failed with error -22 - kernel 6.8 version device is not recognized when using 6.8 kernel version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057783/+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 2052420] Re: nvidia-dkms-* FTBS with linux 6.8
Using kernel 6.8.0-rc5 this is working correctly with nvidia- driver-545=545.29.06-0ubuntu5. dpkg -l | grep nvidia ii libnvidia-cfg1-545:amd64 545.29.06-0ubuntu5 amd64NVIDIA binary OpenGL/GLX configuration library ii libnvidia-common-545 545.29.06-0ubuntu5 all Shared files used by the NVIDIA libraries ii libnvidia-compute-545:amd64545.29.06-0ubuntu5 amd64NVIDIA libcompute package ii libnvidia-compute-545:i386 545.29.06-0ubuntu5 i386 NVIDIA libcompute package ii libnvidia-decode-545:amd64 545.29.06-0ubuntu5 amd64NVIDIA Video Decoding runtime libraries ii libnvidia-decode-545:i386 545.29.06-0ubuntu5 i386 NVIDIA Video Decoding runtime libraries ii libnvidia-encode-545:amd64 545.29.06-0ubuntu5 amd64NVENC Video Encoding runtime library ii libnvidia-encode-545:i386 545.29.06-0ubuntu5 i386 NVENC Video Encoding runtime library ii libnvidia-extra-545:amd64 545.29.06-0ubuntu5 amd64Extra libraries for the NVIDIA driver ii libnvidia-fbc1-545:amd64 545.29.06-0ubuntu5 amd64NVIDIA OpenGL-based Framebuffer Capture runtime library ii libnvidia-fbc1-545:i386545.29.06-0ubuntu5 i386 NVIDIA OpenGL-based Framebuffer Capture runtime library ii libnvidia-gl-545:amd64 545.29.06-0ubuntu5 amd64NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD ii libnvidia-gl-545:i386 545.29.06-0ubuntu5 i386 NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD ii nvidia-compute-utils-545 545.29.06-0ubuntu5 amd64NVIDIA compute utilities ii nvidia-dkms-545545.29.06-0ubuntu5 amd64NVIDIA DKMS package ii nvidia-driver-545 545.29.06-0ubuntu5 amd64NVIDIA driver metapackage ii nvidia-firmware-545-545.29.06 545.29.06-0ubuntu5 amd64Firmware files used by the kernel module ii nvidia-headless-no-dkms-545545.29.06-0ubuntu5 amd64NVIDIA headless metapackage - no DKMS ii nvidia-kernel-common-545 545.29.06-0ubuntu5 amd64Shared files used with the kernel module ii nvidia-kernel-source-545 545.29.06-0ubuntu5 amd64NVIDIA kernel source package ii nvidia-prime 0.8.17.2 all Tools to enable NVIDIA's Prime ii nvidia-settings510.47.03-0ubuntu1 amd64Tool for configuring the NVIDIA graphics driver ii nvidia-utils-545 545.29.06-0ubuntu5 amd64NVIDIA driver support binaries ii screen-resolution-extra0.18.3 all Extension for the nvidia-settings control panel ii xserver-xorg-video-nvidia-545 545.29.06-0ubuntu5 amd64NVIDIA binary Xorg driver -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/2052420 Title: nvidia-dkms-* FTBS with linux 6.8 Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-535 package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-535-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-545 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470 source package in Noble: Fix Released Bug description: [Impact] ... In file included from /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:60: /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:748:40: error: ‘DRM_UNLOCKED’ undeclared here (not in a function); did you mean ‘VM_LOCKED’? 748 | DRM_RENDER_ALLOW|DRM_UNLOCKED), |^~~~ ... [Fix] Apply the attached debdiff. [How to test] Install (and rebuild) the patched package. [Regression potential] Two patches, none
[Kernel-packages] [Bug 2046551] [NEW] why turbostat report C-state with ACPI keyword on RPL-P?
Public bug reported: Hi Ubuntu Kernel Team, I have one question regarding C-states and Thermal functions. Why turbostat report three C-states with ACPI keyword(CxACPI)? Shouldn't I see up to 8 states inclusive? C7-C8? < cpu0: POLL: CPUIDLE CORE POLL IDLE cpu0: C1ACPI: ACPI FFH MWAIT 0x0 cpu0: C2ACPI: ACPI FFH MWAIT 0x21 cpu0: C3ACPI: ACPI FFH MWAIT 0x60 > # sudo turbostat turbostat version 2023.03.17 - Len Brown Kernel command line: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-14-generic root=UUID=33f926b8-92d0-49f9-8c4b-f387ad216fdf ro rootflags=subvol=@ quiet splash vt.handoff=7 CPUID(0): GenuineIntel 0x20 CPUID levels CPUID(1): family:model:stepping 0x6:ba:2 (6:186:2) microcode 0x4305 CPUID(0x8000): max_extended_levels: 0x8008 CPUID(1): SSE3 MONITOR SMX EIST TM2 TSC MSR ACPI-TM HT TM CPUID(6): APERF, TURBO, DTS, PTM, HWP, HWPnotify, HWPwindow, HWPepp, HWPpkg, EPB cpu0: MSR_IA32_MISC_ENABLE: 0x00850089 (TCC EIST MWAIT PREFETCH TURBO) CPUID(7): No-SGX Hybrid CPUID(0x15): eax_crystal: 2 ebx_tsc: 104 ecx_crystal_hz: 3840 TSC: 1996 MHz (3840 Hz * 104 / 2 / 100) CPUID(0x16): base_mhz: 2000 max_mhz: 4800 bus_mhz: 100 cpu0: MSR_MISC_PWR_MGMT: 0x30c2 (ENable-EIST_Coordination ENable-EPB DISable-OOB) RAPL: 9362 sec. Joule Counter Range, at 28 Watts cpu0: MSR_PLATFORM_INFO: 0x804043cf8811400 4 * 100.0 = 400.0 MHz max efficiency frequency 20 * 100.0 = 2000.0 MHz base frequency cpu0: MSR_IA32_POWER_CTL: 0x00f4005f (C1E auto-promotion: ENabled) cpu0: MSR_TURBO_RATIO_LIMIT: 0x282828282d2d3030 40 * 100.0 = 4000.0 MHz max turbo 8 active cores 40 * 100.0 = 4000.0 MHz max turbo 7 active cores 40 * 100.0 = 4000.0 MHz max turbo 6 active cores 40 * 100.0 = 4000.0 MHz max turbo 5 active cores 45 * 100.0 = 4500.0 MHz max turbo 4 active cores 45 * 100.0 = 4500.0 MHz max turbo 3 active cores 48 * 100.0 = 4800.0 MHz max turbo 2 active cores 48 * 100.0 = 4800.0 MHz max turbo 1 active cores cpu0: MSR_SECONDARY_TURBO_RATIO_LIMIT: 0x2424242425252525 36 * 100.0 = 3600.0 MHz max turbo 8 active cores 36 * 100.0 = 3600.0 MHz max turbo 7 active cores 36 * 100.0 = 3600.0 MHz max turbo 6 active cores 36 * 100.0 = 3600.0 MHz max turbo 5 active cores 37 * 100.0 = 3700.0 MHz max turbo 4 active cores 37 * 100.0 = 3700.0 MHz max turbo 3 active cores 37 * 100.0 = 3700.0 MHz max turbo 2 active cores 37 * 100.0 = 3700.0 MHz max turbo 1 active cores cpu0: MSR_CONFIG_TDP_NOMINAL: 0x0013 (base_ratio=19) cpu0: MSR_CONFIG_TDP_LEVEL_1: 0x000d00a0 (PKG_MIN_PWR_LVL1=0 PKG_MAX_PWR_LVL1=0 LVL1_RATIO=13 PKG_TDP_LVL1=160) cpu0: MSR_CONFIG_TDP_LEVEL_2: 0x00140118 (PKG_MIN_PWR_LVL2=0 PKG_MAX_PWR_LVL2=0 LVL2_RATIO=20 PKG_TDP_LVL2=280) cpu0: MSR_CONFIG_TDP_CONTROL: 0x ( lock=0) cpu0: MSR_TURBO_ACTIVATION_RATIO: 0x0012 (MAX_NON_TURBO_RATIO=18 lock=0) cpu0: MSR_PKG_CST_CONFIG_CONTROL: 0x7408 (UNdemote-C1, demote-C1, UNlocked, pkg-cstate-limit=8 (unlimited)) Uncore Frequency pkg0 die0: 400 - 4200 MHz (400 - 4200 MHz) /dev/cpu_dma_latency: 20 usec (default) current_driver: intel_idle current_governor: menu current_governor_ro: menu cpu0: POLL: CPUIDLE CORE POLL IDLE cpu0: C1ACPI: ACPI FFH MWAIT 0x0 cpu0: C2ACPI: ACPI FFH MWAIT 0x21 cpu0: C3ACPI: ACPI FFH MWAIT 0x60 cpu0: cpufreq driver: intel_pstate cpu0: cpufreq governor: powersave cpufreq intel_pstate no_turbo: 0 cpu0: MSR_MISC_FEATURE_CONTROL: 0x (L2-Prefetch L2-Prefetch-pair L1-Prefetch L1-IP-Prefetch) cpu0: MSR_PM_ENABLE: 0x0001 (HWP) cpu0: MSR_HWP_CAPABILITIES: 0x0110193d (high 61 guar 25 eff 16 low 1) cpu0: MSR_HWP_REQUEST: 0x3d06 (min 6 max 61 des 0 epp 0x0 window 0x0 pkg 0x0) cpu0: MSR_HWP_REQUEST_PKG: 0x8000ff01 (min 1 max 255 des 0 epp 0x80 window 0x0) cpu0: MSR_HWP_INTERRUPT: 0x0001 (EN_Guaranteed_Perf_Change, Dis_Excursion_Min) cpu0: MSR_HWP_STATUS: 0x (No-Guaranteed_Perf_Change, No-Excursion_Min) cpu0: EPB: 7 (custom) cpu0: MSR_RAPL_POWER_UNIT: 0x000a0e03 (0.125000 Watts, 0.61 Joules, 0.000977 sec.) cpu0: MSR_PKG_POWER_INFO: 0x00e0 (28 W TDP, RAPL 0 - 0 W, 0.00 sec.) cpu0: MSR_PKG_POWER_LIMIT: 0x4282dd80e0 (UNlocked) cpu0: PKG Limit #1: ENabled (28.000 Watts, 28.00 sec, clamp ENabled) cpu0: PKG Limit #2: ENabled (64.000 Watts, 0.002441* sec, clamp DISabled) cpu0: MSR_VR_CURRENT_CONFIG: 0x03f0 cpu0: PKG Limit #4: 126.00 Watts (UNlocked) cpu0: MSR_DRAM_POWER_LIMIT: 0x (UNlocked) cpu0: DRAM Limit: DISabled (0.000 Watts, 0.000977 sec, clamp DISabled) cpu0: MSR_PP0_POLICY: 9 cpu0: MSR_PP0_POWER_LIMIT: 0x (UNlocked) cpu0: Cores Limit: DISabled (0.000 Watts, 0.000977 sec, clamp DISabled) cpu0: MSR_PP1_POLICY: 13 cpu0: MSR_PP1_POWER_LIMIT: 0x (UNlocked) cpu0: GFX Limit: DISabled (0.000 Watts, 0.000977 sec, clamp DISabled) cpu0: MSR_IA32_TEMPERATURE_TARGET: 0x8064 (100 C) cpu0: MSR_IA32_PACKAGE_THERM_STATUS: 0x8839 (43 C) cpu0: MSR_IA32_PACKAGE_THERM_INTERRUPT: 0x0203 (100 C, 100 C) cpu0: MSR_PKGC3_IRTL: 0x (NOTvalid, 0 ns) cpu0: MSR_PKGC6_IRTL:
[Kernel-packages] [Bug 2000785] Re: package linux-intel-iotg-tools-common 5.15.0-1018.23 failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common
This is reproduced again when using 5.15.0-1045-intel-iotg or 5.15.0-1046-intel-iotg. sudo apt install linux-tools-intel-iotg -f Reading package lists... Done Building dependency tree... Done Reading state information... Done linux-tools-intel-iotg is already the newest version (5.15.0.1045.45). You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: linux-intel-iotg-tools-5.15.0-1045 : Depends: linux-tools-common but it is not going to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2000785 Title: package linux-intel-iotg-tools-common 5.15.0-1018.23 failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-56.62 Status in linux-intel-iotg package in Ubuntu: Confirmed Bug description: Does not let me upgrade with sudo apt upgrade says there is an error even though I have not changed anything in the system files. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-intel-iotg-tools-common 5.15.0-1018.23 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 AptOrdering: linux-intel-iotg-tools-common:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Dec 30 13:50:37 2022 DpkgTerminalLog: Preparing to unpack .../linux-intel-iotg-tools-common_5.15.0-1021.26_all.deb ... Unpacking linux-intel-iotg-tools-common (5.15.0-1021.26) over (5.15.0-1018.23) ... dpkg: error processing archive /var/cache/apt/archives/linux-intel-iotg-tools-common_5.15.0-1021.26_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-56.62 DuplicateSignature: package:linux-intel-iotg-tools-common:5.15.0-1018.23 Unpacking linux-intel-iotg-tools-common (5.15.0-1021.26) over (5.15.0-1018.23) ... dpkg: error processing archive /var/cache/apt/archives/linux-intel-iotg-tools-common_5.15.0-1021.26_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-56.62 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-56.62 InstallationDate: Installed on 2022-10-06 (84 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: linux-intel-iotg Title: package linux-intel-iotg-tools-common 5.15.0-1018.23 failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.15.0-56.62 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2000785/+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 2045652] Re: RIP: 0010:__ieee80211_scan_completed+0x2ba/0x2d0 [mac80211]
** Attachment added: "journalctl-5.15.0-1043-intel-iotg" https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2045652/+attachment/5726397/+files/journalctl-5.15.0-1043-intel-iotg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2045652 Title: RIP: 0010:__ieee80211_scan_completed+0x2ba/0x2d0 [mac80211] Status in linux-intel-iotg package in Ubuntu: New Bug description: Hi Ubuntu Team, I notice this today when using 5.15.0-1043-intel-iotg version: ieee80211 phy0: Hardware restart was requested [ cut here ] WARNING: CPU: 10 PID: 25430 at net/mac80211/scan.c:436 __ieee80211_scan_completed+0x2ba/0x2d0 [mac80211] Modules linked in: cpuid rfcomm ccm cmac algif_hash algif_skcipher af_alg snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic bnep intel_rapl_msr intel_rapl_common intel_tcc_cooling binfmt_misc x86_pkg_temp_thermal intel_powerclamp snd_sof_pci_intel> cmdlinepart ttm uvcvideo(OE) mei_hdcp kfifo_buf tps6598x rapl bluetooth drm_kms_helper videobuf2_vmalloc snd_timer spi_nor hid_sensor_iio_common typec nls_iso8859_1 videobuf2_memops intel_cstate wmi_bmof industrialio videobuf2_v4l2 cfg80211 mtd snd videobuf2_> CPU: 10 PID: 25430 Comm: kworker/u32:5 Tainted: G OE 5.15.0-1043-intel-iotg #49-Ubuntu Hardware name: Intel(R) Client Systems NUC12WSKi7/NUC12WSBi7, BIOS WSADL357.0088.2023.0505.1623 05/05/2023 Workqueue: phy0 ieee80211_scan_work [mac80211] RIP: 0010:__ieee80211_scan_completed+0x2ba/0x2d0 [mac80211] Code: 0f a3 05 69 7f 28 dd 0f 83 32 ff ff ff 48 8b 05 9c 29 0e 00 48 85 c0 74 0c 48 8b 78 08 4c 89 e6 e8 5b 27 04 00 e9 15 ff ff ff <0f> 0b 48 83 c4 08 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc 90 RSP: 0018:977ec35cbdd0 EFLAGS: 00010246 RAX: RBX: RCX: 8c2980051020 RDX: 8c29814ccd40 RSI: 0001 RDI: 8c2986c78820 RBP: 977ec35cbe00 R08: 8c29902dc2b0 R09: R10: 0005 R11: R12: 8c2986c78820 R13: 8c2986c79ab8 R14: R15: 0001 FS: () GS:8c2d0788() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7fa91c2fb140 CR3: 000246362000 CR4: 00750ee0 PKRU: 5554 Call Trace: ? show_trace_log_lvl+0x1d6/0x2ea ? show_trace_log_lvl+0x1d6/0x2ea ? ieee80211_scan_work+0x161/0x660 [mac80211] ? show_regs.part.0+0x23/0x29 ? show_regs.cold+0x8/0xd ? __ieee80211_scan_completed+0x2ba/0x2d0 [mac80211] ? __warn+0x8c/0x100 ? __ieee80211_scan_completed+0x2ba/0x2d0 [mac80211] ? report_bug+0xa4/0xd0 ? handle_bug+0x39/0x90 ? exc_invalid_op+0x19/0x70 ? asm_exc_invalid_op+0x1b/0x20 ? __ieee80211_scan_completed+0x2ba/0x2d0 [mac80211] ieee80211_scan_work+0x161/0x660 [mac80211] ? finish_task_switch.isra.0+0x7e/0x280 process_one_work+0x228/0x3d0 worker_thread+0x53/0x420 ? process_one_work+0x3d0/0x3d0 kthread+0x127/0x150 ? set_kthread_struct+0x50/0x50 ret_from_fork+0x1f/0x30 ---[ end trace aafb2113ef5ea025 ]--- iwlwifi :00:14.3: Master Disable Timed Out, 100 usec Firmware files for iwlwifi in /lib/firmware: ls -l /lib/firmware/iwlwifi-so-a0-gf-a0-* -rw-r--r-- 1 root root 1515812 aug 15 12:07 /lib/firmware/iwlwifi-so-a0-gf-a0-64.ucode -rw-r--r-- 1 root root 1524432 aug 15 12:07 /lib/firmware/iwlwifi-so-a0-gf-a0-67.ucode -rw-r--r-- 1 root root 1533812 aug 15 12:07 /lib/firmware/iwlwifi-so-a0-gf-a0-68.ucode -rw-r--r-- 1 root root 1550124 aug 15 12:07 /lib/firmware/iwlwifi-so-a0-gf-a0-71.ucode -rw-r--r-- 1 root root 1560532 aug 15 12:07 /lib/firmware/iwlwifi-so-a0-gf-a0-72.ucode -rw-r--r-- 1 root root 1563692 aug 15 12:07 /lib/firmware/iwlwifi-so-a0-gf-a0-73.ucode -rw-r--r-- 1 root root 1577460 aug 15 12:07 /lib/firmware/iwlwifi-so-a0-gf-a0-74.ucode -rw-r--r-- 1 root root 1641260 aug 15 12:07 /lib/firmware/iwlwifi-so-a0-gf-a0-77.ucode -rw-r--r-- 1 root root 1667236 aug 15 12:07 /lib/firmware/iwlwifi-so-a0-gf-a0-78.ucode -rw-r--r-- 1 root root 1672988 aug 15 12:07 /lib/firmware/iwlwifi-so-a0-gf-a0-79.ucode Wifi Adapter: lspci -vv -s 00:14.3 [sudo] password for inechita: 00:14.3 Network controller: Intel Corporation Alder Lake-P PCH CNVi WiFi (rev 01) DeviceName: Onboard - Ethernet Subsystem: Intel Corporation Device 0090 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi Devices: 00:00.0 Host bridge: Intel Corporation Device 4621 (rev 02) 00:02.0 VGA compatible
[Kernel-packages] [Bug 2045652] Re: RIP: 0010:__ieee80211_scan_completed+0x2ba/0x2d0 [mac80211]
** Attachment added: "dmesg-5.15.0-1043-intel-iotg" https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2045652/+attachment/5726396/+files/dmesg-5.15.0-1043-intel-iotg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2045652 Title: RIP: 0010:__ieee80211_scan_completed+0x2ba/0x2d0 [mac80211] Status in linux-intel-iotg package in Ubuntu: New Bug description: Hi Ubuntu Team, I notice this today when using 5.15.0-1043-intel-iotg version: ieee80211 phy0: Hardware restart was requested [ cut here ] WARNING: CPU: 10 PID: 25430 at net/mac80211/scan.c:436 __ieee80211_scan_completed+0x2ba/0x2d0 [mac80211] Modules linked in: cpuid rfcomm ccm cmac algif_hash algif_skcipher af_alg snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic bnep intel_rapl_msr intel_rapl_common intel_tcc_cooling binfmt_misc x86_pkg_temp_thermal intel_powerclamp snd_sof_pci_intel> cmdlinepart ttm uvcvideo(OE) mei_hdcp kfifo_buf tps6598x rapl bluetooth drm_kms_helper videobuf2_vmalloc snd_timer spi_nor hid_sensor_iio_common typec nls_iso8859_1 videobuf2_memops intel_cstate wmi_bmof industrialio videobuf2_v4l2 cfg80211 mtd snd videobuf2_> CPU: 10 PID: 25430 Comm: kworker/u32:5 Tainted: G OE 5.15.0-1043-intel-iotg #49-Ubuntu Hardware name: Intel(R) Client Systems NUC12WSKi7/NUC12WSBi7, BIOS WSADL357.0088.2023.0505.1623 05/05/2023 Workqueue: phy0 ieee80211_scan_work [mac80211] RIP: 0010:__ieee80211_scan_completed+0x2ba/0x2d0 [mac80211] Code: 0f a3 05 69 7f 28 dd 0f 83 32 ff ff ff 48 8b 05 9c 29 0e 00 48 85 c0 74 0c 48 8b 78 08 4c 89 e6 e8 5b 27 04 00 e9 15 ff ff ff <0f> 0b 48 83 c4 08 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc 90 RSP: 0018:977ec35cbdd0 EFLAGS: 00010246 RAX: RBX: RCX: 8c2980051020 RDX: 8c29814ccd40 RSI: 0001 RDI: 8c2986c78820 RBP: 977ec35cbe00 R08: 8c29902dc2b0 R09: R10: 0005 R11: R12: 8c2986c78820 R13: 8c2986c79ab8 R14: R15: 0001 FS: () GS:8c2d0788() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7fa91c2fb140 CR3: 000246362000 CR4: 00750ee0 PKRU: 5554 Call Trace: ? show_trace_log_lvl+0x1d6/0x2ea ? show_trace_log_lvl+0x1d6/0x2ea ? ieee80211_scan_work+0x161/0x660 [mac80211] ? show_regs.part.0+0x23/0x29 ? show_regs.cold+0x8/0xd ? __ieee80211_scan_completed+0x2ba/0x2d0 [mac80211] ? __warn+0x8c/0x100 ? __ieee80211_scan_completed+0x2ba/0x2d0 [mac80211] ? report_bug+0xa4/0xd0 ? handle_bug+0x39/0x90 ? exc_invalid_op+0x19/0x70 ? asm_exc_invalid_op+0x1b/0x20 ? __ieee80211_scan_completed+0x2ba/0x2d0 [mac80211] ieee80211_scan_work+0x161/0x660 [mac80211] ? finish_task_switch.isra.0+0x7e/0x280 process_one_work+0x228/0x3d0 worker_thread+0x53/0x420 ? process_one_work+0x3d0/0x3d0 kthread+0x127/0x150 ? set_kthread_struct+0x50/0x50 ret_from_fork+0x1f/0x30 ---[ end trace aafb2113ef5ea025 ]--- iwlwifi :00:14.3: Master Disable Timed Out, 100 usec Firmware files for iwlwifi in /lib/firmware: ls -l /lib/firmware/iwlwifi-so-a0-gf-a0-* -rw-r--r-- 1 root root 1515812 aug 15 12:07 /lib/firmware/iwlwifi-so-a0-gf-a0-64.ucode -rw-r--r-- 1 root root 1524432 aug 15 12:07 /lib/firmware/iwlwifi-so-a0-gf-a0-67.ucode -rw-r--r-- 1 root root 1533812 aug 15 12:07 /lib/firmware/iwlwifi-so-a0-gf-a0-68.ucode -rw-r--r-- 1 root root 1550124 aug 15 12:07 /lib/firmware/iwlwifi-so-a0-gf-a0-71.ucode -rw-r--r-- 1 root root 1560532 aug 15 12:07 /lib/firmware/iwlwifi-so-a0-gf-a0-72.ucode -rw-r--r-- 1 root root 1563692 aug 15 12:07 /lib/firmware/iwlwifi-so-a0-gf-a0-73.ucode -rw-r--r-- 1 root root 1577460 aug 15 12:07 /lib/firmware/iwlwifi-so-a0-gf-a0-74.ucode -rw-r--r-- 1 root root 1641260 aug 15 12:07 /lib/firmware/iwlwifi-so-a0-gf-a0-77.ucode -rw-r--r-- 1 root root 1667236 aug 15 12:07 /lib/firmware/iwlwifi-so-a0-gf-a0-78.ucode -rw-r--r-- 1 root root 1672988 aug 15 12:07 /lib/firmware/iwlwifi-so-a0-gf-a0-79.ucode Wifi Adapter: lspci -vv -s 00:14.3 [sudo] password for inechita: 00:14.3 Network controller: Intel Corporation Alder Lake-P PCH CNVi WiFi (rev 01) DeviceName: Onboard - Ethernet Subsystem: Intel Corporation Device 0090 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi Devices: 00:00.0 Host bridge: Intel Corporation Device 4621 (rev 02) 00:02.0 VGA compatible controller: Intel
[Kernel-packages] [Bug 2045652] [NEW] RIP: 0010:__ieee80211_scan_completed+0x2ba/0x2d0 [mac80211]
Public bug reported: Hi Ubuntu Team, I notice this today when using 5.15.0-1043-intel-iotg version: ieee80211 phy0: Hardware restart was requested [ cut here ] WARNING: CPU: 10 PID: 25430 at net/mac80211/scan.c:436 __ieee80211_scan_completed+0x2ba/0x2d0 [mac80211] Modules linked in: cpuid rfcomm ccm cmac algif_hash algif_skcipher af_alg snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic bnep intel_rapl_msr intel_rapl_common intel_tcc_cooling binfmt_misc x86_pkg_temp_thermal intel_powerclamp snd_sof_pci_intel> cmdlinepart ttm uvcvideo(OE) mei_hdcp kfifo_buf tps6598x rapl bluetooth drm_kms_helper videobuf2_vmalloc snd_timer spi_nor hid_sensor_iio_common typec nls_iso8859_1 videobuf2_memops intel_cstate wmi_bmof industrialio videobuf2_v4l2 cfg80211 mtd snd videobuf2_> CPU: 10 PID: 25430 Comm: kworker/u32:5 Tainted: G OE 5.15.0-1043-intel-iotg #49-Ubuntu Hardware name: Intel(R) Client Systems NUC12WSKi7/NUC12WSBi7, BIOS WSADL357.0088.2023.0505.1623 05/05/2023 Workqueue: phy0 ieee80211_scan_work [mac80211] RIP: 0010:__ieee80211_scan_completed+0x2ba/0x2d0 [mac80211] Code: 0f a3 05 69 7f 28 dd 0f 83 32 ff ff ff 48 8b 05 9c 29 0e 00 48 85 c0 74 0c 48 8b 78 08 4c 89 e6 e8 5b 27 04 00 e9 15 ff ff ff <0f> 0b 48 83 c4 08 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc 90 RSP: 0018:977ec35cbdd0 EFLAGS: 00010246 RAX: RBX: RCX: 8c2980051020 RDX: 8c29814ccd40 RSI: 0001 RDI: 8c2986c78820 RBP: 977ec35cbe00 R08: 8c29902dc2b0 R09: R10: 0005 R11: R12: 8c2986c78820 R13: 8c2986c79ab8 R14: R15: 0001 FS: () GS:8c2d0788() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7fa91c2fb140 CR3: 000246362000 CR4: 00750ee0 PKRU: 5554 Call Trace: ? show_trace_log_lvl+0x1d6/0x2ea ? show_trace_log_lvl+0x1d6/0x2ea ? ieee80211_scan_work+0x161/0x660 [mac80211] ? show_regs.part.0+0x23/0x29 ? show_regs.cold+0x8/0xd ? __ieee80211_scan_completed+0x2ba/0x2d0 [mac80211] ? __warn+0x8c/0x100 ? __ieee80211_scan_completed+0x2ba/0x2d0 [mac80211] ? report_bug+0xa4/0xd0 ? handle_bug+0x39/0x90 ? exc_invalid_op+0x19/0x70 ? asm_exc_invalid_op+0x1b/0x20 ? __ieee80211_scan_completed+0x2ba/0x2d0 [mac80211] ieee80211_scan_work+0x161/0x660 [mac80211] ? finish_task_switch.isra.0+0x7e/0x280 process_one_work+0x228/0x3d0 worker_thread+0x53/0x420 ? process_one_work+0x3d0/0x3d0 kthread+0x127/0x150 ? set_kthread_struct+0x50/0x50 ret_from_fork+0x1f/0x30 ---[ end trace aafb2113ef5ea025 ]--- iwlwifi :00:14.3: Master Disable Timed Out, 100 usec Firmware files for iwlwifi in /lib/firmware: ls -l /lib/firmware/iwlwifi-so-a0-gf-a0-* -rw-r--r-- 1 root root 1515812 aug 15 12:07 /lib/firmware/iwlwifi-so-a0-gf-a0-64.ucode -rw-r--r-- 1 root root 1524432 aug 15 12:07 /lib/firmware/iwlwifi-so-a0-gf-a0-67.ucode -rw-r--r-- 1 root root 1533812 aug 15 12:07 /lib/firmware/iwlwifi-so-a0-gf-a0-68.ucode -rw-r--r-- 1 root root 1550124 aug 15 12:07 /lib/firmware/iwlwifi-so-a0-gf-a0-71.ucode -rw-r--r-- 1 root root 1560532 aug 15 12:07 /lib/firmware/iwlwifi-so-a0-gf-a0-72.ucode -rw-r--r-- 1 root root 1563692 aug 15 12:07 /lib/firmware/iwlwifi-so-a0-gf-a0-73.ucode -rw-r--r-- 1 root root 1577460 aug 15 12:07 /lib/firmware/iwlwifi-so-a0-gf-a0-74.ucode -rw-r--r-- 1 root root 1641260 aug 15 12:07 /lib/firmware/iwlwifi-so-a0-gf-a0-77.ucode -rw-r--r-- 1 root root 1667236 aug 15 12:07 /lib/firmware/iwlwifi-so-a0-gf-a0-78.ucode -rw-r--r-- 1 root root 1672988 aug 15 12:07 /lib/firmware/iwlwifi-so-a0-gf-a0-79.ucode Wifi Adapter: lspci -vv -s 00:14.3 [sudo] password for inechita: 00:14.3 Network controller: Intel Corporation Alder Lake-P PCH CNVi WiFi (rev 01) DeviceName: Onboard - Ethernet Subsystem: Intel Corporation Device 0090 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi Devices: 00:00.0 Host bridge: Intel Corporation Device 4621 (rev 02) 00:02.0 VGA compatible controller: Intel Corporation Alder Lake-P Integrated Graphics Controller (rev 0c) 00:06.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x4 Controller #0 (rev 02) 00:07.0 PCI bridge: Intel Corporation Alder Lake-P Thunderbolt 4 PCI Express Root Port #0 (rev 02) 00:07.2 PCI bridge: Intel Corporation Alder Lake-P Thunderbolt 4 PCI Express Root Port #2 (rev 02) 00:08.0 System peripheral: Intel Corporation 12th Gen Core Processor Gaussian & Neural Accelerator (rev 02) 00:0a.0 Signal processing controller: Intel Corporation Platform Monitoring Technology (rev 01) 00:0d.0 USB controller: Intel Corporation Alder Lake-P
[Kernel-packages] [Bug 2033869] Re: linux-intel-iotg package - bump to 6.6 kernel version - linux-intel-iotg-b
** Summary changed: - linux-intel-iotg package - bump to 6.5 kernel version - linux-intel-iotg-b + linux-intel-iotg package - bump to 6.6 kernel version - linux-intel-iotg-b ** Description changed: - linux-intel-iotg package - bump to 6.5 kernel version - linux-intel- + linux-intel-iotg package - bump to 6.6 kernel version - linux-intel- iotg-b -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2033869 Title: linux-intel-iotg package - bump to 6.6 kernel version - linux-intel- iotg-b Status in linux-intel-iotg package in Ubuntu: New Bug description: linux-intel-iotg package - bump to 6.6 kernel version - linux-intel- iotg-b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2033869/+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 2039802] [NEW] [IOTG][ADL-P] TGPIO enabling
Public bug reported: Hello Ubuntu Team, I notice today using default iot and proposed iot kernel, missing TGPIO and GPIO support. IOT: 5.15.0-1040-intel-iotg Proposed IOT: 5.15.0-1042-intel-iotg With TGPIO support in kernel, i have this in dmesg: dmesg | grep -i gpio [1.954807] acpi MSFT0101:00: GPIO: looking up 0 in _CRS [2.153305] i2c_designware i2c_designware.0: GPIO lookup for consumer scl [2.153307] i2c_designware i2c_designware.0: using ACPI for GPIO lookup [2.153309] acpi device:6b: GPIO: looking up scl-gpios [2.153310] acpi device:6b: GPIO: looking up scl-gpio [2.153312] i2c_designware i2c_designware.0: using lookup tables for GPIO lookup [2.153313] i2c_designware i2c_designware.0: No GPIO consumer scl found [2.189085] i2c_designware i2c_designware.1: GPIO lookup for consumer scl [2.189087] i2c_designware i2c_designware.1: using ACPI for GPIO lookup [2.189088] acpi device:6c: GPIO: looking up scl-gpios [2.189090] acpi device:6c: GPIO: looking up scl-gpio [2.189091] i2c_designware i2c_designware.1: using lookup tables for GPIO lookup [2.189092] i2c_designware i2c_designware.1: No GPIO consumer scl found [2.197541] mdio_bus fixed-0: GPIO lookup for consumer reset [2.197542] mdio_bus fixed-0: using lookup tables for GPIO lookup [2.197543] mdio_bus fixed-0: No GPIO consumer reset found [2.209058] rtc_cmos rtc_cmos: GPIO lookup for consumer wp [2.209059] rtc_cmos rtc_cmos: using lookup tables for GPIO lookup [2.209060] rtc_cmos rtc_cmos: No GPIO consumer wp found [2.626844] gpiochip_find_base: found new base at 664 [2.633323] gpio gpiochip0: (INTC1055:00): created GPIO range 0->25 ==> INTC1055:00 PIN 0->25 [2.633327] gpio gpiochip0: (INTC1055:00): created GPIO range 32->47 ==> INTC1055:00 PIN 26->41 [2.633328] gpio gpiochip0: (INTC1055:00): created GPIO range 64->88 ==> INTC1055:00 PIN 42->66 [2.633329] gpio gpiochip0: (INTC1055:00): created GPIO range 96->103 ==> INTC1055:00 PIN 67->74 [2.61] gpio gpiochip0: (INTC1055:00): created GPIO range 128->151 ==> INTC1055:00 PIN 75->98 [2.62] gpio gpiochip0: (INTC1055:00): created GPIO range 160->180 ==> INTC1055:00 PIN 99->119 [2.63] gpio gpiochip0: (INTC1055:00): created GPIO range 192->215 ==> INTC1055:00 PIN 120->143 [2.64] gpio gpiochip0: (INTC1055:00): created GPIO range 224->252 ==> INTC1055:00 PIN 144->172 [2.65] gpio gpiochip0: (INTC1055:00): created GPIO range 256->279 ==> INTC1055:00 PIN 173->196 [2.67] gpio gpiochip0: (INTC1055:00): created GPIO range 288->312 ==> INTC1055:00 PIN 197->221 [2.68] gpio gpiochip0: (INTC1055:00): created GPIO range 320->344 ==> INTC1055:00 PIN 228->252 [2.69] gpio gpiochip0: (INTC1055:00): created GPIO range 352->359 ==> INTC1055:00 PIN 262->269 [2.633397] gpio gpiochip0: (INTC1055:00): added GPIO chardev (254:0) [2.633412] gpio gpiochip0: registered GPIOs 664 to 1023 on INTC1055:00 [4.144080] usb 3-10: GPIO lookup for consumer reset [4.144084] usb 3-10: using ACPI for GPIO lookup [4.144086] acpi device:5f: GPIO: looking up reset-gpios [4.144088] acpi device:5f: GPIO: looking up reset-gpio [4.144089] usb 3-10: using lookup tables for GPIO lookup [4.144090] usb 3-10: No GPIO consumer reset found [4.184939] usb 4-1: GPIO lookup for consumer privacy [4.184941] usb 4-1: using ACPI for GPIO lookup [4.184943] acpi device:62: GPIO: looking up privacy-gpios [4.184945] acpi device:62: GPIO: looking up privacy-gpio [4.184945] usb 4-1: using lookup tables for GPIO lookup [4.184946] usb 4-1: No GPIO consumer privacy found [4.186515] usb 4-1: GPIO lookup for consumer privacy [4.186516] usb 4-1: using ACPI for GPIO lookup [4.186517] acpi device:62: GPIO: looking up privacy-gpios [4.186518] acpi device:62: GPIO: looking up privacy-gpio [4.186519] usb 4-1: using lookup tables for GPIO lookup [4.186519] usb 4-1: No GPIO consumer privacy found But the support in the IOT kernel does not exist. # dmesg | grep -i gpio # uname -a Linux 5.15.0-1042-intel-iotg #48-Ubuntu SMP Wed Sep 20 15:09:23 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Is it possible that in the next version we will have support for GPIO and TGPIO? ** Affects: linux-intel-iotg (Ubuntu) Importance: Undecided Status: New ** Tags: gpio ** Description changed: Hello Ubuntu Team, I notice today using default iot and proposed iot kernel, missing TGPIO and GPIO support. IOT: 5.15.0-1040-intel-iotg Proposed IOT: 5.15.0-1042-intel-iotg - With TGPIO support in kernel, i have this in dmesg: dmesg | grep -i gpio [1.954807] acpi MSFT0101:00: GPIO: looking up 0 in _CRS [2.153305] i2c_designware i2c_designware.0: GPIO lookup for consumer scl [2.153307] i2c_designware i2c_designware.0: using ACPI for GPIO lookup [2.153309] acpi device:6b: GPIO: looking up scl-gpios
[Kernel-packages] [Bug 2036963] [NEW] Failed to query (GET_CUR) UVC control 1 on unit 3: -32
Public bug reported: OS: Ubuntu 22.04 IOT LTS (Desktop Variant) Kernel: 5.15.0-1041-intel-iotg I saw these messages in dmesg, which kept repeating. They appear from a connected camera. >From what I checked, on 5.15.x and 6.1.x these messages are reproduced. But in more recent versions this no longer appears. I also checked with 6.4.16, and they don't appear here. I think that some patches should be backported to fix this in 5.15.x/6.1.x. Error in dmesg: [ 33.544105] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 33.563270] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 33.574097] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 33.601145] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 33.613708] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 33.623929] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 33.634310] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 33.946547] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 33.957067] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 33.967461] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 33.977853] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 34.289393] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 34.299890] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 34.812146] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 36.124273] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 37.135203] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 38.146115] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 39.156864] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 40.167860] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 42.179408] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 47.192040] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 48.203038] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 49.213861] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 50.224582] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 53.236352] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 54.247259] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 55.258187] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 56.269120] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 58.280241] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 59.291090] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 60.301797] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 71.315896] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 77.328361] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 78.339034] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 91.354741] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 92.365583] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 100.379191] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 101.390003] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 102.400869] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 103.411702] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 107.423497] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 108.434002] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 110.444780] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 112.455848] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 113.466695] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 114.477536] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 115.488395] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 119.500343] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit 3: -32 (exp. 1024). [ 120.511291] usb 4-1: Failed to query (GET_CUR) UVC control 1 on unit
[Kernel-packages] [Bug 2033869] [NEW] linux-intel-iotg package - bump to 6.5 kernel version - linux-intel-iotg-b
Public bug reported: linux-intel-iotg package - bump to 6.5 kernel version - linux-intel- iotg-b ** Affects: linux-intel-iotg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2033869 Title: linux-intel-iotg package - bump to 6.5 kernel version - linux-intel- iotg-b Status in linux-intel-iotg package in Ubuntu: New Bug description: linux-intel-iotg package - bump to 6.5 kernel version - linux-intel- iotg-b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2033869/+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 2033868] [NEW] linux-intel-iotg package - bump to 6.1 kernel version - linux-intel-iotg-a
Public bug reported: linux-intel-iotg package - bump to 6.1 kernel version - linux-intel- iotg-a ** Affects: linux-intel-iotg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2033868 Title: linux-intel-iotg package - bump to 6.1 kernel version - linux-intel- iotg-a Status in linux-intel-iotg package in Ubuntu: New Bug description: linux-intel-iotg package - bump to 6.1 kernel version - linux-intel- iotg-a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2033868/+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 2026887] Re: gnome-shell 42.9 Wayland sessions fail to start on Intel 12th gen or later if running 5.15/5.17 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB
Hi Steve Langasek, I reinstalled today my PC with Ubuntu Desktop IOT. And i use latest packages from proposed repository. This issue is now resolved. My PC now running this: Kernel version: 5.15.0-1035-intel-iotg #40-Ubuntu SMP Fri Jul 14 08:03:36 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Mutter version: dpkg -l | grep mutter ii gir1.2-mutter-10:amd64 42.9-0ubuntu4 amd64GObject introspection data for Mutter ii libmutter-10-0:amd64 42.9-0ubuntu4 amd64window manager library from the Mutter window manager ii mutter-common 42.9-0ubuntu4 all shared files for the Mutter window manager Thank you Daniel and Unnikrishnan for your support. A good day. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2026887 Title: gnome-shell 42.9 Wayland sessions fail to start on Intel 12th gen or later if running 5.15/5.17 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Fix Released Status in linux-intel-iotg package in Ubuntu: Confirmed Status in linux-oem-5.17 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Kinetic: Invalid Status in mutter source package in Lunar: Invalid Status in mutter source package in Mantic: Invalid Bug description: [ Impact ] gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder Lake systems running older kernels such as 5.15. [ Test Plan ] Try to log into gnome-shell. Verify there is a picture on the screen. [ Where problems could occur ] The offending code change relates to Intel-specific chip IDs so the change is limited to Intel systems. Although affected Intel systems worked perfectly before the change so we don't expect any problems in reverting the change. In theory the worst case is limited to more problems like that described in Impact above. [ Workarounds ] Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment or upgrade to a newer kernel: sudo apt install linux-generic-hwe-22.04 [ Other Info ] The log messages relating to this bug are: iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument ... For kinetic: The bug never existed in mutter 43.0 (it was introduced in 43.2) and was already fixed in the kernel anyway. For lunar and later: The bug was already fixed in the kernel. You would only ever encounter it in theory if you downgrade the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026887/+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 2026887] Re: gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers
Hi Andreas, I reinstalled today my PC with Ubuntu Desktop IOT. And i use latest packages from proposed repository. This issue is now resolved. My PC now running this: Kernel version: 5.15.0-1035-intel-iotg #40-Ubuntu SMP Fri Jul 14 08:03:36 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Mutter version: dpkg -l | grep mutter ii gir1.2-mutter-10:amd64 42.9-0ubuntu3 amd64GObject introspection data for Mutter ii libmutter-10-0:amd64 42.9-0ubuntu3 amd64window manager library from the Mutter window manager ii mutter-common 42.9-0ubuntu3 all shared files for the Mutter window manager Thank you Daniel for your support. A good day. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2026887 Title: gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Fix Released Status in linux-intel-iotg package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Kinetic: Invalid Status in mutter source package in Lunar: Invalid Status in mutter source package in Mantic: Invalid Bug description: [ Impact ] gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder Lake systems running older kernels such as 5.15. [ Test Plan ] Try to log into gnome-shell. Verify there is a picture on the screen. [ Where problems could occur ] The offending code change relates to Intel-specific chip IDs so the change is limited to Intel systems. Although affected Intel systems worked perfectly before the change so we don't expect any problems in reverting the change. In theory the worst case is limited to more problems like that described in Impact above. [ Workarounds ] Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment or upgrade to a newer kernel: sudo apt install linux-generic-hwe-22.04 [ Other Info ] The log messages relating to this bug are: iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument ... For kinetic: The bug never existed in mutter 43.0 (it was introduced in 43.2) and was already fixed in the kernel anyway. For lunar and later: The bug was already fixed in the kernel. You would only ever encounter it in theory if you downgrade the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026887/+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 2026887] Re: gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers
Hi Andreas, Will try to check new packages in next days. Thanks for all. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2026887 Title: gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Fix Released Status in linux-intel-iotg package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Kinetic: Invalid Status in mutter source package in Lunar: Invalid Status in mutter source package in Mantic: Invalid Bug description: [ Impact ] gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder Lake systems running older kernels such as 5.15. [ Test Plan ] Try to log into gnome-shell. Verify there is a picture on the screen. [ Where problems could occur ] The offending code change relates to Intel-specific chip IDs so the change is limited to Intel systems. Although affected Intel systems worked perfectly before the change so we don't expect any problems in reverting the change. In theory the worst case is limited to more problems like that described in Impact above. [ Workarounds ] Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment or upgrade to a newer kernel: sudo apt install linux-generic-hwe-22.04 [ Other Info ] The log messages relating to this bug are: iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument ... For kinetic: The bug never existed in mutter 43.0 (it was introduced in 43.2) and was already fixed in the kernel anyway. For lunar and later: The bug was already fixed in the kernel. You would only ever encounter it in theory if you downgrade the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026887/+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 2026887] Re: gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers
Hi Daniel, I reinstalled today my ADL-P PC with Ubuntu Desktop 22.04.02. And this is not reproduced with -generic kernel. I have this: 5.19.0-46-generic #47~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jun 21 15:35:31 UTC 2 x86_64 x86_64 x86_64 GNU/Linux And no error with this. LIBMUTTER VERSION: dpkg -l | grep libmutter ii libmutter-10-0:amd64 42.9-0ubuntu1 amd64window manager library from the Mutter window manage GNOME SHELL VERSION: dpkg -l | grep gnome-shell ii gnome-shell42.9-0ubuntu2 amd64graphical shell for the GNOME desktop KERNEL VERSION: dpkg -l | grep linux-image ii linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 amd64Signed kernel image generic ii linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1 amd64Signed kernel image generic ii linux-image-generic-hwe-22.04 5.19.0.46.47~22.04.21 amd64Generic Linux kernel image -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2026887 Title: gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Fix Released Status in linux-intel-iotg package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Kinetic: Invalid Status in mutter source package in Lunar: Invalid Status in mutter source package in Mantic: Invalid Bug description: [ Impact ] gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder Lake systems running older kernels such as 5.15. [ Test Plan ] Try to log into gnome-shell. Verify there is a picture on the screen. [ Where problems could occur ] The offending code change relates to Intel-specific chip IDs so the change is limited to Intel systems. Although affected Intel systems worked perfectly before the change so we don't expect any problems in reverting the change. In theory the worst case is limited to more problems like that described in Impact above. [ Workarounds ] Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment or upgrade to a newer kernel: sudo apt install linux-generic-hwe-22.04 [ Other Info ] The log messages relating to this bug are: iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument ... For kinetic: The bug never existed in mutter 43.0 (it was introduced in 43.2) and was already fixed in the kernel anyway. For lunar and later: The bug was already fixed in the kernel. You would only ever encounter it in theory if you downgrade the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026887/+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
