[Kernel-packages] [Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
Yep, Focal is also affected. Will this fix also be available for Focal? Edit: I have tried to add it here, but looked wrong. Not sure if it's the right way to add Focal to this bug. ** Also affects: focal (Ubuntu) Importance: Undecided Status: New ** No longer affects: focal (Ubuntu) ** No longer affects: focal (Ubuntu Jammy) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2060780 Title: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: Hi, updated some Ubuntu 22.04 systems to lastest available state this morning, which caused CIFS mounts (from various fileservers) to stop working. Kernel was updated to version 5.15.0-102-generic. I can mount the shares without problems (mount -t cifs), but then, df for example tells me: df: /mnt: Resource temporarily unavailable. I'm able to list and browse all the files, but accessing them (even readonly) is very unstable. Sometimes it works and sometimes it just gives me i/o errors. Switching back to 5.15.0-101-generic or 5.15.0-100-generic solves the problem and everything works again as expected. Seems like some bug has been implemented in 5.15.0-102-generic... To reproduce the problem, I started a while loop on one server to write to some file on a specific mounted CIFS share and read it from another one root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; sleep 1 ; done -bash: /mnt/hallo.txt: Input/output error -bash: /mnt/hallo.txt: Input/output error ^C root@:~$ tail -f /mnt/hallo.txt Tue Apr 9 04:10:52 PM CEST 2024 hallo Tue Apr 9 04:10:53 PM CEST 2024 hallo Tue Apr 9 04:10:54 PM CEST 2024 hallo Tue Apr 9 04:10:55 PM CEST 2024 hallo Tue Apr 9 04:10:56 PM CEST 2024 hallo Tue Apr 9 04:10:57 PM CEST 2024 hallo Tue Apr 9 04:10:58 PM CEST 2024 hallo Tue Apr 9 04:10:59 PM CEST 2024 hallo Tue Apr 9 04:11:00 PM CEST 2024 hallo Tue Apr 9 04:11:01 PM CEST 2024 hallo tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: Resource temporarily unavailable Tue Apr 9 04:11:04 PM CEST 2024 hallo Tue Apr 9 04:11:05 PM CEST 2024 hallo Tue Apr 9 04:11:06 PM CEST 2024 hallo Tue Apr 9 04:11:07 PM CEST 2024 hallo Tue Apr 9 04:11:08 PM CEST 2024 hallo Tue Apr 9 04:11:09 PM CEST 2024 hallo Tue Apr 9 04:11:10 PM CEST 2024 hallo While doing this, both servers tell me, the resource is unavailable root@:~# df -h /mnt df: /mnt: Resource temporarily unavailable root@:~$ df -h /mnt df: /mnt: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+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 2061949] [NEW] nouveau error
Public bug reported: Randomly nouveau throw this error in the kernel log: # dmesg | grep nouveau [ 28.273960] nouveau: detected PR support, will not use DSM [ 28.274007] nouveau :59:00.0: enabling device ( -> 0003) [ 28.274453] nouveau :59:00.0: NVIDIA TU117 (167000a1) [ 28.426297] nouveau :59:00.0: bios: version 90.17.61.00.73 [ 28.432619] nouveau :59:00.0: pmu: firmware unavailable [ 28.438647] nouveau :59:00.0: fb: 2048 MiB GDDR6 [ 28.494446] nouveau :59:00.0: DRM: VRAM: 2048 MiB [ 28.494450] nouveau :59:00.0: DRM: GART: 536870912 MiB [ 28.494454] nouveau :59:00.0: DRM: BIT table 'A' not found [ 28.494456] nouveau :59:00.0: DRM: BIT table 'L' not found [ 28.494459] nouveau :59:00.0: DRM: Pointer to TMDS table not found [ 28.495543] nouveau :59:00.0: DRM: MM: using COPY for buffer copies [ 28.495954] [drm] Initialized nouveau 1.4.0 20120801 for :59:00.0 on minor 0 [ 28.496030] nouveau :59:00.0: [drm] No compatible format found [ 28.496034] nouveau :59:00.0: [drm] Cannot find any crtc or sizes [ 37.185011] Modules linked in: uhid qrtr cmac algif_hash algif_skcipher af_alg bnep snd_ctl_led snd_soc_skl_hda_dsp snd_soc_hdac_hdmi snd_soc_intel_hda_dsp_common snd_sof_probes snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_soc_dmic snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_generic_allocation soundwire_bus xe snd_soc_core xt_multiport xt_tcpudp snd_compress ac97_bus xt_conntrack snd_pcm_dmaengine nf_conntrack snd_hda_intel nf_defrag_ipv6 intel_uncore_frequency snd_intel_dspcfg nf_defrag_ipv4 intel_uncore_frequency_common snd_intel_sdw_acpi nft_compat drm_suballoc_helper intel_tcc_cooling snd_hda_codec x86_pkg_temp_thermal intel_powerclamp snd_hda_core snd_hwdep coretemp nouveau nf_tables binfmt_misc libcrc32c snd_pcm iwlmvm cmdlinepart uvcvideo btu sb kvm_intel snd_seq_midi spi_nor [ 37.185418] nouveau_display_hpd_resume+0x49/0x60 [nouveau] [ 37.185661] nouveau_pmops_runtime_resume+0xef/0x1a0 [nouveau] [ 4142.358848] nouveau :59:00.0: fifo:PBDMA0: CTXNOTVALID chid:2 [ 4142.358854] nouveau :59:00.0: fifo:00:0002:0002:[Xwayland[20073]] errored - disabling channel [ 4142.358866] nouveau :59:00.0: Xwayland[20073]: channel 2 killed! I think this is a regression, because I remember the same issue was fixed by using updated linux-firmware. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-22-generic 6.8.0-22.22 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:neo3076 F pipewire /dev/snd/controlC0: neo3076 F pipewire neo3079 F wireplumber CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 17 07:27:34 2024 InstallationDate: Installed on 2024-03-22 (25 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) MachineType: ASUSTeK COMPUTER INC. ZenBook UX435EG_UX435EG 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=/vmlinuz-6.8.0-22-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash ipv6.disable=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-22-generic N/A linux-backports-modules-6.8.0-22-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-04-11 (6 days ago) dmi.bios.date: 04/22/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX435EG.315 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX435EG dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX435EG.315:bd04/22/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX435EG_UX435EG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX435EG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX435EG_UX435EG dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2061949 Title: nouveau error Status in
[Kernel-packages] [Bug 2051947] Re: Sound: Add rtl quirk of M70-Gen5
** Changed in: hwe-next Status: New => Fix Released -- 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/2051947 Title: Sound: Add rtl quirk of M70-Gen5 Status in HWE Next: Fix Released Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] When plugin the headset jack, only speaker is identified. [Fix] Add ALC283_FIXUP_HEADSET_MIC quirk to make its headset mic work. [Test] Vendor tested on hardware, headset mic works fine. [Where problems could occur] It may break audio. This commit is merged by stable updates in noble kernel, 5.15 doesn't support this platform, SRU for mantic and oem-6.5. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051947/+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 2054773] Re: Fix AMD brightness issue on AUO panel
** Changed in: hwe-next Status: New => Fix Released -- 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/2054773 Title: Fix AMD brightness issue on AUO panel Status in HWE Next: Fix Released Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] When change brightness quickly on gnome menu, AUO panel will be stuck in previous brightness. [Fix] The TCON is random hung by PSR-SU. Force enable ffu mode on PSR-SU panel. [Test] Tested on hardware, the brightness is changed as expected. [Where problems could occur] It may break AMD display. The commit is already in v6.8-rc5, the platform is not fully supported in Jammy 5.15, So SRU oem-6.5 and mantic. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2054773/+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 2060268] Re: Phantom 46" monitor (simpledrm) shown in Settings after installing the Nvidia driver
I'm guessing this might also be the cause of the oversized panning login screen I get with Nvidia 470? ** Also affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/2060268 Title: Phantom 46" monitor (simpledrm) shown in Settings after installing the Nvidia driver Status in linux package in Ubuntu: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in nvidia-graphics-drivers-545 package in Ubuntu: New Bug description: After installing Nvidia driver 545 on a single (27") monitor system, Settings shows a phantom 46" monitor of the same resolution. It looks like the phantom monitor is /dev/dri/card0 which is still controlled by simpledrm, while Nvidia uses /dev/dri/card1. --- ProblemType: Bug ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:dan4631 F pipewire /dev/snd/controlC1: dan4636 F wireplumber CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-01-04 (92 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127) MachineType: Intel(R) Client Systems NUC12DCMi7 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240318.git3b128b60-0ubuntu1 Tags: noble Uname: Linux 6.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 12/20/2021 dmi.bios.release: 5.24 dmi.bios.vendor: Intel Corp. dmi.bios.version: EDADL579.0046.2021.1220.2351 dmi.board.name: NUC12EDBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M27908-302 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.7 dmi.modalias: dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7: dmi.product.family: DC dmi.product.name: NUC12DCMi7 dmi.product.sku: RNUC12DCMi7 dmi.product.version: M30143-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060268/+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 2061940] [NEW] Some DUTs can't boot up after installing the proposed kernel on Mantic
Public bug reported: During the SRU testing for 6.5.0.33 kernel, I found some machines freeze at very early stage of booting process. The last messages displayed on the screen are: EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path EFI stub: Measured initrd data into PCR 9 There are not journal logs existed when I boot with previous kernel. Here is the list of the impacted machines that I found so far https://certification.canonical.com/hardware/202106-29206/ https://certification.canonical.com/hardware/202106-29207/ https://certification.canonical.com/hardware/201912-27623/ https://certification.canonical.com/hardware/202007-28059/ https://certification.canonical.com/hardware/202103-28762/ https://certification.canonical.com/hardware/202012-28510/ ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: cert-sru regression-proposed -- 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/2061940 Title: Some DUTs can't boot up after installing the proposed kernel on Mantic Status in linux package in Ubuntu: New Bug description: During the SRU testing for 6.5.0.33 kernel, I found some machines freeze at very early stage of booting process. The last messages displayed on the screen are: EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path EFI stub: Measured initrd data into PCR 9 There are not journal logs existed when I boot with previous kernel. Here is the list of the impacted machines that I found so far https://certification.canonical.com/hardware/202106-29206/ https://certification.canonical.com/hardware/202106-29207/ https://certification.canonical.com/hardware/201912-27623/ https://certification.canonical.com/hardware/202007-28059/ https://certification.canonical.com/hardware/202103-28762/ https://certification.canonical.com/hardware/202012-28510/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061940/+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 2028158] Re: [SRU] Duplicate Device_dax ids Created and hence Probing is Failing.
Source: https://www.kernel.org/doc/Documentation/memory-hotplug.txt
How to online memory
When the memory is hot-added, the kernel decides whether or not to "online"
it according to the policy which can be read from "auto_online_blocks" file::
% cat /sys/devices/system/memory/auto_online_blocks
The default depends on the CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE kernel config
option. If it is disabled the default is "offline" which means the newly added
memory is not in a ready-to-use state and you have to "online" the newly added
memory blocks manually. Automatic onlining can be requested by writing "online"
to "auto_online_blocks" file::
% echo online > /sys/devices/system/memory/auto_online_blocks
This sets a global policy and impacts all memory blocks that will subsequently
be hotplugged.
If this is enabled by default then the following should achieve the same
goal as disabling the config option:
echo offline > /sys/devices/system/memory/auto_online_blocks
--
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/2028158
Title:
[SRU] Duplicate Device_dax ids Created and hence Probing is Failing.
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Lunar:
Fix Released
Status in linux source package in Mantic:
Fix Released
Bug description:
[Impact]
Description of problem:
Observed device_dax related probe errors in dmesg when HBM CPU is set
to flat mode. Duplicate device_dax ids were created and hence probing
is failing.
How reproducible:
Frequently
Version-Release
Release:22.04.2, 22.10
[Test Case]
Steps to Reproduce:
1. Set HBM cpu to flat mode in memory settings in BIOS.
2. Boot to the OS.
3. Perform OS warm boot cycle test.
4. Observe the dax2.0/dax3.0/dax4.0/dax5.0 probe error.
Actual results:
Observed device_dax related errors in dmesg, device Dax is creating
dummy/duplicate devices and probe failing.
Expected results:
Dummy/duplicate devices should not create.
[Fix]
Upstream Fix
https://lore.kernel.org/linux-mm/166890823379.4183293.15333502171004313377.st...@dwillia2-xfh.jf.intel.com/T/
[Where problems could occur]
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2028158_device_dax_2
Additional info:
SUT is having 2*32C HBM cpus. Eligible system-ram mode change devices should
be only 2[dax0.0, dax1.0], but under "daxctl list -u" is showing 1st time 4
devices [dax0.0, 1.0, 2.0, 3.0], 2 is "state":"disabled" and 2 more devices is
"mode":"devdax" which are actuall devadax to system-ram convertible devices.
After reconfigure-device dax0.0, dax1.0 when you list the devices couple of
more dummy/dumplicate devices are creating with "state":"disabled"[Ex: dax4.0,
5.0 etc..].
root@ubuntu:/home/ubuntu# daxctl list -u
[
{
"chardev":"dax1.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3,
"align":2097152,
"mode":"devdax"---> HBM CPU 1, This we can change the devdax
to
system-ram
},
{
"chardev":"dax2.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax3.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax0.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2,
"align":2097152,
"mode":"devdax" ---> HBM CPU 1, This we can change the devdax
to
system-ram
}
]
root@ubuntu:/home/ubuntu# dmesg | grep -i error
[ 12.748884] device_dax: probe of dax2.0 failed with error -16
[ 12.748902] device_dax: probe of dax3.0 failed with error -16
After reconfig-device devdax to system-ram below are the results:
---
root@ubuntu:/home/ubuntu# daxctl reconfigure-device -m system-ram dax0.0 -u
{
"chardev":"dax0.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2,
"align":2097152,
"mode":"system-ram",
"online_memblocks":32,
"total_memblocks":32,
"movable":true
}
reconfigured 1 device
root@ubuntu:/home/ubuntu# daxctl reconfigure-device -m system-ram dax1.0 -u
{
"chardev":"dax1.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3,
"align":2097152,
"mode":"system-ram",
"online_memblocks":32,
"total_memblocks":32,
"movable":true
}
reconfigured 1 device
root@ubuntu:/home/ubuntu# daxctl list -u
[
{
"chardev":"dax4.0",
[Kernel-packages] [Bug 2060989] Re: package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to install/upgrade: installed linux-headers-6.5.0-27-generic package post-installation script subprocess r
>From the make.log above, it seems that the dkms built nvidia-fs-2.19.6
on 6.5.0-26-generic kernel header. Could you try dkms build the nvidia-
fs-2.19.6 on 6.5.0-27-generic kernel header on your own? (add the -k
6.5.0-27-generic on dkms build)
--
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/2060989
Title:
package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to
install/upgrade: installed linux-headers-6.5.0-27-generic package
post-installation script subprocess returned error exit status 1
Status in linux package in Ubuntu:
In Progress
Bug description:
-
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-27-generic 6.5.0-27.28
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nela 2694 F wireplumber
/dev/snd/controlC1: nela 2694 F wireplumber
/dev/snd/seq:nela 2674 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Thu Apr 11 10:13:36 2024
ErrorMessage: installed linux-headers-6.5.0-27-generic package
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2024-03-30 (12 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic
root=UUID=e960f11c-d239-429e-97af-9073de7f3b3a ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to
install/upgrade: installed linux-headers-6.5.0-27-generic package
post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/02/2021
dmi.bios.release: 1.27
dmi.bios.vendor: LENOVO
dmi.bios.version: HACN27WW
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: Legion S7 15ACH6
dmi.ec.firmware.release: 1.27
dmi.modalias:
dmi:bvnLENOVO:bvrHACN27WW:bd08/02/2021:br1.27:efr1.27:svnLENOVO:pn82K8:pvrLegionS715ACH6:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegionS715ACH6:skuLENOVO_MT_82K8_BU_idea_FM_LegionS715ACH6:
dmi.product.family: Legion S7 15ACH6
dmi.product.name: 82K8
dmi.product.sku: LENOVO_MT_82K8_BU_idea_FM_Legion S7 15ACH6
dmi.product.version: Legion S7 15ACH6
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060989/+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 2061091] Re: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)
And this call trace looks is related to current issue, I guess snd_power_ref_and_wait was waiting for snd_card_disconnect which wakes up power_sleep at the end of the code, but snd_card_disconnect -> snd_device_disconnect_all -> snd_pcm_dev_disconnect was blocked for some reason. Apr 15 21:48:23 xps9320 kernel: [43261.751897] INFO: task kworker/0:6:34416 blocked for more than 120 seconds. Apr 15 21:48:23 xps9320 kernel: [43261.751900] Tainted: G OE 6.5.0-27-generic #28~22.04.1-Ubuntu Apr 15 21:48:23 xps9320 kernel: [43261.751901] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Apr 15 21:48:23 xps9320 kernel: [43261.751903] task:kworker/0:6 state:D stack:0 pid:34416 ppid:2 flags:0x4000 Apr 15 21:48:23 xps9320 kernel: [43261.751907] Workqueue: usb_hub_wq hub_event Apr 15 21:48:23 xps9320 kernel: [43261.751913] Call Trace: Apr 15 21:48:23 xps9320 kernel: [43261.751915] Apr 15 21:48:23 xps9320 kernel: [43261.751916] __schedule+0x2cb/0x750 Apr 15 21:48:23 xps9320 kernel: [43261.751921] schedule+0x63/0x110 Apr 15 21:48:23 xps9320 kernel: [43261.751924] schedule_preempt_disabled+0x15/0x30 Apr 15 21:48:23 xps9320 kernel: [43261.751928] rwsem_down_write_slowpath+0x2a2/0x550 Apr 15 21:48:23 xps9320 kernel: [43261.751940] down_write+0x5c/0x80 Apr 15 21:48:23 xps9320 kernel: [43261.751945] snd_pcm_dev_disconnect+0x1d2/0x280 [snd_pcm] Apr 15 21:48:23 xps9320 kernel: [43261.751964] snd_device_disconnect_all+0x47/0xa0 [snd] Apr 15 21:48:23 xps9320 kernel: [43261.751979] snd_card_disconnect.part.0+0x10d/0x290 [snd] Apr 15 21:48:23 xps9320 kernel: [43261.752019] ? rpm_idle+0x25/0x2b0 Apr 15 21:48:23 xps9320 kernel: [43261.752023] snd_card_disconnect+0x13/0x30 [snd] Apr 15 21:48:23 xps9320 kernel: [43261.752039] usb_audio_disconnect+0x114/0x2c0 [snd_usb_audio] Apr 15 21:48:23 xps9320 kernel: [43261.752064] usb_unbind_interface+0x8e/0x280 Apr 15 21:48:23 xps9320 kernel: [43261.752069] device_remove+0x65/0x80 Apr 15 21:48:23 xps9320 kernel: [43261.752072] device_release_driver_internal+0x20b/0x270 Apr 15 21:48:23 xps9320 kernel: [43261.752077] device_release_driver+0x12/0x20 Apr 15 21:48:23 xps9320 kernel: [43261.752080] bus_remove_device+0xcb/0x140 Apr 15 21:48:23 xps9320 kernel: [43261.752083] device_del+0x161/0x3e0 Apr 15 21:48:23 xps9320 kernel: [43261.752086] ? kobject_put+0x67/0xa0 Apr 15 21:48:23 xps9320 kernel: [43261.752090] usb_disable_device+0xd5/0x280 Apr 15 21:48:23 xps9320 kernel: [43261.752093] usb_disconnect+0xe9/0x2e0 Apr 15 21:48:23 xps9320 kernel: [43261.752097] usb_disconnect+0xcd/0x2e0 Apr 15 21:48:23 xps9320 kernel: [43261.752100] usb_disconnect+0xcd/0x2e0 Apr 15 21:48:23 xps9320 kernel: [43261.752102] ? usb_control_msg+0x106/0x160 Apr 15 21:48:23 xps9320 kernel: [43261.752105] hub_port_connect+0x90/0xc30 Apr 15 21:48:23 xps9320 kernel: [43261.752109] hub_port_connect_change+0x91/0x300 Apr 15 21:48:23 xps9320 kernel: [43261.752113] port_event+0x652/0x810 Apr 15 21:48:23 xps9320 kernel: [43261.752117] hub_event+0x155/0x450 Apr 15 21:48:23 xps9320 kernel: [43261.752120] process_one_work+0x23d/0x450 Apr 15 21:48:23 xps9320 kernel: [43261.752125] worker_thread+0x50/0x3f0 Apr 15 21:48:23 xps9320 kernel: [43261.752128] ? __pfx_worker_thread+0x10/0x10 Apr 15 21:48:23 xps9320 kernel: [43261.752131] kthread+0xef/0x120 Apr 15 21:48:23 xps9320 kernel: [43261.752135] ? __pfx_kthread+0x10/0x10 Apr 15 21:48:23 xps9320 kernel: [43261.752139] ret_from_fork+0x44/0x70 Apr 15 21:48:23 xps9320 kernel: [43261.752143] ? __pfx_kthread+0x10/0x10 Apr 15 21:48:23 xps9320 kernel: [43261.752147] ret_from_fork_asm+0x1b/0x30 Apr 15 21:48:23 xps9320 kernel: [43261.752151] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2061091 Title: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0) Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: Sometimes, when trying to shut down or suspend my laptop, it gets stuck on the console screen. If I was suspending, it eventually gives up and goes back to the X session. During a shutdown it hangs forever and the only solution seems to be to force a reboot with Magic-SysRq. The following appears in `kern.log`: ``` Apr 12 08:59:54 xps9320 kernel: [173172.510341] Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): Apr 12 08:59:54 xps9320 kernel: [173172.515669] task:wireplumber state:D stack:0 pid:2408 ppid:2398 flags:0x0006 Apr 12 08:59:54 xps9320 kernel: [173172.518923] Call Trace: Apr 12 08:59:54 xps9320 kernel: [173172.521755] Apr 12 08:59:54 xps9320 kernel: [173172.524099] __schedule+0x2cb/0x750 Apr 12 08:59:54 xps9320 kernel: [173172.526333] schedule+0x63/0x110 Apr 12 08:59:54 xps9320 kernel:
[Kernel-packages] [Bug 2049733] Re: Dynamically determine acpi_handle_list size
** Tags removed: verification-needed-mantic-linux ** Tags added: verification-done-mantic-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049733 Title: Dynamically determine acpi_handle_list size Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Committed Bug description: [Impact] ACPI handle list will be dynamic allocated without default fixed size. [Fix] Currently the ACPI_MAX_HANDLES is defined fix to 10, and it is not enough for some platforms that called ACPI _PSL method to get passive cooling device objects. then will get the error message "Invalid passive threshold", this patch change the fixed size with the dynamic handle list size which fixes the handle reference error. [Test Case] check the dmesg to see if there is the error message "Invalid passive threshold" [Where problems could occur] Only change the fixed size with the dynamic handle list size. Risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049733/+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 2061091] Re: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)
There is another calltrace in kern.log which might be another issue (probably need a separated bug report). Apr 15 21:45:23 xps9320 kernel: [43079.109011] Apr 15 21:45:23 xps9320 kernel: [43079.112281] UBSAN: shift-out-of-bounds in /build/linux-hwe-6.5-jkqeMi/linux-hwe-6.5-6.5.0/drivers/gpu/drm/display/drm_dp_mst_topology.c:4416:36 Apr 15 21:45:23 xps9320 kernel: [43079.115601] shift exponent -1 is negative Apr 15 21:45:23 xps9320 kernel: [43079.119073] CPU: 0 PID: 34404 Comm: kworker/0:3 Tainted: G OE 6.5.0-27-generic #28~22.04.1-Ubuntu Apr 15 21:45:23 xps9320 kernel: [43079.122523] Hardware name: Dell Inc. XPS 9320/0CW9KM, BIOS 2.8.0 11/13/2023 Apr 15 21:45:23 xps9320 kernel: [43079.126024] Workqueue: events output_poll_execute [drm_kms_helper] Apr 15 21:45:23 xps9320 kernel: [43079.129530] Call Trace: Apr 15 21:45:23 xps9320 kernel: [43079.132985] Apr 15 21:45:23 xps9320 kernel: [43079.136412] dump_stack_lvl+0x48/0x70 Apr 15 21:45:23 xps9320 kernel: [43079.139805] dump_stack+0x10/0x20 Apr 15 21:45:23 xps9320 kernel: [43079.143170] __ubsan_handle_shift_out_of_bounds+0x1ac/0x360 Apr 15 21:45:23 xps9320 kernel: [43079.146525] drm_dp_atomic_release_time_slots.cold+0x17/0x3d [drm_display_helper] Apr 15 21:45:23 xps9320 kernel: [43079.149904] intel_dp_mst_atomic_check+0xaa/0x180 [i915] Apr 15 21:45:23 xps9320 kernel: [43079.153378] ? update_connector_routing+0x2fc/0x3f0 [drm_kms_helper] Apr 15 21:45:23 xps9320 kernel: [43079.156738] drm_atomic_helper_check_modeset+0x300/0x610 [drm_kms_helper] Apr 15 21:45:23 xps9320 kernel: [43079.160084] intel_atomic_check+0xfe/0xb80 [i915] Apr 15 21:45:23 xps9320 kernel: [43079.163518] ? drm_plane_check_pixel_format+0x53/0xe0 [drm] Apr 15 21:45:23 xps9320 kernel: [43079.166858] drm_atomic_check_only+0x1ac/0x400 [drm] Apr 15 21:45:23 xps9320 kernel: [43079.170172] ? update_output_state+0x184/0x1a0 [drm] Apr 15 21:45:23 xps9320 kernel: [43079.173478] drm_atomic_commit+0x58/0xd0 [drm] Apr 15 21:45:23 xps9320 kernel: [43079.176765] ? __pfx___drm_printfn_info+0x10/0x10 [drm] Apr 15 21:45:23 xps9320 kernel: [43079.180049] drm_client_modeset_commit_atomic+0x203/0x240 [drm] Apr 15 21:45:23 xps9320 kernel: [43079.183332] drm_client_modeset_commit_locked+0x5b/0x170 [drm] Apr 15 21:45:23 xps9320 kernel: [43079.186586] ? mutex_lock+0x12/0x50 Apr 15 21:45:23 xps9320 kernel: [43079.189776] drm_client_modeset_commit+0x26/0x50 [drm] Apr 15 21:45:23 xps9320 kernel: [43079.192980] __drm_fb_helper_restore_fbdev_mode_unlocked+0xc2/0x100 [drm_kms_helper] Apr 15 21:45:23 xps9320 kernel: [43079.196179] drm_fb_helper_hotplug_event+0x10b/0x120 [drm_kms_helper] Apr 15 21:45:23 xps9320 kernel: [43079.199336] intel_fbdev_output_poll_changed+0x6b/0xb0 [i915] Apr 15 21:45:23 xps9320 kernel: [43079.202568] output_poll_execute+0x237/0x280 [drm_kms_helper] Apr 15 21:45:23 xps9320 kernel: [43079.205686] ? __schedule+0x2d3/0x750 Apr 15 21:45:23 xps9320 kernel: [43079.208777] process_one_work+0x23d/0x450 Apr 15 21:45:23 xps9320 kernel: [43079.211856] worker_thread+0x50/0x3f0 Apr 15 21:45:23 xps9320 kernel: [43079.214921] ? __pfx_worker_thread+0x10/0x10 Apr 15 21:45:23 xps9320 kernel: [43079.217984] kthread+0xef/0x120 Apr 15 21:45:23 xps9320 kernel: [43079.221037] ? __pfx_kthread+0x10/0x10 Apr 15 21:45:23 xps9320 kernel: [43079.224072] ret_from_fork+0x44/0x70 Apr 15 21:45:23 xps9320 kernel: [43079.227100] ? __pfx_kthread+0x10/0x10 Apr 15 21:45:23 xps9320 kernel: [43079.230123] ret_from_fork_asm+0x1b/0x30 Apr 15 21:45:23 xps9320 kernel: [43079.233124] Apr 15 21:45:23 xps9320 kernel: [43079.235686] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2061091 Title: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0) Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: Sometimes, when trying to shut down or suspend my laptop, it gets stuck on the console screen. If I was suspending, it eventually gives up and goes back to the X session. During a shutdown it hangs forever and the only solution seems to be to force a reboot with Magic-SysRq. The following appears in `kern.log`: ``` Apr 12 08:59:54 xps9320 kernel: [173172.510341] Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): Apr 12 08:59:54 xps9320 kernel: [173172.515669] task:wireplumber state:D stack:0 pid:2408 ppid:2398 flags:0x0006 Apr 12 08:59:54 xps9320 kernel: [173172.518923] Call Trace: Apr 12 08:59:54 xps9320 kernel: [173172.521755] Apr 12 08:59:54 xps9320 kernel: [173172.524099] __schedule+0x2cb/0x750 Apr 12 08:59:54 xps9320 kernel:
[Kernel-packages] [Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
I had a hard time diagnosing this issue due to the difficulty of finding this bug report. As I use Focal, I didn't think to check the Jammy board. The general Ubuntu board has a report for this issue, but since it's marked as a duplicate of this one it is hidden by default. -- 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/2060780 Title: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: Hi, updated some Ubuntu 22.04 systems to lastest available state this morning, which caused CIFS mounts (from various fileservers) to stop working. Kernel was updated to version 5.15.0-102-generic. I can mount the shares without problems (mount -t cifs), but then, df for example tells me: df: /mnt: Resource temporarily unavailable. I'm able to list and browse all the files, but accessing them (even readonly) is very unstable. Sometimes it works and sometimes it just gives me i/o errors. Switching back to 5.15.0-101-generic or 5.15.0-100-generic solves the problem and everything works again as expected. Seems like some bug has been implemented in 5.15.0-102-generic... To reproduce the problem, I started a while loop on one server to write to some file on a specific mounted CIFS share and read it from another one root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; sleep 1 ; done -bash: /mnt/hallo.txt: Input/output error -bash: /mnt/hallo.txt: Input/output error ^C root@:~$ tail -f /mnt/hallo.txt Tue Apr 9 04:10:52 PM CEST 2024 hallo Tue Apr 9 04:10:53 PM CEST 2024 hallo Tue Apr 9 04:10:54 PM CEST 2024 hallo Tue Apr 9 04:10:55 PM CEST 2024 hallo Tue Apr 9 04:10:56 PM CEST 2024 hallo Tue Apr 9 04:10:57 PM CEST 2024 hallo Tue Apr 9 04:10:58 PM CEST 2024 hallo Tue Apr 9 04:10:59 PM CEST 2024 hallo Tue Apr 9 04:11:00 PM CEST 2024 hallo Tue Apr 9 04:11:01 PM CEST 2024 hallo tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: Resource temporarily unavailable Tue Apr 9 04:11:04 PM CEST 2024 hallo Tue Apr 9 04:11:05 PM CEST 2024 hallo Tue Apr 9 04:11:06 PM CEST 2024 hallo Tue Apr 9 04:11:07 PM CEST 2024 hallo Tue Apr 9 04:11:08 PM CEST 2024 hallo Tue Apr 9 04:11:09 PM CEST 2024 hallo Tue Apr 9 04:11:10 PM CEST 2024 hallo While doing this, both servers tell me, the resource is unavailable root@:~# df -h /mnt df: /mnt: Resource temporarily unavailable root@:~$ df -h /mnt df: /mnt: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+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 2058480] Re: [Ubuntu 22.04.4/linux-image-6.5.0-1014-aws] Kernel outputs "UBSAN: array-index-out-of-bounds in /build/linux-aws-6.5-4tw9h1/linux-aws-6.5-6.5.0/drivers/net/xen-netf
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-aws (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2058480 Title: [Ubuntu 22.04.4/linux-image-6.5.0-1014-aws] Kernel outputs "UBSAN: array-index-out-of-bounds in /build/linux-aws-6.5-4tw9h1/linux- aws-6.5-6.5.0/drivers/net/xen-netfront.c:349:9 " multiple times, especially during boot Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: Confirmed Bug description: A newly launched Ubuntu 22.04.4 EC2 instance outputs "UBSAN: array- index-out-of-bounds in /build/linux-aws-6.5-4tw9h1/linux- aws-6.5-6.5.0/drivers/net/xen-netfront.c:349:9" multiple times, especially during boot. Reproducing step: - Launch an Ubuntu 22.04.4 EC2 instance with the instance type t2.*. Additional Info: - Please use t2 instance to make sure to use xen-netfront as a network device. - This messages similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058477, which is related to netvsc.c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058480/+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 2061930] [NEW] linux-nvidia-6.5_6.5.0-1014.14 breaks with earlier BIOS release, and modeset/resolutions are wrong
Public bug reported: There are a gigantic number of changes in 1014.14 compared to 1013 I suspect some of the aspeed fixes have been undone, the mode is now... not what it was before, looks like it's falling back to 1024x768. This patchset also brings in a bunch of... strange patches that don't involve the nvidia tree at all. When I boot an older BIOS series with 1013, works fine, with this it spits out, upon systemd loading some mid-stage stuff: [^[[0;32m OK ^[[ted ^[[0;1;39mRule-based Manager for Device Events and Files^[[0m. [^[[0;32m OK ^[[0m] Mounted ^[[0;1;39mMount unit for snapd, revision 19459^[[0m. Unhandled Exception from EL2 x0 = 0x11f210305619 x1 = 0x x2 = 0x x3 = 0x x4 = 0x5fd6a3d5 x5 = 0x x6 = 0x x7 = 0x x8 = 0x x9 = 0xa0a120ea7d6c x10= 0x x11= 0x x12= 0x x13= 0x0030 x14= 0x x15= 0x x16= 0x x17= 0x x18=000 x19c5d66880 x20= 0x80009be8f760 x21= 0x80009be8f7d0 x22= 0xffe3a0a120ea7d6c x23= 0x x24= 0xa0a123e08aa0 x25= 0xa0a123440008 x26= 0xa0a123440008 x27= 0xa0a0d34a5748 x28= 0x80009be8f7c0 x29= 0x80008000fe00 x30= 0xa0a120ea7d6c scr_el3= 0x0407073d sctlr_el3 = 0x30cd183f cptr_el3 = 0x00100100 tcr_el3= 0x80853510 daif = 0x02c0 mair_el3 = 0x004404ff spsr_el3 = 0x034000el3= 0xa0a0d34a58b4 ttbr0_el3 = 0x0078734a5001 esr_el3= 0x622c5c1f far_el3= 0x42a4e89076a05490 spsr_el1 = 0x elr_el1= 0x spsr_abt = 0x spsr_und = 0x spsr_irq = 0x spsr_fiq = 0x sctlr_el1 = 0x30500980 actlr_el1 = 0x cpacr_el1 = 0x0030 csselr_el1 = 0x0002 sp_el1 = 0xa0a123defea0 esr_el1= 0x ttbr0_el1 00f89cd ttbr1_el1 000f8af0 mair_el1 = 0x00040044 amair_el1 = 0x tcr_el1= 0x005000f5f5507dr_el1 = 0x5fd6a3d5 tpidr_el0 = 0x8000 tpidrro_el0= 0x par_el1= 0x0800 mpidr_el1 = 0x8102 afsr0_el1 = 0x afsr1_el1 = 0x contextidr_el1 = 0x vbar_el1 = 0xa0a120cd1000 cntp_ctl_el0 = 0x cntp_cval_el0 = 0x001f0caabc20 cntv_ctl_el0 cntv_cval_el0 = 0x cntkctl_el1= 0x sp_el0 = 0x0078732cf4f0 isr_el1= 0x0ectlr_el1 = 0x4000340340003000 gicd_ispendr regs (Offsets 0x200 - 0x278) Offset:value 0200: 0xUnhandled Exception in EL3. x30= 0x0078732c4384 x0 = 0x x1 = 0x0078732cb7d8 x2 = 0x0018 x3 = 0x0078732b1720 x4 = 0x x5 = 0x003c x6 = 0x0078732c9109 x7 = 0x22000204 x8 = 0x4000340340003000 x9 = 0xa0a120cd1000 x10= 0x x11= 0x001f0caabc20 x12= 0x x13= 0x00000 x15= 0x0078732cf4f0 x16= 0x2200 x17= 0x0018 x18= 0x0407073d x19= 0x007873386440 x20= 0x80009be8f760 x21= 0x80009be8f7d0 x22= 0xffe3a0a120ea7d6c x23= 0x x24= 0xa0a123e08aa0 x25= 0xa0a123440008 x26= 0xa0a123440008 x27= 0xa0a0 x28= 0x80009be8f7c0 x29= 0x80008000feel3= 0x0407073d sctlr_el3 = 0x30cd183f cptr_el3 = 0x00100100 tcr_el3= 0x80853510 daif = 0x03c0 mair_el3 = 0x spsr_el3 = 0x834002cd elr_el3= 0x0078732b0a0_el3 = 0x0078734a5001 esr_el3= 0xbe00 = 0x42a4e89076a05490 spsr_el1 = 0x elr_el1= 0x spsr_abt = 0x
[Kernel-packages] [Bug 2061713] Re: ASUS Battery Won't Charge if Plugged in While Suspended
** Changed in: linux-signed-hwe-6.5 (Ubuntu) Assignee: (unassigned) => Anthony Wong (anthonywong) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2061713 Title: ASUS Battery Won't Charge if Plugged in While Suspended Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: When running Ubuntu (or any other linux distro i've tried) the laptop will not charge if it is plugged in while suspended. Charging works find if the laptop is awake, or if it is shut down. It also works properly when running windows which makes me think its not a hardware problem but a linux issue. The charge status doesn't seem to update at all when the computer is suspended. If it is charging when its put to sleep then the charge LED on the side is lit, and if I then unplug the charger the LED doesn't turn off until the computer is woken up. If the computer is plugged in while sleeping I know it isn't charging even though the light doesn't turn on because I have left it overnight and the battery stays at the same percentage. I've been unable to find any information about what could be causing this issue. My Laptop is an ASUS Zenbook Flip UX461UA Ubuntu Version: Description: Ubuntu 22.04.4 LTS Release: 22.04 I'm not sure what package would be causing this. What I expect to be happening: The battery should start charging if its plugged in while suspended What happened instead: Battery doesn't charge and charging indicator doesn't change until the computer is woken up ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-27-generic 6.5.0-27.28~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 23:21:17 2024 InstallationDate: Installed on 2024-04-16 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2061713/+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 2061840] Re: Ubuntu 24.04 freezes after plug in power cable
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) -- 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/2061840 Title: Ubuntu 24.04 freezes after plug in power cable Status in linux package in Ubuntu: New Bug description: I have Ubuntu 24.04 installed on my laptop, when I plug in my power cable to my laptop, the whole Ubuntu freezes and nothing is responds, so I have to force shutdown my laptop and restart it. I want to make notice that all other version Ubuntu 23.10, 22.04... with all different flavors work perfect without any issue ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-22-generic 6.8.0-22.22 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:zakaria1758 F pipewire /dev/snd/controlC0: zakaria1765 F wireplumber /dev/snd/controlC1: zakaria1765 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 16 14:40:45 2024 InstallationDate: Installed on 2024-04-14 (2 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2) MachineType: Dell Inc. Latitude E7450 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.8.0-22-generic root=UUID=63a3cbd0-c29b-4ef3-8be8-7c43b782a9b9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-22-generic N/A linux-backports-modules-6.8.0-22-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2020 dmi.bios.release: 65.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: A24 dmi.board.name: 0D8H72 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA24:bd04/11/2020:br65.24:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0D8H72:rvrA00:cvnDellInc.:ct9:cvr:sku062E: dmi.product.name: Latitude E7450 dmi.product.sku: 062E dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061840/+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 2061912] Re: After a very recent update most browsers are not able to load webpages in Ubuntu 24.04
** Changed in: linux-lowlatency (Ubuntu) Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/2061912 Title: After a very recent update most browsers are not able to load webpages in Ubuntu 24.04 Status in linux-lowlatency package in Ubuntu: New Bug description: After a recent update of packages (in the last couple of hours or so) neither Firefox (snap) nor Google Chrome (.deb) nor Chromium (snap) are able to load pages. Gnome Web is the only one that seems to work. Also, apt loads fine. Chromium complains of DNS_PROBE_FINISHED_NO_INTERNET. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.46.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-25.25.3-lowlatency 6.8.1 Uname: Linux 6.8.0-25-lowlatency x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 16 18:55:41 2024 InstallationDate: Installed on 2022-02-02 (804 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 192.168.0.1 dev wlan0 proto dhcp src 192.168.0.128 metric 600 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.128 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-04-11 (5 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN ejecutando 1.46.0 conectado Iniciado total activadoactivado activado missing activado To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/2061912/+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 2061912] Re: After a very recent update most browsers are not able to load webpages in Ubuntu 24.04
** Package changed: network-manager (Ubuntu) => linux-lowlatency (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/2061912 Title: After a very recent update most browsers are not able to load webpages in Ubuntu 24.04 Status in linux-lowlatency package in Ubuntu: New Bug description: After a recent update of packages (in the last couple of hours or so) neither Firefox (snap) nor Google Chrome (.deb) nor Chromium (snap) are able to load pages. Gnome Web is the only one that seems to work. Also, apt loads fine. Chromium complains of DNS_PROBE_FINISHED_NO_INTERNET. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.46.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-25.25.3-lowlatency 6.8.1 Uname: Linux 6.8.0-25-lowlatency x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 16 18:55:41 2024 InstallationDate: Installed on 2022-02-02 (804 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 192.168.0.1 dev wlan0 proto dhcp src 192.168.0.128 metric 600 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.128 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-04-11 (5 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN ejecutando 1.46.0 conectado Iniciado total activadoactivado activado missing activado To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/2061912/+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 2061912] [NEW] After a very recent update most browsers are not able to load webpages in Ubuntu 24.04
You have been subscribed to a public bug: After a recent update of packages (in the last couple of hours or so) neither Firefox (snap) nor Google Chrome (.deb) nor Chromium (snap) are able to load pages. Gnome Web is the only one that seems to work. Also, apt loads fine. Chromium complains of DNS_PROBE_FINISHED_NO_INTERNET. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.46.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-25.25.3-lowlatency 6.8.1 Uname: Linux 6.8.0-25-lowlatency x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 16 18:55:41 2024 InstallationDate: Installed on 2022-02-02 (804 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 192.168.0.1 dev wlan0 proto dhcp src 192.168.0.128 metric 600 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.128 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-04-11 (5 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN ejecutando 1.46.0 conectado Iniciado total activadoactivado activado missing activado ** Affects: linux-lowlatency (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- After a very recent update most browsers are not able to load webpages in Ubuntu 24.04 https://bugs.launchpad.net/bugs/2061912 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency in Ubuntu. -- 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 2060727] Re: The keyboard does not work after latest kernel update
-- 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/2060727 Title: The keyboard does not work after latest kernel update Status in linux package in Ubuntu: Confirmed Bug description: The computer is a ThinkPad L15 Gen 4, its integrated keyboard does not work after the latest kernel update and its subsequent reboot of the laptop. Nothing else is connected to the laptop. -- In /var/log/apt/history.log , the latest we can see is: Start-Date: 2024-04-09 12:37:28 Commandline: apt full-upgrade Install: linux-modules-extra-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), linux-headers-6.5.0-27:amd64 (6.5.0-27.28, automatic), linux-modules-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), linux-image-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), linux-headers-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic) Upgrade: linux-headers-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-image-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-libc-dev:amd64 (6.5.0-26.26, 6.5.0-27.28) End-Date: 2024-04-09 12:37:51 -- $ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.10 Release:23.10 $ # Note: It's Kubuntu 23.10 -- $ uname -a Linux tp 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 7 18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060727/+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 2060727] Re: The keyboard does not work after latest kernel update
Following that conversation: In my case, the bug happens with: $ sudo lshw | grep -A8 '*-firmware' *-firmware description: BIOS vendor: LENOVO physical id: 14 version: R24ET38W (1.21 ) date: 03/01/2024 size: 128KiB capacity: 32MiB capabilities: pci pnp upgrade shadowing cdboot bootselect edd int13floppy720 int5printscreen int9keyboard int14serial int17printer int10video acpi usb biosbootspecification uefi $ uname -a Linux hostname 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 7 18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux $ LANG=C lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 39 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 12 On-line CPU(s) list: 0-11 Vendor ID: GenuineIntel Model name:13th Gen Intel(R) Core(TM) i7-1355U (...) -- 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/2060727 Title: The keyboard does not work after latest kernel update Status in linux package in Ubuntu: Confirmed Bug description: The computer is a ThinkPad L15 Gen 4, its integrated keyboard does not work after the latest kernel update and its subsequent reboot of the laptop. Nothing else is connected to the laptop. -- In /var/log/apt/history.log , the latest we can see is: Start-Date: 2024-04-09 12:37:28 Commandline: apt full-upgrade Install: linux-modules-extra-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), linux-headers-6.5.0-27:amd64 (6.5.0-27.28, automatic), linux-modules-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), linux-image-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), linux-headers-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic) Upgrade: linux-headers-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-image-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-libc-dev:amd64 (6.5.0-26.26, 6.5.0-27.28) End-Date: 2024-04-09 12:37:51 -- $ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.10 Release:23.10 $ # Note: It's Kubuntu 23.10 -- $ uname -a Linux tp 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 7 18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060727/+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 2061900] Re: apply NVIDIA patches April 6-16, 2024
** Also affects: linux-nvidia-tegra (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2061900 Title: apply NVIDIA patches April 6-16, 2024 Status in linux-nvidia-tegra package in Ubuntu: New Status in linux-nvidia-tegra-igx package in Ubuntu: New Bug description: Apply NVIDIA patches April 6-16, 2024: NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234 https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3115016 NVIDIA: SAUCE: enable handling of macronix block protection https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3114006 PCI: dwc: Restore MSI Receiver mask during resume https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3116302 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2061900/+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 2061900] [NEW] apply NVIDIA patches April 6-16, 2024
Public bug reported: Apply NVIDIA patches April 6-16, 2024: NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234 https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3115016 NVIDIA: SAUCE: enable handling of macronix block protection https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3114006 PCI: dwc: Restore MSI Receiver mask during resume https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3116302 ** Affects: linux-nvidia-tegra-igx (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2061900 Title: apply NVIDIA patches April 6-16, 2024 Status in linux-nvidia-tegra-igx package in Ubuntu: New Bug description: Apply NVIDIA patches April 6-16, 2024: NVIDIA: SAUCE: phy: xusb: Disable USB2 tracking for T234 https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3115016 NVIDIA: SAUCE: enable handling of macronix block protection https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3114006 PCI: dwc: Restore MSI Receiver mask during resume https://git-master.nvidia.com/r/c/3rdparty/canonical/linux-jammy/+/3116302 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2061900/+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 2061248] Re: kernel 5.15.0-102 - CIFS mount problem (NAS)
*** This bug is a duplicate of bug 2060780 *** https://bugs.launchpad.net/bugs/2060780 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2061248 Title: kernel 5.15.0-102 - CIFS mount problem (NAS) Status in linux package in Ubuntu: Confirmed Bug description: CIFS are regulary mounted via fstab (system has been stable for several years) and everything was fine with .101 but after the 08-apr-2024 kernel update suddenly the NAS shares are often stuck or timed out, unresponsive and not accessible (unavailable). Reverting from .102 to .101 brought everything back to working order as it was before kernel update. Something in the latest kernel 5.15.0-102 is not good for CIFS shares. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061248/+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 2061897] [NEW] Enable Milk-V Mars board
Public bug reported: Apply relevant patches to the linux-riscv kernel to support the Milk-V Mars board based on the StarFive JH7110 SoC. ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/2061897 Title: Enable Milk-V Mars board Status in linux-riscv package in Ubuntu: New Bug description: Apply relevant patches to the linux-riscv kernel to support the Milk-V Mars board based on the StarFive JH7110 SoC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2061897/+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
Re: [Kernel-packages] [Bug 2060989] Re: package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to install/upgrade: installed linux-headers-6.5.0-27-generic package post-installation script subproce
Hello, below you can find the log: /DKMS make.log for nvidia-fs-2.19.6 for kernel 6.5.0-26-generic (x86_64) Mon Apr 1 07:45:59 PM CEST 2024 Picking NVIDIA driver sources from NVIDIA_SRC_DIR=/usr/src/nvidia-535.161.07/nvidia. If that does not meet your expectation, you might have a stale driver still around and that might cause problems. Getting symbol versions from /lib/modules/6.5.0-26-generic/kernel/nvidia-535/nvidia.ko ... Created: /var/lib/dkms/nvidia-fs/2.19.6/build/nv.symvers checking if uaccess.h access_ok has 3 parameters... no checking if uaccess.h access_ok has 2 parameters... yes Checking if blkdev.h has blk_rq_payload_bytes... yes Checking if fs.h has call_read_iter and call_write_iter... yes Checking if fs.h has filemap_range_has_page... yes Checking if kiocb structue has ki_complete field... yes Checking if vm_fault_t exist in mm_types.h... yes Checking if enum PCIE_SPEED_32_0GT exists in pci.h... yes Checking if atomic64_t counter is of type long... no Checking if RQF_COPY_USER is present or not... no Checking if dma_drain_size and dma_drain_needed are present in struct request_queue... no Checking if struct proc_ops is present or not ... yes Checking if split is present in vm_operations_struct or not ... no Checking if mremap in vm_operations_struct has one parameter... yes Checking if mremap in vm_operations_struct has two parameters... no Checking if symbol module_mutex is present... no Checking if blk-integrity.h is present... yes Checking if KI_COMPLETE has 3 parameters ... no Checking if pin_user_pages_fast symbol is present in kernel or not ... yes Checking if prandom_u32 symbol is present in kernel or not ... no Checking if devnode in class has doesn't have const device or not ... no Checking if class_create has two parameters or not ... no Checking if vma_flags are modifiable directly ... no make[1]: warning: -j4 forced in submake: resetting jobserver mode. make[1]: Entering directory '/usr/src/linux-headers-6.5.0-26-generic' warning: the compiler differs from the one used to build the kernel The kernel was built by: x86_64-linux-gnu-gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0 You are using: gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0 CC [M] /var/lib/dkms/nvidia-fs/2.19.6/build/nvfs-core.o CC [M] /var/lib/dkms/nvidia-fs/2.19.6/build/nvfs-dma.o CC [M] /var/lib/dkms/nvidia-fs/2.19.6/build/nvfs-mmap.o CC [M] /var/lib/dkms/nvidia-fs/2.19.6/build/nvfs-pci.o CC [M] /var/lib/dkms/nvidia-fs/2.19.6/build/nvfs-proc.o CC [M] /var/lib/dkms/nvidia-fs/2.19.6/build/nvfs-mod.o CC [M] /var/lib/dkms/nvidia-fs/2.19.6/build/nvfs-kernel-interface.o CC [M] /var/lib/dkms/nvidia-fs/2.19.6/build/nvfs-stat.o CC [M] /var/lib/dkms/nvidia-fs/2.19.6/build/nvfs-rdma.o CC [M] /var/lib/dkms/nvidia-fs/2.19.6/build/nvfs-batch.o LD [M] /var/lib/dkms/nvidia-fs/2.19.6/build/nvidia-fs.o MODPOST /var/lib/dkms/nvidia-fs/2.19.6/build/Module.symvers WARNING: modpost: "nvidia_p2p_dma_unmap_pages" [/var/lib/dkms/nvidia-fs/2.19.6/build/nvidia-fs.ko] undefined! WARNING: modpost: "nvidia_p2p_get_pages" [/var/lib/dkms/nvidia-fs/2.19.6/build/nvidia-fs.ko] undefined! WARNING: modpost: "nvidia_p2p_put_pages" [/var/lib/dkms/nvidia-fs/2.19.6/build/nvidia-fs.ko] undefined! WARNING: modpost: "nvidia_p2p_dma_map_pages" [/var/lib/dkms/nvidia-fs/2.19.6/build/nvidia-fs.ko] undefined! WARNING: modpost: "nvidia_p2p_free_dma_mapping" [/var/lib/dkms/nvidia-fs/2.19.6/build/nvidia-fs.ko] undefined! WARNING: modpost: "nvidia_p2p_free_page_table" [/var/lib/dkms/nvidia-fs/2.19.6/build/nvidia-fs.ko] undefined! CC [M] /var/lib/dkms/nvidia-fs/2.19.6/build/nvidia-fs.mod.o LD [M] /var/lib/dkms/nvidia-fs/2.19.6/build/nvidia-fs.ko BTF [M] /var/lib/dkms/nvidia-fs/2.19.6/build/nvidia-fs.ko Skipping BTF generation for /var/lib/dkms/nvidia-fs/2.19.6/build/nvidia-fs.ko due to unavailability of vmlinux make[1]: Leaving directory '/usr/src/linux-headers-6.5.0-26-generic'/ Best regards Nela On 4/16/24 16:22, En-Wei Wu wrote: > Could you provide the build log of dkms (run by the apt post script)? > Probably in /var/lib/dkms/gds-nvidia- > fs/2.19.6/6.5.0-27-generic/x86_64/log/make.log. > -- 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/2060989 Title: package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to install/upgrade: installed linux-headers-6.5.0-27-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: In Progress Bug description: - ProblemType: Package DistroRelease: Ubuntu 23.10 Package: linux-headers-6.5.0-27-generic 6.5.0-27.28 ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND
[Kernel-packages] [Bug 2059143] Re: Remove getabis scripts
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1024.24 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 verification-needed-jammy-linux-nvidia-tegra -- 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/2059143 Title: Remove getabis scripts Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] With ABI checks removed from the tree (#LP2055685), there's no need to download the buildinfo from a previous version. [Fix] This is needed only in the main kernels. 1. remove the common getabis script 2. remove per kernel getabis file (this will be done with cranky fix) [Test] Build test on cbd. No issue found. Also cranked the kernels in advance to see if there were issues, but no issue was found. [Regression potential] In the current cycle, the ABI checks have been removed and this is not used anymore. No issues have been found. Now we're just removing an unused feature, therefore the regression potential is none. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059143/+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 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1024.24 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-done-jammy-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-tegra' to 'verification-failed-jammy-linux-nvidia-tegra'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra-v2 verification-needed-jammy-linux-nvidia-tegra -- 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/2060780 Title: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: Hi, updated some Ubuntu 22.04 systems to lastest available state this morning, which caused CIFS mounts (from various fileservers) to stop working. Kernel was updated to version 5.15.0-102-generic. I can mount the shares without problems (mount -t cifs), but then, df for example tells me: df: /mnt: Resource temporarily unavailable. I'm able to list and browse all the files, but accessing them (even readonly) is very unstable. Sometimes it works and sometimes it just gives me i/o errors. Switching back to 5.15.0-101-generic or 5.15.0-100-generic solves the problem and everything works again as expected. Seems like some bug has been implemented in 5.15.0-102-generic... To reproduce the problem, I started a while loop on one server to write to some file on a specific mounted CIFS share and read it from another one root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; sleep 1 ; done -bash: /mnt/hallo.txt: Input/output error -bash: /mnt/hallo.txt: Input/output error ^C root@:~$ tail -f /mnt/hallo.txt Tue Apr 9 04:10:52 PM CEST 2024 hallo Tue Apr 9 04:10:53 PM CEST 2024 hallo Tue Apr 9 04:10:54 PM CEST 2024 hallo Tue Apr 9 04:10:55 PM CEST 2024 hallo Tue Apr 9 04:10:56 PM CEST 2024 hallo Tue Apr 9 04:10:57 PM CEST 2024 hallo Tue Apr 9 04:10:58 PM CEST 2024 hallo Tue Apr 9 04:10:59 PM CEST 2024 hallo Tue Apr 9 04:11:00 PM CEST 2024 hallo Tue Apr 9 04:11:01 PM CEST 2024 hallo tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: Resource temporarily unavailable Tue Apr 9 04:11:04 PM CEST 2024 hallo Tue Apr 9 04:11:05 PM CEST 2024 hallo Tue Apr 9 04:11:06 PM CEST 2024 hallo Tue Apr 9 04:11:07 PM CEST 2024 hallo Tue Apr 9 04:11:08 PM CEST 2024 hallo Tue Apr 9 04:11:09 PM CEST 2024 hallo Tue Apr 9 04:11:10 PM CEST 2024 hallo While doing this, both servers tell me, the resource is unavailable root@:~# df -h /mnt df: /mnt: Resource temporarily unavailable root@:~$ df -h /mnt df: /mnt: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+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 1786013] Autopkgtest regression report (linux-meta-nvidia-tegra/5.15.0.1023.23)
All autopkgtests for the newly accepted linux-meta-nvidia-tegra (5.15.0.1023.23) for jammy have finished running. The following regressions have been reported in tests triggered by the package: wireguard/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-nvidia-tegra [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 2043118] Re: Regression CIFS mounted DFS
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2043118 Title: Regression CIFS mounted DFS Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Incomplete Bug description: On Ubuntu 22.04.3 LTS (jammy jellyfish) we mount a DFS file service using CIFS with kerberos authentication. After the kernel upgrade from 5.15.0-86-generic to 5.15.0-88-generic (exact version: 5.15.0-88.98) this stopped working. The mount seems to have worked, but files and directories are inaccessible. A non-DFS CIFS share mounted on the same client machine is not affected. In our case the filesystem is mounted using autofs with the following mapping: /dfs-share -fstype=cifs,sec=krb5,vers=3,multiuser,noserverino ://example.com/share Kernel log messages: CIFS: Attempting to mount \\example.com\share CIFS: VFS: BAD_NETWORK_NAME: \\example.com\share CIFS: VFS: Verify user has a krb5 ticket and keyutils is installed CIFS: VFS: \\CLx-Ny.EXAMPLE.COM Send error in SessSetup = -126 We confirmed that kernel version 5.15.0-88 causes this by booting different kernel versions repeatedly. When booting 5.15.0-86 everything worked properly as before. Though not familiar with kernel coding, we found changes in the source code that seem to confirm that some code dealing with DFS has changed, moved, or removed. After: git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy This: git diff Ubuntu-5.15.0-86.96 Ubuntu-5.15.0-88.98 -- fs/cifs/cifs_dfs_ref.c This suggests the function cifs_dfs_do_mount() has been (re)moved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043118/+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 1786013] Autopkgtest regression report (linux-meta-nvidia-tegra/5.15.0.1023.23)
All autopkgtests for the newly accepted linux-meta-nvidia-tegra (5.15.0.1023.23) for jammy have finished running. The following regressions have been reported in tests triggered by the package: wireguard/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-nvidia-tegra [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 2061881] [NEW] I can only start Xubutu 24.04 beta in safe mode
Public bug reported: I can also only use safe graphics mode when using the live thumb drive. Using Nouveau drivers do not help. I got to safe mode and then resume and everything works perfectly ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-22-generic 6.8.0-22.22 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Tue Apr 16 19:22:11 2024 InstallationDate: Installed on 2022-01-01 (836 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H510M H ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic root=UUID=1d8096e9-db00-43e9-afb0-200e985ee281 ro recovery nomodeset dis_ucode_ldr 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.8.0-22-generic N/A linux-backports-modules-6.8.0-22-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: H510M H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF11:bd10/26/2021:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnH510MH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH510MH:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H510 MB dmi.product.name: H510M H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- 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/2061881 Title: I can only start Xubutu 24.04 beta in safe mode Status in linux package in Ubuntu: New Bug description: I can also only use safe graphics mode when using the live thumb drive. Using Nouveau drivers do not help. I got to safe mode and then resume and everything works perfectly ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-22-generic 6.8.0-22.22 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Tue Apr 16 19:22:11 2024 InstallationDate: Installed on 2022-01-01 (836 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H510M H ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic root=UUID=1d8096e9-db00-43e9-afb0-200e985ee281 ro recovery nomodeset dis_ucode_ldr 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.8.0-22-generic N/A linux-backports-modules-6.8.0-22-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: H510M H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF11:bd10/26/2021:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnH510MH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH510MH:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H510 MB dmi.product.name: H510M H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug
[Kernel-packages] [Bug 2061869] Re: Snaps unable to connect to network under linux-lowlatency 6.8.0-25.25.3
This is likely a dup of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061851 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/2061869 Title: Snaps unable to connect to network under linux-lowlatency 6.8.0-25.25.3 Status in apparmor package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: After upgrading to linux-lowlatency 6.8.0-25, suddenly snaps can no longer connect to network. I tried downgrading snapd from edge, still no connectivity. Only solution was to downgrade back to 6.8.0-7. I'll also add apparmor in case this is an apparmor issue as well. Marking as "critical" priority as this affects all installs of Ubuntu Studio and affects Firefox and Thunderbird. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2061869/+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 2061869] Re: Snaps unable to connect to network under linux-lowlatency 6.8.0-25.25.3
the kernel team is already rolling kernels with the fix for 2061851 but it is also building in https://launchpad.net/~apparmor- dev/+archive/ubuntu/apparmor-devel ppa -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/2061869 Title: Snaps unable to connect to network under linux-lowlatency 6.8.0-25.25.3 Status in apparmor package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: After upgrading to linux-lowlatency 6.8.0-25, suddenly snaps can no longer connect to network. I tried downgrading snapd from edge, still no connectivity. Only solution was to downgrade back to 6.8.0-7. I'll also add apparmor in case this is an apparmor issue as well. Marking as "critical" priority as this affects all installs of Ubuntu Studio and affects Firefox and Thunderbird. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2061869/+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 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
This bug is awaiting verification that the linux/5.15.0-105.115 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux' to 'verification-done-jammy-linux'. If the problem still exists, change the tag 'verification-needed-jammy- linux' to 'verification-failed-jammy-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-v2 verification-needed-jammy-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2060780 Title: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: Hi, updated some Ubuntu 22.04 systems to lastest available state this morning, which caused CIFS mounts (from various fileservers) to stop working. Kernel was updated to version 5.15.0-102-generic. I can mount the shares without problems (mount -t cifs), but then, df for example tells me: df: /mnt: Resource temporarily unavailable. I'm able to list and browse all the files, but accessing them (even readonly) is very unstable. Sometimes it works and sometimes it just gives me i/o errors. Switching back to 5.15.0-101-generic or 5.15.0-100-generic solves the problem and everything works again as expected. Seems like some bug has been implemented in 5.15.0-102-generic... To reproduce the problem, I started a while loop on one server to write to some file on a specific mounted CIFS share and read it from another one root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; sleep 1 ; done -bash: /mnt/hallo.txt: Input/output error -bash: /mnt/hallo.txt: Input/output error ^C root@:~$ tail -f /mnt/hallo.txt Tue Apr 9 04:10:52 PM CEST 2024 hallo Tue Apr 9 04:10:53 PM CEST 2024 hallo Tue Apr 9 04:10:54 PM CEST 2024 hallo Tue Apr 9 04:10:55 PM CEST 2024 hallo Tue Apr 9 04:10:56 PM CEST 2024 hallo Tue Apr 9 04:10:57 PM CEST 2024 hallo Tue Apr 9 04:10:58 PM CEST 2024 hallo Tue Apr 9 04:10:59 PM CEST 2024 hallo Tue Apr 9 04:11:00 PM CEST 2024 hallo Tue Apr 9 04:11:01 PM CEST 2024 hallo tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: Resource temporarily unavailable Tue Apr 9 04:11:04 PM CEST 2024 hallo Tue Apr 9 04:11:05 PM CEST 2024 hallo Tue Apr 9 04:11:06 PM CEST 2024 hallo Tue Apr 9 04:11:07 PM CEST 2024 hallo Tue Apr 9 04:11:08 PM CEST 2024 hallo Tue Apr 9 04:11:09 PM CEST 2024 hallo Tue Apr 9 04:11:10 PM CEST 2024 hallo While doing this, both servers tell me, the resource is unavailable root@:~# df -h /mnt df: /mnt: Resource temporarily unavailable root@:~$ df -h /mnt df: /mnt: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+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 2061869] [NEW] Snaps unable to connect to network under linux-lowlatency 6.8.0-25.25.3
Public bug reported: After upgrading to linux-lowlatency 6.8.0-25, suddenly snaps can no longer connect to network. I tried downgrading snapd from edge, still no connectivity. Only solution was to downgrade back to 6.8.0-7. I'll also add apparmor in case this is an apparmor issue as well. Marking as "critical" priority as this affects all installs of Ubuntu Studio and affects Firefox and Thunderbird. ** Affects: apparmor (Ubuntu) Importance: Critical Status: New ** Affects: linux-lowlatency (Ubuntu) Importance: Critical Status: New ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Description changed: After upgrading to linux-lowlatency 6.8.0-25, suddenly snaps can no longer connect to network. I tried downgrading snapd from edge, still no connectivity. Only solution was to downgrade back to 6.8.0-7. I'll also add apparmor in case this is an apparmor issue as well. + + Marking as "critical" priority as this affects all installs of Ubuntu + Studio and affects Firefox and Thunderbird. ** Changed in: apparmor (Ubuntu) Importance: Undecided => Critical ** Changed in: linux-lowlatency (Ubuntu) Importance: Undecided => Critical ** Changed in: apparmor (Ubuntu) Milestone: None => ubuntu-24.04 ** Changed in: linux-lowlatency (Ubuntu) Milestone: None => ubuntu-24.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/2061869 Title: Snaps unable to connect to network under linux-lowlatency 6.8.0-25.25.3 Status in apparmor package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: After upgrading to linux-lowlatency 6.8.0-25, suddenly snaps can no longer connect to network. I tried downgrading snapd from edge, still no connectivity. Only solution was to downgrade back to 6.8.0-7. I'll also add apparmor in case this is an apparmor issue as well. Marking as "critical" priority as this affects all installs of Ubuntu Studio and affects Firefox and Thunderbird. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2061869/+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 2061851] Re: linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor profiles/features
** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-ibm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2061851 Title: linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor profiles/features Status in chrony package in Ubuntu: New Status in linux package in Ubuntu: New Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-ibm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in snapd package in Ubuntu: New Status in chrony source package in Noble: New Status in linux source package in Noble: New Status in linux-aws source package in Noble: New Status in linux-azure source package in Noble: New Status in linux-gcp source package in Noble: New Status in linux-ibm source package in Noble: New Status in linux-oracle source package in Noble: New Status in snapd source package in Noble: New Bug description: * Canonical Public Cloud discovered that `chronyc -c sources` now fails with `506 Cannot talk to daemon` with the latest kernels. We are seeing this in linux-azure and linux-gcp kernels (6.8.0-1005.5) * Disabling AppArmor (`sudo systemctl stop apparmor`) completely results in no regression and `chronyc -c sources` returns as expected * Disabling the apparmor profile for `chronyd` only results in no regression and `chronyc -c sources` returns as expected * There are zero entries in dmesg when this occurs * There are zero entries in dmesg when this occurs if the apparmor profile for `chronyd` is placed in complain mode instead of enforce mode * We changed the time server from the internal GCP metadata.google.internal to the ubuntu time server ntp.ubuntu.com with no change in behaviour We also noted issues with DNS resolution in snaps like `google-cloud-cli` in GCE images. * Disabling apparmor completely for snaps too (`sudo systemctl stop snapd.apparmor`) results in no regression and calling the snaps returns as expected. The same issues are present in azure kernel `linux-azure` `6.8.0-1005.5` and the -proposed `6.8.0-25.25` generic kernel. This is a release blocker for Noble release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2061851/+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 2056373] Re: Problems with HVCS and hotplugging
This bug is awaiting verification that the linux-xilinx- zynqmp/5.4.0-1042.46 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-xilinx-zynqmp' to 'verification-done-focal-linux-xilinx-zynqmp'. If the problem still exists, change the tag 'verification-needed-focal-linux-xilinx-zynqmp' to 'verification-failed-focal-linux-xilinx-zynqmp'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-xilinx-zynqmp-v2 verification-needed-focal-linux-xilinx-zynqmp -- 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/2056373 Title: Problems with HVCS and hotplugging Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Invalid Status in linux source package in Noble: Invalid Bug description: SRU Justification: == [Impact] * HVCS (Hypervisor Virtual Console Server) is broken because the virtual terminal mkvterm fails, caused by pvmutil failing. * When mkvterm is ran, it ultimately fails because it calls pvmutil which fails. pvmutil calls drmgr, and drmgr is adding a slot correctly. However, when drmgr writes the slot information to ?/add_slot, the return is -ENODEV. * This leads to HVCS never having probe() called. * In addition, HVCS is missing patches/fixes, and is broken without them. [Fix] * Fix one and two is required for focal only, all other for focal and jammy: * 57409d4fb12c 57409d4fb12c185b2c0689e0496878c8f6bb5b58 "powerpc/pseries: Fix bad drc_index_start value parsing of drc-info entry" * c5e76fa05b2d c5e76fa05b2df519b9f08571cc57e623c1569faa "powerpc/pseries: Fix of_read_drc_info_cell() to point at next record" * 6a9a733edd46 6a9a733edd46732e906d976dc21a42dd361e53cc "hvcs: Fix hvcs port reference counting" * 760aa5e81f33 760aa5e81f33e0da82512c4288489739a6d1c556 "hvcs: Use dev_groups to manage hvcs device attributes" * 503a90dd619d 503a90dd619d52dcac2cc68bd742aa914c7cd47a "hvcs: Use driver groups to manage driver attributes" * 3a8d3b366ce4 3a8d3b366ce47024bf274eac783f8af5df2780f5 "hvcs: Get reference to tty in remove" * d432228bc7b1 d432228bc7b1b3f0ed06510278ff5a77b3749fe6 "hvcs: Use vhangup in hotplug remove" * 28d49f8cbe9c 28d49f8cbe9c7966f91ee1b5ec2f997f6e55bf9f "hvcs: Synchronize hotplug remove with port free" [Test Plan] * The high level test plan is to run mkvterm with an id. * mkvterm will fail because /dev/hvcs* device nodes are missing. * Details see https://bugs.launchpad.net/bugs/2023243 for more information. Especially the script provided by IBM (see original bug description: `---Steps to Reproduce---`). * IBM will (stress) test the updated kernel(s) provided in -proposed. [Where problems could occur] * The first two commits affect arch/powerpc/platforms/pseries/of_helpers.c and are needed to fix the hotplugging issue seen when drmgr goes to write the slot information to /sys/bus/pci/slots/control/add_slot. In case of issues here hotplugging with drmgr might break. * The issue lies in rpadlpar_io and rpaphp calling an of helper function of_read_drc_info_cell(). Without these commits, the value stored drc_index_start is incorrect. This ultimately results in the entire SLOT string being incorrect, and rpaphp never finding the newly added slot by drmgr. rpadlpar then returns -ENODEV. Therefore, HVCS is never probed, and the device nodes are never created. * HVCS, rpadlpar_io, and rpaphp should ideally not even need to be loaded prior to drmgr adding a vio slot. If rpadlpar_io and rpaphp are not loaded, drmgr will load them. In addition, if rpadlpar_io and rpaphp register the new slot correctly, rpadlpar_io will call dlpar_add_vio_slot(), which calls vio_register_device_node() with the device node. This is what tells the driver core to init and probe HVCS (which is needed to create the device nodes). * The remaning 6 commits are needed for HVCS, that is essentially broken without them. Overall, issues they fix are race conditions, hotplug remove issues, as well as memory leaks. * Please notice that this is entirely ppc64el architecture-specifc. [Other Info] * All the commits listed above are included in mantic and noble. Hence
[Kernel-packages] [Bug 2061851] Re: linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor profiles/features
** Tags added: block-proposed block-proposed-noble -- 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/2061851 Title: linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor profiles/features Status in chrony package in Ubuntu: New Status in linux package in Ubuntu: New Status in snapd package in Ubuntu: New Status in chrony source package in Noble: New Status in linux source package in Noble: New Status in snapd source package in Noble: New Bug description: * Canonical Public Cloud discovered that `chronyc -c sources` now fails with `506 Cannot talk to daemon` with the latest kernels. We are seeing this in linux-azure and linux-gcp kernels (6.8.0-1005.5) * Disabling AppArmor (`sudo systemctl stop apparmor`) completely results in no regression and `chronyc -c sources` returns as expected * Disabling the apparmor profile for `chronyd` only results in no regression and `chronyc -c sources` returns as expected * There are zero entries in dmesg when this occurs * There are zero entries in dmesg when this occurs if the apparmor profile for `chronyd` is placed in complain mode instead of enforce mode * We changed the time server from the internal GCP metadata.google.internal to the ubuntu time server ntp.ubuntu.com with no change in behaviour We also noted issues with DNS resolution in snaps like `google-cloud-cli` in GCE images. * Disabling apparmor completely for snaps too (`sudo systemctl stop snapd.apparmor`) results in no regression and calling the snaps returns as expected. The same issues are present in azure kernel `linux-azure` `6.8.0-1005.5` and the -proposed `6.8.0-25.25` generic kernel. This is a release blocker for Noble release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2061851/+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 2061851] Re: linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor profiles/features
** Also affects: chrony (Ubuntu) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu) Importance: Undecided Status: New ** Also affects: chrony (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu Noble) 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/2061851 Title: linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor profiles/features Status in chrony package in Ubuntu: New Status in linux package in Ubuntu: New Status in snapd package in Ubuntu: New Status in chrony source package in Noble: New Status in linux source package in Noble: New Status in snapd source package in Noble: New Bug description: * Canonical Public Cloud discovered that `chronyc -c sources` now fails with `506 Cannot talk to daemon` with the latest kernels. We are seeing this in linux-azure and linux-gcp kernels (6.8.0-1005.5) * Disabling AppArmor (`sudo systemctl stop apparmor`) completely results in no regression and `chronyc -c sources` returns as expected * Disabling the apparmor profile for `chronyd` only results in no regression and `chronyc -c sources` returns as expected * There are zero entries in dmesg when this occurs * There are zero entries in dmesg when this occurs if the apparmor profile for `chronyd` is placed in complain mode instead of enforce mode * We changed the time server from the internal GCP metadata.google.internal to the ubuntu time server ntp.ubuntu.com with no change in behaviour We also noted issues with DNS resolution in snaps like `google-cloud-cli` in GCE images. * Disabling apparmor completely for snaps too (`sudo systemctl stop snapd.apparmor`) results in no regression and calling the snaps returns as expected. The same issues are present in azure kernel `linux-azure` `6.8.0-1005.5` and the -proposed `6.8.0-25.25` generic kernel. This is a release blocker for Noble release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2061851/+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 2061851] [NEW] linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor profiles/features
Public bug reported: * Canonical Public Cloud discovered that `chronyc -c sources` now fails with `506 Cannot talk to daemon` with the latest kernels. We are seeing this in linux-azure and linux-gcp kernels (6.8.0-1005.5) * Disabling AppArmor (`sudo systemctl stop apparmor`) completely results in no regression and `chronyc -c sources` returns as expected * Disabling the apparmor profile for `chronyd` only results in no regression and `chronyc -c sources` returns as expected * There are zero entries in dmesg when this occurs * There are zero entries in dmesg when this occurs if the apparmor profile for `chronyd` is placed in complain mode instead of enforce mode * We changed the time server from the internal GCP metadata.google.internal to the ubuntu time server ntp.ubuntu.com with no change in behaviour We also noted issues with DNS resolution in snaps like `google-cloud-cli` in GCE images. * Disabling apparmor completely for snaps too (`sudo systemctl stop snapd.apparmor`) results in no regression and calling the snaps returns as expected. The same issues are present in azure kernel `linux-azure` `6.8.0-1005.5` and the -proposed `6.8.0-25.25` generic kernel. This is a release blocker for Noble release ** Affects: chrony (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Affects: chrony (Ubuntu Noble) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Affects: snapd (Ubuntu Noble) Importance: Undecided Status: New ** Tags: block-proposed block-proposed-noble -- 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/2061851 Title: linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression iwth new apparmor profiles/features Status in chrony package in Ubuntu: New Status in linux package in Ubuntu: New Status in snapd package in Ubuntu: New Status in chrony source package in Noble: New Status in linux source package in Noble: New Status in snapd source package in Noble: New Bug description: * Canonical Public Cloud discovered that `chronyc -c sources` now fails with `506 Cannot talk to daemon` with the latest kernels. We are seeing this in linux-azure and linux-gcp kernels (6.8.0-1005.5) * Disabling AppArmor (`sudo systemctl stop apparmor`) completely results in no regression and `chronyc -c sources` returns as expected * Disabling the apparmor profile for `chronyd` only results in no regression and `chronyc -c sources` returns as expected * There are zero entries in dmesg when this occurs * There are zero entries in dmesg when this occurs if the apparmor profile for `chronyd` is placed in complain mode instead of enforce mode * We changed the time server from the internal GCP metadata.google.internal to the ubuntu time server ntp.ubuntu.com with no change in behaviour We also noted issues with DNS resolution in snaps like `google-cloud-cli` in GCE images. * Disabling apparmor completely for snaps too (`sudo systemctl stop snapd.apparmor`) results in no regression and calling the snaps returns as expected. The same issues are present in azure kernel `linux-azure` `6.8.0-1005.5` and the -proposed `6.8.0-25.25` generic kernel. This is a release blocker for Noble release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2061851/+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 2037214] Re: evict_inodes inode xxx, i_count = 1, was skipped!
This bug is no longer present in kernel 6.8.0-22-generic from Ubuntu noble.
Thanks for the fix!
--
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/2037214
Title:
evict_inodes inode xxx, i_count = 1, was skipped!
Status in linux package in Ubuntu:
Confirmed
Status in linux-meta-hwe-6.5 package in Ubuntu:
Confirmed
Status in linux-oem-6.5 package in Ubuntu:
Confirmed
Bug description:
Hi,
during boot the kernel logs the following messages:
# dmesg | grep evict_inodes
[ 12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped!
[ 12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 8ff8e64c, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 194d080e, i_count = 1, was skipped!
[ 12.784812] evict_inodes inode 09b77b7b, i_count = 1, was skipped!
[ 12.811217] evict_inodes inode ec873c71, i_count = 1, was skipped!
[ 12.811222] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[ 12.811223] evict_inodes inode b42b829a, i_count = 1, was skipped!
[ 12.811224] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[ 13.412667] evict_inodes inode 61a23a39, i_count = 1, was skipped!
[ 13.412671] evict_inodes inode b42b829a, i_count = 1, was skipped!
[ 13.412671] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[ 13.412672] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[ 13.412673] evict_inodes inode ec873c71, i_count = 1, was skipped!
Those messages are not displayed when I boot my system with a mainline Linux
kernel.
Moreover, in the mainline Linux source code, I do not find the lines where
such a message could be printed.
Therefore, those messages are probably caused by an Ubuntu patch.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-5-generic 6.5.0-5.5
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bonnaudl 4827 F wireplumber
/dev/snd/seq:bonnaudl 4808 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 14:39:10 2023
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off 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-5-generic N/A
linux-backports-modules-6.5.0-5-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214/+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 2060989] Re: package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to install/upgrade: installed linux-headers-6.5.0-27-generic package post-installation script subprocess r
Could you provide the build log of dkms (run by the apt post script)?
Probably in /var/lib/dkms/gds-nvidia-
fs/2.19.6/6.5.0-27-generic/x86_64/log/make.log.
--
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/2060989
Title:
package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to
install/upgrade: installed linux-headers-6.5.0-27-generic package
post-installation script subprocess returned error exit status 1
Status in linux package in Ubuntu:
In Progress
Bug description:
-
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-27-generic 6.5.0-27.28
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nela 2694 F wireplumber
/dev/snd/controlC1: nela 2694 F wireplumber
/dev/snd/seq:nela 2674 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Thu Apr 11 10:13:36 2024
ErrorMessage: installed linux-headers-6.5.0-27-generic package
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2024-03-30 (12 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic
root=UUID=e960f11c-d239-429e-97af-9073de7f3b3a ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-headers-6.5.0-27-generic 6.5.0-27.28 failed to
install/upgrade: installed linux-headers-6.5.0-27-generic package
post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/02/2021
dmi.bios.release: 1.27
dmi.bios.vendor: LENOVO
dmi.bios.version: HACN27WW
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: Legion S7 15ACH6
dmi.ec.firmware.release: 1.27
dmi.modalias:
dmi:bvnLENOVO:bvrHACN27WW:bd08/02/2021:br1.27:efr1.27:svnLENOVO:pn82K8:pvrLegionS715ACH6:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegionS715ACH6:skuLENOVO_MT_82K8_BU_idea_FM_LegionS715ACH6:
dmi.product.family: Legion S7 15ACH6
dmi.product.name: 82K8
dmi.product.sku: LENOVO_MT_82K8_BU_idea_FM_Legion S7 15ACH6
dmi.product.version: Legion S7 15ACH6
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060989/+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 2061830] Re: Limit supported pci-id's to the new ones added by 550
** Also affects: nvidia-graphics-drivers-550 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-550-server (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-550 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-550-server (Ubuntu Mantic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-550 in Ubuntu. https://bugs.launchpad.net/bugs/2061830 Title: Limit supported pci-id's to the new ones added by 550 Status in nvidia-graphics-drivers-550 package in Ubuntu: New Status in nvidia-graphics-drivers-550-server package in Ubuntu: New Status in nvidia-graphics-drivers-550 source package in Jammy: New Status in nvidia-graphics-drivers-550-server source package in Jammy: New Status in nvidia-graphics-drivers-550 source package in Mantic: New Status in nvidia-graphics-drivers-550-server source package in Mantic: New Status in nvidia-graphics-drivers-550 source package in Noble: New Status in nvidia-graphics-drivers-550-server source package in Noble: New Bug description: Since 550 wasn't included in the beta we should limit the potential impact on 24.04 stability by limiting the driver to be loaded only on the new hw supported by this driver. This will be temporary until we are ready to migrate 535 to 550. The id list for 'Pmaliases' is not modified, as that only tells gpu- manager to enable runtime power management for matching GPUs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-550/+bug/2061830/+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 2061840] [NEW] Ubuntu 24.04 freezes after plug in power cable
Public bug reported: I have Ubuntu 24.04 installed on my laptop, when I plug in my power cable to my laptop, the whole Ubuntu freezes and nothing is responds, so I have to force shutdown my laptop and restart it. I want to make notice that all other version Ubuntu 23.10, 22.04... with all different flavors work perfect without any issue ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-22-generic 6.8.0-22.22 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:zakaria1758 F pipewire /dev/snd/controlC0: zakaria1765 F wireplumber /dev/snd/controlC1: zakaria1765 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 16 14:40:45 2024 InstallationDate: Installed on 2024-04-14 (2 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2) MachineType: Dell Inc. Latitude E7450 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.8.0-22-generic root=UUID=63a3cbd0-c29b-4ef3-8be8-7c43b782a9b9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-22-generic N/A linux-backports-modules-6.8.0-22-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2020 dmi.bios.release: 65.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: A24 dmi.board.name: 0D8H72 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA24:bd04/11/2020:br65.24:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0D8H72:rvrA00:cvnDellInc.:ct9:cvr:sku062E: dmi.product.name: Latitude E7450 dmi.product.sku: 062E dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2061840 Title: Ubuntu 24.04 freezes after plug in power cable Status in linux package in Ubuntu: New Bug description: I have Ubuntu 24.04 installed on my laptop, when I plug in my power cable to my laptop, the whole Ubuntu freezes and nothing is responds, so I have to force shutdown my laptop and restart it. I want to make notice that all other version Ubuntu 23.10, 22.04... with all different flavors work perfect without any issue ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-22-generic 6.8.0-22.22 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:zakaria1758 F pipewire /dev/snd/controlC0: zakaria1765 F wireplumber /dev/snd/controlC1: zakaria1765 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 16 14:40:45 2024 InstallationDate: Installed on 2024-04-14 (2 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2) MachineType: Dell Inc. Latitude E7450 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.8.0-22-generic root=UUID=63a3cbd0-c29b-4ef3-8be8-7c43b782a9b9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-22-generic N/A linux-backports-modules-6.8.0-22-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2020 dmi.bios.release: 65.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: A24 dmi.board.name: 0D8H72 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA24:bd04/11/2020:br65.24:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0D8H72:rvrA00:cvnDellInc.:ct9:cvr:sku062E: dmi.product.name: Latitude E7450 dmi.product.sku: 062E dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061840/+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 2060727] Re: The keyboard does not work after latest kernel update
I use the ThinkPad L15 Gen4, BIOS version R24ET38W(1.21) together with kernel 6.5.0-1019-oem, the CPU type is i7-1355U. This combination gives a not working keybord after booting. -- 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/2060727 Title: The keyboard does not work after latest kernel update Status in linux package in Ubuntu: Confirmed Bug description: The computer is a ThinkPad L15 Gen 4, its integrated keyboard does not work after the latest kernel update and its subsequent reboot of the laptop. Nothing else is connected to the laptop. -- In /var/log/apt/history.log , the latest we can see is: Start-Date: 2024-04-09 12:37:28 Commandline: apt full-upgrade Install: linux-modules-extra-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), linux-headers-6.5.0-27:amd64 (6.5.0-27.28, automatic), linux-modules-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), linux-image-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), linux-headers-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic) Upgrade: linux-headers-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-image-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-libc-dev:amd64 (6.5.0-26.26, 6.5.0-27.28) End-Date: 2024-04-09 12:37:51 -- $ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.10 Release:23.10 $ # Note: It's Kubuntu 23.10 -- $ uname -a Linux tp 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 7 18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060727/+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
Re: [Kernel-packages] [Bug 2060727] Re: The keyboard does not work after latest kernel update
I use the ThinkPad L15 Gen4, BIOS version R24ET38W(1.21) together with kernel 6.5.0-1019-oem, the CPU type is i7-1355U. This combination gives a not working keybord after booting. On Tue, Apr 16, 2024 at 8:15 AM AaronMa <2060...@bugs.launchpad.net> wrote: > CPU0: 13th Gen Intel(R) Core(TM) i7-1360P > ThinkPad BIOS R24ET27W (1.10 ), EC R24HT20W > Not reproduced on BIOS version above on kernel 6.5.0-1019 and 6.5.0-27. > > Will try to update BIOS and verify again. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2060727 > > Title: > The keyboard does not work after latest kernel update > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > The computer is a ThinkPad L15 Gen 4, its integrated keyboard does not > work after the latest kernel update and its subsequent reboot of the > laptop. Nothing else is connected to the laptop. > > > -- > > In /var/log/apt/history.log , the latest we can see is: > > Start-Date: 2024-04-09 12:37:28 > Commandline: apt full-upgrade > Install: linux-modules-extra-6.5.0-27-generic:amd64 (6.5.0-27.28, > automatic), linux-headers-6.5.0-27:amd64 (6.5.0-27.28, automatic), > linux-modules-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), > linux-image-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), > linux-headers-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic) > Upgrade: linux-headers-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), > linux-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-image-generic:amd64 > (6.5.0.26.26, 6.5.0.27.27), linux-libc-dev:amd64 (6.5.0-26.26, 6.5.0-27.28) > End-Date: 2024-04-09 12:37:51 > > > -- > > $ lsb_release -rd > No LSB modules are available. > Description:Ubuntu 23.10 > Release:23.10 > > $ # Note: It's Kubuntu 23.10 > > > -- > > $ uname -a > Linux tp 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 7 > 18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060727/+subscriptions > > -- RISC OS Select Adjust, that other system. See also, http://www.riscos.com -- 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/2060727 Title: The keyboard does not work after latest kernel update Status in linux package in Ubuntu: Confirmed Bug description: The computer is a ThinkPad L15 Gen 4, its integrated keyboard does not work after the latest kernel update and its subsequent reboot of the laptop. Nothing else is connected to the laptop. -- In /var/log/apt/history.log , the latest we can see is: Start-Date: 2024-04-09 12:37:28 Commandline: apt full-upgrade Install: linux-modules-extra-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), linux-headers-6.5.0-27:amd64 (6.5.0-27.28, automatic), linux-modules-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), linux-image-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), linux-headers-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic) Upgrade: linux-headers-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-image-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-libc-dev:amd64 (6.5.0-26.26, 6.5.0-27.28) End-Date: 2024-04-09 12:37:51 -- $ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.10 Release:23.10 $ # Note: It's Kubuntu 23.10 -- $ uname -a Linux tp 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 7 18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060727/+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 2061091] Re: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)
Here's the kern.log since the last-but-one reboot. ** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2061091/+attachment/5766127/+files/kern.log.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2061091 Title: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0) Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: Sometimes, when trying to shut down or suspend my laptop, it gets stuck on the console screen. If I was suspending, it eventually gives up and goes back to the X session. During a shutdown it hangs forever and the only solution seems to be to force a reboot with Magic-SysRq. The following appears in `kern.log`: ``` Apr 12 08:59:54 xps9320 kernel: [173172.510341] Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): Apr 12 08:59:54 xps9320 kernel: [173172.515669] task:wireplumber state:D stack:0 pid:2408 ppid:2398 flags:0x0006 Apr 12 08:59:54 xps9320 kernel: [173172.518923] Call Trace: Apr 12 08:59:54 xps9320 kernel: [173172.521755] Apr 12 08:59:54 xps9320 kernel: [173172.524099] __schedule+0x2cb/0x750 Apr 12 08:59:54 xps9320 kernel: [173172.526333] schedule+0x63/0x110 Apr 12 08:59:54 xps9320 kernel: [173172.528585] snd_power_ref_and_wait+0xe5/0x140 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.530825] ? __pfx_autoremove_wake_function+0x10/0x10 Apr 12 08:59:54 xps9320 kernel: [173172.533103] snd_ctl_elem_info+0x4f/0x1b0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.535354] snd_ctl_elem_info_user+0x59/0xc0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.537598] snd_ctl_ioctl+0x1d4/0x650 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.539846] ? __fget_light+0xa5/0x120 Apr 12 08:59:54 xps9320 kernel: [173172.542082] __x64_sys_ioctl+0xa0/0xf0 Apr 12 08:59:54 xps9320 kernel: [173172.544334] do_syscall_64+0x58/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.546566] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.548838] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.551085] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.553342] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.96] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.557828] ? common_interrupt+0x54/0xb0 Apr 12 08:59:54 xps9320 kernel: [173172.560075] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 Apr 12 08:59:54 xps9320 kernel: [173172.562321] RIP: 0033:0x70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.564650] RSP: 002b:7ffef2072940 EFLAGS: 0246 ORIG_RAX: 0010 Apr 12 08:59:54 xps9320 kernel: [173172.566925] RAX: ffda RBX: 7ffef20729b0 RCX: 70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.569222] RDX: 7ffef20729b0 RSI: c1105511 RDI: 0022 Apr 12 08:59:54 xps9320 kernel: [173172.571501] RBP: 7ffef2072b90 R08: 65107d2b6070 R09: 0004 Apr 12 08:59:54 xps9320 kernel: [173172.573762] R10: f014 R11: 0246 R12: 65107d2ee100 Apr 12 08:59:54 xps9320 kernel: [173172.576047] R13: 65107d1fb400 R14: 7ffef2072b30 R15: 7ffef2072ad0 Apr 12 08:59:54 xps9320 kernel: [173172.578308] ``` Another point of interest is that, when in this situation: * `lsusb` hangs after printing out a few lines * Outgoing SSH connections hang unless I clear SSH_AUTH_SOCK. gpg-agent appears to be trying to check for smartcards. So I guess there is some sort of deadlock in the USB subsystem which is causing all the other problems? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-27-generic 6.5.0-27.28~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 12 09:42:52 2024 InstallationDate: Installed on 2022-06-28 (653 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2061091/+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 2061091] Re: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)
rav@xps9320:~$ cat /proc/asound/modules 0 snd_soc_sof_sdw 1 snd_usb_audio -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2061091 Title: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0) Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: Sometimes, when trying to shut down or suspend my laptop, it gets stuck on the console screen. If I was suspending, it eventually gives up and goes back to the X session. During a shutdown it hangs forever and the only solution seems to be to force a reboot with Magic-SysRq. The following appears in `kern.log`: ``` Apr 12 08:59:54 xps9320 kernel: [173172.510341] Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): Apr 12 08:59:54 xps9320 kernel: [173172.515669] task:wireplumber state:D stack:0 pid:2408 ppid:2398 flags:0x0006 Apr 12 08:59:54 xps9320 kernel: [173172.518923] Call Trace: Apr 12 08:59:54 xps9320 kernel: [173172.521755] Apr 12 08:59:54 xps9320 kernel: [173172.524099] __schedule+0x2cb/0x750 Apr 12 08:59:54 xps9320 kernel: [173172.526333] schedule+0x63/0x110 Apr 12 08:59:54 xps9320 kernel: [173172.528585] snd_power_ref_and_wait+0xe5/0x140 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.530825] ? __pfx_autoremove_wake_function+0x10/0x10 Apr 12 08:59:54 xps9320 kernel: [173172.533103] snd_ctl_elem_info+0x4f/0x1b0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.535354] snd_ctl_elem_info_user+0x59/0xc0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.537598] snd_ctl_ioctl+0x1d4/0x650 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.539846] ? __fget_light+0xa5/0x120 Apr 12 08:59:54 xps9320 kernel: [173172.542082] __x64_sys_ioctl+0xa0/0xf0 Apr 12 08:59:54 xps9320 kernel: [173172.544334] do_syscall_64+0x58/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.546566] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.548838] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.551085] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.553342] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.96] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.557828] ? common_interrupt+0x54/0xb0 Apr 12 08:59:54 xps9320 kernel: [173172.560075] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 Apr 12 08:59:54 xps9320 kernel: [173172.562321] RIP: 0033:0x70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.564650] RSP: 002b:7ffef2072940 EFLAGS: 0246 ORIG_RAX: 0010 Apr 12 08:59:54 xps9320 kernel: [173172.566925] RAX: ffda RBX: 7ffef20729b0 RCX: 70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.569222] RDX: 7ffef20729b0 RSI: c1105511 RDI: 0022 Apr 12 08:59:54 xps9320 kernel: [173172.571501] RBP: 7ffef2072b90 R08: 65107d2b6070 R09: 0004 Apr 12 08:59:54 xps9320 kernel: [173172.573762] R10: f014 R11: 0246 R12: 65107d2ee100 Apr 12 08:59:54 xps9320 kernel: [173172.576047] R13: 65107d1fb400 R14: 7ffef2072b30 R15: 7ffef2072ad0 Apr 12 08:59:54 xps9320 kernel: [173172.578308] ``` Another point of interest is that, when in this situation: * `lsusb` hangs after printing out a few lines * Outgoing SSH connections hang unless I clear SSH_AUTH_SOCK. gpg-agent appears to be trying to check for smartcards. So I guess there is some sort of deadlock in the USB subsystem which is causing all the other problems? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-27-generic 6.5.0-27.28~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 12 09:42:52 2024 InstallationDate: Installed on 2022-06-28 (653 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2061091/+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 2061091] Re: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0)
Could you share which audio driver is used in the affected system by "cat /proc/asound/modules"? And pls attach the full kern.log to check if something is suspicious here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2061091 Title: Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0) Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: Sometimes, when trying to shut down or suspend my laptop, it gets stuck on the console screen. If I was suspending, it eventually gives up and goes back to the X session. During a shutdown it hangs forever and the only solution seems to be to force a reboot with Magic-SysRq. The following appears in `kern.log`: ``` Apr 12 08:59:54 xps9320 kernel: [173172.510341] Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0): Apr 12 08:59:54 xps9320 kernel: [173172.515669] task:wireplumber state:D stack:0 pid:2408 ppid:2398 flags:0x0006 Apr 12 08:59:54 xps9320 kernel: [173172.518923] Call Trace: Apr 12 08:59:54 xps9320 kernel: [173172.521755] Apr 12 08:59:54 xps9320 kernel: [173172.524099] __schedule+0x2cb/0x750 Apr 12 08:59:54 xps9320 kernel: [173172.526333] schedule+0x63/0x110 Apr 12 08:59:54 xps9320 kernel: [173172.528585] snd_power_ref_and_wait+0xe5/0x140 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.530825] ? __pfx_autoremove_wake_function+0x10/0x10 Apr 12 08:59:54 xps9320 kernel: [173172.533103] snd_ctl_elem_info+0x4f/0x1b0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.535354] snd_ctl_elem_info_user+0x59/0xc0 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.537598] snd_ctl_ioctl+0x1d4/0x650 [snd] Apr 12 08:59:54 xps9320 kernel: [173172.539846] ? __fget_light+0xa5/0x120 Apr 12 08:59:54 xps9320 kernel: [173172.542082] __x64_sys_ioctl+0xa0/0xf0 Apr 12 08:59:54 xps9320 kernel: [173172.544334] do_syscall_64+0x58/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.546566] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.548838] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.551085] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.553342] ? syscall_exit_to_user_mode+0x37/0x60 Apr 12 08:59:54 xps9320 kernel: [173172.96] ? do_syscall_64+0x67/0x90 Apr 12 08:59:54 xps9320 kernel: [173172.557828] ? common_interrupt+0x54/0xb0 Apr 12 08:59:54 xps9320 kernel: [173172.560075] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 Apr 12 08:59:54 xps9320 kernel: [173172.562321] RIP: 0033:0x70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.564650] RSP: 002b:7ffef2072940 EFLAGS: 0246 ORIG_RAX: 0010 Apr 12 08:59:54 xps9320 kernel: [173172.566925] RAX: ffda RBX: 7ffef20729b0 RCX: 70f3adb1a94f Apr 12 08:59:54 xps9320 kernel: [173172.569222] RDX: 7ffef20729b0 RSI: c1105511 RDI: 0022 Apr 12 08:59:54 xps9320 kernel: [173172.571501] RBP: 7ffef2072b90 R08: 65107d2b6070 R09: 0004 Apr 12 08:59:54 xps9320 kernel: [173172.573762] R10: f014 R11: 0246 R12: 65107d2ee100 Apr 12 08:59:54 xps9320 kernel: [173172.576047] R13: 65107d1fb400 R14: 7ffef2072b30 R15: 7ffef2072ad0 Apr 12 08:59:54 xps9320 kernel: [173172.578308] ``` Another point of interest is that, when in this situation: * `lsusb` hangs after printing out a few lines * Outgoing SSH connections hang unless I clear SSH_AUTH_SOCK. gpg-agent appears to be trying to check for smartcards. So I guess there is some sort of deadlock in the USB subsystem which is causing all the other problems? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-27-generic 6.5.0-27.28~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 12 09:42:52 2024 InstallationDate: Installed on 2022-06-28 (653 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2061091/+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 2061830] [NEW] Limit supported pci-id's to the new ones added by 550
Public bug reported: Since 550 wasn't included in the beta we should limit the potential impact on 24.04 stability by limiting the driver to be loaded only on the new hw supported by this driver. This will be temporary until we are ready to migrate 535 to 550. ** Affects: nvidia-graphics-drivers-550 (Ubuntu) Importance: Undecided Assignee: Timo Aaltonen (tjaalton) Status: New ** Affects: nvidia-graphics-drivers-550-server (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-550 (Ubuntu Noble) Importance: Undecided Assignee: Timo Aaltonen (tjaalton) Status: New ** Affects: nvidia-graphics-drivers-550-server (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-550 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-550 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-550-server (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-550 (Ubuntu Noble) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-550-server in Ubuntu. https://bugs.launchpad.net/bugs/2061830 Title: Limit supported pci-id's to the new ones added by 550 Status in nvidia-graphics-drivers-550 package in Ubuntu: New Status in nvidia-graphics-drivers-550-server package in Ubuntu: New Status in nvidia-graphics-drivers-550 source package in Noble: New Status in nvidia-graphics-drivers-550-server source package in Noble: New Bug description: Since 550 wasn't included in the beta we should limit the potential impact on 24.04 stability by limiting the driver to be loaded only on the new hw supported by this driver. This will be temporary until we are ready to migrate 535 to 550. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-550/+bug/2061830/+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 2060193] Re: iwlwifi microcode crash when using wrong password to join a WPA3 access point
I have the same error but different firmware used on iwlwifi module. It's the same network card. It crashes in a few minutes of use and reveals a slow network connection and packet drops. I can't even test network speed by speedtest.net because the test is ending with an error. Ubuntu 23.10 here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2060193 Title: iwlwifi microcode crash when using wrong password to join a WPA3 access point Status in linux-firmware package in Ubuntu: Confirmed Bug description: I noticed that whenever I try to join a wireless network using WPA3 SAE and type the password wrong, I get a microcode crash from iwlwifi. The chip is Intel 9462 (AX201). Ubuntu release 22.04 LTS, faithfully kept up to date. System info available via: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2058226 Crash log seems to be always similar: Apr 3 22:13:55 waplinuc kernel: [1158486.254336] iwlwifi :00:14.3: Not associated and the session protection is over already... Apr 3 22:13:57 waplinuc kernel: [1158487.456868] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. Apr 3 22:13:57 waplinuc kernel: [1158487.456960] iwlwifi :00:14.3: Start IWL Error Log Dump: Apr 3 22:13:57 waplinuc kernel: [1158487.456962] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6 Apr 3 22:13:57 waplinuc kernel: [1158487.456965] iwlwifi :00:14.3: Loaded firmware version: 77.206b0184.0 QuZ-a0-jf-b0-77.ucode Apr 3 22:13:57 waplinuc kernel: [1158487.456967] iwlwifi :00:14.3: 0x0071 | NMI_INTERRUPT_UMAC_FATAL Apr 3 22:13:57 waplinuc kernel: [1158487.456969] iwlwifi :00:14.3: 0x008022F3 | trm_hw_status0 Apr 3 22:13:57 waplinuc kernel: [1158487.456971] iwlwifi :00:14.3: 0x | trm_hw_status1 Apr 3 22:13:57 waplinuc kernel: [1158487.456973] iwlwifi :00:14.3: 0x004C03F2 | branchlink2 Apr 3 22:13:57 waplinuc kernel: [1158487.456974] iwlwifi :00:14.3: 0x64CC | interruptlink1 Apr 3 22:13:57 waplinuc kernel: [1158487.456976] iwlwifi :00:14.3: 0x64CC | interruptlink2 Apr 3 22:13:57 waplinuc kernel: [1158487.456977] iwlwifi :00:14.3: 0x0001191E | data1 Apr 3 22:13:57 waplinuc kernel: [1158487.456979] iwlwifi :00:14.3: 0x1000 | data2 Apr 3 22:13:57 waplinuc kernel: [1158487.456980] iwlwifi :00:14.3: 0x | data3 Apr 3 22:13:57 waplinuc kernel: [1158487.456982] iwlwifi :00:14.3: 0x04C0678B | beacon time Apr 3 22:13:57 waplinuc kernel: [1158487.456983] iwlwifi :00:14.3: 0x920B688C | tsf low Apr 3 22:13:57 waplinuc kernel: [1158487.456985] iwlwifi :00:14.3: 0x0221 | tsf hi Apr 3 22:13:57 waplinuc kernel: [1158487.456986] iwlwifi :00:14.3: 0x0DFD | time gp1 Apr 3 22:13:57 waplinuc kernel: [1158487.456988] iwlwifi :00:14.3: 0x00A909B7 | time gp2 Apr 3 22:13:57 waplinuc kernel: [1158487.456989] iwlwifi :00:14.3: 0x0001 | uCode revision type Apr 3 22:13:57 waplinuc kernel: [1158487.456991] iwlwifi :00:14.3: 0x004D | uCode version major Apr 3 22:13:57 waplinuc kernel: [1158487.456992] iwlwifi :00:14.3: 0x206B0184 | uCode version minor Apr 3 22:13:57 waplinuc kernel: [1158487.456994] iwlwifi :00:14.3: 0x0351 | hw version Apr 3 22:13:57 waplinuc kernel: [1158487.456995] iwlwifi :00:14.3: 0x00489001 | board version Apr 3 22:13:57 waplinuc kernel: [1158487.456997] iwlwifi :00:14.3: 0x001C | hcmd Apr 3 22:13:57 waplinuc kernel: [1158487.456998] iwlwifi :00:14.3: 0x00023000 | isr0 Apr 3 22:13:57 waplinuc kernel: [1158487.456999] iwlwifi :00:14.3: 0x0004C000 | isr1 Apr 3 22:13:57 waplinuc kernel: [1158487.457001] iwlwifi :00:14.3: 0x08F80002 | isr2 Apr 3 22:13:57 waplinuc kernel: [1158487.457002] iwlwifi :00:14.3: 0x00C3000C | isr3 Apr 3 22:13:57 waplinuc kernel: [1158487.457004] iwlwifi :00:14.3: 0x | isr4 Apr 3 22:13:57 waplinuc kernel: [1158487.457005] iwlwifi :00:14.3: 0x0101001C | last cmd Id Apr 3 22:13:57 waplinuc kernel: [1158487.457006] iwlwifi :00:14.3: 0x0001191E | wait_event Apr 3 22:13:57 waplinuc kernel: [1158487.457008] iwlwifi :00:14.3: 0x54B6 | l2p_control Apr 3 22:13:57 waplinuc kernel: [1158487.457009] iwlwifi :00:14.3: 0x1C02 | l2p_duration Apr 3 22:13:57 waplinuc kernel: [1158487.457011] iwlwifi :00:14.3: 0x0003 | l2p_mhvalid Apr 3 22:13:57 waplinuc kernel: [1158487.457012] iwlwifi :00:14.3: 0x | l2p_addr_match Apr 3 22:13:57 waplinuc kernel: [1158487.457013] iwlwifi :00:14.3: 0x000B | lmpm_pmg_sel Apr 3 22:13:57 waplinuc kernel: [1158487.457015] iwlwifi :00:14.3: 0x | timestamp Apr 3 22:13:57 waplinuc kernel: [1158487.457016] iwlwifi :00:14.3: 0x88D4 |
[Kernel-packages] [Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
> In the meantime, the meta package will be deleted so that other people do not upgrade to 5.15.0-102. Just checking, has that happened? I'm still seeing that offered in response to "apt upgrade" on an older system here: The following NEW packages will be installed: linux-headers-5.15.0-102 linux-headers-5.15.0-102-generic linux-image-5.15.0-102-generic linux-modules-5.15.0-102-generic linux-modules-extra-5.15.0-102-generic -- 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/2060780 Title: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: Hi, updated some Ubuntu 22.04 systems to lastest available state this morning, which caused CIFS mounts (from various fileservers) to stop working. Kernel was updated to version 5.15.0-102-generic. I can mount the shares without problems (mount -t cifs), but then, df for example tells me: df: /mnt: Resource temporarily unavailable. I'm able to list and browse all the files, but accessing them (even readonly) is very unstable. Sometimes it works and sometimes it just gives me i/o errors. Switching back to 5.15.0-101-generic or 5.15.0-100-generic solves the problem and everything works again as expected. Seems like some bug has been implemented in 5.15.0-102-generic... To reproduce the problem, I started a while loop on one server to write to some file on a specific mounted CIFS share and read it from another one root@:~# while true; do echo "$(date) hallo" >> /mnt/hallo.txt; sleep 1 ; done -bash: /mnt/hallo.txt: Input/output error -bash: /mnt/hallo.txt: Input/output error ^C root@:~$ tail -f /mnt/hallo.txt Tue Apr 9 04:10:52 PM CEST 2024 hallo Tue Apr 9 04:10:53 PM CEST 2024 hallo Tue Apr 9 04:10:54 PM CEST 2024 hallo Tue Apr 9 04:10:55 PM CEST 2024 hallo Tue Apr 9 04:10:56 PM CEST 2024 hallo Tue Apr 9 04:10:57 PM CEST 2024 hallo Tue Apr 9 04:10:58 PM CEST 2024 hallo Tue Apr 9 04:10:59 PM CEST 2024 hallo Tue Apr 9 04:11:00 PM CEST 2024 hallo Tue Apr 9 04:11:01 PM CEST 2024 hallo tail: cannot determine location of '/mnt/hallo.txt'. reverting to polling: Resource temporarily unavailable Tue Apr 9 04:11:04 PM CEST 2024 hallo Tue Apr 9 04:11:05 PM CEST 2024 hallo Tue Apr 9 04:11:06 PM CEST 2024 hallo Tue Apr 9 04:11:07 PM CEST 2024 hallo Tue Apr 9 04:11:08 PM CEST 2024 hallo Tue Apr 9 04:11:09 PM CEST 2024 hallo Tue Apr 9 04:11:10 PM CEST 2024 hallo While doing this, both servers tell me, the resource is unavailable root@:~# df -h /mnt df: /mnt: Resource temporarily unavailable root@:~$ df -h /mnt df: /mnt: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+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 2061079] Re: GTK-ngl (new default backend) rendering issues with the nvidia 470 driver
** Also affects: nvidia-graphics-drivers-550 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-550 (Ubuntu) Status: New => Fix Released ** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Status: Invalid => Fix Released ** Changed in: nvidia-graphics-drivers-545 (Ubuntu) Status: Invalid => Fix Released ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: Confirmed => Won't Fix -- 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/2061079 Title: GTK-ngl (new default backend) rendering issues with the nvidia 470 driver Status in GTK+: New Status in gtk4 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-535 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-545 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-550 package in Ubuntu: Fix Released Bug description: With nvidia driver, all GTK4 applications have label rendering issues. They are not refresh until passing the cursor over them, giving blank windows. The corner are white and not themed. Passing from one app scren to another one reproduces the issue. gnome-control-center or files, for instance, are blank by default. As suggested by seb128, exporting GSK_RENDERER=gl fixes the issue. Related upstream bugs and discussions are: - https://blog.gtk.org/2024/01/28/new-renderers-for-gtk/ - https://gitlab.gnome.org/GNOME/gtk/-/issues/6574 - https://gitlab.gnome.org/GNOME/gtk/-/issues/6411 - https://gitlab.gnome.org/GNOME/gtk/-/issues/6542 -- $ glxinfo name of display: :1 display: :1 screen: 0 direct rendering: Yes server glx vendor string: NVIDIA Corporation server glx version string: 1.4 server glx extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_libglvnd, GLX_EXT_stereo_tree, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, GLX_NV_multigpu_context, GLX_NV_robustness_video_memory_purge, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_SGI_video_sync client glx vendor string: NVIDIA Corporation client glx version string: 1.4 client glx extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_stereo_tree, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_NV_copy_buffer, GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, GLX_NV_multigpu_context, GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_stereo_tree, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, GLX_NV_multigpu_context, GLX_NV_robustness_video_memory_purge, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_SGI_video_sync Memory info (GL_NVX_gpu_memory_info): Dedicated video memory: 4096 MB Total available memory: 4096 MB Currently available dedicated video memory: 3041 MB OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: NVIDIA GeForce GTX 1050/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 470.239.06 OpenGL core profile
[Kernel-packages] [Bug 2061814] [NEW] Mantic update: upstream stable patchset 2024-04-16
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2024-04-16 Ported from the following upstream stable releases: v6.1.79, v6.6.18 from git://git.kernel.org/ btrfs: add and use helper to check if block group is used btrfs: do not delete unused block group if it may be used soon btrfs: forbid creating subvol qgroups btrfs: forbid deleting live subvol qgroup btrfs: send: return EOPNOTSUPP on unknown flags btrfs: don't reserve space for checksums when writing to nocow files btrfs: reject encoded write if inode has nodatasum flag set btrfs: don't drop extent_map for free space inode on write error driver core: Fix device_link_flag_is_sync_state_only() of: unittest: Fix compile in the non-dynamic case KVM: selftests: Fix a semaphore imbalance in the dirty ring logging test wifi: iwlwifi: Fix some error codes wifi: iwlwifi: uninitialized variable in iwl_acpi_get_ppag_table() of: property: Improve finding the supplier of a remote-endpoint property net: openvswitch: limit the number of recursions from action sets lan966x: Fix crash when adding interface under a lag spi: ppc4xx: Drop write-only variable ASoC: rt5645: Fix deadlock in rt5645_jack_detect_work() net: sysfs: Fix /sys/class/net/ path for statistics nouveau/svm: fix kvcalloc() argument order MIPS: Add 'memory' clobber to csum_ipv6_magic() inline assembler i40e: Do not allow untrusted VF to remove administratively set MAC i40e: Fix waiting for queues of all VSIs to be disabled scs: add CONFIG_MMU dependency for vfree_atomic() tracing/trigger: Fix to return error if failed to alloc snapshot mm/writeback: fix possible divide-by-zero in wb_dirty_limits(), again scsi: storvsc: Fix ring buffer size calculation dm-crypt, dm-verity: disable tasklets ASoC: amd: yc: Add DMI quirk for MSI Bravo 15 C7VF parisc: Prevent hung tasks when printing inventory on serial console ALSA: hda/realtek: Fix the external mic not being recognised for Acer Swift 1 SF114-32 ALSA: hda/realtek: Enable Mute LED on HP Laptop 14-fq0xxx HID: i2c-hid-of: fix NULL-deref on failed power up HID: wacom: generic: Avoid reporting a serial of '0' to userspace HID: wacom: Do not register input devices until after hid_hw_start iio: hid-sensor-als: Return 0 for HID_USAGE_SENSOR_TIME_TIMESTAMP usb: ucsi: Add missing ppm_lock usb: ulpi: Fix debugfs directory leak usb: ucsi_acpi: Fix command completion handling USB: hub: check for alternate port before enabling A_ALT_HNP_SUPPORT usb: f_mass_storage: forbid async queue when shutdown happen usb: dwc3: gadget: Fix NULL pointer dereference in dwc3_gadget_suspend interconnect: qcom: sc8180x: Mark CO0 BCM keepalive media: ir_toy: fix a memleak in irtoy_tx driver core: fw_devlink: Improve detection of overlapping cycles powerpc/kasan: Fix addr error caused by page alignment cifs: fix underflow in parse_server_interfaces() i2c: qcom-geni: Correct I2C TRE sequence irqchip/loongson-eiointc: Use correct struct type in eiointc_domain_alloc() powerpc/kasan: Limit KASAN thread size increase to 32KB i2c: pasemi: split driver into two separate modules i2c: i801: Fix block process call transactions modpost: trim leading spaces when processing source files list mptcp: get rid of msk->subflow mptcp: fix data re-injection from stale subflow selftests: mptcp: add missing kconfig for NF Filter selftests: mptcp: add missing kconfig for NF Filter in v6 selftests: mptcp: add missing kconfig for NF Mangle selftests: mptcp: increase timeout to 30 min mptcp: drop the push_pending field mptcp: check addrs list in userspace_pm_get_local_id scsi: Revert "scsi: fcoe: Fix potential deadlock on >ctlr_lock" Revert "drm/amd: flush any delayed gfxoff on suspend entry" drm/virtio: Set segment size for virtio_gpu device lsm: fix the logic in security_inode_getsecctx() firewire: core: correct documentation of fw_csr_string() kernel API ALSA: hda/realtek: Apply headset jack quirk for non-bass alc287 thinkpads kbuild: Fix changing ELF file type for output of gen_btf for big endian nfc: nci: free rx_data_reassembly skb on NCI device cleanup net: hsr: remove WARN_ONCE() in send_hsr_supervision_frame() net: stmmac: do not clear TBS enable bit on link up/down xen-netback: properly sync TX responses modpost: Don't let "driver"s reference .exit.* linux/init: remove __memexit* annotations um: Fix adding '-no-pie' for clang modpost: Add '.ltext' and '.ltext.*' to TEXT_SECTIONS ALSA: hda/realtek: Enable headset mic on Vaio VJFE-ADL ASoC: codecs: wcd938x: handle deferred probe ALSA: hda/realtek: fix
[Kernel-packages] [Bug 2028891] Re: HTTP boot grub issue
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-bluefield (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2028891 Title: HTTP boot grub issue Status in linux-bluefield package in Ubuntu: Confirmed Bug description: SRU Justification: [Impact] We have tested PXE boot successfully on the BlueField using grubaa64.efi and grub.cfg but HTTP boot does not work. During HTTP boot, UEFI is able to load the grubaa64.efi but doesn’t load grub.cfg and goes instead into the grub rescue shell. From the grub shell, I try to load the grub.cfg file manually, but I get the error shown below. grub> set ?=0 cmdpath=(http,192.168.200.1) color_highlight=black/light-gray color_normal=light-gray/black feature_200_final=y feature_all_video_module=y feature_chainloader_bpb=y feature_default_font_path=y feature_menuentry_id=y feature_menuentry_options=y feature_nativedisk_cmd=y feature_ntldr=y feature_platform_search_hint=y feature_timeout_style=y grub_cpu=arm64 grub_netfs_type=efi grub_platform=efi lang= locale_dir= net_default_interface=efinet2 net_default_ip=192.168.200.2 net_default_mac= net_default_server=192.168.200.1 net_efinet2_ip=192.168.200.2 net_efinet2_mac= package_version=2.06-2ubuntu14.1 pager= prefix=(http,192.168.200.1)/grub pxe_default_server=192.168.200.1 root=http,192.168.200.1 secondary_locale_dir= configfile (http,192.168.200.1)/grub/grub.cfg this doesn't works: error: Fail to send a request! status=0x8002. However it works if I run: configfile (tftp,192.168.200.1)/grub/grub.cfg This forum discusses a similar issue which points to a grub issue: https://groups.google.com/g/linux.debian.bugs.dist/c/CqfwbhAd-Xg Could you please help investigate this? Or point me to the right person? [Fix] * Unknown yet. Investigate grub. [Test Case] * HTTP boot via OOB * HTTP boot via Connect X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2028891/+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 177235] Business Opportunity
-- 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/177235 Title: slow USB 2.0 drive: it's mounted as USB 1.0, not USB 2.0! Status in linux package in Ubuntu: Incomplete Bug description: In gutsy 7.10 dist-upgraded to the max: Ubuntu 64-bit sometimes does not mount USB 2.0 devices as 2.0. 1) plugin in the USB drive 2) mount it if not automounted (sometimes it doesn't) 3) right-click, properties in nautilus, go to drive tab, see speed "12 Mbps" 4) umount it, unplug it 5) sudo rmmod ehci_hcd 6) plugin the USB drive 7) sudo modprobe ehci_hcd 8) mount it if not automounted 9) right-click, properties in nautilus, go to drive tab, see speed "480 Mbps" Something is horribly wrong at recognizing the proper USB speed mode of external drives. From /var/log/messages: note how the first time the drive is mounted properly as high speed, the second time as slow, then as high speed again with the trick of modprobe'ing the ehci_hcd driver. Somehow, the second time the driver sees the same USB hard drive, it fails to recognize it as USB 2.0. (when I modprobe the driver, the USB mouse and keyboard are also recognized, don't be confused by these). If you need more info let me know. Dec 18 11:46:50 instar kernel: [1089450.444192] usb 1-2: USB disconnect, address 3 Dec 18 11:47:23 instar kernel: [1089483.715043] ehci_hcd :00:1d.7: remove, state 4 Dec 18 11:47:23 instar kernel: [1089483.715053] usb usb5: USB disconnect, address 1 Dec 18 11:47:23 instar kernel: [1089483.719139] ehci_hcd :00:1d.7: USB bus 5 deregistered Dec 18 11:47:23 instar kernel: [1089483.720334] ACPI: PCI interrupt for device :00:1d.7 disabled Dec 18 11:47:45 instar kernel: [1089505.912002] usb 1-2: new full speed USB device using uhci_hcd and address 4 Dec 18 11:47:45 instar kernel: [1089506.134623] usb 1-2: configuration #1 chosen from 1 choice Dec 18 11:47:45 instar kernel: [1089506.137630] scsi7 : SCSI emulation for USB Mass Storage devices Dec 18 11:47:50 instar kernel: [1089511.132544] scsi 7:0:0:0: Direct-Access SEAGATE ST3320820A 3.AA PQ: 0 ANSI: 2 Dec 18 11:47:50 instar kernel: [1089511.137515] sd 7:0:0:0: [sde] 625142448 512-byte hardware sectors (320073 MB) Dec 18 11:47:50 instar kernel: [1089511.142502] sd 7:0:0:0: [sde] Write Protect is off Dec 18 11:47:50 instar kernel: [1089511.147491] sd 7:0:0:0: [sde] 625142448 512-byte hardware sectors (320073 MB) Dec 18 11:47:50 instar kernel: [1089511.152399] sd 7:0:0:0: [sde] Write Protect is off Dec 18 11:47:50 instar kernel: [1089511.152410] sde: sde1 Dec 18 11:47:50 instar kernel: [1089511.171501] sd 7:0:0:0: [sde] Attached SCSI disk Dec 18 11:47:50 instar kernel: [1089511.171542] sd 7:0:0:0: Attached scsi generic sg5 type 0 Dec 18 11:48:12 instar kernel: [1089532.675957] ACPI: PCI Interrupt :00:1d.7[A] -> GSI 20 (level, low) -> IRQ 20 Dec 18 11:48:12 instar kernel: [1089532.677029] ehci_hcd :00:1d.7: EHCI Host Controller Dec 18 11:48:12 instar kernel: [1089532.677207] ehci_hcd :00:1d.7: new USB bus registered, assigned bus number 5 Dec 18 11:48:12 instar kernel: [1089532.677244] ehci_hcd :00:1d.7: debug port 1 Dec 18 11:48:12 instar kernel: [1089532.677262] ehci_hcd :00:1d.7: irq 20, io mem 0xffafbc00 Dec 18 11:48:12 instar kernel: [1089532.682397] ehci_hcd :00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 Dec 18 11:48:12 instar kernel: [1089532.682516] usb usb5: configuration #1 chosen from 1 choice Dec 18 11:48:12 instar kernel: [1089532.682548] hub 5-0:1.0: USB hub found Dec 18 11:48:12 instar kernel: [1089532.682559] hub 5-0:1.0: 8 ports detected Dec 18 11:48:12 instar kernel: [1089533.022143] usb 5-2: new high speed USB device using ehci_hcd and address 2 Dec 18 11:48:12 instar kernel: [1089533.154844] usb 5-2: configuration #1 chosen from 1 choice Dec 18 11:48:12 instar kernel: [1089533.155098] scsi8 : SCSI emulation for USB Mass Storage devices Dec 18 11:48:13 instar kernel: [1089533.521886] usb 1-2: USB disconnect, address 4 Dec 18 11:48:13 instar kernel: [1089533.649595] usb 2-1: USB disconnect, address 3 Dec 18 11:48:13 instar kernel: [1089533.889048] usb 2-1: new low speed USB device using uhci_hcd and address 4 Dec 18 11:48:13 instar kernel: [1089534.065223] usb 2-1: configuration #1 chosen from 1 choice Dec 18 11:48:13 instar kernel: [1089534.082362] input: Logitech USB Receiver as /class/input/input12 Dec 18 11:48:13 instar kernel: [1089534.082393] input: USB HID v1.10 Keyboard [Logitech USB Receiver] on usb-:00:1d.1-1 Dec 18 11:48:13 instar kernel: [1089534.111043] /build/buildd/linux-source-2.6.22-2.6.22/drivers/hid/usbhid/hid-core.c: Fixing up Logitech keyboard report descriptor Dec 18 11:48:13 instar kernel: [1089534.111596] input: Logitech USB Receiver as
[Kernel-packages] [Bug 2028891] Re: HTTP boot grub issue
Hi, I tested this with latest ubuntu 22.04 snapshot, and the issue still occurs. I was able to workaround it by replacing grub on http server from the one from Mantic Minotaur (grub-efi-arm64-signed_1.197+2.12~rc1-10ubuntu4_arm64.deb). Are there any plans of fixing that in near future? Thanks Pawel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2028891 Title: HTTP boot grub issue Status in linux-bluefield package in Ubuntu: Confirmed Bug description: SRU Justification: [Impact] We have tested PXE boot successfully on the BlueField using grubaa64.efi and grub.cfg but HTTP boot does not work. During HTTP boot, UEFI is able to load the grubaa64.efi but doesn’t load grub.cfg and goes instead into the grub rescue shell. From the grub shell, I try to load the grub.cfg file manually, but I get the error shown below. grub> set ?=0 cmdpath=(http,192.168.200.1) color_highlight=black/light-gray color_normal=light-gray/black feature_200_final=y feature_all_video_module=y feature_chainloader_bpb=y feature_default_font_path=y feature_menuentry_id=y feature_menuentry_options=y feature_nativedisk_cmd=y feature_ntldr=y feature_platform_search_hint=y feature_timeout_style=y grub_cpu=arm64 grub_netfs_type=efi grub_platform=efi lang= locale_dir= net_default_interface=efinet2 net_default_ip=192.168.200.2 net_default_mac= net_default_server=192.168.200.1 net_efinet2_ip=192.168.200.2 net_efinet2_mac= package_version=2.06-2ubuntu14.1 pager= prefix=(http,192.168.200.1)/grub pxe_default_server=192.168.200.1 root=http,192.168.200.1 secondary_locale_dir= configfile (http,192.168.200.1)/grub/grub.cfg this doesn't works: error: Fail to send a request! status=0x8002. However it works if I run: configfile (tftp,192.168.200.1)/grub/grub.cfg This forum discusses a similar issue which points to a grub issue: https://groups.google.com/g/linux.debian.bugs.dist/c/CqfwbhAd-Xg Could you please help investigate this? Or point me to the right person? [Fix] * Unknown yet. Investigate grub. [Test Case] * HTTP boot via OOB * HTTP boot via Connect X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2028891/+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 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Description changed: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu releases (Jammy, Mantic and Noble) Tvrtko Ursulin (4): - tools/intel_gpu_top: Fix clients header width when no clients - tools/intel_gpu_top: Fix client layout on first sample period - tools/intel_gpu_top: Optimise interactive display a bit - tools/intel_gpu_top: Handle narrow terminals more gracefully + tools/intel_gpu_top: Fix clients header width when no clients + tools/intel_gpu_top: Fix client layout on first sample period + tools/intel_gpu_top: Optimise interactive display a bit + tools/intel_gpu_top: Handle narrow terminals more gracefully + + NOTES: + For Noble, all the 4 patches will be backported + For Mantic, Jammy, only "tools/intel_gpu_top: Handle narrow terminals more gracefully" will be backported because the others are not applicable to Jammy/Mantic (related to refactoring that happened after Mantic release) [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: Fix Released Status in intel-gpu-tools source package in Jammy: In Progress Status in intel-gpu-tools source package in Mantic: In Progress Status in intel-gpu-tools source package in Noble: Fix Released Bug description: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu releases (Jammy, Mantic and Noble) Tvrtko Ursulin (4): tools/intel_gpu_top: Fix clients header width when no clients tools/intel_gpu_top: Fix client layout on first sample period tools/intel_gpu_top: Optimise interactive display a bit tools/intel_gpu_top: Handle narrow terminals more gracefully NOTES: For Noble, all the 4 patches will be backported For Mantic, Jammy, only "tools/intel_gpu_top: Handle narrow terminals more gracefully" will be backported because the others are not applicable to Jammy/Mantic (related to refactoring that happened after Mantic release) [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it
[Kernel-packages] [Bug 2061324] Re: Error when re-building package from source
build fix is usually not accepted in SRU, this fix will be part of
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314
** Changed in: intel-gpu-tools (Ubuntu Jammy)
Status: New => In Progress
** Changed in: intel-gpu-tools (Ubuntu Jammy)
Assignee: (unassigned) => Hector CAO (hectorcao)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2061324
Title:
Error when re-building package from source
Status in intel-gpu-tools package in Ubuntu:
In Progress
Status in intel-gpu-tools source package in Jammy:
In Progress
Bug description:
[ Impact ]
Impossible to build the package from source on Ubuntu 22.04, users will get
this error:
```
int main(void) {
void *a = (void*) _create;
long long b = (long long) a;
return (int) b;
}
Compiler stdout:
Compiler stderr:
Checking for function "memfd_create" : YES
Configuring config.h using configuration
../lib/meson.build:155:4: ERROR: Function does not take positional arguments.
dh_auto_configure: error: cd build && LC_ALL=C.UTF-8 meson ..
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dtests=disabled returned
exit code 1
make[1]: *** [debian/rules:19: override_dh_auto_configure] Error 255
make[1]: Leaving directory '/home/ubuntu/hector/intel-gpu-tools-1.26'
make: *** [debian/rules:39: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
```
The problem comes from the bad call to meson function underscorify in
lib/meson.build
This problem has been fixed upstream:
963917a3565466832a3b2fc22e9285d34a0bf944
lib/meson.build: Fix underscorify call
f.underscorify() is correct, f.underscorify(f) is an error that later
meson versions don't like at all.
The proposed fix for Ubuntu consists of backporting this patch.
[ Test Plan ]
Build the package from source on Ubuntu 22.04
The build command is : dpkg-buildpackage -us -uc -b
Ubuntu release : Jammy 22.04
Meson version : 0.61.2
[ Where problems could occur ]
The problem occurs only at build process
[ Other Info ]
This issue only happens at build and has been fixed upstream.
It is safe to have it in SRU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+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 1049466] Business Opportunity
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1049466 Title: Need support of Ralink RT3290 wifi support Status in Linux: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Precise: Invalid Status in linux-firmware source package in Precise: Fix Released Status in linux source package in Quantal: Invalid Status in linux-firmware source package in Quantal: Won't Fix Status in linux source package in Raring: Fix Released Status in linux-firmware source package in Raring: Fix Released Status in linux package in Baltix: Opinion Status in linux package in Gentoo Linux: New Bug description: RT3290 wifi chip is becoming common on consumer notebooks. Its support starts from 3.6 so support on 12.10 may need lbm-cw. commit a89534edaaa7008992b878680490e9b02a665563 Author: Woody Hung Date: Wed Jun 13 15:01:16 2012 +0800 rt2x00 : RT3290 chip support v4 This patch support the new chipset rt3290 wifi implementation in rt2x00. It initailize the related mac, bbp and rf register in startup phase. And this patch modify the efuse read/write method for the different efuse data offset of rt3290. Signed-off-by: Woody Hung Signed-off-by: John W. Linville To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1049466/+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 2061376] Re: Touchpad scroll bounces back 22.04.4
I think this affects all laptop touchpads. I have Lenovo Thinkpad X1 Yoga Gen 5 and Lenovo Thinkpad E15 Gen 2 which both have this undesired scroll effect. Videos of what is happening: 1st video of finger movements and screen: https://youtu.be/qyhPLnkcWC0 2nd video of screen recording: https://youtube.com/shorts/LP3vMRGzvR8 ** Attachment added: "Thinkpad E15 Gen 2" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061376/+attachment/5766082/+files/evtest_DevInputEvent7_OppositeDirection.log -- 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/2061376 Title: Touchpad scroll bounces back 22.04.4 Status in linux package in Ubuntu: New Bug description: When scrolling anywhere using 2 fingers the scroll bounces back if fingers are lifted up from touchpad. Soft finger point muscles have some flex to them and I strongly believe this causes the scroll bounce back. Easily repeated to both directions. In bounce scroll rapidly moves to the opposite direction of where user wanted to scroll when lifting up fingers. Attached is log file evtest_event5.log from single scroll where there was bounce at lifting fingers. Hardware details: xinput --list WARNING: running xinput against an Xwayland server. See the xinput man page for details. ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ xwayland-pointer:16 id=6[slave pointer (2)] ⎜ ↳ xwayland-relative-pointer:16id=7[slave pointer (2)] ⎜ ↳ xwayland-pointer-gestures:16id=8[slave pointer (2)] ⎜ ↳ xwayland-touch:16 id=10 [slave pointer (2)] ⎜ ↳ xwayland-tablet stylus:16 id=11 [slave pointer (2)] ⎜ ↳ xwayland-tablet eraser:16 id=12 [slave pointer (2)] ⎜ ↳ xwayland-tablet cursor:16 id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ xwayland-keyboard:16id=9[slave keyboard (3)] lshw *-input:0 product: Sleep Button physical id: 2 logical name: input0 logical name: /dev/input/event0 capabilities: platform *-input:1 product: Lid Switch physical id: 3 logical name: input1 logical name: /dev/input/event1 capabilities: platform *-input:2 product: Intel HID events physical id: 4 logical name: input17 logical name: /dev/input/event9 capabilities: platform *-input:3 product: ThinkPad Extra Buttons physical id: 5 logical name: input18 logical name: /dev/input/event10 capabilities: platform *-input:4 product: SYNA8007:00 06CB:CD8C Mouse physical id: 6 logical name: input19 logical name: /dev/input/event4 logical name: /dev/input/mouse0 capabilities: i2c *-input:5 product: Power Button physical id: 7 logical name: input2 logical name: /dev/input/event2 capabilities: platform *-input:6 product: SYNA8007:00 06CB:CD8C Touchpad physical id: 8 logical name: input20 logical name: /dev/input/event5 logical name: /dev/input/mouse1 capabilities: i2c *-input:7 product: Video Bus physical id: 9 logical name: input22 logical name: /dev/input/event11 capabilities: platform *-input:8 product: sof-hda-dsp Mic physical id: a logical name: input23 logical name: /dev/input/event12 *-input:9 product: sof-hda-dsp Headphone physical id: b logical name: input24 logical name: /dev/input/event13 *-input:10 product: sof-hda-dsp HDMI/DP,pcm=3 physical id: c logical name: input25 logical name: /dev/input/event14 *-input:11 product: sof-hda-dsp HDMI/DP,pcm=4 physical id: d logical name: input26 logical name: /dev/input/event15 *-input:12 product: sof-hda-dsp HDMI/DP,pcm=5 physical id: e logical name: input27 logical name: /dev/input/event16 *-input:13 product: AT Translated Set 2 keyboard physical id: f logical name: input3 logical name: /dev/input/event3 logical name: input3::capslock logical name: input3::numlock logical name: input3::scrolllock capabilities: i8042
[Kernel-packages] [Bug 2061747] [NEW] obsolete out-of-tree ivsc dkms in favor of in-tree one
Public bug reported: Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel demands the use of in-tree IVSC drivers instead of out-of-tree dkms from https://github.com/intel/ivsc-driver. ** Affects: ipu6-drivers (Ubuntu) Importance: Undecided Status: New ** Affects: ivsc-driver (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-6.8 (Ubuntu) Importance: Undecided Status: New ** Affects: ipu6-drivers (Ubuntu Noble) Importance: Undecided Status: New ** Affects: ivsc-driver (Ubuntu Noble) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Affects: linux-oem-6.8 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: ipu6-drivers (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-6.8 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: ivsc-driver (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: ipu6-drivers (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.8 (Ubuntu Noble) 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/2061747 Title: obsolete out-of-tree ivsc dkms in favor of in-tree one Status in ipu6-drivers package in Ubuntu: New Status in ivsc-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in linux-oem-6.8 package in Ubuntu: New Status in ipu6-drivers source package in Noble: New Status in ivsc-driver source package in Noble: New Status in linux source package in Noble: New Status in linux-oem-6.8 source package in Noble: New Bug description: Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel demands the use of in-tree IVSC drivers instead of out-of-tree dkms from https://github.com/intel/ivsc-driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2061747/+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 2061079] Re: GTK-ngl (new default backend) rendering issues with the nvidia 470 driver
Confirming that it’s fixed on the same machine with 550. -- 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/2061079 Title: GTK-ngl (new default backend) rendering issues with the nvidia 470 driver Status in GTK+: New Status in gtk4 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-545 package in Ubuntu: Invalid Bug description: With nvidia driver, all GTK4 applications have label rendering issues. They are not refresh until passing the cursor over them, giving blank windows. The corner are white and not themed. Passing from one app scren to another one reproduces the issue. gnome-control-center or files, for instance, are blank by default. As suggested by seb128, exporting GSK_RENDERER=gl fixes the issue. Related upstream bugs and discussions are: - https://blog.gtk.org/2024/01/28/new-renderers-for-gtk/ - https://gitlab.gnome.org/GNOME/gtk/-/issues/6574 - https://gitlab.gnome.org/GNOME/gtk/-/issues/6411 - https://gitlab.gnome.org/GNOME/gtk/-/issues/6542 -- $ glxinfo name of display: :1 display: :1 screen: 0 direct rendering: Yes server glx vendor string: NVIDIA Corporation server glx version string: 1.4 server glx extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_libglvnd, GLX_EXT_stereo_tree, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, GLX_NV_multigpu_context, GLX_NV_robustness_video_memory_purge, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_SGI_video_sync client glx vendor string: NVIDIA Corporation client glx version string: 1.4 client glx extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_stereo_tree, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_NV_copy_buffer, GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, GLX_NV_multigpu_context, GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_stereo_tree, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, GLX_NV_multigpu_context, GLX_NV_robustness_video_memory_purge, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_SGI_video_sync Memory info (GL_NVX_gpu_memory_info): Dedicated video memory: 4096 MB Total available memory: 4096 MB Currently available dedicated video memory: 3041 MB OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: NVIDIA GeForce GTX 1050/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 470.239.06 OpenGL core profile shading language version string: 4.60 NVIDIA OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: GL_AMD_multi_draw_indirect, GL_AMD_seamless_cubemap_per_texture, GL_AMD_vertex_shader_layer, GL_AMD_vertex_shader_viewport_index, GL_ARB_ES2_compatibility, GL_ARB_ES3_1_compatibility, GL_ARB_ES3_2_compatibility, GL_ARB_ES3_compatibility, GL_ARB_arrays_of_arrays,
[Kernel-packages] [Bug 2061376] Re: Touchpad scroll bounces back 22.04.4
** Summary changed: - Touchpad scroll bounces back 22.04.4 Thinkpad X1 Yoga Gen5 + Touchpad scroll bounces back 22.04.4 -- 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/2061376 Title: Touchpad scroll bounces back 22.04.4 Status in linux package in Ubuntu: New Bug description: When scrolling anywhere using 2 fingers the scroll bounces back if fingers are lifted up from touchpad. Soft finger point muscles have some flex to them and I strongly believe this causes the scroll bounce back. Easily repeated to both directions. In bounce scroll rapidly moves to the opposite direction of where user wanted to scroll when lifting up fingers. Attached is log file evtest_event5.log from single scroll where there was bounce at lifting fingers. Hardware details: xinput --list WARNING: running xinput against an Xwayland server. See the xinput man page for details. ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ xwayland-pointer:16 id=6[slave pointer (2)] ⎜ ↳ xwayland-relative-pointer:16id=7[slave pointer (2)] ⎜ ↳ xwayland-pointer-gestures:16id=8[slave pointer (2)] ⎜ ↳ xwayland-touch:16 id=10 [slave pointer (2)] ⎜ ↳ xwayland-tablet stylus:16 id=11 [slave pointer (2)] ⎜ ↳ xwayland-tablet eraser:16 id=12 [slave pointer (2)] ⎜ ↳ xwayland-tablet cursor:16 id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ xwayland-keyboard:16id=9[slave keyboard (3)] lshw *-input:0 product: Sleep Button physical id: 2 logical name: input0 logical name: /dev/input/event0 capabilities: platform *-input:1 product: Lid Switch physical id: 3 logical name: input1 logical name: /dev/input/event1 capabilities: platform *-input:2 product: Intel HID events physical id: 4 logical name: input17 logical name: /dev/input/event9 capabilities: platform *-input:3 product: ThinkPad Extra Buttons physical id: 5 logical name: input18 logical name: /dev/input/event10 capabilities: platform *-input:4 product: SYNA8007:00 06CB:CD8C Mouse physical id: 6 logical name: input19 logical name: /dev/input/event4 logical name: /dev/input/mouse0 capabilities: i2c *-input:5 product: Power Button physical id: 7 logical name: input2 logical name: /dev/input/event2 capabilities: platform *-input:6 product: SYNA8007:00 06CB:CD8C Touchpad physical id: 8 logical name: input20 logical name: /dev/input/event5 logical name: /dev/input/mouse1 capabilities: i2c *-input:7 product: Video Bus physical id: 9 logical name: input22 logical name: /dev/input/event11 capabilities: platform *-input:8 product: sof-hda-dsp Mic physical id: a logical name: input23 logical name: /dev/input/event12 *-input:9 product: sof-hda-dsp Headphone physical id: b logical name: input24 logical name: /dev/input/event13 *-input:10 product: sof-hda-dsp HDMI/DP,pcm=3 physical id: c logical name: input25 logical name: /dev/input/event14 *-input:11 product: sof-hda-dsp HDMI/DP,pcm=4 physical id: d logical name: input26 logical name: /dev/input/event15 *-input:12 product: sof-hda-dsp HDMI/DP,pcm=5 physical id: e logical name: input27 logical name: /dev/input/event16 *-input:13 product: AT Translated Set 2 keyboard physical id: f logical name: input3 logical name: /dev/input/event3 logical name: input3::capslock logical name: input3::numlock logical name: input3::scrolllock capabilities: i8042 *-input:14 product: TPPS/2 ALPS TrackPoint physical id: 10 logical name: input5 logical name: /dev/input/event6 logical name: /dev/input/mouse2 capabilities: i8042 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061376/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 2061079] Re: GTK-ngl (new default backend) rendering issues with the nvidia 470 driver
** Summary changed: - GTK-ngl (new default backend) rendering issues with the nvidia driver + GTK-ngl (new default backend) rendering issues with the nvidia 470 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/2061079 Title: GTK-ngl (new default backend) rendering issues with the nvidia 470 driver Status in GTK+: New Status in gtk4 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-545 package in Ubuntu: Invalid Bug description: With nvidia driver, all GTK4 applications have label rendering issues. They are not refresh until passing the cursor over them, giving blank windows. The corner are white and not themed. Passing from one app scren to another one reproduces the issue. gnome-control-center or files, for instance, are blank by default. As suggested by seb128, exporting GSK_RENDERER=gl fixes the issue. Related upstream bugs and discussions are: - https://blog.gtk.org/2024/01/28/new-renderers-for-gtk/ - https://gitlab.gnome.org/GNOME/gtk/-/issues/6574 - https://gitlab.gnome.org/GNOME/gtk/-/issues/6411 - https://gitlab.gnome.org/GNOME/gtk/-/issues/6542 -- $ glxinfo name of display: :1 display: :1 screen: 0 direct rendering: Yes server glx vendor string: NVIDIA Corporation server glx version string: 1.4 server glx extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_libglvnd, GLX_EXT_stereo_tree, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, GLX_NV_multigpu_context, GLX_NV_robustness_video_memory_purge, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_SGI_video_sync client glx vendor string: NVIDIA Corporation client glx version string: 1.4 client glx extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_stereo_tree, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_NV_copy_buffer, GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, GLX_NV_multigpu_context, GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_stereo_tree, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, GLX_NV_multigpu_context, GLX_NV_robustness_video_memory_purge, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_SGI_video_sync Memory info (GL_NVX_gpu_memory_info): Dedicated video memory: 4096 MB Total available memory: 4096 MB Currently available dedicated video memory: 3041 MB OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: NVIDIA GeForce GTX 1050/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 470.239.06 OpenGL core profile shading language version string: 4.60 NVIDIA OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: GL_AMD_multi_draw_indirect, GL_AMD_seamless_cubemap_per_texture, GL_AMD_vertex_shader_layer, GL_AMD_vertex_shader_viewport_index, GL_ARB_ES2_compatibility, GL_ARB_ES3_1_compatibility,
[Kernel-packages] [Bug 2061049] Re: Fix random HuC/GuC initialization failure of Intel i915 driver
and noble:linux of course -- 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/2061049 Title: Fix random HuC/GuC initialization failure of Intel i915 driver Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.8 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux-oem-6.8 source package in Jammy: Invalid Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: Invalid Status in linux-oem-6.8 source package in Noble: New Bug description: [Impact] i915 error can sometimes be found in kernel message when booting the machine w/ power unplugged kernel: i915 :00:02.0: [drm] *ERROR* GT1: GuC initialization failed -EIO kernel: i915 :00:02.0: [drm] *ERROR* GT1: Enabling uc failed (-5) kernel: i915 :00:02.0: [drm] *ERROR* GT1: Failed to initialize GPU, declaring it wedged! The GPU won't work with this failure [Fix] Backport the upatream fix for allowing slow HuC loading. [Test] 1. Unplug the power of the laptop and make sure it's charged by battery 2. Cold boot or Warm boot the machine and check the GuC init fail message. 3. Go to settings - > about --> graphics to make sure the GPU information is correct every boot. [Where problems could occur] Simply increase the loading time of HuC still get a working system. Should be low risk of regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2061049/+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 2061049] Re: Fix random HuC/GuC initialization failure of Intel i915 driver
please send for oem-6.8 too if it's an issue there -- 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/2061049 Title: Fix random HuC/GuC initialization failure of Intel i915 driver Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.8 package in Ubuntu: New Status in linux source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux-oem-6.8 source package in Jammy: Invalid Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: Invalid Status in linux-oem-6.8 source package in Noble: New Bug description: [Impact] i915 error can sometimes be found in kernel message when booting the machine w/ power unplugged kernel: i915 :00:02.0: [drm] *ERROR* GT1: GuC initialization failed -EIO kernel: i915 :00:02.0: [drm] *ERROR* GT1: Enabling uc failed (-5) kernel: i915 :00:02.0: [drm] *ERROR* GT1: Failed to initialize GPU, declaring it wedged! The GPU won't work with this failure [Fix] Backport the upatream fix for allowing slow HuC loading. [Test] 1. Unplug the power of the laptop and make sure it's charged by battery 2. Cold boot or Warm boot the machine and check the GuC init fail message. 3. Go to settings - > about --> graphics to make sure the GPU information is correct every boot. [Where problems could occur] Simply increase the loading time of HuC still get a working system. Should be low risk of regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2061049/+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 2061079] Re: GTK-ngl (new default backend) rendering issues with the nvidia driver
Confirmed on Nvidia 470. The newer drivers 535 and 545 however do not have the bug. I couldn't test 550 due to bug 2061738. Please also be aware of bug 2059847. -- 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/2061079 Title: GTK-ngl (new default backend) rendering issues with the nvidia driver Status in GTK+: New Status in gtk4 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-545 package in Ubuntu: Invalid Bug description: With nvidia driver, all GTK4 applications have label rendering issues. They are not refresh until passing the cursor over them, giving blank windows. The corner are white and not themed. Passing from one app scren to another one reproduces the issue. gnome-control-center or files, for instance, are blank by default. As suggested by seb128, exporting GSK_RENDERER=gl fixes the issue. Related upstream bugs and discussions are: - https://blog.gtk.org/2024/01/28/new-renderers-for-gtk/ - https://gitlab.gnome.org/GNOME/gtk/-/issues/6574 - https://gitlab.gnome.org/GNOME/gtk/-/issues/6411 - https://gitlab.gnome.org/GNOME/gtk/-/issues/6542 -- $ glxinfo name of display: :1 display: :1 screen: 0 direct rendering: Yes server glx vendor string: NVIDIA Corporation server glx version string: 1.4 server glx extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_libglvnd, GLX_EXT_stereo_tree, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, GLX_NV_multigpu_context, GLX_NV_robustness_video_memory_purge, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_SGI_video_sync client glx vendor string: NVIDIA Corporation client glx version string: 1.4 client glx extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_stereo_tree, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_NV_copy_buffer, GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, GLX_NV_multigpu_context, GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_stereo_tree, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, GLX_NV_multigpu_context, GLX_NV_robustness_video_memory_purge, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_SGI_video_sync Memory info (GL_NVX_gpu_memory_info): Dedicated video memory: 4096 MB Total available memory: 4096 MB Currently available dedicated video memory: 3041 MB OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: NVIDIA GeForce GTX 1050/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 470.239.06 OpenGL core profile shading language version string: 4.60 NVIDIA OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: GL_AMD_multi_draw_indirect, GL_AMD_seamless_cubemap_per_texture, GL_AMD_vertex_shader_layer, GL_AMD_vertex_shader_viewport_index, GL_ARB_ES2_compatibility, GL_ARB_ES3_1_compatibility,
[Kernel-packages] [Bug 2061738] [NEW] Nvidia driver 550 fails to install any kernel module on Noble
Public bug reported: Nvidia driver 550 fails to install any kernel module on Noble. I've tried installing it multiple times through 'Additional Drivers' and on the command line. The nvidia 550 packages install successfully but no kernel module is installed. This problem does NOT occur with 470, 535 or 545. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nvidia-driver-550 550.67-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Apr 16 15:26:32 2024 InstallationDate: Installed on 2024-01-04 (103 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nvidia-graphics-drivers-550 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-550 (Ubuntu) Importance: Critical Status: New ** Tags: amd64 apport-bug noble nvidia -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-550 in Ubuntu. https://bugs.launchpad.net/bugs/2061738 Title: Nvidia driver 550 fails to install any kernel module on Noble Status in nvidia-graphics-drivers-550 package in Ubuntu: New Bug description: Nvidia driver 550 fails to install any kernel module on Noble. I've tried installing it multiple times through 'Additional Drivers' and on the command line. The nvidia 550 packages install successfully but no kernel module is installed. This problem does NOT occur with 470, 535 or 545. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nvidia-driver-550 550.67-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Apr 16 15:26:32 2024 InstallationDate: Installed on 2024-01-04 (103 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nvidia-graphics-drivers-550 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-550/+bug/2061738/+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 2061079] Re: GTK-ngl (new default backend) rendering issues with the nvidia driver
** Also affects: nvidia-graphics-drivers-545 (Ubuntu) Importance: Undecided Status: New ** No longer affects: gtk4 (Ubuntu Noble) ** No longer affects: nvidia-graphics-drivers-545 (Ubuntu Noble) ** Changed in: nvidia-graphics-drivers-545 (Ubuntu) Status: New => Invalid ** Also affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: New => Confirmed ** Also affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-545 in Ubuntu. https://bugs.launchpad.net/bugs/2061079 Title: GTK-ngl (new default backend) rendering issues with the nvidia driver Status in GTK+: New Status in gtk4 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-545 package in Ubuntu: Invalid Bug description: With nvidia driver, all GTK4 applications have label rendering issues. They are not refresh until passing the cursor over them, giving blank windows. The corner are white and not themed. Passing from one app scren to another one reproduces the issue. gnome-control-center or files, for instance, are blank by default. As suggested by seb128, exporting GSK_RENDERER=gl fixes the issue. Related upstream bugs and discussions are: - https://blog.gtk.org/2024/01/28/new-renderers-for-gtk/ - https://gitlab.gnome.org/GNOME/gtk/-/issues/6574 - https://gitlab.gnome.org/GNOME/gtk/-/issues/6411 - https://gitlab.gnome.org/GNOME/gtk/-/issues/6542 -- $ glxinfo name of display: :1 display: :1 screen: 0 direct rendering: Yes server glx vendor string: NVIDIA Corporation server glx version string: 1.4 server glx extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_libglvnd, GLX_EXT_stereo_tree, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, GLX_NV_multigpu_context, GLX_NV_robustness_video_memory_purge, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_SGI_video_sync client glx vendor string: NVIDIA Corporation client glx version string: 1.4 client glx extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_stereo_tree, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_NV_copy_buffer, GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, GLX_NV_multigpu_context, GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_stereo_tree, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, GLX_NV_multigpu_context, GLX_NV_robustness_video_memory_purge, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_SGI_video_sync Memory info (GL_NVX_gpu_memory_info): Dedicated video memory: 4096 MB Total available memory: 4096 MB Currently available dedicated video memory: 3041 MB OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: NVIDIA
[Kernel-packages] [Bug 2060727] Re: The keyboard does not work after latest kernel update
CPU0: 13th Gen Intel(R) Core(TM) i7-1360P ThinkPad BIOS R24ET27W (1.10 ), EC R24HT20W Not reproduced on BIOS version above on kernel 6.5.0-1019 and 6.5.0-27. Will try to update BIOS and verify again. -- 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/2060727 Title: The keyboard does not work after latest kernel update Status in linux package in Ubuntu: Confirmed Bug description: The computer is a ThinkPad L15 Gen 4, its integrated keyboard does not work after the latest kernel update and its subsequent reboot of the laptop. Nothing else is connected to the laptop. -- In /var/log/apt/history.log , the latest we can see is: Start-Date: 2024-04-09 12:37:28 Commandline: apt full-upgrade Install: linux-modules-extra-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), linux-headers-6.5.0-27:amd64 (6.5.0-27.28, automatic), linux-modules-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), linux-image-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic), linux-headers-6.5.0-27-generic:amd64 (6.5.0-27.28, automatic) Upgrade: linux-headers-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-image-generic:amd64 (6.5.0.26.26, 6.5.0.27.27), linux-libc-dev:amd64 (6.5.0-26.26, 6.5.0-27.28) End-Date: 2024-04-09 12:37:51 -- $ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.10 Release:23.10 $ # Note: It's Kubuntu 23.10 -- $ uname -a Linux tp 6.5.0-27-generic #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 7 18:21:00 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060727/+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 2046315] Re: panel flickering after the i915.psr2 is enabled
** Description changed: + SRU verificaton for Noble and oem-6.8-noble: + + [Impact] + In Dell oem project, we found the graphic is flickering on some + machines, finally we narrowed down the issue on (some specific panels + + i915.psr2 enabled), and the issue was reported to Intel, Intel fixed + the issue in the most recent mainline kernel. Here backporting the + patches to Noble kernel. + + It is hard to backport the patches to mantic and oem-6.5, so we wrote + a workaround patch to disable the psr2 for those pannels in the oem-6.5. + + https://gitlab.freedesktop.org/drm/intel/-/issues/9739 + + [Fix] + cherry-pick 8 patches from mainline kernel + + [Test] + I applied the patches to Noble kernel and built a testing kernel, and + Dell validated the testing kernel on those machines, the graphic + didn't flicker anymore. + + I installed the testing kernel on some machines with Intel 13th, 12th + 11th and 10th gen cpu, the grahic worked well too. + + [Where problems could occur] + This patchset changes the fast wake settings for some gpu, it is + possible to make the graphic flicker, but this possibility is very + low, since the patchset comes from mainline kernel and we validated + the patchset on different gens of Intel cpus. + + === + BugLink: https://bugs.launchpad.net/bugs/2046315 [Impact] On serveral Dell laptops, the screen often displays garbage or the screen is flicking This PR is just a workaround, the upstream bug is here: https://gitlab.freedesktop.org/drm/intel/-/issues/9739#note_2187863 After the upstream fix this bug with a real fix, I will revert the workaround and backport the real fix to Noble and Jammy oem-kernel. [Fix] There is no real fix so far, ODM recommends to use a workaround to disable PSR2, this is a temp solution, after we get the real fix, we could revert the temp workaround. [Test case] booting with the patched kernel, If the pannel's edid is in the qurik list, the PSR2 will be disabled (checking /sys/kernel/debug/dri/0/i915_edp_psr_status; if the pannel's edid is not in the quirk list, the graphic driver will work as before. [Where problems could occur] It is possible that the temp solution couldn't work, then the screen will still show garbage and the screen is flicking, another possible regression is the screen has no problem before, but after running patched kernel, the PSR2 is disabled and the system cost more power, but this possibility is very low, I tested the patched on some dell machines, all worked well. -- 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/2046315 Title: panel flickering after the i915.psr2 is enabled Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.8 package in Ubuntu: New Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux-oem-6.8 source package in Jammy: Invalid Status in linux source package in Noble: Triaged Status in linux-oem-6.5 source package in Noble: Invalid Status in linux-oem-6.8 source package in Noble: New Bug description: SRU verificaton for Noble and oem-6.8-noble: [Impact] In Dell oem project, we found the graphic is flickering on some machines, finally we narrowed down the issue on (some specific panels + i915.psr2 enabled), and the issue was reported to Intel, Intel fixed the issue in the most recent mainline kernel. Here backporting the patches to Noble kernel. It is hard to backport the patches to mantic and oem-6.5, so we wrote a workaround patch to disable the psr2 for those pannels in the oem-6.5. https://gitlab.freedesktop.org/drm/intel/-/issues/9739 [Fix] cherry-pick 8 patches from mainline kernel [Test] I applied the patches to Noble kernel and built a testing kernel, and Dell validated the testing kernel on those machines, the graphic didn't flicker anymore. I installed the testing kernel on some machines with Intel 13th, 12th 11th and 10th gen cpu, the grahic worked well too. [Where problems could occur] This patchset changes the fast wake settings for some gpu, it is possible to make the graphic flicker, but this possibility is very low, since the patchset comes from mainline kernel and we validated the patchset on different gens of Intel cpus. === BugLink: https://bugs.launchpad.net/bugs/2046315 [Impact] On serveral Dell laptops, the screen often displays garbage or the screen is flicking This PR is just a workaround, the upstream bug is here: https://gitlab.freedesktop.org/drm/intel/-/issues/9739#note_2187863 After the upstream fix this bug
