[Kernel-packages] [Bug 1925421] Re: arm64 support
** No longer affects: linux-gcp (Ubuntu Bionic) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1925421 Title: arm64 support Status in linux-gcp package in Ubuntu: New Status in linux-oracle package in Ubuntu: Fix Released Status in linux-oracle-5.4 package in Ubuntu: Invalid Status in linux-oracle-5.8 package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: Invalid Status in linux-oracle-5.4 source package in Bionic: Fix Released Status in linux-oracle-5.8 source package in Bionic: New Status in linux-gcp source package in Focal: New Status in linux-oracle source package in Focal: Fix Released Status in linux-oracle-5.4 source package in Focal: Invalid Status in linux-oracle-5.8 source package in Focal: Fix Released Status in linux-oracle source package in Groovy: Fix Released Status in linux-oracle-5.4 source package in Groovy: Invalid Status in linux-oracle-5.8 source package in Groovy: Fix Committed Status in linux-oracle source package in Hirsute: Fix Released Status in linux-oracle-5.4 source package in Hirsute: Invalid Status in linux-oracle-5.8 source package in Hirsute: Invalid Status in linux-oracle source package in Impish: Fix Released Status in linux-oracle-5.4 source package in Impish: Invalid Status in linux-oracle-5.8 source package in Impish: Invalid Bug description: See https://canonical.lightning.force.com/lightning/r/Case/5003z2BzFG4AAN/view for more info [Impact] No support for arm64 currently [Fix] Add arm64 support, including hardware support patches [Test] Confirm that it boots on desired arm64 hardware, as well as VMs [Regression Potential] This was never working on arm64 so there should be no risk of regression. The requested changes included some refactorings of early memory initialization code (all arches) so this presents a small risk. The changes were tested on arm64 as well amd64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1925421/+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 1912052] Re: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 21.04 (not even wired, cable headset)
Bug status updated from the other bugs in comment #28. ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Hirsute) Status: Fix Committed => Won't Fix ** Changed in: linux (Ubuntu Impish) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912052 Title: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 21.04 (not even wired, cable headset) Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in linux source package in Focal: Fix Released Status in linux source package in Hirsute: Won't Fix Status in linux source package in Impish: Fix Released Status in linux source package in Jammy: Fix Released Bug description: Recently, external microphone has stopped working while using classic wired audio combo jack headset. Basics: 1) Headset's microphone works fine both in MS Windows on the same machine and on older Xubuntu on another machine. 2) Internal laptop mic works normally. 3) Yes, I have mic unmuted in settings. I've followed whole step1 from this troubleshoot guide: https://help.ubuntu.com/community/SoundTroubleshootingProcedure Did not help. There are more information with screenshots here: https://askubuntu.com/questions/1305942/external-headset-microphone- not-working-on-ubuntu-20-10-not-even-wired-cable-h: ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crysman2301 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 16 13:31:13 2021 InstallationDate: Installed on 2020-06-19 (210 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-12-08 (38 days ago) dmi.bios.date: 07/17/2020 dmi.bios.release: 1.5 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.05 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:br1.5:efr1.2:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1912052/+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 1966066] Re: audio from external sound card is distorted
This is the first post I ever make on a bug on a linux based OS.
I'm using a ten year old Toshiba Satellite L855 that I just bought RAM
for, my surprise when I plug in a Mackie ProFx16v2 and there's this
horrible pop coming from the headphones. Long story short, after losing
a day, at 2300 I'm using 5.13.0-19 generic kernel and there are no more
pops. For some reason the 5.13.0-37 doesn't even boot.
I hope it somehow adds up to the conversation.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1966066
Title:
audio from external sound card is distorted
Status in linux package in Ubuntu:
Fix Committed
Status in linux-signed-hwe-5.13 package in Ubuntu:
Invalid
Status in linux source package in Impish:
Fix Committed
Status in linux-signed-hwe-5.13 source package in Impish:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux-signed-hwe-5.13 source package in Jammy:
Invalid
Bug description:
[Impact]
Commit d215f63d49da ("ALSA: usb-audio: Check available frames for the
next packet size") landed in 5.13.0-35 introduced regression to USB
audio device.
It's because this patch introduced the available frame size check, but
the conversion forgot to initialize the temporary variable properly.
A workaround is to modify /etc/pulse/daemon.conf, set the
default-sample-rate to 48000, uncomment it by removing the semicolon
at the beginning of the line. And restart pulseaudio with:
systemctl --user restart pulseaudio.service
[Fix]
* 23939115 ALSA: usb-audio: Fix packet size calculation regression
This patch can be cherry-picked into Impish kernel, and it's already in
the master-next branch of Jammy tree.
[Test]
Test kernels built with 5.13.0-37 + this patch, can be found in:
* Focal-5.13 -
https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/focal/
* Impish-5.13 -
https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/impish/
Both kernels were tested by affected users and they're working as
expected.
[Where problems could occur]
If this patch is incorrect, it might affect USB audio devices.
[Original Bug Report]
The sound card is a Focusrite Scarlett 2i2.
The sound is distorted everywhere.
Sound via HDMI works.
Seen others having the same problem:
(Edit because of previously wrong link here)
https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card
ubuntu release: Ubuntu 20.04.4 LTS
package name involved in bug: linux-image-5.13.0-37-generic
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 23 12:56:02 2022
InstallationDate: Installed on 2020-12-18 (459 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: linux-signed-hwe-5.13
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966066/+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 1969407] Re: DMCUB hangs if a PSR unsupported set version command is sent on AMD Rembrandt platform
SRU: https://lists.ubuntu.com/archives/kernel- team/2022-April/129563.html (unstable, oem-5.17) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1969407 Title: DMCUB hangs if a PSR unsupported set version command is sent on AMD Rembrandt platform Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: Observed the boot issue on AMD Rembrandt based platforms with the upstream 5.17 kernel https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/tag/?h=v5.17. The symptom are below: 1. The boot process takes more longer than what we usually do 2. After the boot is completed, the touchpad/mouse is almost frozen Upstream commit https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1210b17dd4ece454d68a9283f391e3b036aeb010 fixed this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1969407/+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 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
Missing the GAMMA_LUT property on this OLED panel still feels like an
i915 kernel bug to me. Not something Intel would intentionally omit.
Please try the latest DRM kernel here:
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/
The upstream mutter bug report also mentioned that a newer kernel solved
it for them.
--
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/1967274
Title:
Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post
KMS update: CRTC property (GAMMA_LUT) not found]
Status in Mutter:
Unknown
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Triaged
Status in mutter package in Ubuntu:
In Progress
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+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 1969407] [NEW] DMCUB hangs if a PSR unsupported set version command is sent on AMD Rembrandt platform
Public bug reported: Observed the boot issue on AMD Rembrandt based platforms with the upstream 5.17 kernel https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/tag/?h=v5.17. The symptom are below: 1. The boot process takes more longer than what we usually do 2. After the boot is completed, the touchpad/mouse is almost frozen Upstream commit https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1210b17dd4ece454d68a9283f391e3b036aeb010 fixed this issue. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: High Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Affects: linux-oem-5.17 (Ubuntu) Importance: High Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: High Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Affects: linux-oem-5.17 (Ubuntu Jammy) Importance: High Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Tags: amd oem-priority originate-from-1966411 ** Description changed: Observed the boot issue on AMD Rembrandt based platforms with the upstream 5.17 kernel https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/tag/?h=v5.17. The symptom are below: 1. The boot process takes more longer than what we usually do 2. After the boot is completed, the touchpad/mouse is almost frozen + + Upstream commit + https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1210b17dd4ece454d68a9283f391e3b036aeb010 + fixed this issue. ** Tags added: amd oem-priority originate-from-1966411 ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- 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/1969407 Title: DMCUB hangs if a PSR unsupported set version command is sent on AMD Rembrandt platform Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: Observed the boot issue on AMD Rembrandt based platforms with the upstream 5.17 kernel https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/tag/?h=v5.17. The symptom are below: 1. The boot process takes more longer than what we usually do 2. After the boot is completed, the touchpad/mouse is almost frozen Upstream commit https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1210b17dd4ece454d68a9283f391e3b036aeb010 fixed this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1969407/+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 1969275] Re: end kernel panic not syncing attempted to kill init exit code 0x00000009 and the pc dont turn off
ok this is the screen after reboot or shut down ** Attachment added: "IMG20220419022725.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969275/+attachment/5581336/+files/IMG20220419022725.jpg -- 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/1969275 Title: end kernel panic not syncing attempted to kill init exit code 0x0009 and the pc dont turn off Status in linux package in Ubuntu: Incomplete Bug description: the pc can not be turn off untill i will force hiw to push the button for severla second and if not the screen freeze on this bug end kernel panic not syncing attempted to kill init exit code 0x0009 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-107-generic 5.4.0-107.121~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 16 16:32:04 2022 InstallationDate: Installed on 2021-09-23 (205 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969275/+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 1969275] Re: end kernel panic not syncing attempted to kill init exit code 0x00000009 and the pc dont turn off
ok this is the screen after reboot or shut down ** Attachment added: "IMG20220416160255.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969275/+attachment/5581335/+files/IMG20220416160255.jpg -- 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/1969275 Title: end kernel panic not syncing attempted to kill init exit code 0x0009 and the pc dont turn off Status in linux package in Ubuntu: Incomplete Bug description: the pc can not be turn off untill i will force hiw to push the button for severla second and if not the screen freeze on this bug end kernel panic not syncing attempted to kill init exit code 0x0009 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-107-generic 5.4.0-107.121~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 16 16:32:04 2022 InstallationDate: Installed on 2021-09-23 (205 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969275/+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 1924298] Re: accept returns duplicate endpoints under load
I am impacted by this bug as well, as reported in my Tomcat 9-based
application logs:
[2022-04-18 21:45:44.764] ERROR [http-nio-9083-Acceptor ]
org.apache.tomcat.util.net.Acceptor Socket accept failed
java.io.IOException: Duplicate accept detected. This is a known OS bug.
Please consider reporting that you are affected:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924298
This app runs on AWS ECS Fargate v1.4 in a Ubuntu 18.04 amd64 based
image using the BellSoft Liberica JRE 11. I get this log messages a
couple times a day on average.
The application continues running, seemingly without any problems. The
ERROR log trigger alerts which we will adapt to ignore, but I wanted to
add my experience with this issue here.
--
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/1924298
Title:
accept returns duplicate endpoints under load
Status in Linux:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
When accepting client connections under load, duplicate endpoints may
be returned. These endpoints will have different (usually sequential)
file descriptors but will refer to the same connection (same server
IP, same server port, same client IP, same client port). Both copies
of the endpoint appear to be functional.
Reproduction requires:
- compilation of the attached server.c program
- wrk (https://github.com/wg/wrk) to generate load
The steps to reproduce are:
- run 'server' application in one console window
- run 'for i in {1..50}; do /opt/wrk/wrk -t 2 -c 1000 -d 5s --latency
--timeout 1s http://localhost:/post; done' in a second console window
- run the same command in a third window to generate concurrent load
You may need to run additional instance of the wrk command in multiple
windows to trigger the issue.
When the problem occurs the server executable will exit and print some
debugging info. e.g.:
accerror = 1950892, counter = 10683, port = 59892, clientfd = 233, lastClient
= 232
This indicates that the sockets with file descriptors 233 and 232 are
duplicates.
The issue has been reproduced on fully patched versions of Ubuntu
20.04 and 18.04. Other versions have not been tested.
This issue was originally observed in Java and was reported against the
Spring Framework:
https://github.com/spring-projects/spring-framework/issues/26434
Investigation from the Spring team and the Apache Tomcat team identified that
it appeared to be a JDK issue:
https://bugs.openjdk.java.net/browse/JDK-8263243
Further research from the JDK team determined that the issue was at
the OS level. Hence this report.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-71-generic 5.4.0-71.79
ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101
Uname: Linux 5.4.0-71-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 15 12:52:53 2021
HibernationDevice: RESUME=UUID=f5a46e09-d99b-4475-8ab6-2cd70da8418d
InstallationDate: Installed on 2017-02-02 (1532 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
IwConfig:
lono wireless extensions.
docker0 no wireless extensions.
eno1 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. Default string
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-71-generic
root=/dev/mapper/ubuntu--vg-root ro text
RelatedPackageVersions:
linux-restricted-modules-5.4.0-71-generic N/A
linux-backports-modules-5.4.0-71-generic N/A
linux-firmware1.187.10
RfKill:
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-09-07 (219 days ago)
dmi.bios.date: 06/13/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F22
dmi.board.asset.tag: Default string
dmi.board.name: X99-SLI-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF22:bd06/13/2016:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: Default string
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/linux/+bug/1924298/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe :
[Kernel-packages] [Bug 1967727] Re: Random screen blanks with "CPU pipe B FIFO underrun" error
i add kernel param 'intel_iommu=on,igfx_off' three days ago, until now everything is fine -- 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/1967727 Title: Random screen blanks with "CPU pipe B FIFO underrun" error Status in linux package in Ubuntu: Confirmed Bug description: On a clean 22.04 install, the screen randomly blanks once in a while for a couple of seconds, then comes back. I see the following message in dmesg when it happens: [ 6614.338572] i915 :00:02.0: [drm] *ERROR* CPU pipe B FIFO underrun ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Mon Apr 4 10:16:27 2022 InstallationDate: Installed on 2022-04-03 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: LENOVO 20F6CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967727/+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 1969275] Re: end kernel panic not syncing attempted to kill init exit code 0x00000009 and the pc dont turn off
Thanks for the bug report. Can you please upload a picture of the screen during freeze? We need more information from the 'kernel panic' message. ** Package changed: linux-signed-hwe-5.4 (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1969275 Title: end kernel panic not syncing attempted to kill init exit code 0x0009 and the pc dont turn off Status in linux package in Ubuntu: Incomplete Bug description: the pc can not be turn off untill i will force hiw to push the button for severla second and if not the screen freeze on this bug end kernel panic not syncing attempted to kill init exit code 0x0009 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-107-generic 5.4.0-107.121~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 16 16:32:04 2022 InstallationDate: Installed on 2021-09-23 (205 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969275/+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 1969383] [NEW] package zfs-dkms 2.0.6-1ubuntu2.1 failed to install/upgrade: »installiertes zfs-dkms-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 10 zurü
Public bug reported: it happened during upgrade from 21.04 to 21.10 ProblemType: Package DistroRelease: Ubuntu 21.10 Package: zfs-dkms 2.0.6-1ubuntu2.1 Uname: Linux 5.16.17-surface x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Apr 18 22:11:50 2022 ErrorMessage: »installiertes zfs-dkms-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 10 zurück InstallationDate: Installed on 2022-01-28 (80 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: zfs-linux Title: package zfs-dkms 2.0.6-1ubuntu2.1 failed to install/upgrade: »installiertes zfs-dkms-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 10 zurück UpgradeStatus: Upgraded to impish on 2022-04-18 (0 days ago) ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1969383 Title: package zfs-dkms 2.0.6-1ubuntu2.1 failed to install/upgrade: »installiertes zfs-dkms-Skript des Paketes post- installation«-Unterprozess gab den Fehlerwert 10 zurück Status in zfs-linux package in Ubuntu: New Bug description: it happened during upgrade from 21.04 to 21.10 ProblemType: Package DistroRelease: Ubuntu 21.10 Package: zfs-dkms 2.0.6-1ubuntu2.1 Uname: Linux 5.16.17-surface x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Apr 18 22:11:50 2022 ErrorMessage: »installiertes zfs-dkms-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 10 zurück InstallationDate: Installed on 2022-01-28 (80 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: zfs-linux Title: package zfs-dkms 2.0.6-1ubuntu2.1 failed to install/upgrade: »installiertes zfs-dkms-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 10 zurück UpgradeStatus: Upgraded to impish on 2022-04-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1969383/+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 1969247] Re: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy
** Changed in: zfs Status: Unknown => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1969247 Title: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy Status in Native ZFS for Linux: New Status in mysql-8.0 package in Ubuntu: Invalid Status in zfs-linux package in Ubuntu: Confirmed Bug description: [Summary] When running Jammy on zfs or LXD with a zfs pool on a Jammy host, fallocate creates a zero-sized file. The issue was originally found when installing mysql on LXD, where fallocate would create a zero-sized ib_logfile1 file. The original information in this bug is based on that. [Steps to Reproduce] touch foo.img fallocate -z -l 10M foo.img ls -la foo.img On a non-zfs Jammy system this will show something like: -rw-r--r-- 1 root root 10M ... while on zfs it will show: -rw-rw-r-- 1 root root 0 ... [Original Description] I came across this error when testing various mysql setups in an LXD container and managed to reproduce it consistently. I'm unable to reproduce on Ubuntu desktop or server though since the prerequisites are probably handled properly there. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 15 21:31:09 2022 Dmesg: ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 KernLog: Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many levels of symbolic links: '/etc/mysql/my.cnf' MySQLVarLibDirListing: ['ibdata1', 'ib_logfile0', '#innodb_temp', 'debian-5.7.flag', '#ib_16384_0.dblwr', 'client-cert.pem', 'undo_001', 'server-cert.pem', 'mysql.ibd', '#ib_16384_1.dblwr', 'client-key.pem', 'ca-key.pem', 'sys', 'private_key.pem', 'mysql', 'undo_002', 'binlog.index', 'performance_schema', 'ib_buffer_pool', 'auto.cnf', 'ib_logfile1', 'public_key.pem', 'ca.pem', 'server-key.pem'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=93666562-b5e4-4fb4-ba8c-7b42a3e6bf61 ro quiet splash mem_sleep_default=deep vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1969247/+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 1968519] Re: [Lenovo Ubuntu 22.04 Bug]The Physical VGA displayer shows no signal (black screen) when install Ubuntu 22.04
I have seen this bug too. System: Dell R740xd I have tried booting using both EFI and legacy BIOS. I have tried using the latest 22.04 server beta and daily release. -- 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/1968519 Title: [Lenovo Ubuntu 22.04 Bug]The Physical VGA displayer shows no signal (black screen) when install Ubuntu 22.04 Status in linux package in Ubuntu: Confirmed Bug description: Description: When we install Ubuntu 22.04, the physical VGA displayer show black screen. It can only show rarely boot logs just for few seconds after kebyboard Enter key be pressed to install Ubuntu OS, and then the physical VGA displayer keeps black screen, but the XCC remote KVM monitor can show the boot log and the GUI interface. Produce Steps: 1. Connect a physical VGA displayer. 2. Fresh install Ubuntu22.04 on a server that integrated Matrox MGA G200-family. 3. When the install menu comes out, press keyboard Enter key, the physical VGA displayer just get the signal for few seconds and then the monitor go to black screen. Configuration: Systems：Lenovo SR590, SR650, SR630 with magag200 as GFX OS:jammy-live-server20220405-amd64.iso CPU:Intel(R) Xeon(R) Bronze 3104 CPU @ 1.70GHz UEFI:3.30 (Build ID: IVE178D) XCC:1.30 (Build ID: PDL114N) HDD:1.00TB 7.2K 6Gbps SATA 3.5" HD Actual results: The VGA display keep the black screen, during Ubuntu 22.04 installation. Expected results: The VGA display is OK when install the Ubuntu 22.04 in a server that integrated Matrox MGA G200-family video processor Additional info: 1. The issue can be reproduced 100% in the server that integrated Matrox MGA G200-family platforms. 2. Both UEFI mode and legacy mode are failed. 3. After we finish installing Ubuntu OS through XCC remote KVM monitor, and reboot the system, the physical VGA displayer still show nothing after a few seconds. 4. We did more tests, modified the cmdline of the kernel, add "nomodeset", the VGA displayer display well. 5. This issue could be found on both Intel and AMD platforms , which have onboard video chip as mgag200, also called pilot 4. 6. Upstream kernel patch https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.18-rc1=147696720eca12ae48d020726208b9a61cdd80bc (drm/mgag200: Select clock in PLL update functions) probalby resovle the issue on BIOS legacy mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gcp-5.4/5.4.0.1072.56)
All autopkgtests for the newly accepted linux-meta-gcp-5.4 (5.4.0.1072.56) for bionic have finished running. The following regressions have been reported in tests triggered by the package: r8168/8.045.08-2ubuntu1 (amd64) dpdk/17.11.10-0ubuntu0.1 (amd64) snapd/2.54.3+18.04.2ubuntu0.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-gcp-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1969247] Re: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy
** Summary changed: - fallocate produces zero-size files on zfs in Jammy + fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy ** Description changed: - I came across this error when testing various mysql setups in an LXD - container and managed to reproduce it consistently. I'm unable to - reproduce on Ubuntu desktop or server though since the prerequisites are - probably handled properly there. + [Summary] + + When running Jammy on zfs or LXD with a zfs pool on a Jammy host, + fallocate creates a zero-sized file. + + The issue was originally found when installing mysql on LXD, where + fallocate would create a zero-sized ib_logfile1 file. The original + information in this bug is based on that. + + [Steps to Reproduce] + + touch foo.img + fallocate -z -l 10M foo.img + ls -la foo.img + + On a non-zfs Jammy system this will show something like: + -rw-r--r-- 1 root root 10M ... + + while on zfs it will show: + -rw-rw-r-- 1 root root 0 ... + + [Original Description] + I came across this error when testing various mysql setups in an LXD container and managed to reproduce it consistently. I'm unable to reproduce on Ubuntu desktop or server though since the prerequisites are probably handled properly there. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 15 21:31:09 2022 Dmesg: ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 KernLog: Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many levels of symbolic links: '/etc/mysql/my.cnf' MySQLVarLibDirListing: ['ibdata1', 'ib_logfile0', '#innodb_temp', 'debian-5.7.flag', '#ib_16384_0.dblwr', 'client-cert.pem', 'undo_001', 'server-cert.pem', 'mysql.ibd', '#ib_16384_1.dblwr', 'client-key.pem', 'ca-key.pem', 'sys', 'private_key.pem', 'mysql', 'undo_002', 'binlog.index', 'performance_schema', 'ib_buffer_pool', 'auto.cnf', 'ib_logfile1', 'public_key.pem', 'ca.pem', 'server-key.pem'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=93666562-b5e4-4fb4-ba8c-7b42a3e6bf61 ro quiet splash mem_sleep_default=deep vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Bug watch added: github.com/openzfs/zfs/issues #13329 https://github.com/openzfs/zfs/issues/13329 ** Also affects: zfs via https://github.com/openzfs/zfs/issues/13329 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1969247 Title: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy Status in Native ZFS for Linux: Unknown Status in mysql-8.0 package in Ubuntu: Invalid Status in zfs-linux package in Ubuntu: Confirmed Bug description: [Summary] When running Jammy on zfs or LXD with a zfs pool on a Jammy host, fallocate creates a zero-sized file. The issue was originally found when installing mysql on LXD, where fallocate would create a zero-sized ib_logfile1 file. The original information in this bug is based on that. [Steps to Reproduce] touch foo.img fallocate -z -l 10M foo.img ls -la foo.img On a non-zfs Jammy system this will show something like: -rw-r--r-- 1 root root 10M ... while on zfs it will show: -rw-rw-r-- 1 root root 0 ... [Original Description] I came across this error when testing various mysql setups in an LXD container and managed to reproduce it consistently. I'm unable to reproduce on Ubuntu desktop or server though since the prerequisites are probably handled properly there. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 15 21:31:09 2022 Dmesg: ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 KernLog: Logs.var.log.daemon.log:
[Kernel-packages] [Bug 1969247] Re: mysql-server install crashes in LXD container on Jammy host
mysql's install also fails with the same error when using a native Jammy Desktop with zfs. I can also confirm fallocate fails on this system as it produces zero-size files on its own. I'm going to mark mysql invalid here and set this up as a kernel bug for zfs ** Changed in: mysql-8.0 (Ubuntu) Status: Confirmed => Invalid ** Changed in: mysql-8.0 (Ubuntu) Assignee: Lena Voytek (lvoytek) => (unassigned) ** Changed in: zfs-linux (Ubuntu) Status: New => Confirmed ** Summary changed: - mysql-server install crashes in LXD container on Jammy host + fallocate produces zero-size files on zfs in Jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1969247 Title: fallocate produces zero-size files on zfs in Jammy Status in mysql-8.0 package in Ubuntu: Invalid Status in zfs-linux package in Ubuntu: Confirmed Bug description: I came across this error when testing various mysql setups in an LXD container and managed to reproduce it consistently. I'm unable to reproduce on Ubuntu desktop or server though since the prerequisites are probably handled properly there. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 15 21:31:09 2022 Dmesg: ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 KernLog: Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many levels of symbolic links: '/etc/mysql/my.cnf' MySQLVarLibDirListing: ['ibdata1', 'ib_logfile0', '#innodb_temp', 'debian-5.7.flag', '#ib_16384_0.dblwr', 'client-cert.pem', 'undo_001', 'server-cert.pem', 'mysql.ibd', '#ib_16384_1.dblwr', 'client-key.pem', 'ca-key.pem', 'sys', 'private_key.pem', 'mysql', 'undo_002', 'binlog.index', 'performance_schema', 'ib_buffer_pool', 'auto.cnf', 'ib_logfile1', 'public_key.pem', 'ca.pem', 'server-key.pem'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=93666562-b5e4-4fb4-ba8c-7b42a3e6bf61 ro quiet splash mem_sleep_default=deep vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1969247/+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 1969374] [NEW] linux-bluefield: Fix build failure in mlxbf_gige
Public bug reported: SRU Justification [Impact] The latest PR to fix a certification issue has introduced a build failure. Specifically: net: mellanox: mlxbf_gige: Replace non-standard interrupt handling A build of the kernel fails with the following error: drivers/net/ethernet/mellanox/mlxbf_gige/mlxbf_gige_main.c:380:12: error: implicit declaration of function 'acpi_dev_gpio_irq_get_by'; did you mean 'acpi_dev_gpio_irq_get'? [-Werror=implicit-function-declaration] [Fix] Cherry-picking: 809390219fb9c gpiolib: acpi: Allow to find GpioInt() resource by name and index The above commit reworks GpioInt() to allow finding the resource via name and index while preserving previous functionality. [Test Case] Beyond ensuring build still works, no testing of drivers using the reworked acpi_dev_gpio_irq_get function will be done, but it should still work as previously designed when NULL is passed for name. [Where problems could occur] Chance of regression should be very low with this change. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1969374 Title: linux-bluefield: Fix build failure in mlxbf_gige Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification [Impact] The latest PR to fix a certification issue has introduced a build failure. Specifically: net: mellanox: mlxbf_gige: Replace non-standard interrupt handling A build of the kernel fails with the following error: drivers/net/ethernet/mellanox/mlxbf_gige/mlxbf_gige_main.c:380:12: error: implicit declaration of function 'acpi_dev_gpio_irq_get_by'; did you mean 'acpi_dev_gpio_irq_get'? [-Werror=implicit-function-declaration] [Fix] Cherry-picking: 809390219fb9c gpiolib: acpi: Allow to find GpioInt() resource by name and index The above commit reworks GpioInt() to allow finding the resource via name and index while preserving previous functionality. [Test Case] Beyond ensuring build still works, no testing of drivers using the reworked acpi_dev_gpio_irq_get function will be done, but it should still work as previously designed when NULL is passed for name. [Where problems could occur] Chance of regression should be very low with this change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1969374/+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 1969375] [NEW] systemd-cryptenroll does not support TPM2 devices
Public bug reported: systemd-cryptenroll can make use of tpm2 modules to bind against secure boot pcrs and enable auto unlocking of luks devices. Following the instructions here: https://wiki.archlinux.org/title/Trusted_Platform_Module#systemd-cryptenroll the following commands fail on ubuntu jammy (5.15.0-25-generic) root@testbox:~# systemd-cryptenroll --tpm2-device=list TPM2 not supported on this build. root@testbox:~# systemd-cryptenroll --tpm2-device=auto --tpm2-pcrs=7 /dev/sda3 Please enter current passphrase for disk /dev/sda3: *** root@testbox:~# echo $? 1 It appears that this issue has been resolved in the debian build for systemd here: https://salsa.debian.org/systemd- team/systemd/-/commit/6b5e99f1d7f63c0c83007de9f98f7745f4a564f8 Can we get the same modifications to the Jammy systemd build? ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: luks systemd tpm2 ** Package changed: linux (Ubuntu) => systemd (Ubuntu) ** Description changed: systemd-cryptenroll can make use of tpm2 modules to bind against secure - boot pcrs an enable auto unlocking of luks devices. + boot pcrs and enable auto unlocking of luks devices. - Following the instructions here: + Following the instructions here: https://wiki.archlinux.org/title/Trusted_Platform_Module#systemd-cryptenroll the following commands fail on ubuntu jammy (5.15.0-25-generic) root@testbox:~# systemd-cryptenroll --tpm2-device=list TPM2 not supported on this build. root@testbox:~# systemd-cryptenroll --tpm2-device=auto --tpm2-pcrs=7 /dev/sda3 Please enter current passphrase for disk /dev/sda3: *** root@testbox:~# echo $? 1 It appears that this issue has been resolved in the debian build for systemd here: https://salsa.debian.org/systemd- team/systemd/-/commit/6b5e99f1d7f63c0c83007de9f98f7745f4a564f8 Can we get the same modifications to the Jammy systemd build? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1969375 Title: systemd-cryptenroll does not support TPM2 devices Status in systemd package in Ubuntu: New Bug description: systemd-cryptenroll can make use of tpm2 modules to bind against secure boot pcrs and enable auto unlocking of luks devices. Following the instructions here: https://wiki.archlinux.org/title/Trusted_Platform_Module#systemd-cryptenroll the following commands fail on ubuntu jammy (5.15.0-25-generic) root@testbox:~# systemd-cryptenroll --tpm2-device=list TPM2 not supported on this build. root@testbox:~# systemd-cryptenroll --tpm2-device=auto --tpm2-pcrs=7 /dev/sda3 Please enter current passphrase for disk /dev/sda3: *** root@testbox:~# echo $? 1 It appears that this issue has been resolved in the debian build for systemd here: https://salsa.debian.org/systemd- team/systemd/-/commit/6b5e99f1d7f63c0c83007de9f98f7745f4a564f8 Can we get the same modifications to the Jammy systemd build? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1969375/+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 1969247] Re: mysql-server install crashes in LXD container on Jammy host
** Also affects: zfs-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1969247 Title: mysql-server install crashes in LXD container on Jammy host Status in mysql-8.0 package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: New Bug description: I came across this error when testing various mysql setups in an LXD container and managed to reproduce it consistently. I'm unable to reproduce on Ubuntu desktop or server though since the prerequisites are probably handled properly there. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 15 21:31:09 2022 Dmesg: ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 KernLog: Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many levels of symbolic links: '/etc/mysql/my.cnf' MySQLVarLibDirListing: ['ibdata1', 'ib_logfile0', '#innodb_temp', 'debian-5.7.flag', '#ib_16384_0.dblwr', 'client-cert.pem', 'undo_001', 'server-cert.pem', 'mysql.ibd', '#ib_16384_1.dblwr', 'client-key.pem', 'ca-key.pem', 'sys', 'private_key.pem', 'mysql', 'undo_002', 'binlog.index', 'performance_schema', 'ib_buffer_pool', 'auto.cnf', 'ib_logfile1', 'public_key.pem', 'ca.pem', 'server-key.pem'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=93666562-b5e4-4fb4-ba8c-7b42a3e6bf61 ro quiet splash mem_sleep_default=deep vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1969247/+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 1962315] Re: xenial upgrade of lockdown patches dropped ioport denial
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Fix Released ** Information type changed from Private Security to Public Security -- 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/1962315 Title: xenial upgrade of lockdown patches dropped ioport denial Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Released Bug description: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/xenial/commit/?id=cc223b88b8e59fca362b426b0cccfe580fd8a68e Has been shipped from Ubuntu-4.4.0-18.34 until Ubuntu-4.4.0-186.216 As part of an upgrade to newer edition of lockdown patches it was reverted https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/xenial/commit/?id=009ff27aac7cf36458a035122ecb9cfd4e4d073a But equivalent functionality does not appear to have been applied. This was done as part of lockdown patches updates - see BugLink: https://bugs.launchpad.net/bugs/1884159 https://lists.ubuntu.com/archives/kernel-team/2020-June/111301.html Now audit is need to be done w.r.t. those patch series across all the kernels they were applied to ensure nothing else has regressed, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962315/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gcp-5.4/5.4.0.1071.55)
All autopkgtests for the newly accepted linux-meta-gcp-5.4 (5.4.0.1071.55) for bionic have finished running. The following regressions have been reported in tests triggered by the package: r8168/8.045.08-2ubuntu1 (amd64) dpdk/17.11.10-0ubuntu0.1 (amd64) snapd/2.54.3+18.04.2ubuntu0.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-gcp-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gcp-5.4/5.4.0.1071.55)
All autopkgtests for the newly accepted linux-meta-gcp-5.4 (5.4.0.1071.55) for bionic have finished running. The following regressions have been reported in tests triggered by the package: dpdk/17.11.10-0ubuntu0.1 (amd64) snapd/2.54.3+18.04.2ubuntu0.2 (amd64) r8168/8.045.08-2ubuntu1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-gcp-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gcp-5.4/5.4.0.1071.55)
All autopkgtests for the newly accepted linux-meta-gcp-5.4 (5.4.0.1071.55) for bionic have finished running. The following regressions have been reported in tests triggered by the package: snapd/2.54.3+18.04.2ubuntu0.2 (amd64) dpdk/17.11.10-0ubuntu0.1 (amd64) r8168/8.045.08-2ubuntu1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-gcp-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934620] Re: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS
Hi Sujith, have you been able to get the nvidia bug report log for them to help debug this 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/1934620 Title: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS Status in dellserver: Won't Fix Status in linux package in Ubuntu: Incomplete Bug description: Installing NVidia A100-80GB GPUs in R750XA fails to initialize BAR memory space for GPUs. Multiple error messages in kernel.log file. Summary: * Dell prefers to set SRIOV to disabled in bios globally * This bug does not occur IF: SRIOV is enabled in BIOS OR "pci=realloc=off" is passed to the kernel at boot time * This bug only affects systems with NVIDIA A100-80GB GPUs, it does not affect systems with NVIDIA A100-40GB GPUs To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934620/+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 1803881] Re: thermal thermal_zone4: failed to read out thermal zone (-61)
I have the same problem: thermal thermal_zone6: failed to read out
thermal zone (-61)
lenovo Thinkpad X1 Carbon 9th Gen
Ubuntu 20.04
Kernel 5.14.0-1032-oem
Firmware 1.187.29
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1803881
Title:
thermal thermal_zone4: failed to read out thermal zone (-61)
Status in linux package in Ubuntu:
Incomplete
Status in thermald package in Ubuntu:
Confirmed
Bug description:
Thermald can't read zone4. It's making my fan go crazy, this issue
seems to be a bit more controlled in 18.10.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
sudo apt-cache policy thermald
thermald:
Installed: 1.7.0-5ubuntu1
Candidate: 1.7.0-5ubuntu1
Version table:
*** 1.7.0-5ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
cat /sys/class/thermal/thermal_zone4/type
iwlwifi
find /sys/class/thermal/thermal_zone4/ -type f -print -exec cat {} \;
/sys/class/thermal/thermal_zone4/uevent
/sys/class/thermal/thermal_zone4/trip_point_5_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_3_type
passive
/sys/class/thermal/thermal_zone4/trip_point_4_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_2_type
passive
/sys/class/thermal/thermal_zone4/power/runtime_active_time
0
/sys/class/thermal/thermal_zone4/power/runtime_active_kids
0
/sys/class/thermal/thermal_zone4/power/runtime_usage
0
/sys/class/thermal/thermal_zone4/power/runtime_status
unsupported
/sys/class/thermal/thermal_zone4/power/autosuspend_delay_ms
cat: /sys/class/thermal/thermal_zone4/power/autosuspend_delay_ms:
Input/output error
/sys/class/thermal/thermal_zone4/power/async
disabled
/sys/class/thermal/thermal_zone4/power/runtime_suspended_time
0
/sys/class/thermal/thermal_zone4/power/runtime_enabled
disabled
/sys/class/thermal/thermal_zone4/power/control
auto
/sys/class/thermal/thermal_zone4/available_policies
power_allocator user_space bang_bang fair_share step_wise
/sys/class/thermal/thermal_zone4/policy
step_wise
/sys/class/thermal/thermal_zone4/trip_point_3_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_1_type
passive
/sys/class/thermal/thermal_zone4/k_d
cat: /sys/class/thermal/thermal_zone4/k_d: Input/output error
/sys/class/thermal/thermal_zone4/sustainable_power
cat: /sys/class/thermal/thermal_zone4/sustainable_power: Input/output error
/sys/class/thermal/thermal_zone4/type
iwlwifi
/sys/class/thermal/thermal_zone4/trip_point_7_type
passive
/sys/class/thermal/thermal_zone4/offset
cat: /sys/class/thermal/thermal_zone4/offset: Input/output error
/sys/class/thermal/thermal_zone4/slope
cat: /sys/class/thermal/thermal_zone4/slope: Input/output error
/sys/class/thermal/thermal_zone4/trip_point_2_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_0_type
passive
/sys/class/thermal/thermal_zone4/trip_point_6_type
passive
/sys/class/thermal/thermal_zone4/emul_temp
cat: /sys/class/thermal/thermal_zone4/emul_temp: Permission denied
/sys/class/thermal/thermal_zone4/k_po
cat: /sys/class/thermal/thermal_zone4/k_po: Input/output error
/sys/class/thermal/thermal_zone4/integral_cutoff
cat: /sys/class/thermal/thermal_zone4/integral_cutoff: Input/output error
/sys/class/thermal/thermal_zone4/k_i
cat: /sys/class/thermal/thermal_zone4/k_i: Input/output error
/sys/class/thermal/thermal_zone4/trip_point_1_temp
-32768000
/sys/class/thermal/thermal_zone4/k_pu
cat: /sys/class/thermal/thermal_zone4/k_pu: Input/output error
/sys/class/thermal/thermal_zone4/temp
46000
/sys/class/thermal/thermal_zone4/trip_point_7_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_5_type
passive
/sys/class/thermal/thermal_zone4/trip_point_0_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_6_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_4_type
passive
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803881/+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 1966061] Re: thinkpad_acpi: Support privacy-screen
** Tags added: patch -- 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/1966061 Title: thinkpad_acpi: Support privacy-screen Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Bug description: On 5.15.0-23-generic, the lcdshadow is not synced. $ cat /proc/acpi/ibm/lcdshadow status: 0 commands: 0, 1 And after press the Fn + D, the screen display angle changed, but the content of /proc/acpi/ibm/lcdshadow d0 not change. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966061/+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 1966061] Re: thinkpad_acpi: Support privacy-screen
** Patch removed: "5.17.0-1003.3-oem-privacy-support.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966061/+attachment/5581234/+files/5.17.0-1003.3-oem-privacy-support.patch -- 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/1966061 Title: thinkpad_acpi: Support privacy-screen Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Bug description: On 5.15.0-23-generic, the lcdshadow is not synced. $ cat /proc/acpi/ibm/lcdshadow status: 0 commands: 0, 1 And after press the Fn + D, the screen display angle changed, but the content of /proc/acpi/ibm/lcdshadow d0 not change. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966061/+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 1969326] Re: Enable hotspot feature for Realtek 8821CE
** Tags added: oem-priority originate-from-1967256 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1969326 Title: Enable hotspot feature for Realtek 8821CE Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: In Progress Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1969326/+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 1966061] Re: thinkpad_acpi: Support privacy-screen
In oem kernel, I found part of the 0004-drm-privacy-screen-add- notifier.patch and 0006-thinkpad_acpi-add-hotkey-notify.patch are missed. commit 8a12b170558aabb31cc98fda0da6a56b518cadaa Author: Hans de Goede Date: Tue Oct 5 22:23:16 2021 +0200 drm/privacy-screen: Add notifier support (v2) ommit 1b8101d51873d4644f0ff15f6eac46614542a76b Author: Hans de Goede Date: Tue Oct 5 22:23:18 2021 +0200 platform/x86: thinkpad_acpi: Add hotkey_notify_extended_hotkey() helper ** Patch added: "5.17.0-1003.3-oem-privacy-support.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966061/+attachment/5581234/+files/5.17.0-1003.3-oem-privacy-support.patch -- 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/1966061 Title: thinkpad_acpi: Support privacy-screen Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Bug description: On 5.15.0-23-generic, the lcdshadow is not synced. $ cat /proc/acpi/ibm/lcdshadow status: 0 commands: 0, 1 And after press the Fn + D, the screen display angle changed, but the content of /proc/acpi/ibm/lcdshadow d0 not change. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966061/+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 1967848] Re: FLOGI failure and port state bypassed connecting to 3PAR storage on Ubuntu 18.04.3
I tried running this command but couldn't get the response from Launchpad: #apport-collect 1967848 The authorization page: (https://launchpad.net/+authorize-token?oauth_token=r81hpQV9xltgDDw5TDtz_permission=DESKTOP_INTEGRATION) should be opening in your browser. Use your browser to authorize this program to access Launchpad on your behalf. Waiting to hear from Launchpad about your decision... ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967848 Title: FLOGI failure and port state bypassed connecting to 3PAR storage on Ubuntu 18.04.3 Status in linux package in Ubuntu: Confirmed Bug description: This bug is raised as per the suggestion by Jeff Email snapshot: -- File a bug, point me to a patch, and I'll see if I can pull it. Though we'd need more info... for are we talking the 4.15 GA kernel, or the 5.4 kernel? It would be a bit more involved If I have to pull the patch into 4 different kernels in order to get it back into 4.15 to avoid regressions. BUT it's not difficult, assuming any patches are only applied to lpfc. Once it lands in the scsi tree we can start looking, though I'd be more comfy for it to be in linux-next or mainline. I'll also need someone to fill out some info on the bug to create the SRU justification. -- There is an issue in which we are seeing login failure with Ubuntu 18.04.3, inbox driver version 12.0.0.0 but this issue is not seen with Ubuntu 20.04.2 with inbox driver 12.0.0.6. I found that upstream commit id [0a9e9687acaf6ac1198fd41f03d64f8b92e4515e] could potentially fix this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967848/+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 1966061] Re: thinkpad_acpi: Support privacy-screen
** Patch added: "0007-thinkpad_acpi-privacy-screen.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966061/+attachment/5581227/+files/0007-thinkpad_acpi-privacy-screen.patch -- 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/1966061 Title: thinkpad_acpi: Support privacy-screen Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Bug description: On 5.15.0-23-generic, the lcdshadow is not synced. $ cat /proc/acpi/ibm/lcdshadow status: 0 commands: 0, 1 And after press the Fn + D, the screen display angle changed, but the content of /proc/acpi/ibm/lcdshadow d0 not change. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966061/+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 1966061] Re: thinkpad_acpi: Support privacy-screen
All the other patches could be applied on 5.15.0-27-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1966061 Title: thinkpad_acpi: Support privacy-screen Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Bug description: On 5.15.0-23-generic, the lcdshadow is not synced. $ cat /proc/acpi/ibm/lcdshadow status: 0 commands: 0, 1 And after press the Fn + D, the screen display angle changed, but the content of /proc/acpi/ibm/lcdshadow d0 not change. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966061/+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 1966061] Re: thinkpad_acpi: Support privacy-screen
** Patch added: "0008-thinkpad_acpi-register.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966061/+attachment/5581228/+files/0008-thinkpad_acpi-register.patch -- 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/1966061 Title: thinkpad_acpi: Support privacy-screen Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Bug description: On 5.15.0-23-generic, the lcdshadow is not synced. $ cat /proc/acpi/ibm/lcdshadow status: 0 commands: 0, 1 And after press the Fn + D, the screen display angle changed, but the content of /proc/acpi/ibm/lcdshadow d0 not change. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966061/+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 1966061] Re: thinkpad_acpi: Support privacy-screen
** Patch added: "0009-drm-i915-add-intel_modeset_probe_defer.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966061/+attachment/5581229/+files/0009-drm-i915-add-intel_modeset_probe_defer.patch -- 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/1966061 Title: thinkpad_acpi: Support privacy-screen Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Bug description: On 5.15.0-23-generic, the lcdshadow is not synced. $ cat /proc/acpi/ibm/lcdshadow status: 0 commands: 0, 1 And after press the Fn + D, the screen display angle changed, but the content of /proc/acpi/ibm/lcdshadow d0 not change. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966061/+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 1966061] Re: thinkpad_acpi: Support privacy-screen
** Patch added: "0006-thinkpad_acpi-add-hotkey-notify.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966061/+attachment/5581226/+files/0006-thinkpad_acpi-add-hotkey-notify.patch -- 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/1966061 Title: thinkpad_acpi: Support privacy-screen Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Bug description: On 5.15.0-23-generic, the lcdshadow is not synced. $ cat /proc/acpi/ibm/lcdshadow status: 0 commands: 0, 1 And after press the Fn + D, the screen display angle changed, but the content of /proc/acpi/ibm/lcdshadow d0 not change. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966061/+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 1966061] Re: thinkpad_acpi: Support privacy-screen
** Patch added: "0001-drm-connector-add-support-for-privacy-screen.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966061/+attachment/5581222/+files/0001-drm-connector-add-support-for-privacy-screen.patch -- 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/1966061 Title: thinkpad_acpi: Support privacy-screen Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Bug description: On 5.15.0-23-generic, the lcdshadow is not synced. $ cat /proc/acpi/ibm/lcdshadow status: 0 commands: 0, 1 And after press the Fn + D, the screen display angle changed, but the content of /proc/acpi/ibm/lcdshadow d0 not change. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966061/+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 1966061] Re: thinkpad_acpi: Support privacy-screen
** Patch added: "0004-drm-privacy-screen-add-notifier.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966061/+attachment/5581225/+files/0004-drm-privacy-screen-add-notifier.patch -- 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/1966061 Title: thinkpad_acpi: Support privacy-screen Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Bug description: On 5.15.0-23-generic, the lcdshadow is not synced. $ cat /proc/acpi/ibm/lcdshadow status: 0 commands: 0, 1 And after press the Fn + D, the screen display angle changed, but the content of /proc/acpi/ibm/lcdshadow d0 not change. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966061/+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 1966061] Re: thinkpad_acpi: Support privacy-screen
** Patch added: "0003-drm-privacy-screen-add-x86.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966061/+attachment/5581224/+files/0003-drm-privacy-screen-add-x86.patch -- 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/1966061 Title: thinkpad_acpi: Support privacy-screen Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Bug description: On 5.15.0-23-generic, the lcdshadow is not synced. $ cat /proc/acpi/ibm/lcdshadow status: 0 commands: 0, 1 And after press the Fn + D, the screen display angle changed, but the content of /proc/acpi/ibm/lcdshadow d0 not change. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966061/+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 1966061] Re: thinkpad_acpi: Support privacy-screen
** Patch added: "0002-drm-add-privacy-screen-class.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966061/+attachment/5581223/+files/0002-drm-add-privacy-screen-class.patch -- 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/1966061 Title: thinkpad_acpi: Support privacy-screen Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Bug description: On 5.15.0-23-generic, the lcdshadow is not synced. $ cat /proc/acpi/ibm/lcdshadow status: 0 commands: 0, 1 And after press the Fn + D, the screen display angle changed, but the content of /proc/acpi/ibm/lcdshadow d0 not change. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966061/+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 1966061] Re: thinkpad_acpi: Support privacy-screen
There is one rejection for below commit, so I updated it. commit 6306d8dbfae6abbc049cb92fc7cf2acbcd983f8d Author: Hans de Goede Date: Tue Oct 5 22:23:22 2021 +0200 drm/i915: Add privacy-screen support (v3) --- drivers/gpu/drm/i915/display/intel_ddi.c +++ drivers/gpu/drm/i915/display/intel_ddi.c @@ -3113,6 +3115,7 @@ static void intel_ddi_update_pipe_dp(struct intel_atomic_state *state, intel_drrs_update(intel_dp, crtc_state); intel_backlight_update(state, encoder, crtc_state, conn_state); + drm_connector_update_privacy_screen(conn_state); } void intel_ddi_update_pipe(struct intel_atomic_state *state, ** Patch added: "0010-drm-i915-add-privacy-screen.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966061/+attachment/5581221/+files/0010-drm-i915-add-privacy-screen.patch -- 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/1966061 Title: thinkpad_acpi: Support privacy-screen Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Bug description: On 5.15.0-23-generic, the lcdshadow is not synced. $ cat /proc/acpi/ibm/lcdshadow status: 0 commands: 0, 1 And after press the Fn + D, the screen display angle changed, but the content of /proc/acpi/ibm/lcdshadow d0 not change. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966061/+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 1966061] Re: thinkpad_acpi: Support privacy-screen
There is one rejection for emerge, so I updated the patch. commit 334f74ee85dc26a50c1a2b0da82517595191f92f Author: Hans de Goede Date: Tue Oct 5 22:23:17 2021 +0200 drm/connector: Add a drm_connector privacy-screen helper functions (v2) --- drivers/gpu/drm/drm_connector.c +++ drivers/gpu/drm/drm_connector.c @@ -549,6 +555,10 @@ int drm_connector_register(struct drm_connector *connector) /* Let userspace know we have a new connector */ drm_sysfs_hotplug_event(connector->dev); + if (connector->privacy_screen) + drm_privacy_screen_register_notifier(connector->privacy_screen, + >privacy_screen_notifier); + mutex_lock(_list_lock); list_add_tail(>global_connector_list_entry, _list); mutex_unlock(_list_lock); ** Patch added: "0005-drm-connector-add-privacy-screen.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966061/+attachment/5581220/+files/0005-drm-connector-add-privacy-screen.patch -- 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/1966061 Title: thinkpad_acpi: Support privacy-screen Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Bug description: On 5.15.0-23-generic, the lcdshadow is not synced. $ cat /proc/acpi/ibm/lcdshadow status: 0 commands: 0, 1 And after press the Fn + D, the screen display angle changed, but the content of /proc/acpi/ibm/lcdshadow d0 not change. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966061/+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 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade
** Changed in: grub2-signed (Ubuntu Jammy) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade Status in grub2 package in Ubuntu: Fix Released Status in grub2-signed package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in subiquity package in Ubuntu: Invalid Status in grub2 source package in Jammy: Fix Released Status in grub2-signed source package in Jammy: Fix Released Status in linux source package in Jammy: Invalid Status in subiquity source package in Jammy: Invalid Bug description: = Description = Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht) Image: Jammy Beta (220330) I setup my pxe server to provision jammy beta and got the following kernel panic message after grub stage: log from console log [1.176614] integrity: Couldn't parse dbx signatures: -74^M [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)^M [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic #23-Ubuntu^M [1.387535] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26^M [1.400215] Call trace:^M [1.402649] dump_backtrace+0x0/0x1ec^M [1.406310] show_stack+0x24/0x30^M [1.409614] dump_stack_lvl+0x68/0x84^M [1.413271] dump_stack+0x18/0x34^M [1.416573] panic+0x18c/0x39c^M [1.419616] mount_block_root+0x160/0x210^M [1.423622] mount_root+0x12c/0x14c^M [1.427097] prepare_namespace+0x140/0x1a0^M [1.431182] kernel_init_freeable+0x1c8/0x214^M [1.435527] kernel_init+0x30/0x160^M [1.439006] ret_from_fork+0x10/0x20^M [1.442573] SMP: stopping secondary CPUs^M [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M [1.453404] PHYS_OFFSET: 0x8000^M [1.456879] CPU features: 0x85c1,a3302e42^M [1.461225] Memory Limit: none^M [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---^M = Steps to Reproduce = 1. Followed this guide to setup the pxe server https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240 with the jammy beta image (220330) http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso 1-1. You may use this script to perform the set-up https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo ./setup-pxe-server.sh --url http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso` 2. Boot the system via PXE 3. Select Ubuntu at Grub menu = Expected Result = The image is loaded to the system locally via PXE, and subiquity is launched = Actual Result = Console log simply shows nothing for 10 seconds and then the kernel panic shows up. = Additional Information = - If we install via the virtual CD of the server, subiquity could be launched and the installation process completes successfully. - MAAS could deploy Jammy to the Mt. Jade server as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1967562/+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 1966061] Re: thinkpad_acpi: Support privacy-screen
Tested on 5.17.0-1003-oem kernel, this privacy item could be showed. But it couldn't sync with 'Fn + D', if it is disabled, click the 'Fn + D', it changed enabled, and changed back to disabled quickly. Looks like it's a kind of bug. Tested my own build image based on 5.15.0-27-generic with upstream patches, it works perfectly. So the new issue might be related kernel side. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966061/comments/3 Tested kernel are here. https://people.canonical.com/~binli/5.15.0-27.28binli1/ -- 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/1966061 Title: thinkpad_acpi: Support privacy-screen Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Bug description: On 5.15.0-23-generic, the lcdshadow is not synced. $ cat /proc/acpi/ibm/lcdshadow status: 0 commands: 0, 1 And after press the Fn + D, the screen display angle changed, but the content of /proc/acpi/ibm/lcdshadow d0 not change. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966061/+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 1966061] Re: thinkpad_acpi: Support privacy-screen
With the 10 patches on 5.15.0-25-generic kernel, this issue is fixed. 6306d8dbfae6abbc049cb92fc7cf2acbcd983f8d Tue Oct 5 22:23:22 2021 +0200 - Hans de Goede: drm/i915: Add privacy-screen support (v3) 94b541f53db1ec6b99fc2186b084177cf6e18824 Tue Oct 5 22:23:21 2021 +0200 - Hans de Goede: drm/i915: Add intel_modeset_probe_defer() helper f809891ee51b706e1a2a42998d8766c120660796 Tue Oct 5 22:23:20 2021 +0200 - Hans de Goede: platform/x86: thinkpad_acpi: Register a privacy-screen device e8b7eb66738f559da1688ef3e4038180d7343547 Tue Oct 5 22:23:19 2021 +0200 - Hans de Goede: platform/x86: thinkpad_acpi: Get privacy-screen / lcdshadow ACPI handles only once 1b8101d51873d4644f0ff15f6eac46614542a76b Tue Oct 5 22:23:18 2021 +0200 - Hans de Goede: platform/x86: thinkpad_acpi: Add hotkey_notify_extended_hotkey() helper 334f74ee85dc26a50c1a2b0da82517595191f92f Tue Oct 5 22:23:17 2021 +0200 - Hans de Goede: drm/connector: Add a drm_connector privacy-screen helper functions (v2) 8a12b170558aabb31cc98fda0da6a56b518cadaa Tue Oct 5 22:23:16 2021 +0200 - Hans de Goede: drm/privacy-screen: Add notifier support (v2) befe5404a00b3b1547c944738df4a9229909bdc9 Tue Oct 5 22:23:15 2021 +0200 - Hans de Goede: drm/privacy-screen: Add X86 specific arch init code 0002 a1a98689301b9af0313e4c1ba44558e8b67ff76e Tue Oct 5 22:23:14 2021 +0200 - Hans de Goede: drm: Add privacy-screen class (v4) 0001 107fe904302092c683cf5462b4af3cb3cfa40998 Tue Oct 5 22:23:13 2021 +0200 - Rajat Jain: drm/connector: Add support for privacy-screen properties (v4) -- 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/1966061 Title: thinkpad_acpi: Support privacy-screen Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Bug description: On 5.15.0-23-generic, the lcdshadow is not synced. $ cat /proc/acpi/ibm/lcdshadow status: 0 commands: 0, 1 And after press the Fn + D, the screen display angle changed, but the content of /proc/acpi/ibm/lcdshadow d0 not change. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966061/+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 1966061] Re: thinkpad_acpi: Support privacy-screen
** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1966061 Title: thinkpad_acpi: Support privacy-screen Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Bug description: On 5.15.0-23-generic, the lcdshadow is not synced. $ cat /proc/acpi/ibm/lcdshadow status: 0 commands: 0, 1 And after press the Fn + D, the screen display angle changed, but the content of /proc/acpi/ibm/lcdshadow d0 not change. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966061/+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
