Hello Salvatore, Thank you for the information, that is exactly in line with what I was typing in my previous message that just took so long to write.
Then I eagerly await 6.1.129. :) Regards, Alf Nilsson On Tue, Feb 25, 2025 at 8:06 PM Alf Nilsson <alf.nils...@gmail.com> wrote: > Hello Salvatore, > > I do have it uncompressed: > affetwoday@lenovo-m83:/usr/src/linux-source-6.1$ ls -l > total 968 > drwxr-xr-x 24 root root 4096 Aug 8 2023 arch > drwxr-xr-x 3 root root 4096 Jul 6 2023 block > drwxr-xr-x 2 root root 4096 Jul 6 2023 certs > -rw-r--r-- 1 root root 496 Jul 6 2023 COPYING > -rw-r--r-- 1 root root 101639 Jul 6 2023 CREDITS > drwxr-xr-x 4 root root 4096 Jul 6 2023 crypto > drwxr-xr-x 86 root root 4096 Aug 8 2023 Documentation > drwxr-xr-x 139 root root 4096 Jul 6 2023 drivers > drwxr-xr-x 81 root root 4096 Aug 8 2023 fs > drwxr-xr-x 33 root root 4096 Aug 11 2023 include > drwxr-xr-x 2 root root 4096 Aug 8 2023 init > drwxr-xr-x 2 root root 4096 Jul 6 2023 io_uring > drwxr-xr-x 2 root root 4096 Jul 6 2023 ipc > -rw-r--r-- 1 root root 2573 Jul 6 2023 Kbuild > -rw-r--r-- 1 root root 555 Jul 6 2023 Kconfig > drwxr-xr-x 22 root root 4096 Aug 8 2023 kernel > drwxr-xr-x 22 root root 12288 Aug 8 2023 lib > drwxr-xr-x 6 root root 4096 Jul 6 2023 LICENSES > -rw-r--r-- 1 root root 688533 Jul 6 2023 MAINTAINERS > -rw-r--r-- 1 root root 72209 Aug 8 2023 Makefile > drwxr-xr-x 6 root root 4096 Aug 8 2023 mm > drwxr-xr-x 71 root root 4096 Jul 6 2023 net > -rw-r--r-- 1 root root 727 Jul 6 2023 README > drwxr-xr-x 6 root root 4096 Jul 6 2023 rust > drwxr-xr-x 39 root root 4096 Jul 6 2023 samples > drwxr-xr-x 17 root root 4096 Aug 8 2023 scripts > drwxr-xr-x 14 root root 4096 Aug 8 2023 security > drwxr-xr-x 27 root root 4096 Jul 6 2023 sound > drwxr-xr-x 41 root root 4096 Jul 6 2023 tools > drwxr-xr-x 4 root root 4096 Jul 6 2023 usr > drwxr-xr-x 4 root root 4096 Jul 6 2023 virt > > And I only installed the source package using apt. So really strange that > my 6.1.128-1 does not have the breaking change, but the one you are looking > at has it. > > I will download the deb package again and recheck it. > And....I re-downloaded 6.1.128-1....and now it has the code that breaks > the uvc_driver.c > > So that means that : The kernel build is then correct as the 128-1 code > still has the broken driver. > (But my locally installed apt source, for some reason does not have it) > > And about debugging, I don't really feel the need due to that I have been > following the upstream development of the uvcvideo driver. > > Upstream commit that broke it: > > https://github.com/torvalds/linux/commit/3dd075fe8ebbc6fcbf998f81a75b8c4b159a6195 > First RC with broken code: Linux 6.12-rc3 > > Upstream commit that un-broke it: > > https://github.com/torvalds/linux/commit/8004d635f27bbccaa5c083c50d4d5302a6ffa00e > First RC with un-broken code: Linux 6.14-rc1 > > Do you need the same info from the stable branch? > > Regards, > Alf Nilsson > > > On Tue, Feb 25, 2025 at 1:43 PM Salvatore Bonaccorso <car...@debian.org> > wrote: > >> Control: tags -1 + moreinfo >> Control: found -1 6.1.123-1 >> >> HI Alf, >> >> On Tue, Feb 25, 2025 at 02:53:10AM +0700, Alf Nilsson wrote: >> > Hello Salvatore, >> > >> > Strange about the 6.1 source. >> > >> > root@lenovo-m83:~# aptitude search linux-source-6.1 -vv >> > i A linux-source-6.1 >> > - Linux kernel source for version 6.1 with >> > Debian patches >> > v linux-source-6.1:i386 >> > - >> > >> > >> > root@lenovo-m83:~# aptitude show linux-source-6.1 >> > Package: linux-source-6.1 >> > Version: 6.1.128-1 >> > State: installed >> > Automatically installed: yes >> > Multi-Arch: foreign >> > Priority: optional >> > Section: kernel >> > Maintainer: Debian Kernel Team <debian-ker...@lists.debian.org> >> > Architecture: all >> > Uncompressed Size: 139 M >> > Depends: binutils, xz-utils >> > Recommends: build-essential, bc, rsync, kmod, cpio, bison, flex, >> > libelf-dev, libssl-dev, linux-config-6.1 >> > Suggests: libncurses-dev | ncurses-dev, qtbase5-dev, pkg-config >> > Provides: linux-source-6.1:i386 (= 6.1.128-1) >> > Description: Linux kernel source for version 6.1 with Debian patches >> > This package provides source code for the Linux kernel version 6.1. >> This >> > source closely tracks official Linux kernel releases. Debian's >> > modifications to that source consist of security fixes, bug fixes, and >> > features that have already been (or are believed to be) accepted by the >> > upstream maintainers. >> > Homepage: https://www.kernel.org/ >> > >> > root@lenovo-m83:/# grep -R 'Found multiple Units' >> /usr/src/linux-source-6.1 >> > root@lenovo-m83:/# >> > >> > So not found in my source code on a Debian 12 system. >> >> Ah, this is because you have not uncompressend the provided source. >> linux-source-6.1 contains /usr/src/linux-source-6.1.tar.xz >> >> > > Is this a regression? Which is the last 6.1.y kernel which worked? >> > > >> > root@lenovo-m83:/var/run# uname -vr >> > 6.1.0-28-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.119-1 (2024-11-22) >> >> So this is good to know, so it regressed between 6.1.119 and 6.1.123. >> >> > > Can you test recent kernels from unstable (6.12.16-1) or experimental >> > > (6.13.4-1~exp1), does the issue replicate there as well? >> > root@debian-unstable:~# uname -vr >> > 6.12.16-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.16-1 (2025-02-22) >> > >> > Works fine in unstable. >> > >> > Reboot now to 3.1.0-31-amd. >> > >> > root@lenovo-m83:~# uname -vr >> > 6.1.0-31-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.128-1 (2025-02-07) >> > >> > Attaching a boot kernel log with the camera attached. >> > (See kernel.log) >> >> Thanks. >> >> Would you be able to bisect the changes upstream between 6.1.119 and >> 6.1.123? >> >> https://wiki.debian.org/DebianKernel/GitBisect >> >> contains instructions on how to do so. Our goal would be to identify >> which commit between 6.1.119 and 6.1.123 upstream does regress the >> functionality so it can either double-checked against upper stable >> series and/or report upstream for the 6.1.y branch. >> >> So we need your help here in debugging as you have the HW. Is the >> above helping you on how to proceed? >> >> Regards, >> Salvatore >> >
