[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform
** Description changed: [SRU Justification] == ipu6-driver == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. [Fix] - The proposed debdiff contains accumulative fixes for a few bugs, including: - * bug 2026402: to support compiling against v6.6 unstable kernel - * bug 2012407: add CONFIG_VIDEO_V4L2_I2C to BUILD_EXCLUSIVE_CONFIG - * bug 2021740: add modaliases - * bug 2031412: support mipi camera on Intel Meteor Lake platform + Based on upstream tag + https://github.com/intel/ipu6-drivers/releases/tag/Release_20231019, and + an additional patch to enable/fix compilation of additional sensor + modules. [Test Case] This is verified on MTL Lattice and VSC platforms, as well as previous generations e.g. TGL and ADL. + + To actually verify the camera framework: + ``` + $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 + $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel + $ sudo apt install linux-oem-22.04d-exp + $ sudo apt install linux-modules-ipu6-oem-22.04d-exp + $ sudo apt install linux-modules-ivsc-oem-22.04d-exp + $ sudo apt install linux-modules-usbio-oem-22.04d-exp + $ sudo apt install gstreamer1.0-icamera v4l2-relayd + ``` + And then browse https://webcamtests.com/ for testing. [Where problems could occur] This is a new platform. We've been verifying its functions and features, and are still polishing it. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic and on, and yet the lastest stable driver was verified after Mantic was released, it's being proposed to Noble instead. == ivsc-driver == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. [Fix] 4 commits from the latest trunk branch on upstream repository https://github.com/intel/ivsc-driver. [Test Case] With all other changes in position, Intel VSC driver modules are to be loaded as a soft dependency of some selected camera sensor modules. LJCA modules should be loaded automatically on MTL platforms as well. + + To actually verify the camera framework: + ``` + $ sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 + $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel + $ sudo apt install linux-oem-22.04d-exp + $ sudo apt install linux-modules-ipu6-oem-22.04d-exp + $ sudo apt install linux-modules-ivsc-oem-22.04d-exp + $ sudo apt install linux-modules-usbio-oem-22.04d-exp + $ sudo apt install gstreamer1.0-icamera v4l2-relayd + ``` + And then browse https://webcamtests.com/ for testing. [Where problems could occur] While it changes how LJCA modules match from ACPI ID, it's also tested and verified on previous generations using IVSC, e.g. TGL, ADL. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic and on, and yet the lastest stable driver was verified after Mantic was released, it's being proposed to Noble instead. == linux/linux-oem-6.5 == [Impact] Need kernel driver fixes for int3472/iommu for Intel IPU6 platform on MTL. [Fix] Two fixes in need. One, we need IOMMU passthrough for MTL platform. The other, fix is for handshake pin support for Lattice MIPI aggregator. The Intel IPU6 camera drivers are not yet all upstreamed yet. So far Intel VSC, LJCA (the previous MIPI aggregator for ADL/RPL platforms) are in v6.6 already, and IPU6 ISYS is under upstream review. More components to come according to Intel. These two fixes are therefore for related components for not-yet fully upstreamed IPU6 as needed for out-of-tree dkms drivers. [Test Case] ``` $ sudo dmesg | grep "Passthrough IOMMU for integrated Intel IPU" $ sudo dmesg | grep int3472 # should have no "int3472-discrete INT3472:0c: GPIO type 0x12 unknown; the sensor may not work" ``` [Where problems could occur] IOMMU Passthrough as necessary to enable IPU6 on Intel platforms, and it has been patching a few generations e.g. Bug 1989041 for Raptor Lake, Bug 1958004 for TGL and ADL. As IPU is not an external facing device which is not risky. For INT3472, the proposed patch might receive further updates per current upstream reviewers' opinions. [Other Info] Nominated for linux/mantic and oem-6.5/jammy as they're for MTL. == linux-firmware == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. [Fix] Firmware blobs from upstream ipu6-camera-bins repository. [Test Case] With firmware loaded correctly, there should be firmware version printed: intel-ipu6 intel-ipu: FW version: 20220510 For camera functions, we'll need also updates in the ipu6-drivers, ivsc-drivers dkms as well. [Where problems could occur] This is a new platform. We've been verifying its functions and features, and
[Kernel-packages] [Bug 2041782] [NEW] spi: spi-cadence-quadspi: Fix ospi resume failures conflicts
Public bug reported: jammy:xilinx-zynqmp is carrying a patch subject "spi: spi-cadence- quadspi: Fix ospi resume failure" from the Xilinx tree , branch xlnx_rebase_v5.15_LTS_2022.1_update . This commit hasn't been upstreamed and completely rewrites the function cqspi_resume(). A change has landed in the v5.15.111 upstream stable release which conflicts with this Xilinx patch in such a way that we don't know how to resolve the conflicts and keep the functionality intact. We have found where Xlinx resolved the merge on the XIlinx 6.1 branch but it doesn't seem correct. In the original commit: (https://github.com/Xilinx/linux- xlnx/commit/6edac18033db445439ca57c23b8cee29a6bbdf0f) in the function cqspi_resume() , the call to cqspi_controller_enable() is removed and ZynqMP specific controls are added. Upstream fixed an issue with suspend-resume (https://github.com/torvalds/linux/commit/2087e85bb66ee3652dafe732bb9b9b896229eafc). The upstream fix replaces the cqspi_controller_enable() with some clock initializations and a call to cqspi_controller_init() which does some register writes before calling cqspi_controller_enable(). Xilinx resolve the conflict by concatenating the two commit's changes to cqspi_resume() (https://github.com/Xilinx/linux-xlnx/blob/xlnx_rebase_v6.1_LTS_2023.1_update/drivers/spi/spi-cadence-quadspi.c#L2271), the end result is that cqspi_resume() consists of ZynqMP specific controls followed by a (nested) call to cqspi_controller_enable(), the exact function call that was removed in XIlinx's original commit. This bug is to track how this merge conflict is resolved. ** Affects: linux-xilinx-zynqmp (Ubuntu) Importance: Undecided Status: New ** Affects: linux-xilinx-zynqmp (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-xilinx-zynqmp (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2041782 Title: spi: spi-cadence-quadspi: Fix ospi resume failures conflicts Status in linux-xilinx-zynqmp package in Ubuntu: New Status in linux-xilinx-zynqmp source package in Jammy: New Bug description: jammy:xilinx-zynqmp is carrying a patch subject "spi: spi-cadence- quadspi: Fix ospi resume failure" from the Xilinx tree , branch xlnx_rebase_v5.15_LTS_2022.1_update . This commit hasn't been upstreamed and completely rewrites the function cqspi_resume(). A change has landed in the v5.15.111 upstream stable release which conflicts with this Xilinx patch in such a way that we don't know how to resolve the conflicts and keep the functionality intact. We have found where Xlinx resolved the merge on the XIlinx 6.1 branch but it doesn't seem correct. In the original commit: (https://github.com/Xilinx/linux- xlnx/commit/6edac18033db445439ca57c23b8cee29a6bbdf0f) in the function cqspi_resume() , the call to cqspi_controller_enable() is removed and ZynqMP specific controls are added. Upstream fixed an issue with suspend-resume (https://github.com/torvalds/linux/commit/2087e85bb66ee3652dafe732bb9b9b896229eafc). The upstream fix replaces the cqspi_controller_enable() with some clock initializations and a call to cqspi_controller_init() which does some register writes before calling cqspi_controller_enable(). Xilinx resolve the conflict by concatenating the two commit's changes to cqspi_resume() (https://github.com/Xilinx/linux-xlnx/blob/xlnx_rebase_v6.1_LTS_2023.1_update/drivers/spi/spi-cadence-quadspi.c#L2271), the end result is that cqspi_resume() consists of ZynqMP specific controls followed by a (nested) call to cqspi_controller_enable(), the exact function call that was removed in XIlinx's original commit. This bug is to track how this merge conflict is resolved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2041782/+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 2033527] Re: it seems sha256-ssse3 was not loaded
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/2033527 Title: it seems sha256-ssse3 was not loaded Status in linux package in Ubuntu: Expired Bug description: juliank: it seems sha256-ssse3 was not loaded seems like potentially sha56-ssse3 and sha1-ssse3 are either not built-in, or are missing aliases to cause them to be loaded on boot on compatible hardware. and probably they should just be built in anyway. whereas sha512-ssse3 does get autoloaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033527/+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 2031093] Re: libgnutls report "trap invalid opcode" when trying to install packages over https
This issue has gone, repos can be cloned and packages can be installed now. ** Tags removed: verification-needed-jammy-linux-raspi verification-needed-jammy-linux-xilinx-zynqmp verification-needed-lunar-linux verification-needed-lunar-linux-azure verification-needed-lunar-linux-starfive verification-needed-trusty-linux-azure ** Tags added: verification-done-jammy-linux-raspi verification-done-jammy-linux-xilinx-zynqmp verification-done-lunar-linux verification-done-lunar-linux-azure verification-done-lunar-linux-starfive verification-done-trusty-linux-azure ** Tags removed: verification-needed-focal-linux-riscv-5.15 verification-needed-jammy-linux ** Tags added: verification-done-focal-linux-riscv-5.15 verification-done-jammy-linux ** Tags removed: verification-needed-focal-linux-aws-5.15 verification-needed-focal-linux-azure verification-needed-focal-linux-nvidia-tegra-5.15 verification-needed-jammy-linux-aws verification-needed-jammy-linux-aws-6.2 verification-needed-jammy-linux-azure verification-needed-jammy-linux-intel-iotg verification-needed-jammy-linux-nvidia-6.2 verification-needed-jammy-linux-nvidia-tegra verification-needed-jammy-linux-nvidia-tegra-igx ** Tags added: verification-done-focal-linux-aws-5.15 verification-done-focal-linux-azure verification-done-focal-linux-nvidia-tegra-5.15 verification-done-jammy-linux-aws verification-done-jammy-linux-aws-6.2 verification-done-jammy-linux-azure verification-done-jammy-linux-intel-iotg verification-done-jammy-linux-nvidia-6.2 verification-done-jammy-linux-nvidia-tegra verification-done-jammy-linux-nvidia-tegra-igx -- 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/2031093 Title: libgnutls report "trap invalid opcode" when trying to install packages over https Status in ubuntu-kernel-tests: New Status in gnutls28 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in gnutls28 source package in Focal: Confirmed Status in linux source package in Focal: Fix Released Status in gnutls28 source package in Jammy: Confirmed Status in linux source package in Jammy: Fix Released Status in gnutls28 source package in Lunar: Confirmed Status in linux source package in Lunar: Fix Released Bug description: [Impact] When booting linux with Gather Data Sampling mitigations without updated microcode on an affected CPU, AVX will be disabled. This will cause programs connecting to https using gnutls on Jammy to break, including apt and git. [Test case] git clone https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests Cloning into 'autotest-client-tests'... error: git-remote-https died of signal 4 dmesg: [ 806.072080] traps: git-remote-http[2561] trap invalid opcode ip:7fa2e7dac44a sp:7ffed6796480 error:0 in libgnutls.so.30.31.0[7fa2e7c85000+129000] Works fine with the mitigation disabled by default. [Potential regressions] Users booting on affected parts without microcode updates will be subject to Gather Data Sampling attacks (which can be done by local untrusted attackers), which may leak confidential data, including keys. - When trying to install linux-libc-dev on Oracle BM.Standard2.52 (seems to be the only affected instance) with Jammy 5.15.0-81-generic, it will get interrupted with: E: Method https has died unexpectedly! E: Sub-process https received signal 4. $ sudo apt install linux-libc-dev Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: linux-libc-dev 0 upgraded, 1 newly installed, 0 to remove and 54 not upgraded. Need to get 1353 kB of archives. After this operation, 6943 kB of additional disk space will be used. E: Method https has died unexpectedly! E: Sub-process https received signal 4. From dmesg you will see: [ 1078.750067] traps: https[4572] trap invalid opcode ip:7f3c1e6316be sp:7ffea26b61c0 error:0 in libgnutls.so.30.31.0[7f3c1e50f000+129000] Also, git clone is not working as well. $ git clone --depth=1 https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests Cloning into 'autotest-client-tests'... error: git-remote-https died of signal 4 dmesg: [ 806.072080] traps: git-remote-http[2561] trap invalid opcode ip:7fa2e7dac44a sp:7ffed6796480 error:0 in libgnutls.so.30.31.0[7fa2e7c85000+129000] libgnutls30 version:3.7.3-4ubuntu1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2031093/+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 1977827] Re: ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-kvm / L-kvm
This issue is only affecting our KVM kernels, test passed on other kernels. ** Tags removed: verification-needed-focal-linux-aws-5.15 verification-needed-jammy-linux-aws verification-needed-jammy-linux-azure verification-needed-jammy-linux-xilinx-zynqmp ** Tags added: verification-done-focal-linux-aws-5.15 verification-done-jammy-linux-aws verification-done-jammy-linux-azure verification-done-jammy-linux-xilinx-zynqmp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1977827 Title: ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-kvm / L-kvm Status in ubuntu-kernel-tests: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Fix Released Bug description: (Thibf got this issue fixed for KVM kernels, for PPC please refer to bug 2026592) Issue found on Jammy 5.15.0-36.37 with Power9 node baltar Test failed with: # [15] Generic dynamic event - check if duplicate events are caught [FAIL] Test Log: make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' TAP version 13 1..1 # selftests: ftrace: ftracetest # === Ftrace unit tests === # [1] Basic trace file check [PASS] # [2] Basic test for tracers [PASS] # [3] Basic trace clock test [PASS] # [4] Basic event tracing check [PASS] # [5] Change the ringbuffer size [PASS] # [6] Snapshot and tracing setting [PASS] # [7] trace_pipe and trace_marker[PASS] # [8] Test ftrace direct functions against tracers [UNRESOLVED] # [9] Test ftrace direct functions against kprobes [UNRESOLVED] # [10] Generic dynamic event - add/remove eprobe events [PASS] # [11] Generic dynamic event - add/remove kprobe events [PASS] # [12] Generic dynamic event - add/remove synthetic events [PASS] # [13] Generic dynamic event - selective clear (compatibility) [PASS] # [14] Generic dynamic event - generic clear event [PASS] # [15] Generic dynamic event - check if duplicate events are caught [FAIL] # [16] event tracing - enable/disable with event level files [PASS] # [17] event tracing - restricts events based on pid notrace filtering [PASS] # [18] event tracing - restricts events based on pid [PASS] # [19] event tracing - enable/disable with subsystem level files [PASS] # [20] event tracing - enable/disable with top level files [PASS] # [21] Test trace_printk from module [PASS] # [22] ftrace - function graph filters with stack tracer [PASS] # [23] ftrace - function graph filters [PASS] # [24] ftrace - function pid notrace filters [PASS] # [25] ftrace - function pid filters [PASS] # [26] ftrace - stacktrace filter command[PASS] # [27] ftrace - function trace with cpumask [PASS] # [28] ftrace - test for function event triggers [PASS] # [29] ftrace - function trace on module [PASS] # [30] ftrace - function profiling [PASS] # [31] ftrace - function profiler with function tracing [PASS] # [32] ftrace - test reading of set_ftrace_filter[PASS] # [33] ftrace - test for function traceon/off triggers [PASS] # [34] ftrace - test tracing error log support [PASS] # [35] Test creation and deletion of trace instances while setting an event [PASS] # [36] Test creation and deletion of trace instances [PASS] # [37] Kprobe dynamic event - adding and removing[PASS] # [38] Kprobe dynamic event - busy event check [PASS] # [39] Kprobe dynamic event with arguments [PASS] # [40] Kprobe event with comm arguments [PASS] # [41] Kprobe event string type argument [PASS] # [42] Kprobe event symbol argument [PASS] # [43] Kprobe event argument syntax [PASS] # [44] Kprobes event arguments with types[PASS] # [45] Kprobe event user-memory access [UNSUPPORTED] # [46] Kprobe event auto/manual naming [PASS] # [47] Kprobe dynamic event with function tracer [PASS] # [48] Create/delete multiprobe on kprobe event [PASS] # [49] Kprobe event parser error log check [PASS] # [50] Kretprobe dynamic event with arguments[PASS] # [51] Kretprobe dynamic event with maxactive[PASS] # [52] Kretprobe %return suffix test [PASS] # [53] Register/unregister many kprobe events[PASS] # [54] Kprobe profile[PASS] # [55] Uprobe event parser error log check [PASS] # [56] test for the preemptirqsoff tracer[UNSUPPORTED] # [57] Meta-selftest: Checkbashisms [PASS] # [58] Test wakeup tracer[PASS] # [59] Test wakeup RT tracer [PASS] # [60] event trigger - test inter-event histogram trigge
[Kernel-packages] [Bug 2035181] Re: Regression for ubuntu_bpf test build caused by upstream bdeeed3498c7
This issue has gone with linux-nvidia-tegra-5.15/5.15.0-1018.18~20.04.1
as well.
** Tags removed: verification-needed-focal-linux-nvidia-tegra-5.15
** Tags added: verification-done-focal-linux-nvidia-tegra-5.15
--
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/2035181
Title:
Regression for ubuntu_bpf test build caused by upstream bdeeed3498c7
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Lunar:
Confirmed
Bug description:
[Impact]
Commit bdeeed3498c7 ("libbpf: fix offsetof() and container_of() to work
with CO-RE") from stable update breaks the ubuntu_bpf test build and
cause net:udpgro_bench.sh, net:udpgro.sh, net:veth.sh in
ubuntu_kernel_selftests stopped working, as they require bpf selftest
to be built first.
The following is extracted from the commit message:
The problem is the new offsetof() does not play nice with static asserts.
Given that the context is a static assert (and CO-RE relocation is not
needed at compile time), offsetof() usage can be replaced by restoring
the original offsetof() definition as __builtin_offsetof().
[Test Plan]
Build bpf selftest in tools/testing/selftests with the following command:
make headers; make -C tools/testing/selftests TARGETS=bpf SKIP_TARGETS= \
clean all KDIR=/usr/src/linux-headers-5.15.0-85-generic/
The build can finish successfully with patched kernel source code.
[Where problems could occur]
Fix limited to testing tool, if this fix is incorrect the bpf selftest
build will remain broken.
== Original bug report ==
Issue found with Jammy 5.15.0-85.95 in cycle 2023.09.04
This issue does not exist with 5.15.0-83.92 in cycle 2023.08.07 (-84
is a security cycle, in which the ubuntu_bpf test was not triggered
there)
Test build failed with:
CLNG-BPF [test_maps] test_btf_map_in_map.o
CLNG-BPF [test_maps] test_btf_newkv.o
CLNG-BPF [test_maps] test_btf_nokv.o
CLNG-BPF [test_maps] test_btf_skc_cls_ingress.o
CLNG-BPF [test_maps] test_cgroup_link.o
CLNG-BPF [test_maps] test_check_mtu.o
CLNG-BPF [test_maps] test_cls_redirect.o
make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf'
make: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests'
stderr:
Warning: Kernel ABI header at 'tools/include/uapi/linux/bpf.h' differs from
latest version at 'include/uapi/linux/bpf.h'
Warning: Kernel ABI header at 'tools/include/uapi/linux/netlink.h' differs
from latest version at 'include/uapi/linux/netlink.h'
Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs
from latest version at 'include/uapi/linux/if_link.h'
progs/test_cls_redirect.c:90:2: error: static_assert expression is not an
integral constant expression
sizeof(flow_ports_t) !=
^~~
progs/test_cls_redirect.c:91:3: note: cast that performs the conversions of a
reinterpret_cast is not allowed in a constant expression
offsetofend(struct bpf_sock_tuple, ipv4.dport) -
^
progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
(offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
^
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:81:33:
note: expanded from macro 'offsetof'
#define offsetof(type, member) ((unsigned long)&((type *)0)->member)
^
progs/test_cls_redirect.c:95:2: error: static_assert expression is not an
integral constant expression
sizeof(flow_ports_t) !=
^~~
progs/test_cls_redirect.c:96:3: note: cast that performs the conversions of a
reinterpret_cast is not allowed in a constant expression
offsetofend(struct bpf_sock_tuple, ipv6.dport) -
^
progs/test_cls_redirect.c:32:3: note: expanded from macro 'offsetofend'
(offsetof(TYPE, MEMBER) + sizeofTYPE *)0)->MEMBER)))
^
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helpers.h:81:33:
note: expanded from macro 'offsetof'
#define offsetof(type, member) ((unsigned long)&((type *)0)->member)
^
2 errors generated.
make[1]: *** [Makefile:470:
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/test_cls_redirect.o]
Error 1
make: *** [Makefile:171: all] Error 2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2035181/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : k
[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform
** Description changed: [SRU Justification] + + == ipu6-driver == + + [Impact] + + Missing Intel MIPI firmware for Meteor Lake platform. + + [Fix] + + The proposed debdiff contains accumulative fixes for a few bugs, including: + * bug 2026402: to support compiling against v6.6 unstable kernel + * bug 2012407: add CONFIG_VIDEO_V4L2_I2C to BUILD_EXCLUSIVE_CONFIG + * bug 2021740: add modaliases + * bug 2031412: support mipi camera on Intel Meteor Lake platform + + [Test Case] + + This is verified on MTL Lattice and VSC platforms, as well as previous + generations e.g. TGL and ADL. + + [Where problems could occur] + + This is a new platform. We've been verifying its functions and features, and + are still polishing it. + + [Other Info] + + While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and + linux/mantic and on, and yet the lastest stable driver was verified after Mantic was released, it's being proposed to Noble instead. == ivsc-driver == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. [Fix] 4 commits from the latest trunk branch on upstream repository https://github.com/intel/ivsc-driver. [Test Case] With all other changes in position, Intel VSC driver modules are to be loaded as a soft dependency of some selected camera sensor modules. LJCA modules should be loaded automatically on MTL platforms as well. [Where problems could occur] While it changes how LJCA modules match from ACPI ID, it's also tested and verified on previous generations using IVSC, e.g. TGL, ADL. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic and on, and yet the lastest stable driver was verified after Mantic was released, it's being proposed to Noble instead. == linux/linux-oem-6.5 == [Impact] Need kernel driver fixes for int3472/iommu for Intel IPU6 platform on MTL. [Fix] Two fixes in need. One, we need IOMMU passthrough for MTL platform. The other, fix is for handshake pin support for Lattice MIPI aggregator. The Intel IPU6 camera drivers are not yet all upstreamed yet. So far Intel VSC, LJCA (the previous MIPI aggregator for ADL/RPL platforms) are in v6.6 already, and IPU6 ISYS is under upstream review. More components to come according to Intel. These two fixes are therefore for related components for not-yet fully upstreamed IPU6 as needed for out-of-tree dkms drivers. [Test Case] ``` $ sudo dmesg | grep "Passthrough IOMMU for integrated Intel IPU" $ sudo dmesg | grep int3472 # should have no "int3472-discrete INT3472:0c: GPIO type 0x12 unknown; the sensor may not work" ``` [Where problems could occur] IOMMU Passthrough as necessary to enable IPU6 on Intel platforms, and it has been patching a few generations e.g. Bug 1989041 for Raptor Lake, Bug 1958004 for TGL and ADL. As IPU is not an external facing device which is not risky. For INT3472, the proposed patch might receive further updates per current upstream reviewers' opinions. [Other Info] Nominated for linux/mantic and oem-6.5/jammy as they're for MTL. == linux-firmware == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. [Fix] Firmware blobs from upstream ipu6-camera-bins repository. [Test Case] With firmware loaded correctly, there should be firmware version printed: intel-ipu6 intel-ipu: FW version: 20220510 For camera functions, we'll need also updates in the ipu6-drivers, ivsc-drivers dkms as well. [Where problems could occur] This is a new platform. We've been verifying its functions and features, and are still polishing it. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic, so only Jammy/Mantic are nominated. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2031412 Title: Support mipi camera on Intel Meteor Lake platform Status in HWE Next: New Status in ipu6-drivers package in Ubuntu: In Progress Status in ivsc-driver package in Ubuntu: In Progress Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in ipu6-drivers source package in Jammy: Won't Fix Status in ivsc-driver source package in Jammy: Won't Fix Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: In Progress Status in ipu6-drivers source package in Mantic: New Status in ivsc-driver source package in Mantic: New Status in linux source package in Mantic: Fix Committed Status in linux-firmware source pac
[Kernel-packages] [Bug 2041777] [NEW] nfsd hangs forever
Public bug reported: Two times (on October 11 and October 21st) we hadnext issue: server with nfs-kernel-server.service: nfs service hangs forever at some point. The load is not heavy (but I have never been able to check nfsstat or nfsiostat on that server). The logs are the same bunch of messages (for nfsd and kworker tasks respectively): Oct 11 13:18:50 dataserv2 kernel: [689338.249129] INFO: task nfsd:5516 blocked for more than 120 seconds. Oct 11 13:18:50 dataserv2 kernel: [689338.249611] Not tainted 6.2.0-33-generic #33~22.04.1-Ubuntu Oct 11 13:18:50 dataserv2 kernel: [689338.250041] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Oct 11 13:18:50 dataserv2 kernel: [689338.250469] task:nfsdstate:D stack:0 pid:5516 ppid:2 flags:0x4000 Oct 11 13:18:50 dataserv2 kernel: [689338.250477] Call Trace: Oct 11 13:18:50 dataserv2 kernel: [689338.250480] Oct 11 13:18:50 dataserv2 kernel: [689338.250486] __schedule+0x2b7/0x5f0 Oct 11 13:18:50 dataserv2 kernel: [689338.250500] schedule+0x68/0x110 Oct 11 13:18:50 dataserv2 kernel: [689338.250508] raid5_get_active_stripe+0x1f5/0x280 [raid456] Oct 11 13:18:50 dataserv2 kernel: [689338.250526] ? __pfx_autoremove_wake_function+0x10/0x10 Oct 11 13:18:50 dataserv2 kernel: [689338.250536] make_stripe_request+0x9c/0x390 [raid456] Oct 11 13:18:50 dataserv2 kernel: [689338.250550] raid5_make_request+0x1ac/0x480 [raid456] Oct 11 13:18:50 dataserv2 kernel: [689338.250562] ? __pfx_woken_wake_function+0x10/0x10 Oct 11 13:18:50 dataserv2 kernel: [689338.250567] md_handle_request+0x140/0x1e0 Oct 11 13:18:50 dataserv2 kernel: [689338.250575] ? __bio_split_to_limits+0x110/0x2b0 Oct 11 13:18:50 dataserv2 kernel: [689338.250581] md_submit_bio+0x66/0xb0 Oct 11 13:18:50 dataserv2 kernel: [689338.250586] __submit_bio+0xa4/0x1a0 Oct 11 13:18:50 dataserv2 kernel: [689338.250590] __submit_bio_noacct+0x81/0x1f0 Oct 11 13:18:50 dataserv2 kernel: [689338.250593] submit_bio_noacct_nocheck+0x102/0x1e0 Oct 11 13:18:50 dataserv2 kernel: [689338.250597] submit_bio_noacct+0x1d0/0x700 Oct 11 13:18:50 dataserv2 kernel: [689338.250600] submit_bio+0x28/0x90 Oct 11 13:18:50 dataserv2 kernel: [689338.250602] iomap_submit_ioend+0x53/0x90 Oct 11 13:18:50 dataserv2 kernel: [689338.250609] iomap_writepage_map+0x217/0x430 Oct 11 13:18:50 dataserv2 kernel: [689338.250613] iomap_do_writepage+0x161/0x240 Oct 11 13:18:50 dataserv2 kernel: [689338.250617] write_cache_pages+0x19c/0x540 Oct 11 13:18:50 dataserv2 kernel: [689338.250624] ? __pfx_iomap_do_writepage+0x10/0x10 Oct 11 13:18:50 dataserv2 kernel: [689338.250629] iomap_writepages+0x21/0x50 Oct 11 13:18:50 dataserv2 kernel: [689338.250635] xfs_vm_writepages+0x82/0xc0 [xfs] Oct 11 13:18:50 dataserv2 kernel: [689338.250790] do_writepages+0xd3/0x1e0 Oct 11 13:18:50 dataserv2 kernel: [689338.250794] ? iomap_iter+0x95/0x150 Oct 11 13:18:50 dataserv2 kernel: [689338.250798] ? iomap_zero_range+0x7a/0x280 Oct 11 13:18:50 dataserv2 kernel: [689338.250803] filemap_fdatawrite_wbc+0x7c/0xb0 Oct 11 13:18:50 dataserv2 kernel: [689338.250808] __filemap_fdatawrite_range+0x54/0x80 Oct 11 13:18:50 dataserv2 kernel: [689338.250813] filemap_write_and_wait_range+0x5c/0xd0 Oct 11 13:18:50 dataserv2 kernel: [689338.250817] xfs_setattr_size+0x29b/0x3e0 [xfs] Oct 11 13:18:50 dataserv2 kernel: [689338.250951] xfs_vn_setattr_size+0x4a/0xb0 [xfs] Oct 11 13:18:50 dataserv2 kernel: [689338.251053] xfs_vn_setattr+0x79/0x130 [xfs] Oct 11 13:18:50 dataserv2 kernel: [689338.251155] notify_change+0x43b/0x5c0 Oct 11 13:18:50 dataserv2 kernel: [689338.251162] nfsd_setattr+0x20f/0x4b0 [nfsd] Oct 11 13:18:50 dataserv2 kernel: [689338.251213] ? nfsd_setattr+0x20f/0x4b0 [nfsd] Oct 11 13:18:50 dataserv2 kernel: [689338.251253] nfsd3_proc_setattr+0xa1/0x100 [nfsd] Oct 11 13:18:50 dataserv2 kernel: [689338.251300] nfsd_dispatch+0x176/0x2b0 [nfsd] Oct 11 13:18:50 dataserv2 kernel: [689338.251346] svc_process_common+0x36e/0x690 [sunrpc] Oct 11 13:18:50 dataserv2 kernel: [689338.251409] ? __pfx_nfsd_dispatch+0x10/0x10 [nfsd] Oct 11 13:18:50 dataserv2 kernel: [689338.251449] ? __pfx_nfsd+0x10/0x10 [nfsd] Oct 11 13:18:50 dataserv2 kernel: [689338.251489] svc_process+0xb2/0x110 [sunrpc] Oct 11 13:18:50 dataserv2 kernel: [689338.251537] nfsd+0xda/0x1c0 [nfsd] Oct 11 13:18:50 dataserv2 kernel: [689338.251577] kthread+0xee/0x120 Oct 11 13:18:50 dataserv2 kernel: [689338.251584] ? __pfx_kthread+0x10/0x10 Oct 11 13:18:50 dataserv2 kernel: [689338.251588] ret_from_fork+0x2c/0x50 Oct 11 13:18:50 dataserv2 kernel: [689338.251594] Oct 11 13:18:50 dataserv2 kernel: [689338.251640] INFO: task kworker/u194:3:470724 blocked for more than 120 seconds. Oct 11 13:18:50 dataserv2 kernel: [689338.252079] Not tainted 6.2.0-33-generic #33~22.04.1-Ubuntu Oct 11 13:18:50 dataserv2 kernel: [689338.252511] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Oct 11 13:1
[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform
Re-do debdiff against latest version 0~git202302081010.7fdfb5eb-0ubuntu0.23.10.2 instead. ** Patch removed: "ipu6-drivers_0~git202310180730.3f813580-0ubuntu0.24.04.1.debdiff" https://bugs.launchpad.net/ubuntu/noble/+source/ivsc-driver/+bug/2031412/+attachment/5714242/+files/ipu6-drivers_0~git202310180730.3f813580-0ubuntu0.24.04.1.debdiff ** Patch added: "ipu6-drivers_0~git202310180730.3f813580-0ubuntu0.24.04.1.debdiff" https://bugs.launchpad.net/ubuntu/noble/+source/ivsc-driver/+bug/2031412/+attachment/5714245/+files/ipu6-drivers_0~git202310180730.3f813580-0ubuntu0.24.04.1.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2031412 Title: Support mipi camera on Intel Meteor Lake platform Status in HWE Next: New Status in ipu6-drivers package in Ubuntu: In Progress Status in ivsc-driver package in Ubuntu: In Progress Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in ipu6-drivers source package in Jammy: Won't Fix Status in ivsc-driver source package in Jammy: Won't Fix Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: In Progress Status in ipu6-drivers source package in Mantic: New Status in ivsc-driver source package in Mantic: New Status in linux source package in Mantic: Fix Committed Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Status in ipu6-drivers source package in Noble: In Progress Status in ivsc-driver source package in Noble: In Progress Status in linux source package in Noble: Triaged Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [SRU Justification] == ivsc-driver == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. [Fix] 4 commits from the latest trunk branch on upstream repository https://github.com/intel/ivsc-driver. [Test Case] With all other changes in position, Intel VSC driver modules are to be loaded as a soft dependency of some selected camera sensor modules. LJCA modules should be loaded automatically on MTL platforms as well. [Where problems could occur] While it changes how LJCA modules match from ACPI ID, it's also tested and verified on previous generations using IVSC, e.g. TGL, ADL. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic and on, and yet the lastest stable driver was verified after Mantic was released, it's being proposed to Noble instead. == linux/linux-oem-6.5 == [Impact] Need kernel driver fixes for int3472/iommu for Intel IPU6 platform on MTL. [Fix] Two fixes in need. One, we need IOMMU passthrough for MTL platform. The other, fix is for handshake pin support for Lattice MIPI aggregator. The Intel IPU6 camera drivers are not yet all upstreamed yet. So far Intel VSC, LJCA (the previous MIPI aggregator for ADL/RPL platforms) are in v6.6 already, and IPU6 ISYS is under upstream review. More components to come according to Intel. These two fixes are therefore for related components for not-yet fully upstreamed IPU6 as needed for out-of-tree dkms drivers. [Test Case] ``` $ sudo dmesg | grep "Passthrough IOMMU for integrated Intel IPU" $ sudo dmesg | grep int3472 # should have no "int3472-discrete INT3472:0c: GPIO type 0x12 unknown; the sensor may not work" ``` [Where problems could occur] IOMMU Passthrough as necessary to enable IPU6 on Intel platforms, and it has been patching a few generations e.g. Bug 1989041 for Raptor Lake, Bug 1958004 for TGL and ADL. As IPU is not an external facing device which is not risky. For INT3472, the proposed patch might receive further updates per current upstream reviewers' opinions. [Other Info] Nominated for linux/mantic and oem-6.5/jammy as they're for MTL. == linux-firmware == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. [Fix] Firmware blobs from upstream ipu6-camera-bins repository. [Test Case] With firmware loaded correctly, there should be firmware version printed: intel-ipu6 intel-ipu: FW version: 20220510 For camera functions, we'll need also updates in the ipu6-drivers, ivsc-drivers dkms as well. [Where problems could occur] This is a new platform. We've been verifying its functions and features, and are still polishing it. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic, so only Jammy/Mantic are nominated. To manage notifications a
[Kernel-packages] [Bug 1919154] Re: Enable CONFIG_NO_HZ_FULL on supported architectures
Thanks Jay for pointing this out! I just read the man page of vdso, it says gettimeofday is not a real system call and just read the shared memory exports by kernel. It shouldn't be used to measure the user-kernel context switch overhead caused by NO_HZ_FULL. >From what the tests does, I think scheduling jitter should be more suitable >for measuring the overhead. It measures the time of doing a fixed amount of work multiple times, if there is no additional context-switch overhead, the result should be similar under the same workloads when NO_HZ_FULL is built-in, and I didn't generate any workload on the test machine -- 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/1919154 Title: Enable CONFIG_NO_HZ_FULL on supported architectures Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: Won't Fix Status in linux source package in Hirsute: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux source package in Mantic: In Progress Bug description: [Impact] The CONFIG_NO_HZ_FULL=y Kconfig option causes the kernel to avoid sending scheduling-clock interrupts to CPUs with a single runnable task, and such CPUs are said to be "adaptive-ticks CPUs". This is important for applications with aggressive real-time response constraints because it allows them to improve their worst-case response times by the maximum duration of a scheduling-clock interrupt. It is also important for computationally intensive short-iteration workloads: If any CPU is delayed during a given iteration, all the other CPUs will be forced to wait idle while the delayed CPU finishes. Thus, the delay is multiplied by one less than the number of CPUs. In these situations, there is again strong motivation to avoid sending scheduling-clock interrupts. [Test Plan] In order to verify the change will not cause performance issues in context switch we should compare the results for: ./stress-ng --seq 0 --metrics-brief -t 15 Running on a dedicated machine and with the following services disabled: smartd.service, iscsid.service, apport.service, cron.service, anacron.timer, apt-daily.timer, apt-daily-upgrade.timer, fstrim.timer, logrotate.timer, motd-news.timer, man-db.timer. The results didn't show any performance regression: https://kernel.ubuntu.com/~mhcerri/lp1919154/ [Where problems could occur] Performance degradation might happen for workloads with intensive context switching. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919154/+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 2031412] Re: Support mipi camera on Intel Meteor Lake platform
** Description changed: [SRU Justification] + + == ivsc-driver == + + [Impact] + + Missing Intel MIPI firmware for Meteor Lake platform. + + [Fix] + + 4 commits from the latest trunk branch on upstream repository + https://github.com/intel/ivsc-driver. + + [Test Case] + + With all other changes in position, Intel VSC driver modules are to be + loaded as a soft dependency of some selected camera sensor modules. LJCA + modules should be loaded automatically on MTL platforms as well. + + [Where problems could occur] + + While it changes how LJCA modules match from ACPI ID, it's also tested + and verified on previous generations using IVSC, e.g. TGL, ADL. + + [Other Info] + + While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and + linux/mantic and on, and yet the lastest stable driver was verified after Mantic was released, it's being proposed to Noble instead. == linux/linux-oem-6.5 == [Impact] Need kernel driver fixes for int3472/iommu for Intel IPU6 platform on MTL. [Fix] Two fixes in need. One, we need IOMMU passthrough for MTL platform. The other, fix is for handshake pin support for Lattice MIPI aggregator. The Intel IPU6 camera drivers are not yet all upstreamed yet. So far Intel VSC, LJCA (the previous MIPI aggregator for ADL/RPL platforms) are in v6.6 already, and IPU6 ISYS is under upstream review. More components to come according to Intel. These two fixes are therefore for related components for not-yet fully upstreamed IPU6 as needed for out-of-tree dkms drivers. [Test Case] ``` $ sudo dmesg | grep "Passthrough IOMMU for integrated Intel IPU" $ sudo dmesg | grep int3472 # should have no "int3472-discrete INT3472:0c: GPIO type 0x12 unknown; the sensor may not work" ``` [Where problems could occur] IOMMU Passthrough as necessary to enable IPU6 on Intel platforms, and it has been patching a few generations e.g. Bug 1989041 for Raptor Lake, Bug 1958004 for TGL and ADL. As IPU is not an external facing device which is not risky. For INT3472, the proposed patch might receive further updates per current upstream reviewers' opinions. [Other Info] Nominated for linux/mantic and oem-6.5/jammy as they're for MTL. == linux-firmware == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. [Fix] Firmware blobs from upstream ipu6-camera-bins repository. [Test Case] With firmware loaded correctly, there should be firmware version printed: intel-ipu6 intel-ipu: FW version: 20220510 For camera functions, we'll need also updates in the ipu6-drivers, ivsc-drivers dkms as well. [Where problems could occur] This is a new platform. We've been verifying its functions and features, and are still polishing it. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic, so only Jammy/Mantic are nominated. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2031412 Title: Support mipi camera on Intel Meteor Lake platform Status in HWE Next: New Status in ipu6-drivers package in Ubuntu: In Progress Status in ivsc-driver package in Ubuntu: In Progress Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in ipu6-drivers source package in Jammy: Won't Fix Status in ivsc-driver source package in Jammy: Won't Fix Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: In Progress Status in ipu6-drivers source package in Mantic: New Status in ivsc-driver source package in Mantic: New Status in linux source package in Mantic: Fix Committed Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Status in ipu6-drivers source package in Noble: In Progress Status in ivsc-driver source package in Noble: In Progress Status in linux source package in Noble: Triaged Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [SRU Justification] == ivsc-driver == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. [Fix] 4 commits from the latest trunk branch on upstream repository https://github.com/intel/ivsc-driver. [Test Case] With all other changes in position, Intel VSC driver modules are to be loaded as a soft dependency of some selected camera sensor modules. LJCA modules should be loaded automatically on MTL platforms as well. [Where problems could occur] While it changes ho
[Kernel-packages] [Bug 2031412] Re: Support mipi camera on Intel Meteor Lake platform
Attach debdiff for ivsc-driver/noble. Need sponsoring. ** Patch added: "ivsc-driver_0~git202212210258.94ecb88b-0ubuntu0.24.04.1.debdiff" https://bugs.launchpad.net/ubuntu/noble/+source/ivsc-driver/+bug/2031412/+attachment/5714243/+files/ivsc-driver_0~git202212210258.94ecb88b-0ubuntu0.24.04.1.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2031412 Title: Support mipi camera on Intel Meteor Lake platform Status in HWE Next: New Status in ipu6-drivers package in Ubuntu: In Progress Status in ivsc-driver package in Ubuntu: In Progress Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in ipu6-drivers source package in Jammy: Won't Fix Status in ivsc-driver source package in Jammy: Won't Fix Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: In Progress Status in ipu6-drivers source package in Mantic: New Status in ivsc-driver source package in Mantic: New Status in linux source package in Mantic: Fix Committed Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Status in ipu6-drivers source package in Noble: In Progress Status in ivsc-driver source package in Noble: In Progress Status in linux source package in Noble: Triaged Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [SRU Justification] == linux/linux-oem-6.5 == [Impact] Need kernel driver fixes for int3472/iommu for Intel IPU6 platform on MTL. [Fix] Two fixes in need. One, we need IOMMU passthrough for MTL platform. The other, fix is for handshake pin support for Lattice MIPI aggregator. The Intel IPU6 camera drivers are not yet all upstreamed yet. So far Intel VSC, LJCA (the previous MIPI aggregator for ADL/RPL platforms) are in v6.6 already, and IPU6 ISYS is under upstream review. More components to come according to Intel. These two fixes are therefore for related components for not-yet fully upstreamed IPU6 as needed for out-of-tree dkms drivers. [Test Case] ``` $ sudo dmesg | grep "Passthrough IOMMU for integrated Intel IPU" $ sudo dmesg | grep int3472 # should have no "int3472-discrete INT3472:0c: GPIO type 0x12 unknown; the sensor may not work" ``` [Where problems could occur] IOMMU Passthrough as necessary to enable IPU6 on Intel platforms, and it has been patching a few generations e.g. Bug 1989041 for Raptor Lake, Bug 1958004 for TGL and ADL. As IPU is not an external facing device which is not risky. For INT3472, the proposed patch might receive further updates per current upstream reviewers' opinions. [Other Info] Nominated for linux/mantic and oem-6.5/jammy as they're for MTL. == linux-firmware == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. [Fix] Firmware blobs from upstream ipu6-camera-bins repository. [Test Case] With firmware loaded correctly, there should be firmware version printed: intel-ipu6 intel-ipu: FW version: 20220510 For camera functions, we'll need also updates in the ipu6-drivers, ivsc-drivers dkms as well. [Where problems could occur] This is a new platform. We've been verifying its functions and features, and are still polishing it. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic, so only Jammy/Mantic are nominated. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2031412/+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 2031412] Re: Support mipi camera on Intel Meteor Lake platform
Attach debdiff for noble. Need sponsoring. ** Also affects: linux (Ubuntu Noble) Importance: High Assignee: You-Sheng Yang (vicamo) Status: Triaged ** Also affects: linux-firmware (Ubuntu Noble) Importance: High Assignee: You-Sheng Yang (vicamo) Status: Fix Released ** Also affects: ivsc-driver (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: ipu6-drivers (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Changed in: ivsc-driver (Ubuntu Jammy) Status: New => Won't Fix ** Changed in: ipu6-drivers (Ubuntu Jammy) Status: New => Won't Fix ** Changed in: ipu6-drivers (Ubuntu Noble) Importance: Undecided => High ** Changed in: ipu6-drivers (Ubuntu Noble) Status: New => In Progress ** Changed in: ipu6-drivers (Ubuntu Noble) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: ivsc-driver (Ubuntu Noble) Importance: Undecided => High ** Changed in: ivsc-driver (Ubuntu Noble) Status: New => In Progress ** Changed in: ivsc-driver (Ubuntu Noble) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Patch added: "ipu6-drivers_0~git202310180730.3f813580-0ubuntu0.24.04.1.debdiff" https://bugs.launchpad.net/ubuntu/noble/+source/ivsc-driver/+bug/2031412/+attachment/5714242/+files/ipu6-drivers_0~git202310180730.3f813580-0ubuntu0.24.04.1.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2031412 Title: Support mipi camera on Intel Meteor Lake platform Status in HWE Next: New Status in ipu6-drivers package in Ubuntu: In Progress Status in ivsc-driver package in Ubuntu: In Progress Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in ipu6-drivers source package in Jammy: Won't Fix Status in ivsc-driver source package in Jammy: Won't Fix Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: In Progress Status in ipu6-drivers source package in Mantic: New Status in ivsc-driver source package in Mantic: New Status in linux source package in Mantic: Fix Committed Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Status in ipu6-drivers source package in Noble: In Progress Status in ivsc-driver source package in Noble: In Progress Status in linux source package in Noble: Triaged Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [SRU Justification] == linux/linux-oem-6.5 == [Impact] Need kernel driver fixes for int3472/iommu for Intel IPU6 platform on MTL. [Fix] Two fixes in need. One, we need IOMMU passthrough for MTL platform. The other, fix is for handshake pin support for Lattice MIPI aggregator. The Intel IPU6 camera drivers are not yet all upstreamed yet. So far Intel VSC, LJCA (the previous MIPI aggregator for ADL/RPL platforms) are in v6.6 already, and IPU6 ISYS is under upstream review. More components to come according to Intel. These two fixes are therefore for related components for not-yet fully upstreamed IPU6 as needed for out-of-tree dkms drivers. [Test Case] ``` $ sudo dmesg | grep "Passthrough IOMMU for integrated Intel IPU" $ sudo dmesg | grep int3472 # should have no "int3472-discrete INT3472:0c: GPIO type 0x12 unknown; the sensor may not work" ``` [Where problems could occur] IOMMU Passthrough as necessary to enable IPU6 on Intel platforms, and it has been patching a few generations e.g. Bug 1989041 for Raptor Lake, Bug 1958004 for TGL and ADL. As IPU is not an external facing device which is not risky. For INT3472, the proposed patch might receive further updates per current upstream reviewers' opinions. [Other Info] Nominated for linux/mantic and oem-6.5/jammy as they're for MTL. == linux-firmware == [Impact] Missing Intel MIPI firmware for Meteor Lake platform. [Fix] Firmware blobs from upstream ipu6-camera-bins repository. [Test Case] With firmware loaded correctly, there should be firmware version printed: intel-ipu6 intel-ipu: FW version: 20220510 For camera functions, we'll need also updates in the ipu6-drivers, ivsc-drivers dkms as well. [Where problems could occur] This is a new platform. We've been verifying its functions and features, and are still polishing it. [Other Info] While Intel Meteor Lake is only supported by linux-oem-6.5/jammy and linux/mantic, so only Jammy/Mantic are n
[Kernel-packages] [Bug 2039570] Re: Fullscreen in any Wayland/Xwayland window shows a blank screen
I just realised that this doesn't happen when you suspend the computer
and then resume it.
--
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/2039570
Title:
Fullscreen in any Wayland/Xwayland window shows a blank screen
Status in linux package in Ubuntu:
Confirmed
Bug description:
When I go into "fullscreen" watching a video while browsing in Firefox
or when playing a game through Steam (fullscreen mode), the screen
goes black.
The workaround I have discovered to get back is to enter the gdm from
"Ctrl + alt + F1" and then return to the session you were in
(normally, "Ctrl + alt + F2).
Edit: It happens when I connect a second monitor and use it as the
primary display while the laptop screen is disabled.
MSI laptop.
CPU: AMD Ryzen 7 Series 4000
GPU: AMD Radeon RX 5600m
RAM: 16GB
NVM: 1TB.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: noctis 2095 F wireplumber
/dev/snd/controlC0: noctis 2095 F wireplumber
/dev/snd/seq:noctis 2090 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 15:00:55 2023
InstallationDate: Installed on 2023-10-13 (4 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB:
0 amdgpudrmfb
1 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=fb325c2c-11c5-43e3-aceb-e921d5a7b323 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/26/2020
dmi.bios.release: 1.1
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E17EKAMS.101
dmi.board.asset.tag: Default string
dmi.board.name: MS-17EK
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrE17EKAMS.101:bd10/26/2020:br1.1:svnMicro-StarInternationalCo.,Ltd.:pnAlpha17A4DEK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17EK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku17EK.1:
dmi.product.family: Al
dmi.product.name: Alpha 17 A4DEK
dmi.product.sku: 17EK.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039570/+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 1960865] Re: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [G
An update: With recent driver updates it seems that there's no problem anymore. To get to this stage, I had to clear out all and any configurations. Run update initiramfs Clean install works as well... With one caveat - Alt-DP is only working on one of the two USB-C(thunderbolt) ports. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1960865 Title: System freeze when plugging USB-C monitor into a hybrid Intel/Nvidia laptop: [drm:__nv_drm_gem_nvkms_memory_prime_get_sg_table [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to get memory pages for NvKmsKapiMemory Status in Mutter: New Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: I recently upgraded my NVidia drivers on my ThinkPad P1 Gen 3. If I start Ubuntu on Wayland session and plug in my USB-C monitor the system reliably completely freeze. The freeze is also reproducible if the screen is plugged in during startup and trying to login into a Wayland session. Only Wayland session experiences a crash. The crash happens ONLY if the USB-C monitor is plugged in. USB-C monitor is also a USB3 hub. Hardware seems to work fine, as Windows shows no issues with the setup. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.103.01 Thu Jan 6 12:10:04 UTC 2022 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-7ubuntu2) ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 14 16:39:34 2022 DistUpgraded: 2021-10-14 18:36:11,564 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-H GT2 [UHD Graphics] [17aa:22c1] NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:22c1] InstallationDate: Installed on 2020-10-05 (497 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 20THCT01WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-10-14 (122 days ago) dmi.bios.date: 12/27/2021 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: N2VET36W (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20THCT01WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.10 dmi.modalias: dmi:bvnLENOVO:bvrN2VET36W(1.21):bd12/27/2021:br1.21:efr1.10:svnLENOVO:pn20THCT01WW:pvrThinkPadP1Gen3:rvnLENOVO:rn20THCT01WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TH_BU_Think_FM_ThinkPadP1Gen3: dmi.product.family: ThinkPad P1 Gen 3 dmi.product.name: 20THCT01WW dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3 dmi.product.version: ThinkPad P1 Gen 3 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-vide
[Kernel-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
I can totally confirm this issue affecting my Thinkpad P14s with Ryzen 7 is fixed by the mutter release in Proposed. Eabling the Prodosed repo did not get me any updates but after installing mutter with "sudo apt install -t mantic-proposed mutter" all is well in town :) Thanks so much for this! -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: Fix Released Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Committed Status in linux source package in Mantic: Triaged Status in mutter source package in Mantic: Fix Committed Bug description: [ Impact ] gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, sometimes when the screen locks, sometimes when launching particular apps. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Test Plan ] Not all Ryzen systems (including one I just purchased) are able to reproduce the bug. We have no choice but to leave final verification to the community. Anyone affected should try locking their screen and verify they are not instantly returned to the login screen. [ Where problems could occur ] Anywhere in frame scheduling and particularly for mouse cursor movement since that's what the real-time thread exists to optimize. [ Original Description ] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034477]
The patch from #86 works without problems on my IdeaPad Slim 3 14AMN8 Ryzen 3 7320U. Kernel: 6.5.9-arch2-1, EndeavourOS A big thank you to Mario and Hans, I had a great first experience compiling my own kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in ideapad-laptop: New Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-hwe-6.2 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Confirmed Status in linux-hwe-6.2 source package in Jammy: Confirmed Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux-oem-6.5 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed Status in linux source package in Mantic: Confirmed Status in linux source package in Noble: Confirmed Status in Fedora: New Bug description: Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2041751] [NEW] RM: Remove dangerously insecure MPPE PPTP from Ubuntu
*** This bug is a security vulnerability *** Public security bug reported: Remove dangerously insecure MPPE PPTP from Ubuntu https://pptpclient.sourceforge.net/protocol-security.phtml It has been dead for over 20 years now. IPSec OpenVPN Strongswan are much better alternatives. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: network-manager-pptp (Ubuntu) Importance: Undecided Status: New ** Affects: pptp-linux (Ubuntu) Importance: Undecided Status: New ** Affects: pptpd (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Remove dangerously insecure MPPE PPTP from Ubuntu + RM: Remove dangerously insecure MPPE PPTP from Ubuntu ** Also affects: pptpd (Ubuntu) Importance: Undecided Status: New ** Also affects: pptp-linux (Ubuntu) Importance: Undecided Status: New ** Also affects: network-manager-pptp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2041751 Title: RM: Remove dangerously insecure MPPE PPTP from Ubuntu Status in linux package in Ubuntu: New Status in network-manager-pptp package in Ubuntu: New Status in pptp-linux package in Ubuntu: New Status in pptpd package in Ubuntu: New Bug description: Remove dangerously insecure MPPE PPTP from Ubuntu https://pptpclient.sourceforge.net/protocol-security.phtml It has been dead for over 20 years now. IPSec OpenVPN Strongswan are much better alternatives. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041751/+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 2040039] Re: Ubuntu Server 22.04.3 randomly freezes
Same thing here, but installed on a VPS at OVH. Strangely enough, it freezes for no obvious reason (no special activities/events in syslog) at around 14:30 CET every 2 days. The CPU load of the VPS increases linearly, while RAM usage decreases linearly from the time of the freeze. >From that time, even the console (TTY) is freezed. Only hard reboot possible. -- 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/2040039 Title: Ubuntu Server 22.04.3 randomly freezes Status in linux package in Ubuntu: Confirmed Bug description: Hi, I have a physical machine on which I have installed Ubuntu Server 22.04.3 . It randomly freezes. I read few forums and gathered previous boot report as well. Other information as requested: No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.3 LTS Release:22.04 Codename: jammy ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-87-generic 5.15.0-87.97 ProcVersionSignature: Ubuntu 5.15.0-87.97-generic 5.15.122 Uname: Linux 5.15.0-87-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-87-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Sat Oct 21 02:41:33 2023 InstallationDate: Installed on 2023-09-19 (31 days ago) InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230810) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 2M/x2 /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M MachineType: Gigabyte Technology Co., Ltd. H510M H ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-87-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro RelatedPackageVersions: linux-restricted-modules-5.15.0-87-generic N/A linux-backports-modules-5.15.0-87-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2023 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F17 dmi.board.asset.tag: Default string dmi.board.name: H510M H 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:bvnAmericanMegatrendsInternational,LLC.:bvrF17:bd03/10/2023:br5.19:svnGigabyteTechnologyCo.,Ltd.:pnH510MH:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH510MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H510 MB dmi.product.name: H510M H dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040039/+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 2040106] Re: Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10
I had the same problem and I was able to fix this on my machine using
guidelines from @joepadmiraal - thank you!
Here are the steps I followed:
1. I went to to https://cdn.kernel.org/pub/linux/kernel/firmware/ and
downloaded https://cdn.kernel.org/pub/linux/kernel/firmware/linux-
firmware-20230804.tar.gz file into /home/andrzej/Downloads.
2. I unpacked the downloaded file into /home/andrzej/Downloads/linux-
firmware-20230804
tar zxvf ./linux-firmware-20230804.tar.gz
3. I created a backup directory /home/andrzej/lib-firmware-backup.
mkdir /home/andrzej/lib-firmware-backup
4. I backed up Wi-Fi firmware files.
sudo mv /lib/firmware/iwlwifi-* /home/andrzej/lib-firmware-backup
5. I copied Wi-Fi firmware files from downloaded archive into /lib/firmware.
sudo cp /home/andrzej/Downloads/linux-firmware-20230804/iwlwifi-*
/lib/firmware
Note that the files in /lib/firmware are compressed (they have *.zst
extension), and the files the downloaded archive are not compressed.
This is not a problem; I just put uncompressed files in /lib/firmware
and things worked fine.
6. I backed up Bluetooth firmware files.
sudo mv /lib/firmware/intel/ibt-* /home/andrzej/lib-firmware-
backup/intel
7. I copied Bluetooth firmware files from downloaded archive into
/lib/firmware.
sudo cp /home/andrzej/Downloads/linux-firmware-20230804/intel/ibt-*
/lib/firmware/intel
After restarting the machine, Wi-Fi and Bluetooth are back.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2040106
Title:
Intel wifi and bluetooth firmware broken after upgrade to Ubuntu 23.10
Status in linux-firmware package in Ubuntu:
Confirmed
Bug description:
After upgrading from Ubuntu 23.04 to 23.10 on a Dell Precision 5560, wifi and
bluetooth did not work anymore.
Looking at the dmesg output I saw this:
Direct firmware load for iwlwifi-QuZ-a0-hr-b0-59.ucode failed with error -2
..
Direct firmware load for iwlwifi-QuZ-a0-hr-b0-39.ucode failed with error -2
no suitable firmware found!
minimum version required: iwlwifi-QuZ-a0-hr-b0-39
minimum version required: iwlwifi-QuZ-a0-hr-b0-59
These files did seem to exist in /lib/firmware.
I did sudo apt install linux-firmware/mantic --reinstall
Which did not fix it.
I manually overwrote the iwlwifi... files with the corresponding files from
linux-firmware-20230804.tar.gz and this did fix the issue.
I did the same for ibt-19-0-4.sfi and that fixed the bluetooth issue.
So my best guess is that something is wrong in the latest firmware
package.
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 23.10
Release: 23.10
Codename: mantic
apt-cache policy linux-firmware
linux-firmware:
Installed: 20230919.git3672ccab-0ubuntu2.1
Candidate: 20230919.git3672ccab-0ubuntu2.1
Version table:
*** 20230919.git3672ccab-0ubuntu2.1 500
500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-firmware 20230919.git3672ccab-0ubuntu2.1
ProcVersionSignature: Ubuntu 5.10.0-1053.55-oem 5.10.83
Uname: Linux 5.10.0-1053-oem x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: joep 2545 F wireplumber
/dev/snd/controlC0: joep 2545 F wireplumber
/dev/snd/seq:joep 2537 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 22 15:19:18 2023
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85
InstallationDate: Installed on 2021-10-16 (736 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1053-oem
root=UUID=482b1305-d8fa-4fb1-be20-ae911e6a4def ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.10.0-1053-oem N/A
linux-backports-modules-5.10.0-1053-oem N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux-firmware
UpgradeStatus: Upgraded to mantic on 2023-10-22 (0 days ago)
dmi.bios.date: 07/13/2023
dmi.bios.release: 1.22
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.22.0
dmi.board.name: 0NG7N9
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDel
[Kernel-packages] [Bug 2029010] Re: dummy sound on huawei mate d15 laptop
I sent a request to the linux kernel bugzilla. https://bugzilla.kernel.org/show_bug.cgi?id=218085 ** Bug watch added: Linux Kernel Bug Tracker #218085 https://bugzilla.kernel.org/show_bug.cgi?id=218085 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2029010 Title: dummy sound on huawei mate d15 laptop Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: New Status in alsa-ucm-conf package in Ubuntu: New Status in firmware-sof package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: I tried different options, but I couldn't raise the sound. saber716rus@saber716rus-BOM-WXX9 ~> cat /etc/os-release NAME="Green Linux" VERSION="21.2 (Victoria)" ID=linuxmint ID_LIKE="ubuntu debian" PRETTY_NAME="Green Linux 21.2.0 Pro (Cubic 2023-06-14 22:01)" VERSION_ID="21" HOME_URL="https://greenlinux.ru/"; SUPPORT_URL="https://forum.linuxmint.su/"; BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/ru/latest/"; PRIVACY_POLICY_URL="https://greenlinux.ru/"; VERSION_CODENAME=victoria UBUNTU_CODENAME=jammy saber716rus@saber716rus-BOM-WXX9 ~ [1]> cat /proc/asound/cards 0 [Generic]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0xd03c irq 80 1 [acp]: acp - acp HUAWEI-BOM_WXX9-M1010-BOM_WXX9_PCB_B2 saber716rus@saber716rus-BOM-WXX9 ~> To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2029010/+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 2041670]
Yes, sorry, I pasted the text into the report and somehow forgot to put sudo ./reproducer I just wanted to clarify that the open with O_DIRECT and O_CREAT failure should not leave the file around if the open call gets an error return since this is not consistent with other file systems. Also it's not consistent with other open failure modes. Otherwise we need to fix every open call to remove any left over files if open fails and a file may be left over from the failed open. -- 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/2041670 Title: tmpfs: O_DIRECT | O_CREATE open reports open failure but actually creates a file. Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: creating a file on tmpfs with open(filename, O_RDWR | O_DIRECT | O_CREAT, 0666) reports an open failure error EINVAL, but still creates the file. The file should not be created if we hit such an error. Tested and fails on: mantic amd64: 6.5.0-10-generic lunar amd64: 6.2.0-35-generic jammie amd64: 5.15.0-generic focal: 5.4.0-165-generic bionic: 4.15.0-213-generic trusty: 4.4.0-148-generic sudo mkdir /mnt/tmpfs sudo mount -t tmpfs -o size=1G,nr_inodes=10k,mode=777 tmpfs /mnt/tmpfs sudo chmod 666 /mnt/tmpfs gcc reproducer.c -o reproducer sudo ./reproducer Run the attached program. It reports an open failure (errno 22, EINVAL) but still manages to create the file. Note this was original discovered by running stress-ng on tmpfs with the open stressor: stress-ng --open 1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2041670/+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 2041748] [NEW] gpio-fan overlay no longer working after upgrade to 23.10 (fan always on)
Public bug reported: After upgrading to 23.10 the gpio-fan overlay no longer seems to work on my Pi 4 B. dtoverlay=gpio-fan,gpiopin=3,temp=7 With 22.04 und 23.04 the fan was off until 70 degree were reached. But with 23.10 the fan is always on now. Here's the full /boot/firmware/config.txt: [pi4] max_framebuffers=2 arm_boost=1 [all] arm_64bit=1 kernel=vmlinuz cmdline=cmdline.txt initramfs initrd.img followkernel # Enable the audio output, I2C and SPI interfaces on the GPIO header dtparam=audio=on dtparam=i2c_arm=on dtparam=spi=on # Enable the serial pins enable_uart=1 # Comment out the following line if the edges of the desktop appear outside # the edges of your display disable_overscan=1 # If you have issues with audio, you may try uncommenting the following line # which forces the HDMI output into HDMI mode instead of DVI (which doesn't # support audio output) #hdmi_drive=2 # If you have a CM4, uncomment the following line to enable the USB2 outputs # on the IO board (assuming your CM4 is plugged into such a board) #dtoverlay=dwc2,dr_mode=host dtoverlay=gpio-fan,gpiopin=3,temp=7 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-raspi 6.5.0.1006.7 ProcVersionSignature: Ubuntu 6.5.0-1006.8-raspi 6.5.3 Uname: Linux 6.5.0-1006-raspi aarch64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k6.5.0-1006-raspi. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.27.0-0ubuntu5 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: CloudSubPlatform: config-disk (/dev/mmcblk0p1) Date: Sun Oct 29 16:34:49 2023 ImageMediaBuild: 20201022 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M PciMultimedia: ProcEnviron: LANG=en_US.UTF-8 LC_CTYPE=UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=0 bcm2708_fb.fbheight=0 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:FE:2D:4A vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash RelatedPackageVersions: linux-restricted-modules-6.5.0-1006-raspi N/A linux-backports-modules-6.5.0-1006-raspi N/A linux-firmware20230919.git3672ccab-0ubuntu2.1 SourcePackage: linux-raspi StagingDrivers: bcm2835_mmal_vchiq bcm2835_isp rpivid_hevc bcm2835_codec vc_sm_cma snd_bcm2835 bcm2835_v4l2 UpgradeStatus: Upgraded to mantic on 2023-10-29 (0 days ago) acpidump: ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image cloud-image mantic raspi-image staging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2041748 Title: gpio-fan overlay no longer working after upgrade to 23.10 (fan always on) Status in linux-raspi package in Ubuntu: New Bug description: After upgrading to 23.10 the gpio-fan overlay no longer seems to work on my Pi 4 B. dtoverlay=gpio-fan,gpiopin=3,temp=7 With 22.04 und 23.04 the fan was off until 70 degree were reached. But with 23.10 the fan is always on now. Here's the full /boot/firmware/config.txt: [pi4] max_framebuffers=2 arm_boost=1 [all] arm_64bit=1 kernel=vmlinuz cmdline=cmdline.txt initramfs initrd.img followkernel # Enable the audio output, I2C and SPI interfaces on the GPIO header dtparam=audio=on dtparam=i2c_arm=on dtparam=spi=on # Enable the serial pins enable_uart=1 # Comment out the following line if the edges of the desktop appear outside # the edges of your display disable_overscan=1 # If you have issues with audio, you may try uncommenting the following line # which forces the
[Kernel-packages] [Bug 787738]
Issue happen again: here is the log excerpt: [1.114640] psmouse serio1: synaptics: queried max coordinates: x [..5676], y [..4758] [1.227504] psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1096..] [1.227508] psmouse serio1: synaptics: Trying to set up SMBus access [1.230179] psmouse serio1: synaptics: SMbus companion is not ready yet [1.287961] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2b1, caps: 0xf008a3/0x943300/0x12e800/0x41, board id: 3053, fw id: 2491654 [1.287971] psmouse serio1: synaptics: serio: Synaptics pass-through port at isa0060/serio1/input0 [2.038184] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 [7.767620] psmouse serio1: synaptics: queried max coordinates: x [..5676], y [..4758] [7.799610] psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1096..] [7.799618] psmouse serio1: synaptics: Trying to set up SMBus access [8.335736] psmouse serio3: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 [81220.734879] psmouse serio3: TrackPoint at rmi4-00.fn03/serio0/input0 lost synchronization, throwing 1 bytes away. [81220.933317] psmouse serio3: resync failed, issuing reconnect request [118134.901594] psmouse serio3: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 [139642.459611] psmouse serio3: TrackPoint at rmi4-00.fn03/serio0/input0 lost synchronization, throwing 1 bytes away. [139642.933809] psmouse serio3: resync failed, issuing reconnect request Moreover, when laptop is suspended more than ca 1 hour, after resume the touchpad is working 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/787738 Title: [Thinkpad X220/E220s/E420s] trackpoint/trackpoint displays odd behaviour Status in Linux: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Natty: Invalid Status in linux source package in Oneiric: Invalid Status in Fedora: New Bug description: Using the touchpad does not result in expected behavior. The touchpad has three "mouse" buttons on top, and none of these buttons currently function. Using xev does not show any output from these buttons. The touchpad itself works fine. There are two bottom buttons integrated with the touchpad, which do not work consistantly. The left button will sometimes act like a left-click and sometime like a right click, making it hard to move applications on the screen. The right button acts like a left click and only sometimes bring up menus. Trying to change from a left hand to a right hand mouse in mouse options does not change the behavior. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: linux-image-2.6.38-8-generic 2.6.38-8.42 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1235 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xd252 irq 44' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:14f1506e,17aa21da,0010 HDA:80862805,80860101,0010' Controls : 20 Simple ctrls : 8 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw unknown' Mixer name : 'ThinkPad EC (unknown)' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Tue May 24 14:44:59 2011 HibernationDevice: RESUME=UUID=dd9d30b2-4950-42af-87e2-b304fc01e83d InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) MachineType: LENOVO 428623U ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=4985f74f-9e44-411f-8d41-73f9f68c057d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-2.6.38-8-generic N/A linux-backports-modules-2.6.38-8-generic N/A linux-firmware1.52 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET28WW (1.00 ) dmi.board.asset.tag: Not Available dmi.board.name: 428623U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Informatio
[Kernel-packages] [Bug 2041741] Re: Fan speed Control not working on RASPERRY PI 5 RUNNING UBUNTU 23.10
** Package changed: ubuntu => linux-raspi (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2041741 Title: Fan speed Control not working on RASPERRY PI 5 RUNNING UBUNTU 23.10 Status in linux-raspi package in Ubuntu: New Bug description: The fan speed control when running Ubuntu 23.10 on a Raspberry Pi 5 does not appear to be working. The fan runs at near maximum speed all the time and the cur_state in /sys/class/thermal/cooling_device0/ is stuck at the value of 4 no matter what the CPU temperature. I suspect it is related to this fault reported on Raspberry Pi OS: https://forums.raspberrypi.com/viewtopic.php?t=356881 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2041741/+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 2041741] [NEW] Fan speed Control not working on RASPERRY PI 5 RUNNING UBUNTU 23.10
You have been subscribed to a public bug: The fan speed control when running Ubuntu 23.10 on a Raspberry Pi 5 does not appear to be working. The fan runs at near maximum speed all the time and the cur_state in /sys/class/thermal/cooling_device0/ is stuck at the value of 4 no matter what the CPU temperature. I suspect it is related to this fault reported on Raspberry Pi OS: https://forums.raspberrypi.com/viewtopic.php?t=356881 ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Fan speed Control not working on RASPERRY PI 5 RUNNING UBUNTU 23.10 https://bugs.launchpad.net/bugs/2041741 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
