[Kernel-packages] [Bug 2035135] Re: Oracle Cloud systems not getting Jammy kernel updates
Noticed this as well on Ubuntu 22.04 oracle arm64 (stuck at 5.15.0-1040) . No oracle kernel update since 2 months+? I decided to install latest generic hwe kernel instead and got rid of all oracle kernels. ``` sudo apt install linux-image-generic-hwe-22.04 reboot ``` ``` dpkg -l | grep -i oracle sudo apt purge linux-headers*oracle linux-image*oracle linux-modules*oracle linux-oracle linux-oracle* ``` -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2035135 Title: Oracle Cloud systems not getting Jammy kernel updates Status in linux-meta-oracle package in Ubuntu: Confirmed Bug description: (Please forgive my ignorance of the kernel release process, maybe I've gotten this all wrong.) There have been several kernel releases for Jammy lately but the two systems I have on Oracle Cloud (one amd64 and one arm64) have not been receiving updates since kernel 5.15.0-1040. It looks like the linux- oracle package is no longer getting updated? Were we supposed to change to a new package called linux-oracle-lts-22.04? lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 apt-cache policy linux-oracle linux-oracle: Installed: 5.15.0.1040.35 Candidate: 5.15.0.1040.35 Version table: *** 5.15.0.1040.35 500 500 http://iad-ad-3.clouds.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.1002.2 500 500 http://iad-ad-3.clouds.archive.ubuntu.com/ubuntu jammy/main amd64 Packages apt-cache policy linux-oracle-lts-22.04 linux-oracle-lts-22.04: Installed: (none) Candidate: 5.15.0.1042.37 Version table: 5.15.0.1042.37 500 500 http://iad-ad-3.clouds.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oracle/+bug/2035135/+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 2035135] Re: Oracle Cloud systems not getting Jammy kernel updates
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-meta-oracle (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2035135 Title: Oracle Cloud systems not getting Jammy kernel updates Status in linux-meta-oracle package in Ubuntu: Confirmed Bug description: (Please forgive my ignorance of the kernel release process, maybe I've gotten this all wrong.) There have been several kernel releases for Jammy lately but the two systems I have on Oracle Cloud (one amd64 and one arm64) have not been receiving updates since kernel 5.15.0-1040. It looks like the linux- oracle package is no longer getting updated? Were we supposed to change to a new package called linux-oracle-lts-22.04? lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 apt-cache policy linux-oracle linux-oracle: Installed: 5.15.0.1040.35 Candidate: 5.15.0.1040.35 Version table: *** 5.15.0.1040.35 500 500 http://iad-ad-3.clouds.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.15.0.1002.2 500 500 http://iad-ad-3.clouds.archive.ubuntu.com/ubuntu jammy/main amd64 Packages apt-cache policy linux-oracle-lts-22.04 linux-oracle-lts-22.04: Installed: (none) Candidate: 5.15.0.1042.37 Version table: 5.15.0.1042.37 500 500 http://iad-ad-3.clouds.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oracle/+bug/2035135/+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 2031835] Re: NVME drive is not brought up after suspend
I replaced the Crucial drive with KINGSTON SKC3000D2048G and the problem has disappeared, crucial CT2000P5PSSD8 still has the same issue. -- 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/2031835 Title: NVME drive is not brought up after suspend Status in linux package in Ubuntu: Confirmed Bug description: I have replaced the NVME drive from Kingston 1TB NVME (which worked after suspending fine but failed) to Crucial CT2000P5PSSD8 (P7CR403), which stays dead after waking up from suspending. The drive stays in power-off mode even after reset and is not visible in BIOS until full power cycle (the motherboard can stay powered on so the power-cycle can be done with the front button rather than switch at power supply) There is nothing in dmesg that would suggest there is an issue other than at the wakeup there is information that the nvme0 drive cannot perform reset. I can't attach logs as my system is dead at that point. I tested it on both 22.04 and 23.04 (I upgraded hoping that 6.2 kernel my resolve the issue) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CasperVersion: 1.480 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 LiveMediaBuild: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: Gigabyte Technology Co., Ltd. AB350-Gaming NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz layerfs-path=minimal.standard.live.squashfs --- quiet splash ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 RelatedPackageVersions: linux-restricted-modules-6.2.0-20-generic N/A linux-backports-modules-6.2.0-20-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1 Tags: lunar Uname: Linux 6.2.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 02/09/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F51h dmi.board.asset.tag: Default string dmi.board.name: AB350-Gaming-CF 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.:bvrF51h:bd02/09/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnAB350-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350-Gaming-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: AB350-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2031835/+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 2036184] Re: Infiniate systemd loop when power off the machine with multiple MD RAIDs
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1004.4
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-oem-6.5' to 'verification-done-
jammy-linux-oem-6.5'. If the problem still exists, change the tag
'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy-
linux-oem-6.5'.
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-oem-6.5-v2
verification-needed-jammy-linux-oem-6.5
--
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/2036184
Title:
Infiniate systemd loop when power off the machine with multiple MD
RAIDs
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
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:
In Progress
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[Impact]
The system with multiple MD RAIDs sometimes hangs while rebooting, that's
because of the systemd can't stop and close the MD disk.
[Fix]
This commit fixes the issue, and this issue has been introduced by
12a6caf27324 ("md: only delete entries from all_mddevs when the disk is freed")
after v6.0
https://patchwork.kernel.org/project/linux-
raid/patch/20230914152416.10819-1-mariusz.tkac...@linux.intel.com/
[Test case]
1. Reboot the system with multiple MD RAIDs at least 10 times.
2. Make sure the system can reboot successfully every time.
3. You should not see error messages like below.
[ 205.360738] systemd-shutdown[1]: Stopping MD devices.
[ 205.366384] systemd-shutdown[1]: sd-device-enumerator: Scan all dirs
[ 205.373327] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/bus
[ 205.380427] systemd-shutdown[1]: sd-device-enumerator: Scanning /sys/class
[ 205.388257] systemd-shutdown[1]: Stopping MD /dev/md127 (9:127).
[ 205.394880] systemd-shutdown[1]: Failed to sync MD block device /dev/md127,
ignoring: Input/output error
[ 205.404975] md: md127 stopped.
[ 205.470491] systemd-shutdown[1]: Stopping MD /dev/md126 (9:126).
[ 205.770179] md: md126: resync interrupted.
[ 205.776258] md126: detected capacity change from 1900396544 to 0
[ 205.783349] md: md126 stopped.
[ 205.862258] systemd-shutdown[1]: Stopping MD /dev/md125 (9:125).
[ 205.862435] md: md126 stopped.
[ 205.868376] systemd-shutdown[1]: Failed to sync MD block device /dev/md125,
ignoring: Input/output error
[ 205.872845] block device autoloading is deprecated and will be removed.
[ 205.880955] md: md125 stopped.
[ 205.934349] systemd-shutdown[1]: Stopping MD /dev/md124p2 (259:7).
[ 205.947707] systemd-shutdown[1]: Could not stop MD /dev/md124p2: Device or
resource busy
[ 205.957004] systemd-shutdown[1]: Stopping MD /dev/md124p1 (259:6).
[ 205.964177] systemd-shutdown[1]: Could not stop MD /dev/md124p1: Device or
resource busy
[ 205.973155] systemd-shutdown[1]: Stopping MD /dev/md124 (9:124).
[ 205.979789] systemd-shutdown[1]: Could not stop MD /dev/md124: Device or
resource busy
[ 205.988475] systemd-shutdown[1]: Not all MD devices stopped, 4 left.
[Where problems could occur]
It fixes the data race issue, should not introduce any regression.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2036184/+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 2035299] Re: dell-uart-backlight fails to communicate with the scalar IC somtimes.
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1004.4
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-oem-6.5' to 'verification-done-
jammy-linux-oem-6.5'. If the problem still exists, change the tag
'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy-
linux-oem-6.5'.
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-oem-6.5-v2
verification-needed-jammy-linux-oem-6.5
--
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/2035299
Title:
dell-uart-backlight fails to communicate with the scalar IC somtimes.
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
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:
In Progress
Status in linux source package in Mantic:
In Progress
Status in linux-oem-6.5 source package in Mantic:
Invalid
Bug description:
[Impact]
Boots up the system and sometimes we can see below messages and that leads to
backlight driver doesn't get loaded.
[ 86.424880] dell_uart_backlight:dell_uart_get_display_mode:tx: 6a 10 85
[ 86.603936] [7439] dell_uart_backlight:dell_uart_get_display_mode:rx: NULL
[ 87.596047] dell_uart_backlight:dell_uart_get_display_mode:tx: 6a 10 85
[ 87.775209] [7439] dell_uart_backlight:dell_uart_get_display_mode:rx: NULL
[Fix]
After applying the patch below, it seems that the read() command may fail to
receive a response, even when increasing the retry times. It never gets a
response when it fails.
fbf84fb368923 ("UBUNTU: SAUCE: platform/x86: dell-uart-backlight:
replace chars_in_buffer() with flush_chars()")
To fix this, try adding a small delay after the write() function as a
workaround.
[Test case]
1. Add dell_uart_backlight.dyndbg="+pt" to the kernel cmdline
2. Boots up the system and check dmesg
3. Make sure there is no dell_uart_backlight rx NULL message in dmesg
4. Try to unload/reload dell_uart_backlight couple times and check dmesg again
[Where problems could occur]
sleep for 1ms is pretty short that it's not possible to lead to messages loss.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2035299/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
Same problem - lenovo V15 G4 AMN - AMD Athlon silver 7120U -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2034477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
