[Kernel-packages] [Bug 1720219] Re: Repeated keys stop after a few characters (^@ character spam every second)
Just want to thank all people involved in the solution of this bug. I just upgraded to Ubuntu 17.10 and I almost get mad with these ^@^@^@^@^@^@^@^@^@^@^@^@ that makes impossible to login in a tty. Thank you. -- 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/1720219 Title: Repeated keys stop after a few characters (^@ character spam every second) Status in linux package in Ubuntu: Confirmed Bug description: Long pressing a key will only repeat a few characters or won't repeat at all in the default 17.10 GNOME environment, it affects all keys including backspace and arrows. It isn't application specific, the problem is always there whether be it terminal or firefox. Setting the repeat delay to 0 will instantly trigger it, however it will still stop after a few characters. I freshly installed 17.10 on a Lenovo Ideapad 700, I haven't had the problem in 16.04 with GNOME 3.22. Edit: Happens in Xorg as well. --- ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: fecka 1156 F...m pulseaudio /dev/snd/controlC0: fecka 1156 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-09-28 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170924) MachineType: LENOVO 80RU Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=ec711d91-c22f-4be9-8820-b1bdca284667 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 Tags: artful wayland-session Uname: Linux 4.13.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/29/2016 dmi.bios.vendor: LENOVO dmi.bios.version: E5CN56WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 700-15ISK 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: Lenovo ideapad 700-15ISK dmi.modalias: dmi:bvnLENOVO:bvrE5CN56WW:bd09/29/2016:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80RU dmi.product.version: Lenovo ideapad 700-15ISK dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: fecka 1156 F...m pulseaudio /dev/snd/controlC0: fecka 1156 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-09-28 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170924) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:0821 Realtek Semiconductor Corp. Bus 001 Device 004: ID 174f:14e6 Syntek Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80RU Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=ec711d91-c22f-4be9-8820-b1bdca284667 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 Tags: artful wayland-session Uname: Linux 4.13.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/29/2016 dmi.bios.vendor: LENOVO dmi.bios.version: E5CN56WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 700-15ISK 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: Lenovo ideapad 700-15ISK dmi.modalias: dmi:bvnLENOVO:bvrE5CN56WW:bd09/29/2016:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80RU dmi.product.version: Lenovo ideapad 700-15ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720219/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1457697] Re: [Vivid] kernel 3.19.0-17 fails to find HDMI sound output
I have the same problem. I'm using Ubuntu 15.04 64 bits (Desktop Edition). CPU Intel Core i7-4790, GPU Intel HD4600. Using latest BIOS and microcode. There is no HDMI out sound with latest kernel 3.19.0-18-generic. When I boot with previous kernel (3.19.0-16-generic) the HDMI sound works. Here is an screenshot of the sound config under 3.19.0-16-generic. It shows the HDMI device, and it works: http://rt002nf0.eresmas.net/Temp/FPGLINUX%203.19.0-16-generic_01.jpg Here is the same screenshot under the newest kernel 3.19.0-18-generic. No HDMI driver shown: http://rt002nf0.eresmas.net/Temp/FPGLINUX%203.19.0-18-generic_01.jpg If I can help in any way, please, don't hesitate to ask. Thanks and best regards. -- 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/1457697 Title: [Vivid] kernel 3.19.0-17 fails to find HDMI sound output Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to 15.04, HDMI is not listed in the audio playback devices. Audio works normally if I select an older kernel version. Kernel versions that cause problem : 3.19.0-17 and 3.19.0-18 Kernel version not causing the problem : 3.16.0-38 Here is the output when listing audio playback devices on 3.19.0-18 antoine@Salon:~$ aplay -l Liste des Périphériques Matériels PLAYBACK carte 1: PCH [HDA Intel PCH], périphérique 0: ALC887-VD Analog [ALC887-VD Analog] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 antoine@Salon:~$ uname -a Linux Salon 3.19.0-18-generic #18-Ubuntu SMP Tue May 19 18:31:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-18-generic 3.19.0-18.18 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: CurrentDesktop: Unity Date: Thu May 21 19:25:32 2015 HibernationDevice: RESUME=UUID=a8a7a46c-693f-4d19-86e4-f3f23054d7a4 InstallationDate: Installed on 2013-11-23 (544 days ago) InstallationMedia: This JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] failed with exit code 1: No journal files were found. MachineType: MSI MS-7799 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic root=UUID=e9c33ba8-b3de-4e30-9cce-3094bd5d1d96 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-05-19 (2 days ago) WifiSyslog: dmi.bios.date: 03/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.0B19 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81TI (MS-7799) dmi.board.vendor: MSI dmi.board.version: 2.1 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.0B19:bd03/25/2014:svnMSI:pnMS-7799:pvr2.1:rvnMSI:rnH81TI(MS-7799):rvr2.1:cvnMSI:ct3:cvr2.1: dmi.product.name: MS-7799 dmi.product.version: 2.1 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457697/+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 1457697] Re: [Vivid] kernel 3.19.0-17 fails to find HDMI sound output
BTW: there are several similar bug reports... https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457369 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457446 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458196 -- 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/1457697 Title: [Vivid] kernel 3.19.0-17 fails to find HDMI sound output Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to 15.04, HDMI is not listed in the audio playback devices. Audio works normally if I select an older kernel version. Kernel versions that cause problem : 3.19.0-17 and 3.19.0-18 Kernel version not causing the problem : 3.16.0-38 Here is the output when listing audio playback devices on 3.19.0-18 antoine@Salon:~$ aplay -l Liste des Périphériques Matériels PLAYBACK carte 1: PCH [HDA Intel PCH], périphérique 0: ALC887-VD Analog [ALC887-VD Analog] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 antoine@Salon:~$ uname -a Linux Salon 3.19.0-18-generic #18-Ubuntu SMP Tue May 19 18:31:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-18-generic 3.19.0-18.18 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: CurrentDesktop: Unity Date: Thu May 21 19:25:32 2015 HibernationDevice: RESUME=UUID=a8a7a46c-693f-4d19-86e4-f3f23054d7a4 InstallationDate: Installed on 2013-11-23 (544 days ago) InstallationMedia: This JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] failed with exit code 1: No journal files were found. MachineType: MSI MS-7799 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic root=UUID=e9c33ba8-b3de-4e30-9cce-3094bd5d1d96 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-18-generic N/A linux-backports-modules-3.19.0-18-generic N/A linux-firmware 1.143.1 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-05-19 (2 days ago) WifiSyslog: dmi.bios.date: 03/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.0B19 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81TI (MS-7799) dmi.board.vendor: MSI dmi.board.version: 2.1 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.0B19:bd03/25/2014:svnMSI:pnMS-7799:pvr2.1:rvnMSI:rnH81TI(MS-7799):rvr2.1:cvnMSI:ct3:cvr2.1: dmi.product.name: MS-7799 dmi.product.version: 2.1 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1457697/+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 2060919] [NEW] Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu"
8 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 abr 11 09:34:59 fpgmsi kernel: RSP: 002b:7bd4d59498a0 EFLAGS: 0246 ORIG_RAX: 0010 abr 11 09:34:59 fpgmsi kernel: RAX: ffda RBX: 0023 RCX: 7bd4ff12396f abr 11 09:34:59 fpgmsi kernel: RDX: 0023 RSI: 40049409 RDI: 002c abr 11 09:34:59 fpgmsi kernel: RBP: 002c R08: 7bd4c80008e0 R09: 0007 abr 11 09:34:59 fpgmsi kernel: R10: 7bd4c80026b0 R11: 0246 R12: 7bd4c8001380 abr 11 09:34:59 fpgmsi kernel: R13: 7bd4d5949a10 R14: 7bd4c8001e20 R15: 7bd4d5949a00 abr 11 09:34:59 fpgmsi kernel: abr 11 09:34:59 fpgmsi kernel: Modules linked in: rfcomm snd_seq_dummy snd_hrtimer vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) nls_utf8 cifs cifs_arc4 cifs_md4 fscache netfs cmac algif_hash algif_skcipher af_alg nft_chain_nat nvidia_uvm(POE) nf_nat bnep zram xt_tcpudp sunrpc xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat nf_tables binfmt_misc nfnetlink nls_iso8859_1 intel_rapl_msr intel_rapl_common intel_uncore_frequency intel_uncore_frequency_common snd_sof_pci_intel_tgl nvidia_drm(POE) snd_sof_intel_hda_common nvidia_modeset(POE) soundwire_intel x86_pkg_temp_thermal intel_powerclamp snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_hda_codec_realtek snd_sof snd_hda_codec_generic ledtrig_audio snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_generic_allocation snd_hda_codec_hdmi soundwire_bus snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec snd_hda_core abr 11 09:34:59 fpgmsi kernel: snd_hwdep coretemp iwlmvm snd_pcm btusb btrtl kvm_intel btbcm snd_seq_midi snd_seq_midi_event btintel cmdlinepart mac80211 btmtk snd_rawmidi spi_nor nvidia(POE) libarc4 kvm bluetooth snd_seq mtd iwlwifi pmt_telemetry snd_seq_device pmt_class snd_timer irqbypass rapl ecdh_generic joydev intel_cstate input_leds wmi_bmof mxm_wmi ecc cfg80211 snd mei_me i2c_i801 spi_intel_pci soundcore mei spi_intel i2c_smbus intel_vsec serial_multi_instantiate acpi_pad acpi_tad mac_hid tcp_bbr sch_fq vmwgfx drm_ttm_helper ttm drm_kms_helper parport_pc ppdev lp parport drm efi_pstore dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log msr lz4 lz4_compress hid_generic usbhid hid crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic ghash_clmulni_intel sha256_ssse3 sha1_ssse3 aesni_intel nvme crypto_simd cryptd nvme_core igc ahci xhci_pci libahci nvme_common abr 11 09:34:59 fpgmsi kernel: xhci_pci_renesas video wmi pinctrl_alderlake abr 11 09:34:59 fpgmsi kernel: CR2: fffe abr 11 09:34:59 fpgmsi kernel: ---[ end trace ]--- abr 11 09:34:59 fpgmsi kernel: RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs] abr 11 09:34:59 fpgmsi kernel: Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 0c 53 48 83 ec 08 48 8b 7f 30 44 89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 db 74 77 <48> 8b 13 b8 00 10 00 00 f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3 abr 11 09:34:59 fpgmsi kernel: RSP: 0018:aab6865ffbf8 EFLAGS: 00010282 abr 11 09:34:59 fpgmsi kernel: RAX: RBX: fffe RCX: abr 11 09:34:59 fpgmsi kernel: RDX: RSI: RDI: abr 11 09:34:59 fpgmsi kernel: RBP: aab6865ffc28 R08: 0001 R09: abr 11 09:34:59 fpgmsi kernel: R10: 00023854 R11: R12: abr 11 09:34:59 fpgmsi kernel: R13: aab6865ffc78 R14: 906675d8aed0 R15: aab6865ffc70 abr 11 09:34:59 fpgmsi kernel: FS: 7bd4d594b6c0() GS:90753f80() knlGS: abr 11 09:34:59 fpgmsi kernel: CS: 0010 DS: ES: CR0: 80050033 abr 11 09:34:59 fpgmsi kernel: CR2: fffe CR3: 00017022a000 CR4: 00750ef0 abr 11 09:34:59 fpgmsi kernel: PKRU: 5554 abr 11 09:34:59 fpgmsi kernel: note: Thread (pooled)[28103] exited with irqs disabled After that error the CIFS filesystem just became unusable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.5.0-27-generic 6.5.0-27.28 ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fprietog 11499 F wireplumber /dev/snd/controlC1: fprietog 11499 F wireplumber /dev/snd/seq:fprietog 11497 F
[Kernel-packages] [Bug 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu"
0 ]---
abr 11 09:34:59 fpgmsi kernel: RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs]
abr 11 09:34:59 fpgmsi kernel: Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee
0c 53 48 83 ec 08 48 8b 7f 30 44 89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85
db 74 77 <48> 8b 13 b8 00 10 00 00 f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3
abr 11 09:34:59 fpgmsi kernel: RSP: 0018:aab6865ffbf8 EFLAGS: 00010282
abr 11 09:34:59 fpgmsi kernel: RAX: RBX: fffe
RCX:
abr 11 09:34:59 fpgmsi kernel: RDX: RSI:
RDI:
abr 11 09:34:59 fpgmsi kernel: RBP: aab6865ffc28 R08: 0001
R09:
abr 11 09:34:59 fpgmsi kernel: R10: 00023854 R11:
R12:
abr 11 09:34:59 fpgmsi kernel: R13: aab6865ffc78 R14: 906675d8aed0
R15: aab6865ffc70
abr 11 09:34:59 fpgmsi kernel: FS: 7bd4d594b6c0()
GS:90753f80() knlGS:
abr 11 09:34:59 fpgmsi kernel: CS: 0010 DS: ES: CR0:
80050033
abr 11 09:34:59 fpgmsi kernel: CR2: fffe CR3: 00017022a000
CR4: 00750ef0
abr 11 09:34:59 fpgmsi kernel: PKRU: 5554
abr 11 09:34:59 fpgmsi kernel: note: Thread (pooled)[28103] exited with irqs
disabled
After that error the CIFS filesystem just became unusable.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-27-generic 6.5.0-27.28
ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fprietog 11499 F wireplumber
/dev/snd/controlC1: fprietog 11499 F wireplumber
/dev/snd/seq:fprietog 11497 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 11 09:35:10 2024
InstallationDate: Installed on 2015-04-02 (3296 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic
root=UUID=07a25daf-33fb-475f-86e0-72ec5d0b3702 ro noplymouth
nvidia-drm.modeset=1
RelatedPackageVersions:
linux-restricted-modules-6.5.0-27-generic N/A
linux-backports-modules-6.5.0-27-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.9
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-10-25 (169 days ago)
dmi.bios.date: 04/26/2022
dmi.bios.release: 5.24
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: D.50
dmi.board.asset.tag: Default string
dmi.board.name: PRO Z690-A WIFI (MS-7D25)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 2.1
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 2.1
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrD.50:bd04/26/2022:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMAGZ690CodexX5(MS-B930):pvr2.1:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ690-AWIFI(MS-7D25):rvr2.1:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.1:skuB930.D:
dmi.product.family: Desktop
dmi.product.name: MAG Z690 Codex X5 (MS-B930)
dmi.product.sku: B930.D
dmi.product.version: 2.1
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060919/+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 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).
fc70
abr 11 09:34:59 fpgmsi kernel: FS: 7bd4d594b6c0()
GS:90753f80() knlGS:
abr 11 09:34:59 fpgmsi kernel: CS: 0010 DS: ES: CR0:
80050033
abr 11 09:34:59 fpgmsi kernel: CR2: fffe CR3: 00017022a000
CR4: 00750ef0
abr 11 09:34:59 fpgmsi kernel: PKRU: 5554
abr 11 09:34:59 fpgmsi kernel: note: Thread (pooled)[28103] exited with irqs
disabled
After that error the CIFS filesystem just became unusable.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-27-generic 6.5.0-27.28
ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fprietog 11499 F wireplumber
/dev/snd/controlC1: fprietog 11499 F wireplumber
/dev/snd/seq:fprietog 11497 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 11 09:35:10 2024
InstallationDate: Installed on 2015-04-02 (3296 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic
root=UUID=07a25daf-33fb-475f-86e0-72ec5d0b3702 ro noplymouth
nvidia-drm.modeset=1
RelatedPackageVersions:
linux-restricted-modules-6.5.0-27-generic N/A
linux-backports-modules-6.5.0-27-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.9
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-10-25 (169 days ago)
dmi.bios.date: 04/26/2022
dmi.bios.release: 5.24
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: D.50
dmi.board.asset.tag: Default string
dmi.board.name: PRO Z690-A WIFI (MS-7D25)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 2.1
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 2.1
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrD.50:bd04/26/2022:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMAGZ690CodexX5(MS-B930):pvr2.1:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ690-AWIFI(MS-7D25):rvr2.1:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.1:skuB930.D:
dmi.product.family: Desktop
dmi.product.name: MAG Z690 Codex X5 (MS-B930)
dmi.product.sku: B930.D
dmi.product.version: 2.1
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060919/+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 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).
11 09:34:59 fpgmsi kernel: CS: 0010 DS: ES: CR0:
80050033
abr 11 09:34:59 fpgmsi kernel: CR2: fffe CR3: 00017022a000
CR4: 00750ef0
abr 11 09:34:59 fpgmsi kernel: PKRU: 5554
abr 11 09:34:59 fpgmsi kernel: note: Thread (pooled)[28103] exited with irqs
disabled
After that error the CIFS filesystem just became unusable.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-27-generic 6.5.0-27.28
ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fprietog 11499 F wireplumber
/dev/snd/controlC1: fprietog 11499 F wireplumber
/dev/snd/seq:fprietog 11497 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 11 09:35:10 2024
InstallationDate: Installed on 2015-04-02 (3296 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic
root=UUID=07a25daf-33fb-475f-86e0-72ec5d0b3702 ro noplymouth
nvidia-drm.modeset=1
RelatedPackageVersions:
linux-restricted-modules-6.5.0-27-generic N/A
linux-backports-modules-6.5.0-27-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.9
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-10-25 (169 days ago)
dmi.bios.date: 04/26/2022
dmi.bios.release: 5.24
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: D.50
dmi.board.asset.tag: Default string
dmi.board.name: PRO Z690-A WIFI (MS-7D25)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 2.1
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 2.1
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrD.50:bd04/26/2022:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMAGZ690CodexX5(MS-B930):pvr2.1:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ690-AWIFI(MS-7D25):rvr2.1:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.1:skuB930.D:
dmi.product.family: Desktop
dmi.product.name: MAG Z690 Codex X5 (MS-B930)
dmi.product.sku: B930.D
dmi.product.version: 2.1
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060919/+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 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).
> I think this patch is probably not needed in 6.5, and causes the issue. How > about I build > you a test kernel with "cifs: fix flushing folio regression for 6.1 backport" > reverted, > and then we see if it fixes things? Yep, fantastic. I can reproduce this problem anytime so I can test it. > If you can help me make a reproducer, that would be great. I can test myself then. Here is some info from a faulty system. Hope it helps: * fstab mount: //192.168.1.10/FPGNAS /mnt/FPGNAS_CIFS cifs _netdev,x-systemd.requires=network-online.target,async,nosuid,nodev,noexec,iocharset=utf8,file_mode=0640,dir_mode=0750,uid=1026,gid=100,credentials=/etc/.cifspwd,rw 0 0 * mount info: //192.168.1.10/FPGNAS on /mnt/FPGNAS_CIFS type cifs (rw,nosuid,nodev,noexec,relatime,vers=3.1.1,cache=strict,username=fprietog,uid=1026,noforceuid,gid=100,noforcegid,addr=192.168.1.10,file_mode=0640,dir_mode=0750,iocharset=utf8,soft,nounix,serverino,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1,closetimeo=1,_netdev,x-systemd.requires=network-online.target) * cp from a file to a file both in same share: # cd /mnt/FPGNAS_CIFS/tmp /mnt/FPGNAS_CIFS/tmp# touch sample1.txt /mnt/FPGNAS_CIFS/tmp# cp sample1.txt sample2.txt Terminado (killed) After that error the CIFS mount become unusable as any operation just hangs. * The remote cifs server is a Synology DS213j NAS. Samba version is: # smbd -V Version 4.15.9 Synology Build 42934, Jul 5 2023 16:52:06 Please, let me know if I can give you any other info that helps to solve the problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2060919 Title: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64). Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: New Status in linux-hwe-6.5 package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Confirmed Bug description: Remote filesystems mounted as CIFS are not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" for x86_64 (and also after updating to Kernel "6.5.0-1014-raspi #17-Ubuntu" in aarch64). The remote filesystem is correctly mounted and seems to work but trying to write data to the filesystem ends in a kernel error exception. After that error the CIFS filesystem just became unusable. Previous Kernel version works correctly. = Example for Kernel "6.5.0-27-generic #28-Ubuntu" (x86_64) = # lsb_release -rd No LSB modules are available. Description: Ubuntu 23.10 Release: 23.10 # uname -a Linux fpgmsi 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 # cat /proc/version_signature Ubuntu 6.5.0-27.28-generic 6.5.13 How to reproduce the problem For instance, I'm using KeePassXC (https://launchpad.net/ubuntu/+source/keepassxc) to update a database located at CIFS filesystem. Any change done to that database causes this Kernel error exception: abr 11 09:34:59 fpgmsi kernel: BUG: unable to handle page fault for address: fffe abr 11 09:34:59 fpgmsi kernel: #PF: supervisor read access in kernel mode abr 11 09:34:59 fpgmsi kernel: #PF: error_code(0x) - not-present page abr 11 09:34:59 fpgmsi kernel: PGD f45a3f067 P4D f45a3f067 PUD f45a41067 PMD 0 abr 11 09:34:59 fpgmsi kernel: Oops: [#1] PREEMPT SMP NOPTI abr 11 09:34:59 fpgmsi kernel: CPU: 0 PID: 28103 Comm: Thread (pooled) Tainted: P OE 6.5.0-27-generic #28-Ubuntu abr 11 09:34:59 fpgmsi kernel: Hardware name: Micro-Star International Co., Ltd. MAG Z690 Codex X5 (MS-B930)/PRO Z690-A WIFI (MS-7D25), BIOS D.50 04/26/2022 abr 11 09:34:59 fpgmsi kernel: RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs] abr 11 09:34:59 fpgmsi kernel: Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 0c 53 48 83 ec 08 48 8b 7f 30 44 89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 db 74 77 <48> 8b 13 b8 00 10 00 00 f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3 abr 11 09:34:59 fpgmsi kernel: RSP: 0018:aab6865ffbf8 EFLAGS: 00010282 abr 11 09:34:59 fpgmsi kernel: RAX: RBX: fffe RCX: abr 11 09:34:59 fpgmsi kernel: RDX: RSI: RDI: abr 11 09:34:59 fpgmsi kernel: RBP: aab6865ffc28 R08: 0001 R09: abr 11 09:34:59 fpgmsi kernel: R10: 00023854 R11: R12: abr 11 09:34:59 fpgmsi kernel: R1
[Kernel-packages] [Bug 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).
FS: 7bd4d594b6c0()
GS:90753f80() knlGS:
abr 11 09:34:59 fpgmsi kernel: CS: 0010 DS: ES: CR0:
80050033
abr 11 09:34:59 fpgmsi kernel: CR2: fffe CR3: 00017022a000
CR4: 00750ef0
abr 11 09:34:59 fpgmsi kernel: PKRU: 5554
abr 11 09:34:59 fpgmsi kernel: note: Thread (pooled)[28103] exited with irqs
disabled
After that error the CIFS filesystem just became unusable.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-27-generic 6.5.0-27.28
ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fprietog 11499 F wireplumber
/dev/snd/controlC1: fprietog 11499 F wireplumber
/dev/snd/seq:fprietog 11497 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 11 09:35:10 2024
InstallationDate: Installed on 2015-04-02 (3296 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic
root=UUID=07a25daf-33fb-475f-86e0-72ec5d0b3702 ro noplymouth
nvidia-drm.modeset=1
RelatedPackageVersions:
linux-restricted-modules-6.5.0-27-generic N/A
linux-backports-modules-6.5.0-27-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.9
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-10-25 (169 days ago)
dmi.bios.date: 04/26/2022
dmi.bios.release: 5.24
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: D.50
dmi.board.asset.tag: Default string
dmi.board.name: PRO Z690-A WIFI (MS-7D25)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 2.1
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 2.1
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrD.50:bd04/26/2022:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMAGZ690CodexX5(MS-B930):pvr2.1:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ690-AWIFI(MS-7D25):rvr2.1:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.1:skuB930.D:
dmi.product.family: Desktop
dmi.product.name: MAG Z690 Codex X5 (MS-B930)
dmi.product.sku: B930.D
dmi.product.version: 2.1
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060919/+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 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).
br 11 09:34:59 fpgmsi kernel: RBP: aab6865ffc28 R08: 0001
R09:
abr 11 09:34:59 fpgmsi kernel: R10: 00023854 R11:
R12:
abr 11 09:34:59 fpgmsi kernel: R13: aab6865ffc78 R14: 906675d8aed0
R15: aab6865ffc70
abr 11 09:34:59 fpgmsi kernel: FS: 7bd4d594b6c0()
GS:90753f80() knlGS:
abr 11 09:34:59 fpgmsi kernel: CS: 0010 DS: ES: CR0:
80050033
abr 11 09:34:59 fpgmsi kernel: CR2: fffe CR3: 00017022a000
CR4: 00750ef0
abr 11 09:34:59 fpgmsi kernel: PKRU: 5554
abr 11 09:34:59 fpgmsi kernel: note: Thread (pooled)[28103] exited with irqs
disabled
After that error the CIFS filesystem just became unusable.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-27-generic 6.5.0-27.28
ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fprietog 11499 F wireplumber
/dev/snd/controlC1: fprietog 11499 F wireplumber
/dev/snd/seq:fprietog 11497 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 11 09:35:10 2024
InstallationDate: Installed on 2015-04-02 (3296 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic
root=UUID=07a25daf-33fb-475f-86e0-72ec5d0b3702 ro noplymouth
nvidia-drm.modeset=1
RelatedPackageVersions:
linux-restricted-modules-6.5.0-27-generic N/A
linux-backports-modules-6.5.0-27-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.9
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-10-25 (169 days ago)
dmi.bios.date: 04/26/2022
dmi.bios.release: 5.24
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: D.50
dmi.board.asset.tag: Default string
dmi.board.name: PRO Z690-A WIFI (MS-7D25)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 2.1
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 2.1
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrD.50:bd04/26/2022:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMAGZ690CodexX5(MS-B930):pvr2.1:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ690-AWIFI(MS-7D25):rvr2.1:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.1:skuB930.D:
dmi.product.family: Desktop
dmi.product.name: MAG Z690 Codex X5 (MS-B930)
dmi.product.sku: B930.D
dmi.product.version: 2.1
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060919/+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 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).
9:34:59 fpgmsi kernel: FS: 7bd4d594b6c0()
GS:90753f80() knlGS:
abr 11 09:34:59 fpgmsi kernel: CS: 0010 DS: ES: CR0:
80050033
abr 11 09:34:59 fpgmsi kernel: CR2: fffe CR3: 00017022a000
CR4: 00750ef0
abr 11 09:34:59 fpgmsi kernel: PKRU: 5554
abr 11 09:34:59 fpgmsi kernel: note: Thread (pooled)[28103] exited with irqs
disabled
After that error the CIFS filesystem just became unusable.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-27-generic 6.5.0-27.28
ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fprietog 11499 F wireplumber
/dev/snd/controlC1: fprietog 11499 F wireplumber
/dev/snd/seq:fprietog 11497 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 11 09:35:10 2024
InstallationDate: Installed on 2015-04-02 (3296 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic
root=UUID=07a25daf-33fb-475f-86e0-72ec5d0b3702 ro noplymouth
nvidia-drm.modeset=1
RelatedPackageVersions:
linux-restricted-modules-6.5.0-27-generic N/A
linux-backports-modules-6.5.0-27-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.9
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-10-25 (169 days ago)
dmi.bios.date: 04/26/2022
dmi.bios.release: 5.24
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: D.50
dmi.board.asset.tag: Default string
dmi.board.name: PRO Z690-A WIFI (MS-7D25)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 2.1
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 2.1
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrD.50:bd04/26/2022:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMAGZ690CodexX5(MS-B930):pvr2.1:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ690-AWIFI(MS-7D25):rvr2.1:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.1:skuB930.D:
dmi.product.family: Desktop
dmi.product.name: MAG Z690 Codex X5 (MS-B930)
dmi.product.sku: B930.D
dmi.product.version: 2.1
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060919/+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 2060919] Re: Remote filesystems mounted as CIFS not working after update to Kernel "6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu" (aarch64).
9:34:59 fpgmsi kernel: R13: aab6865ffc78 R14: 906675d8aed0
R15: aab6865ffc70
abr 11 09:34:59 fpgmsi kernel: FS: 7bd4d594b6c0()
GS:90753f80() knlGS:
abr 11 09:34:59 fpgmsi kernel: CS: 0010 DS: ES: CR0:
80050033
abr 11 09:34:59 fpgmsi kernel: CR2: fffe CR3: 00017022a000
CR4: 00750ef0
abr 11 09:34:59 fpgmsi kernel: PKRU: 5554
abr 11 09:34:59 fpgmsi kernel: note: Thread (pooled)[28103] exited with irqs
disabled
After that error the CIFS filesystem just became unusable.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-27-generic 6.5.0-27.28
ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: fprietog 11499 F.... wireplumber
/dev/snd/controlC1: fprietog 11499 F wireplumber
/dev/snd/seq:fprietog 11497 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 11 09:35:10 2024
InstallationDate: Installed on 2015-04-02 (3296 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic
root=UUID=07a25daf-33fb-475f-86e0-72ec5d0b3702 ro noplymouth
nvidia-drm.modeset=1
RelatedPackageVersions:
linux-restricted-modules-6.5.0-27-generic N/A
linux-backports-modules-6.5.0-27-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.9
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-10-25 (169 days ago)
dmi.bios.date: 04/26/2022
dmi.bios.release: 5.24
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: D.50
dmi.board.asset.tag: Default string
dmi.board.name: PRO Z690-A WIFI (MS-7D25)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 2.1
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 2.1
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrD.50:bd04/26/2022:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMAGZ690CodexX5(MS-B930):pvr2.1:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ690-AWIFI(MS-7D25):rvr2.1:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.1:skuB930.D:
dmi.product.family: Desktop
dmi.product.name: MAG Z690 Codex X5 (MS-B930)
dmi.product.sku: B930.D
dmi.product.version: 2.1
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060919/+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 2054724] [NEW] "nvidia-dkms-545_545.29.06-0ubuntu0.23.10.2" package isn't automatically installed by metapackage "nvidia-driver-545_545.29.06-0ubuntu0.23.10.2"
Public bug reported: Problem summary: The metapackage "nvidia-driver-545_545.29.06-0ubuntu0.23.10.2" contains these dependencies for package "nvidia-dkms-545": nvidia-dkms-545 (<= 545.29.06-1) nvidia-dkms-545 (>= 545.29.06) But installing that metapackage "nvidia- driver-545_545.29.06-0ubuntu0.23.10.2" doesn't requires nor auto-install package "nvidia-dkms-545_545.29.06-0ubuntu0.23.10.2". It seems that these dependencies aren't honored at all. In fact you can manually install/uninstall "nvidia-dkms-545" package without having any effect to "nvidia-driver-545" metapackage. Note: I haven't checked the open driver version but it probably has the same problem as dependencies are similar. Aditional info: --- # lsb_release -rd No LSB modules are available. Description:Ubuntu 23.10 Release:23.10 # apt-cache policy nvidia-driver-545 nvidia-driver-545: Instalados: 545.29.06-0ubuntu0.23.10.2 Candidato: 545.29.06-0ubuntu0.23.10.2 Tabla de versión: *** 545.29.06-0ubuntu0.23.10.2 500 500 http://archive.ubuntu.com/ubuntu mantic-updates/restricted amd64 Packages 100 /var/lib/dpkg/status # apt-cache policy nvidia-dkms-545 nvidia-dkms-545: Instalados: 545.29.06-0ubuntu0.23.10.2 Candidato: 545.29.06-0ubuntu0.23.10.2 Tabla de versión: *** 545.29.06-0ubuntu0.23.10.2 500 500 http://archive.ubuntu.com/ubuntu mantic-updates/restricted amd64 Packages 100 /var/lib/dpkg/status ** Affects: nvidia-graphics-drivers-545 (Ubuntu) Importance: Undecided Status: New ** Description changed: Problem summary: The metapackage "nvidia-driver-545_545.29.06-0ubuntu0.23.10.2" contains these dependencies for package "nvidia-dkms-545": nvidia-dkms-545 (<= 545.29.06-1) nvidia-dkms-545 (>= 545.29.06) But installing that metapackage "nvidia- driver-545_545.29.06-0ubuntu0.23.10.2" doesn't requires nor auto-install package "nvidia-dkms-545_545.29.06-0ubuntu0.23.10.2". It seems that these dependencies aren't honored at all. In fact you can manually install/uninstall "nvidia-dkms-545" package without having any effect to "nvidia-driver-545" metapackage. + Note: I haven't checked the open driver version but it probably has the + same problem as dependencies are similar. + Aditional info: --- # lsb_release -rd No LSB modules are available. Description: Ubuntu 23.10 Release: 23.10 # apt-cache policy nvidia-driver-545 nvidia-driver-545: - Instalados: 545.29.06-0ubuntu0.23.10.2 - Candidato: 545.29.06-0ubuntu0.23.10.2 - Tabla de versión: - *** 545.29.06-0ubuntu0.23.10.2 500 - 500 http://archive.ubuntu.com/ubuntu mantic-updates/restricted amd64 Packages - 100 /var/lib/dpkg/status + Instalados: 545.29.06-0ubuntu0.23.10.2 + Candidato: 545.29.06-0ubuntu0.23.10.2 + Tabla de versión: + *** 545.29.06-0ubuntu0.23.10.2 500 + 500 http://archive.ubuntu.com/ubuntu mantic-updates/restricted amd64 Packages + 100 /var/lib/dpkg/status # apt-cache policy nvidia-dkms-545 nvidia-dkms-545: - Instalados: 545.29.06-0ubuntu0.23.10.2 - Candidato: 545.29.06-0ubuntu0.23.10.2 - Tabla de versión: - *** 545.29.06-0ubuntu0.23.10.2 500 - 500 http://archive.ubuntu.com/ubuntu mantic-updates/restricted amd64 Packages - 100 /var/lib/dpkg/status + Instalados: 545.29.06-0ubuntu0.23.10.2 + Candidato: 545.29.06-0ubuntu0.23.10.2 + Tabla de versión: + *** 545.29.06-0ubuntu0.23.10.2 500 + 500 http://archive.ubuntu.com/ubuntu mantic-updates/restricted amd64 Packages + 100 /var/lib/dpkg/status -- 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/2054724 Title: "nvidia-dkms-545_545.29.06-0ubuntu0.23.10.2" package isn't automatically installed by metapackage "nvidia- driver-545_545.29.06-0ubuntu0.23.10.2" Status in nvidia-graphics-drivers-545 package in Ubuntu: New Bug description: Problem summary: The metapackage "nvidia-driver-545_545.29.06-0ubuntu0.23.10.2" contains these dependencies for package "nvidia-dkms-545": nvidia-dkms-545 (<= 545.29.06-1) nvidia-dkms-545 (>= 545.29.06) But installing that metapackage "nvidia- driver-545_545.29.06-0ubuntu0.23.10.2" doesn't requires nor auto- install package "nvidia-dkms-545_545.29.06-0ubuntu0.23.10.2". It seems that these dependencies aren't honored at all. In fact you can manually install/uninstall "nvidia-dkms-545" package without having any effect to "nvidia-driver-545" metapackage. Note: I haven't checked the open driver version but it probably has the same problem as dependencies are similar. Aditional info: --- # lsb_release -rd No LSB modules are available. Description: Ubuntu 23.10 Release: 23.10 # apt-cache policy nvidia-driver-545
[Kernel-packages] [Bug 2054784] [NEW] Crash in systemd service "nvidia-persistenced" because of deletion of "nvidia-persistenced" user profile on old package "nvidia-compute-utils" purge
Public bug reported: Problem summary: Every time I upgraded nvidia drivers from version XXX to YYY there is a crash in systemd service "nvidia-persistenced" because of deletion of "nvidia-persistenced" user profile after old package "nvidia-compute-utils-XXX" is purged. Example of the problem: --- - Current driver installed: "nvidia-driver-535" - Upgrade to "nvidia-driver-545" - The upgrade will remove previous "nvidia-driver-535" related packages but some of them are not purged. One of these non purged packages is "nvidia-compute-utils-535". - After "nvidia-driver-545" was installed there is a warning on every apt upgrade because it detects packages uninstalled with remaining configuration files, "nvidia-compute-utils-535" package among them, and if you purge that package (something you should do sooner or later) the user profile "nvidia-persistenced" is deleted and systemd service "nvidia-persistenced" will crash in next boot until that profile is created again. The problem is caused because of this automation in "nvidia-compute-utils" .deb package: - On install, "postinst" script creates the user and group for "nvidia-persistenced". - On remove or purge, "postrm" script deletes the "nvidia-persistenced" user. So, when upgraded driver from 535 to 545: - Package "nvidia-compute-utils-535" is removed but not purged. (user "nvidia-persistenced" is deleted, OK) - Package "nvidia-compute-utils-545" is installed. (user "nvidia-persistenced" is created, OK) - When old "nvidia-compute-utils-535" package is purged it deletes "nvidia-persistenced" user profile despite the fact that a newer version of the package is installed and that user is needed. Possible solution: -- Remove deletion of that user profile in "nvidia-compute-utils" package "postrm" file when "purge" is executed, leaving it only for "remove" in this sentence: ... case "$1" in remove|purge) # Remove the nvidia-persistenced user ... ** Affects: nvidia-graphics-drivers-545 (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-545 in Ubuntu. https://bugs.launchpad.net/bugs/2054784 Title: Crash in systemd service "nvidia-persistenced" because of deletion of "nvidia-persistenced" user profile on old package "nvidia-compute- utils" purge Status in nvidia-graphics-drivers-545 package in Ubuntu: New Bug description: Problem summary: Every time I upgraded nvidia drivers from version XXX to YYY there is a crash in systemd service "nvidia-persistenced" because of deletion of "nvidia-persistenced" user profile after old package "nvidia-compute-utils-XXX" is purged. Example of the problem: --- - Current driver installed: "nvidia-driver-535" - Upgrade to "nvidia-driver-545" - The upgrade will remove previous "nvidia-driver-535" related packages but some of them are not purged. One of these non purged packages is "nvidia-compute-utils-535". - After "nvidia-driver-545" was installed there is a warning on every apt upgrade because it detects packages uninstalled with remaining configuration files, "nvidia-compute-utils-535" package among them, and if you purge that package (something you should do sooner or later) the user profile "nvidia-persistenced" is deleted and systemd service "nvidia-persistenced" will crash in next boot until that profile is created again. The problem is caused because of this automation in "nvidia-compute-utils" .deb package: - On install, "postinst" script creates the user and group for "nvidia-persistenced". - On remove or purge, "postrm" script deletes the "nvidia-persistenced" user. So, when upgraded driver from 535 to 545: - Package "nvidia-compute-utils-535" is removed but not purged. (user "nvidia-persistenced" is deleted, OK) - Package "nvidia-compute-utils-545" is installed. (user "nvidia-persistenced" is created, OK) - When old "nvidia-compute-utils-535" package is purged it deletes "nvidia-persistenced" user profile despite the fact that a newer version of the package is installed and that user is needed. Possible solution: -- Remove deletion of that user profile in "nvidia-compute-utils" package "postrm" file when "purge" is executed, leaving it only for "remove" in this sentence: ... case "$1" in remove|purge) # Remove the nvidia-persistenced user ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-545/+bug/2054784/+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 2060919] Re: cifs: Copying file to same directory results in page fault
> If I upgrade to 24.04 which just came out today with the 6.8 kernel, would that also fix this? Seems that this kernel doesn't have this problem, so yes, it will fix the problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2060919 Title: cifs: Copying file to same directory results in page fault Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2060919 [Impact] Copying or modifying a file to the same directory within a cifs mount results in a page fault, and the process that initiated the copy being killed. This could be cp, nautilus, etc. This results in the following oops: BUG: unable to handle page fault for address: fffe #PF: supervisor read access in kernel mode #PF: error_code(0x) - not-present page PGD f45a3f067 P4D f45a3f067 PUD f45a41067 PMD 0 Oops: [#1] PREEMPT SMP NOPTI CPU: 0 PID: 28103 Comm: Thread (pooled) Tainted: P OE 6.5.0-27-generic #28-Ubuntu RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs] Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 0c 53 48 83 ec 08 48 8b 7f 30 44 89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 db 74 77 <48> 8b 13 b8 00 10 00 00 f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3 RSP: 0018:aab6865ffbf8 EFLAGS: 00010282 RAX: RBX: fffe RCX: RDX: RSI: RDI: RBP: aab6865ffc28 R08: 0001 R09: R10: 00023854 R11: R12: R13: aab6865ffc78 R14: 906675d8aed0 R15: aab6865ffc70 FS: 7bd4d594b6c0() GS:90753f80() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: fffe CR3: 00017022a000 CR4: 00750ef0 PKRU: 5554 Call Trace: ? show_regs+0x6d/0x80 ? __die+0x24/0x80 ? page_fault_oops+0x99/0x1b0 ? kernelmode_fixup_or_oops+0xb2/0x140 ? __bad_area_nosemaphore+0x1a5/0x2c0 ? bad_area_nosemaphore+0x16/0x30 ? do_kern_addr_fault+0x7b/0xa0 ? exc_page_fault+0x1a4/0x1b0 ? asm_exc_page_fault+0x27/0x30 ? cifs_flush_folio+0x41/0xf0 [cifs] ? cifs_flush_folio+0x37/0xf0 [cifs] cifs_remap_file_range+0x172/0x660 [cifs] do_clone_file_range+0x101/0x2d0 vfs_clone_file_range+0x3f/0x150 ioctl_file_clone+0x52/0xc0 do_vfs_ioctl+0x68f/0x910 ? __fget_light+0xa5/0x120 __x64_sys_ioctl+0x7d/0xf0 do_syscall_64+0x59/0x90 ? kmem_cache_free+0x22/0x3e0 ? putname+0x5b/0x80 ? exit_to_user_mode_prepare+0x30/0xb0 ? syscall_exit_to_user_mode+0x37/0x60 ? do_syscall_64+0x68/0x90 ? do_syscall_64+0x68/0x90 ? do_syscall_64+0x68/0x90 There is no known workaround. [Fix] The stacktrace is very similar to a regression reported to upstream 6.1.y: https://lore.kernel.org/linux- mm/a76b370f93cb928c049b94e1fde0d2da506dfcb2.ca...@amazon.com/T/ The thread mentions that: commit 7b2404a886f8b91250c31855d287e632123e1746 Author: David Howells Date: Fri Dec 1 00:22:00 2023 + Subject: cifs: Fix flushing, invalidation and file size with copy_file_range() Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7b2404a886f8b91250c31855d287e632123e1746 introduced the issue to Debian's 6.1 kernel. This got backported to Ubuntu in: commit 3adbe2ccd8b9b8fde93e03958d6176945794d288 Author: David Howells Date: Fri Dec 1 00:22:00 2023 + Subject: cifs: Fix flushing, invalidation and file size with copy_file_range() $ git describe --contains 3adbe2ccd8b9b8fde93e03958d6176945794d288 Ubuntu-6.5.0-20.20~107 Which we have been using for some time now, and is not the culprit. Reading the regression mailing list thread, they mention that things work differently in 6.1: > Yeah. __filemap_get_folio() works differently in v6.1.y. There it returns a > folio or NULL. In 6.7 it returns a folio or a negative error code. The error > check in cifs_flush_folio() needs to change to something like: > > folio = filemap_get_folio(inode->i_mapping, index); > if (!folio) > return -ENOMEM; > > David 6.1.y then got a specific patch to fix the issue in 6.1, which is: commit 21bb2ba4f1ac1e3a57594be62dd74e7b1401b2b1 Author: Steve French Date: Fri Jan 12 23:08:51 2024 -0600 Subject: cifs: fix flushing folio regression for 6.1 backport Link: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/mantic/commit/?id=21bb2ba4f1ac1e3a57594be62dd74e7b1401b2b1 $ git describe --contains 21bb2ba4f1ac1e3a57594be62dd74e7b1401b2b1 Ubuntu-6.5.0-27.28~162 Since the Ubuntu mantic kernel consumes both 6.1.y and 6.7.y / 6.8.y stable patches, this patch was applied to mantic's 6.5 kernel by mistake, and contains the wrong logic for how _
[Kernel-packages] [Bug 2060919] Re: cifs: Copying file to same directory results in page fault
Test done. Kernel 6.5.0-35-generic works as expected and solved the problem: root@fpgmsi:~# uname -rv 6.5.0-35-generic #35-Ubuntu SMP PREEMPT_DYNAMIC Fri Apr 26 11:23:57 UTC 2024 root@fpgmsi:~# mount -t cifs -o username=fprietog //192.168.1.10/FPGNAS/ /mnt/share Password for fprietog@//192.168.1.10/FPGNAS/: root@fpgmsi:~# cd /mnt/share/tmp root@fpgmsi:/mnt/share/tmp# touch file1.txt root@fpgmsi:/mnt/share/tmp# cp file1.txt file2.txt Thank you very much! ** 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/2060919 Title: cifs: Copying file to same directory results in page fault Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2060919 [Impact] Copying or modifying a file to the same directory within a cifs mount results in a page fault, and the process that initiated the copy being killed. This could be cp, nautilus, etc. This results in the following oops: BUG: unable to handle page fault for address: fffe #PF: supervisor read access in kernel mode #PF: error_code(0x) - not-present page PGD f45a3f067 P4D f45a3f067 PUD f45a41067 PMD 0 Oops: [#1] PREEMPT SMP NOPTI CPU: 0 PID: 28103 Comm: Thread (pooled) Tainted: P OE 6.5.0-27-generic #28-Ubuntu RIP: 0010:cifs_flush_folio+0x41/0xf0 [cifs] Code: 49 89 cd 31 c9 41 54 49 89 f4 48 c1 ee 0c 53 48 83 ec 08 48 8b 7f 30 44 89 45 d4 e8 79 b3 23 f1 48 89 c3 31 c0 48 85 db 74 77 <48> 8b 13 b8 00 10 00 00 f7 c2 00 00 01 00 74 10 0f b6 4b 51 48 d3 RSP: 0018:aab6865ffbf8 EFLAGS: 00010282 RAX: RBX: fffe RCX: RDX: RSI: RDI: RBP: aab6865ffc28 R08: 0001 R09: R10: 00023854 R11: R12: R13: aab6865ffc78 R14: 906675d8aed0 R15: aab6865ffc70 FS: 7bd4d594b6c0() GS:90753f80() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: fffe CR3: 00017022a000 CR4: 00750ef0 PKRU: 5554 Call Trace: ? show_regs+0x6d/0x80 ? __die+0x24/0x80 ? page_fault_oops+0x99/0x1b0 ? kernelmode_fixup_or_oops+0xb2/0x140 ? __bad_area_nosemaphore+0x1a5/0x2c0 ? bad_area_nosemaphore+0x16/0x30 ? do_kern_addr_fault+0x7b/0xa0 ? exc_page_fault+0x1a4/0x1b0 ? asm_exc_page_fault+0x27/0x30 ? cifs_flush_folio+0x41/0xf0 [cifs] ? cifs_flush_folio+0x37/0xf0 [cifs] cifs_remap_file_range+0x172/0x660 [cifs] do_clone_file_range+0x101/0x2d0 vfs_clone_file_range+0x3f/0x150 ioctl_file_clone+0x52/0xc0 do_vfs_ioctl+0x68f/0x910 ? __fget_light+0xa5/0x120 __x64_sys_ioctl+0x7d/0xf0 do_syscall_64+0x59/0x90 ? kmem_cache_free+0x22/0x3e0 ? putname+0x5b/0x80 ? exit_to_user_mode_prepare+0x30/0xb0 ? syscall_exit_to_user_mode+0x37/0x60 ? do_syscall_64+0x68/0x90 ? do_syscall_64+0x68/0x90 ? do_syscall_64+0x68/0x90 There is no known workaround. [Fix] The stacktrace is very similar to a regression reported to upstream 6.1.y: https://lore.kernel.org/linux- mm/a76b370f93cb928c049b94e1fde0d2da506dfcb2.ca...@amazon.com/T/ The thread mentions that: commit 7b2404a886f8b91250c31855d287e632123e1746 Author: David Howells Date: Fri Dec 1 00:22:00 2023 + Subject: cifs: Fix flushing, invalidation and file size with copy_file_range() Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7b2404a886f8b91250c31855d287e632123e1746 introduced the issue to Debian's 6.1 kernel. This got backported to Ubuntu in: commit 3adbe2ccd8b9b8fde93e03958d6176945794d288 Author: David Howells Date: Fri Dec 1 00:22:00 2023 + Subject: cifs: Fix flushing, invalidation and file size with copy_file_range() $ git describe --contains 3adbe2ccd8b9b8fde93e03958d6176945794d288 Ubuntu-6.5.0-20.20~107 Which we have been using for some time now, and is not the culprit. Reading the regression mailing list thread, they mention that things work differently in 6.1: > Yeah. __filemap_get_folio() works differently in v6.1.y. There it returns a > folio or NULL. In 6.7 it returns a folio or a negative error code. The error > check in cifs_flush_folio() needs to change to something like: > > folio = filemap_get_folio(inode->i_mapping, index); > if (!folio) > return -ENOMEM; > > David 6.1.y then got a specific patch to fix the issue in 6.1, which is: commit 21bb2ba4f1ac1e3a57594be62dd74e7b1401b2b1 Author: Steve French Date: Fri Jan 12 23:08:51 2024 -0600 Subject: cifs: fix flushing folio regression for 6.1 ba
[Kernel-packages] [Bug 1976147] [NEW] [Kernel 5.15] System messages (kernel and systemd) are not shown during boot until it reach a late stage
Public bug reported: # lsb_release -rd Description:Ubuntu 22.04 LTS Release:22.04 # uname -a Linux fpgrpi 5.15.0-1008-raspi #8-Ubuntu SMP PREEMPT Thu May 19 11:58:51 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux Problem summary: System is a Raspberry Pi 4 Model B Rev 1.4. When you remove the 'quiet' and 'splash' options in file /boot/firmware/cmdline.txt in order to see "live" the kernel and systemd messages generated during boot these messages are not shown from the start of the boot process. It remains a blank screen until boot process reached a late stage (maybe the gpu driver init but I'm not sure). It works with previous kernels 5.13 from Impish (it show all messages from the boot start) but is broken in kernels 5.15 from jammy. What was expected: -- As in kernel 5.13 the boot will show 4 raspberries in the top of the screen and the kernel and systemd messages generated will be shown from the start of the boot process. How to reproduce: - Remove the 'quiet' option in file /boot/firmware/cmdline.txt in order to see "live" the kernel and systemd messages generated during boot. With kernel 5.13 these messages are shown from the boot process start but with kernel 5.15 the screen remains blank until a late boot stage. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1976147 Title: [Kernel 5.15] System messages (kernel and systemd) are not shown during boot until it reach a late stage Status in linux-raspi package in Ubuntu: New Bug description: # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 # uname -a Linux fpgrpi 5.15.0-1008-raspi #8-Ubuntu SMP PREEMPT Thu May 19 11:58:51 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux Problem summary: System is a Raspberry Pi 4 Model B Rev 1.4. When you remove the 'quiet' and 'splash' options in file /boot/firmware/cmdline.txt in order to see "live" the kernel and systemd messages generated during boot these messages are not shown from the start of the boot process. It remains a blank screen until boot process reached a late stage (maybe the gpu driver init but I'm not sure). It works with previous kernels 5.13 from Impish (it show all messages from the boot start) but is broken in kernels 5.15 from jammy. What was expected: -- As in kernel 5.13 the boot will show 4 raspberries in the top of the screen and the kernel and systemd messages generated will be shown from the start of the boot process. How to reproduce: - Remove the 'quiet' option in file /boot/firmware/cmdline.txt in order to see "live" the kernel and systemd messages generated during boot. With kernel 5.13 these messages are shown from the boot process start but with kernel 5.15 the screen remains blank until a late boot stage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1976147/+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 1923667] [NEW] Desktop shifted 1 pixel to the right when using full kms driver (Raspberry Pi 4B).
Public bug reported: - System: Raspberry Pi 4 Model B Rev 1.4 - O.S. Ubuntu 21.04 Desktop Beta arm64 - Kernel: Linux fpgrpi 5.11.0-1005-raspi #5-Ubuntu SMP PREEMPT Fri Apr 9 13:10:37 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux - Package version: linux-raspi 5.11.0.1005.3 - Desktop: GNOME 3.38.4 tk: GTK 3.24.25 wm: gnome-shell dm: GDM3 3.38.2.1 Distro: Ubuntu 21.04 (Hirsute Hippo) - Display: server: X.Org 1.20.10 compositor: gnome-shell driver: loaded: modesetting unloaded: fbdev display ID: :1 - OpenGL: renderer: V3D 4.2 v: 2.1 Mesa 21.0.1 direct render: Yes Problem summary: Most of times, after boot, the desktop is shifted 1 pixel to the right when attached to an HDMI monitor. It means that the most right vertical line is shown at the left of the screen. It only happens using the full kms drivers vc4-kms-v3d and vc4-kms-v3d- pi4, and not always but most of times. It doesn't happen using the fake kms driver vc4-fkms-v3d. I'm using X.Org, not Wayland. I've checked dmesg and journalctl messages and didn't found any related error. I also tried a fresh install of Ubuntu 21.04 Beta and got the same problem. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1923667 Title: Desktop shifted 1 pixel to the right when using full kms driver (Raspberry Pi 4B). Status in linux-raspi package in Ubuntu: New Bug description: - System: Raspberry Pi 4 Model B Rev 1.4 - O.S. Ubuntu 21.04 Desktop Beta arm64 - Kernel: Linux fpgrpi 5.11.0-1005-raspi #5-Ubuntu SMP PREEMPT Fri Apr 9 13:10:37 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux - Package version: linux-raspi 5.11.0.1005.3 - Desktop: GNOME 3.38.4 tk: GTK 3.24.25 wm: gnome-shell dm: GDM3 3.38.2.1 Distro: Ubuntu 21.04 (Hirsute Hippo) - Display: server: X.Org 1.20.10 compositor: gnome-shell driver: loaded: modesetting unloaded: fbdev display ID: :1 - OpenGL: renderer: V3D 4.2 v: 2.1 Mesa 21.0.1 direct render: Yes Problem summary: Most of times, after boot, the desktop is shifted 1 pixel to the right when attached to an HDMI monitor. It means that the most right vertical line is shown at the left of the screen. It only happens using the full kms drivers vc4-kms-v3d and vc4-kms- v3d-pi4, and not always but most of times. It doesn't happen using the fake kms driver vc4-fkms-v3d. I'm using X.Org, not Wayland. I've checked dmesg and journalctl messages and didn't found any related error. I also tried a fresh install of Ubuntu 21.04 Beta and got the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1923667/+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 2007259] [NEW] Kernel 5.19.0-1013-raspi boots to blank screen (no gdm login shown)
Public bug reported: - Summary Kernel 5.19.0-1013-raspi boots to blank screen so no gdm login is shown. Previous kernel 5.19.0-1012-raspi boots to gdm login as expected. It's a Raspberry Pi 4 Model B Rev 1.4 - lsb_release -rd Description:Ubuntu 22.10 Release:22.10 - What you expected to happen Kernel 5.19.0-1013-raspi will boot to gdm login. - What happened instead Kernel 5.19.0-1013-raspi will boot to blank screen. Previous kernel 5.19.0-1012-raspi boots to gdm login as expected. I've attached these dmesg and journalctl log files to compare boot in 5.19.0-1013-raspi (BAD) and 5.19.0-1013-raspi (OK): - boot_5.19.0-1012-raspi_OK_dmesg.txt - boot_5.19.0-1012-raspi_OK_journalctl.txt - boot_5.19.0-1013-raspi_BAD_dmesg.txt - boot_5.19.0-1013-raspi_BAD_journalctl.txt ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Attachment added: "boot_5.19.0-1012-raspi_OK_dmesg.txt" https://bugs.launchpad.net/bugs/2007259/+attachment/5647041/+files/boot_5.19.0-1012-raspi_OK_dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2007259 Title: Kernel 5.19.0-1013-raspi boots to blank screen (no gdm login shown) Status in linux-raspi package in Ubuntu: New Bug description: - Summary Kernel 5.19.0-1013-raspi boots to blank screen so no gdm login is shown. Previous kernel 5.19.0-1012-raspi boots to gdm login as expected. It's a Raspberry Pi 4 Model B Rev 1.4 - lsb_release -rd Description: Ubuntu 22.10 Release: 22.10 - What you expected to happen Kernel 5.19.0-1013-raspi will boot to gdm login. - What happened instead Kernel 5.19.0-1013-raspi will boot to blank screen. Previous kernel 5.19.0-1012-raspi boots to gdm login as expected. I've attached these dmesg and journalctl log files to compare boot in 5.19.0-1013-raspi (BAD) and 5.19.0-1013-raspi (OK): - boot_5.19.0-1012-raspi_OK_dmesg.txt - boot_5.19.0-1012-raspi_OK_journalctl.txt - boot_5.19.0-1013-raspi_BAD_dmesg.txt - boot_5.19.0-1013-raspi_BAD_journalctl.txt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2007259/+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 2017209] Re: systemd-oomd fails with "ConditionControlGroupController=memory was not met"
I see that memory cgroup is not enabled: # cat /proc/cgroups | grep y #subsys_name hierarchy num_cgroups enabled memory 0 121 0 So a workaround is to enable it adding "cgroup_enable=memory" to "/boot/firmware/cmdline.txt" kernel parameters file for Raspberry Pi boards. As systemd-oomd worked in Ubuntu 22.10 (Kinetic) without the need of set this kernel parameter the only conclusion I've reached is that this cgroup has been disabled in a point between kernel 5.19 (kinetic) and kernel 6.2 (lunar) releases. So I've searched the Raspberry Pi kernel commits related and found this one: https://github.com/raspberrypi/linux/commit/28aec65bb1743c9bfa53b036999f9835c889704e cgroup: Disable cgroup "memory" by default Some Raspberry Pis have limited RAM and most users won't use the cgroup memory support so it is disabled by default. Enable with: cgroup_enable=memory At this point I don't know what team should fix this bug. I've updated it for linux-raspi package. ** Package changed: systemd (Ubuntu) => linux-raspi (Ubuntu) ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2017209 Title: systemd-oomd fails with "ConditionControlGroupController=memory was not met" Status in linux-raspi package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: PROBLEM SUMMARY: Just upgraded to Ubuntu 23.04 (lunar) from Ubuntu 22.10 (kinetic). systemd-oomd fails with "ConditionControlGroupController=memory was not met" during boot. If you manually started it after boot it starts but after a few minutes it fails with the same error. These are the journalctl entries regarding this problem: abr 20 23:12:48 fpgrpi systemd[1]: Listening on systemd-oomd.socket - Userspace Out-Of-Memory (OOM) Killer Socket. abr 20 23:12:48 fpgrpi systemd[1]: systemd-oomd.service - Userspace Out-Of-Memory (OOM) Killer was skipped because of an unmet condition check (ConditionControlGroupController=memory). --- Line repeat 20 times --- abr 20 23:12:49 fpgrpi systemd[1]: systemd-oomd.service - Userspace Out-Of-Memory (OOM) Killer was skipped because of an unmet condition check (ConditionControlGroupController=memory). abr 20 23:12:49 fpgrpi systemd[1]: systemd-oomd.socket: Trigger limit hit, refusing further activation. abr 20 23:12:49 fpgrpi systemd[1]: systemd-oomd.socket: Failed with result 'trigger-limit-hit'. This is the systemctl status for systemd-oomd.service and systemd-oomd.socket: # systemctl status systemd-oomd.service ○ systemd-oomd.service - Userspace Out-Of-Memory (OOM) Killer Loaded: loaded (/lib/systemd/system/systemd-oomd.service; enabled; preset: enabled) Active: inactive (dead) TriggeredBy: × systemd-oomd.socket Condition: start condition failed at Thu 2023-04-20 23:21:07 CEST; 9h ago └─ ConditionControlGroupController=memory was not met Docs: man:systemd-oomd.service(8) # systemctl status systemd-oomd.socket × systemd-oomd.socket - Userspace Out-Of-Memory (OOM) Killer Socket Loaded: loaded (/lib/systemd/system/systemd-oomd.socket; enabled; preset: enabled) Active: failed (Result: trigger-limit-hit) since Thu 2023-04-20 23:21:07 CEST; 9h ago Duration: 2min 2.252s Triggers: ● systemd-oomd.service Docs: man:systemd-oomd.service(8) Listen: /run/systemd/oom/io.system.ManagedOOM (Stream) ADITIONAL INFO: --- Machine is an arm64 "Raspberry Pi 4 Model B Rev 1.4 8GB" # uname -a Linux fpgrpi 6.2.0-1004-raspi #5-Ubuntu SMP PREEMPT Mon Apr 3 11:15:14 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 # apt-cache policy systemd-oomd systemd-oomd: Instalados: 252.5-2ubuntu3 Candidato: 252.5-2ubuntu3 Tabla de versión: *** 252.5-2ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports lunar/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2017209/+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 1993041] [NEW] nvidia-driver-515 (515.76-0ubuntu0.22.04.1): blank screen after boot, can't log in
Public bug reported: System: Ubuntu 22.04.1 LTS (x86-64) Kernel: 5.15.0-50-generic NVIDIA card: NVIDIA Corporation GA102 [GeForce RTX 3080 Lite Hash Rate] (rev a1) Problem summary: Just updated "nvidia-driver-515" package from "515.65.01-0ubuntu0.22.04.1" to newest "515.76-0ubuntu0.22.04.1". It results in a blank screen after boot and before showing graphical login (gdm) so can't log in. Seems that keyboard doesn't work in this situation so I can't change to a text session. Instead, I used a remote ssh session to get some info: journalctl.txt, dmesg.txt, lspci.txt and nvidia-smi.txt files attached. Card is connected to monitor using HDMI output. Notes: - Previous "nvidia-driver-515" version, "515.65.01-0ubuntu0.22.04.1", worked as expected. Unfortunately I can't install that version again because it seems to be deleted from the repository. - Previous "nvidia-driver-510" version, "510.85.02-0ubuntu0.22.04.1", works as expected. ** Affects: nvidia-graphics-drivers-515 (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-515 in Ubuntu. https://bugs.launchpad.net/bugs/1993041 Title: nvidia-driver-515 (515.76-0ubuntu0.22.04.1): blank screen after boot, can't log in Status in nvidia-graphics-drivers-515 package in Ubuntu: New Bug description: System: Ubuntu 22.04.1 LTS (x86-64) Kernel: 5.15.0-50-generic NVIDIA card: NVIDIA Corporation GA102 [GeForce RTX 3080 Lite Hash Rate] (rev a1) Problem summary: Just updated "nvidia-driver-515" package from "515.65.01-0ubuntu0.22.04.1" to newest "515.76-0ubuntu0.22.04.1". It results in a blank screen after boot and before showing graphical login (gdm) so can't log in. Seems that keyboard doesn't work in this situation so I can't change to a text session. Instead, I used a remote ssh session to get some info: journalctl.txt, dmesg.txt, lspci.txt and nvidia-smi.txt files attached. Card is connected to monitor using HDMI output. Notes: - Previous "nvidia-driver-515" version, "515.65.01-0ubuntu0.22.04.1", worked as expected. Unfortunately I can't install that version again because it seems to be deleted from the repository. - Previous "nvidia-driver-510" version, "510.85.02-0ubuntu0.22.04.1", works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-515/+bug/1993041/+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 1978051] [NEW] "kernel: vc4-drm gpu: swiotlb buffer is full" messages when connected to a gnome-remote-desktop session in wayland
Public bug reported: Problem summary: System is a Raspberry Pi 4 Model B Rev 1.4 (8Gb) While you are connected to a gnome-remote-desktop session in Wayland (using either RDP or VNC backends) the system log is populated with these kind of messages several times per second: ... jun 08 10:13:08 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4194304 bytes), total 32768 (slots), used 14 (slots) jun 08 10:13:08 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4194304 bytes), total 32768 (slots), used 106 (slots) jun 08 10:13:08 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 2 (slots) jun 08 10:13:08 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 2 (slots) jun 08 10:13:08 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 2 (slots) jun 08 10:13:08 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 2 (slots) jun 08 10:13:09 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 1933312 bytes), total 32768 (slots), used 2 (slots) jun 08 10:13:09 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4194304 bytes), total 32768 (slots), used 14 (slots) jun 08 10:13:09 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4194304 bytes), total 32768 (slots), used 106 (slots) jun 08 10:13:09 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 2 (slots) jun 08 10:13:13 fpgrpi kernel: swiotlb_tbl_map_single: 82 callbacks suppressed ... The gnome-remote-desktop session works as expected but performance is degraded. These messages stops when you disconnect to gnome-remote-desktop session. While you are connected to a gnome-remote-desktop session under X11 there are no messages at all and performance is better. So it seems to be a Wayland only problem. How to reproduce: - Connect to a gnome-remote-session under Wayland (it doesn't care if you connect to RDP or VNC backend). These messages will start to populate system log immediately. Aditional info: --- # lsb_release -rd Description:Ubuntu 22.04 LTS Release:22.04 #uname -a Linux fpgrpi 5.15.0-1011-raspi #13-Ubuntu SMP PREEMPT Thu Jun 2 11:44:34 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux #apt-cache policy gnome-remote-desktop gnome-remote-desktop: Instalados: 42.1.1-0ubuntu1 Candidato: 42.1.1-0ubuntu1 Tabla de versión: *** 42.1.1-0ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 Packages 100 /var/lib/dpkg/status ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1978051 Title: "kernel: vc4-drm gpu: swiotlb buffer is full" messages when connected to a gnome-remote-desktop session in wayland Status in linux-raspi package in Ubuntu: New Bug description: Problem summary: System is a Raspberry Pi 4 Model B Rev 1.4 (8Gb) While you are connected to a gnome-remote-desktop session in Wayland (using either RDP or VNC backends) the system log is populated with these kind of messages several times per second: ... jun 08 10:13:08 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4194304 bytes), total 32768 (slots), used 14 (slots) jun 08 10:13:08 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4194304 bytes), total 32768 (slots), used 106 (slots) jun 08 10:13:08 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 2 (slots) jun 08 10:13:08 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 2 (slots) jun 08 10:13:08 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 2 (slots) jun 08 10:13:08 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 2 (slots) jun 08 10:13:09 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 1933312 bytes), total 32768 (slots), used 2 (slots) jun 08 10:13:09 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4194304 bytes), total 32768 (slots), used 14 (slots) jun 08 10:13:09 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4194304 bytes), total 32768 (slots), used 106 (slots) jun 08 10:13:09 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 2 (slots) jun 08 10:13:13 fpgrpi kernel: swiotlb_tbl_map_single: 82 callbacks suppressed ... The gnome-remote-desktop session works as expected but performance is degraded. These messages stops when you disconnect to gnome-remote-desktop session. While you are connected to a gnome-remote-desktop s
[Kernel-packages] [Bug 2081746] [NEW] Ubuntu 24.10 Beta, Raspberry Pi 4: kdump-tools service not started, with errors
Public bug reported: As I understand this kdump-tools service is installed by default in Ubuntu 24.10 Beta. In my tests it seems to work as expected under x86_64 architecture booting with grub. But, with the Raspberry Pi 4, aarch64 architecture, it doesn't work. SYSTEM INFO: Model: Raspberry Pi 4 Model B Rev 1.4 Fresh install using this preinstalled image: https://cdimage.ubuntu.com/ubuntu/releases/24.10/beta/ubuntu-24.10-beta-preinstalled-desktop-arm64+raspi.img.xz # lsb_release -rd Description:Ubuntu Oracular Oriole (development branch) Release:24.10 # uname -a Linux fpgrpitest 6.8.0-1004-raspi #4-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 02:29:55 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -rd Description:Ubuntu Oracular Oriole (development branch) Release:24.10 root@fpgrpitest:~# apt-cache policy kdump-tools kdump-tools: Installed: 1:1.10.3ubuntu3 Candidate: 1:1.10.3ubuntu3 Version table: *** 1:1.10.3ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports oracular/main arm64 Packages 100 /var/lib/dpkg/status 1ST. PROBLEM SUMMARY: - kdump-tools service is enabled by default but it doesn't start because there is "no crashkernel= parameter in the kernel cmdline": Sep 22 07:09:09 fpgrpitest systemd[1]: Starting kdump-tools.service - Kernel crash dump capture service... Sep 22 07:09:09 fpgrpitest kdump-tools[1031]: Starting kdump-tools: Sep 22 07:09:09 fpgrpitest kdump-tools[1138]: * no crashkernel= parameter in the kernel cmdline Sep 22 07:09:09 fpgrpitest systemd[1]: Finished kdump-tools.service - Kernel crash dump capture service. I suspect that it's because for the Raspberry Pi 4 the kernel boot parameters are stored in this file: /boot/firmware/cmdline.txt Notice that it doesn't use grub that is where kernel boot parameters are stored for X86_64 architecture. So I think it's needed to update the /boot/firmware/cmdline.txt file with the crashkernel parameter. 2ND. PROBLEM SUMMARY: - So, trying to fix the 1st problem I added the same crashkernel parameter used in X86_64 architecture to file /boot/firmware/cmdline.txt. So I added "crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M" but it doesn't work showing this error in the journalctl: Sep 23 16:17:43 fpgrpitest systemd[1]: Starting kdump-tools.service - Kernel crash dump capture service... Sep 23 16:17:43 fpgrpitest kdump-tools[919]: Starting kdump-tools: Sep 23 16:17:43 fpgrpitest kdump-tools[1004]: * Creating symlink /var/lib/kdump/vmlinuz Sep 23 16:17:43 fpgrpitest kdump-tools[1086]: kdump-tools: Generating /var/lib/kdump/initrd.img-6.8.0-1004-raspi Sep 23 16:17:43 fpgrpitest kdump-tools[1004]: * Creating symlink /var/lib/kdump/initrd.img Sep 23 16:17:45 fpgrpitest kdump-tools[5226]: kexec_load failed: Function not implemented Sep 23 16:17:45 fpgrpitest kdump-tools[5226]: entry = 0x1d9c03680 flags = 0xb70001 Sep 23 16:17:45 fpgrpitest kdump-tools[5226]: nr_segments = 5 Sep 23 16:17:45 fpgrpitest kdump-tools[5226]: segment[0].buf = 0x9c600010 Sep 23 16:17:45 fpgrpitest kdump-tools[5226]: segment[0].bufsz = 0x1c84008 Sep 23 16:17:45 fpgrpitest kdump-tools[5226]: segment[0].mem = 0x1d6e0 Sep 23 16:17:45 fpgrpitest kdump-tools[5226]: segment[0].memsz = 0x1d6 Sep 23 16:17:45 fpgrpitest kdump-tools[5226]: segment[1].buf = 0x9f200010 Sep 23 16:17:45 fpgrpitest kdump-tools[5226]: segment[1].bufsz = 0x10940c2 Sep 23 16:17:45 fpgrpitest kdump-tools[5226]: segment[1].mem = 0x1d8b6 Sep 23 16:17:45 fpgrpitest kdump-tools[5226]: segment[1].memsz = 0x1095000 Sep 23 16:17:45 fpgrpitest kdump-tools[5226]: segment[2].buf = 0xc88d9590 Sep 23 16:17:45 fpgrpitest kdump-tools[5226]: segment[2].bufsz = 0xdda1 Sep 23 16:17:45 fpgrpitest kdump-tools[5226]: segment[2].mem = 0x1d9bf5000 Sep 23 16:17:45 fpgrpitest kdump-tools[5226]: segment[2].memsz = 0xe000 Sep 23 16:17:45 fpgrpitest kdump-tools[5226]: segment[3].buf = 0xc88e7960 Sep 23 16:17:45 fpgrpitest kdump-tools[5226]: segment[3].bufsz = 0x3538 Sep 23 16:17:45 fpgrpitest kdump-tools[5226]: segment[3].mem = 0x1d9c03000 Sep 23 16:17:45 fpgrpitest kdump-tools[5226]: segment[3].memsz = 0x4000 Sep 23 16:17:45 fpgrpitest kdump-tools[5226]: segment[4].buf = 0xc88a1740 Sep 23 16:17:45 fpgrpitest kdump-tools[5226]: segment[4].bufsz = 0x400 Sep 23 16:17:45 fpgrpitest kdump-tools[5226]: segment[4].mem = 0x1f6dff000 Sep 23 16:17:45 fpgrpitest kdump-tools[5226]: segment[4].memsz = 0x1000 Sep 23 16:17:45 fpgrpitest kdump-tools[1004]: * failed to load kdump kernel Sep 23 16:17:45 fpgrpitest kdump-tools[5227]: failed to load kdump kernel Sep 23 16:17:45 fpgrpitest systemd[1]: Finished kdump-tools.service - Kernel crash dump capture service. Seems that the current kernel is not ready/enabled for this tool. Notice that this kernel used in Ubuntu 24.10 Beta for the Raspberry Pi is a very old version 6.8... AFAIK t
