Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #91720 > unrolled thread

Bug#1131025: linux-image-6.12.73+deb13-amd64: echo vfio-pci >driver_override does not work for DVB Adapter

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1131025: linux-image-6.12.73+deb13-amd64: echo vfio-pci >driver_override does not work for DVB Adapter Salvatore Bonaccorso <carnil@debian.org> - 2026-03-18 13:50 +0100
    Processed: Re: Bug#1131025: linux-image-6.12.73+deb13-amd64: echo  vfio-pci >driver_override does not work for DVB Adapter "Debian Bug Tracking System" <owner@bugs.debian.org> - 2026-03-18 13:50 +0100
    Bug#1131025: linux-image-6.12.73+deb13-amd64: echo vfio-pci >driver_override does not work for DVB Adapter Salvatore Bonaccorso <carnil@debian.org> - 2026-03-18 14:50 +0100
      Processed: Re: Bug#1131025: linux-image-6.12.73+deb13-amd64: echo  vfio-pci >driver_override does not work for DVB Adapter "Debian Bug Tracking System" <owner@bugs.debian.org> - 2026-03-18 14:50 +0100
      Bug#1131025: linux-image-6.12.73+deb13-amd64: echo vfio-pci >driver_override does not work for DVB Adapter Salvatore Bonaccorso <carnil@debian.org> - 2026-03-22 09:30 +0100

#91720 — Bug#1131025: linux-image-6.12.73+deb13-amd64: echo vfio-pci >driver_override does not work for DVB Adapter

Control: tags -1 + moreinfo

Hi,

On Tue, Mar 17, 2026 at 08:18:17AM +0100, Bernd Schumacher wrote:
> Package: src:linux
> Version: 6.12.73-1
> Severity: normal
> X-Debbugs-Cc: debian-amd64@lists.debian.org
> User: debian-amd64@lists.debian.org
> Usertags: amd64
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>    * What led up to the situation?
> I have a kvm with linux-image-6.1.0-43-amd64 running vdr and femon.
> On the host I do echovfio-pci >/sys/bus/pci/devices/0000:$PCI/driver_override.
> Then I give the DVB Adapter to the kvm.
> 
> It works, if I boot linux-image-6.12.63+deb13-amd64 on the host.
> If it works dmesg on the kvm says:
> 05:00.0 Multimedia controller: Digital Devices GmbH Octopus DVB Adapter
> dmesg:
> [    2.443770] dvbdev: DVB: registering new adapter (DDBridge)
> [    2.443772] dvbdev: DVB: registering new adapter (DDBridge)
> ...
> [    2.694180] ddbridge 0000:05:00.0: attach tuner input 0 adr 60
> [    2.694183] ddbridge 0000:05:00.0: DVB: registering adapter 0 frontend 0 (STV090x Multistandard)...
> ...
> [    2.738542] ddbridge 0000:05:00.0: attach tuner input 1 adr 63
> [    2.738545] ddbridge 0000:05:00.0: DVB: registering adapter 1 frontend 0 (STV090x Multistandard)...
> 
> 
> It does not work, if I boot linux-image-6.12.73+deb13-amd64 on thehost.
> If it does not work dmesg on th kvm says:
> [    2.413879] ddbridge 0000:05:00.0: detected Digital Devices Cine S2 V6 DVB adapter
> [    2.413901] ddbridge 0000:05:00.0: cannot read registers
> [    2.414569] ddbridge 0000:05:00.0: fail
> 
> If I run femon it says:
> femon: opening frontend failed: No such file or directory
> 
>    * What exactly did you do (or not do) that was effective (or
>      ineffective)?
>    * What was the outcome of this action?
>    * What outcome did you expect instead?
> 
> *** End of the template - remove these template lines ***

Given you have the range 6.12.63 (good) .. 6.12.73 (bad), can you

1. confirm if 6.12.74-2 still as well is broken

and if so

2. would you be able to bisect the upstream changes beween 6.12.63 and
6.12.73 to identify the commit which introduces this regression for
you? (Do you need instructions for that?).

Regards,
Salvatore

[toc] | [next] | [standalone]

#91725 — Processed: Re: Bug#1131025: linux-image-6.12.73+deb13-amd64: echo vfio-pci >driver_override does not work for DVB Adapter

Processing control commands:

> tags -1 + moreinfo
Bug #1131025 [src:linux] linux-image-6.12.73+deb13-amd64: echo vfio-pci >driver_override does not work for DVB Adapter
Added tag(s) moreinfo.

-- 
1131025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1131025
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#91730

Control: found -1 6.12.74-2

Hi Bernd,

On Wed, Mar 18, 2026 at 02:30:28PM +0100, Bernd Schumacher wrote:
> Hi Salvatore,
> 
> Am Mittwoch, dem 18.03.2026 um 13:41 +0100 schrieb Salvatore
> Bonaccorso:
> > 
> > Given you have the range 6.12.63 (good) .. 6.12.73 (bad), can you
> > 
> > 1. confirm if 6.12.74-2 still as well is broken
> > 
> Yes I confirm, that the same problem exists with:
> ii  linux-image-6.12.74+deb13+1-amd64        6.12.74-2 

Thanks for the confirmation.

> > and if so
> > 
> > 2. would you be able to bisect the upstream changes beween 6.12.63
> > and
> > 6.12.73 to identify the commit which introduces this regression for
> > you? (Do you need instructions for that?).
> Yes, I need instructions how I can find the relevant change. 

So first thanks if you find time to do that work, that is great. Here
are the instructions, it will involve doing some rounds of compiling
and testing kernels as follows:

    git clone --single-branch -b linux-6.12.y https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
    cd linux-stable
    git checkout v6.12.63
    cp /boot/config-$(uname -r) .config
    yes '' | make localmodconfig
    make savedefconfig
    mv defconfig arch/x86/configs/my_defconfig

    # test 6.12.63 to ensure this is "good"
    make my_defconfig
    make -j $(nproc) bindeb-pkg
    ... install the resulting .deb package and confirm problem does not exist

    # test 6.12.73 to ensure this is "bad"
    git checkout v6.12.73
    make my_defconfig
    make -j $(nproc) bindeb-pkg
    ... install the resulting .deb package and confirm problem exists.

With that confirmed, the bisection can start:
 
    git bisect start
    git bisect good v6.12.63
    git bisect bad v6.12.73
 
In each bisection step git checks out a state between the oldest
known-bad and the newest known-good commit. In each step test using:
 
    make my_defconfig
    make -j $(nproc) bindeb-pkg
    ... install, verify if problem exists
 
and if the problem is hit run:
 
    git bisect bad
 
and if the problem doesn't trigger run:
 
    git bisect good
 
. Please pay attention to always select the just built kernel for
booting, it won't always be the default kernel picked up by grub.
 
Iterate until git announces to have identified the first bad commit.
 
Then provide the output of
 
    git bisect log
 
In the course of the bisection you might have to uninstall previous
kernels again to not exhaust the disk space in /boot. Also in the end
uninstall all self-built kernels again.

Hope this helps so far.

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#91731 — Processed: Re: Bug#1131025: linux-image-6.12.73+deb13-amd64: echo vfio-pci >driver_override does not work for DVB Adapter

Processing control commands:

> found -1 6.12.74-2
Bug #1131025 [src:linux] linux-image-6.12.73+deb13-amd64: echo vfio-pci >driver_override does not work for DVB Adapter
Marked as found in versions linux/6.12.74-2.

-- 
1131025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1131025
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#91773

Control: tags -1 + moreinfo

Hi Bernd,

Sorry for the late reply.

On Wed, Mar 18, 2026 at 05:19:10PM +0100, Bernd Schumacher wrote:
> Hi Salvatore,
> 
> Thanks for the clear instructions.
> 
> git bisect log says:
> 
> git bisect start
> # Status: warte auf guten und schlechten Commit
> # good: [567bd8cbc2fe6b28b78864cbbbc41b0d405eb83c] Linux 6.12.63
> git bisect good 567bd8cbc2fe6b28b78864cbbbc41b0d405eb83c
> # Status: warte auf schlechten Commit, 1 guter Commit bekannt
> # bad: [5fb0303f6cb6a89bcfb19bd7a68cb793c86e78b2] Linux 6.12.73
> git bisect bad 5fb0303f6cb6a89bcfb19bd7a68cb793c86e78b2
> # good: [b1dd6860167667008c3b6f27628d071dc3daaf04] smb/client: fix
> NT_STATUS_UNABLE_TO_FREE_VM value
> git bisect good b1dd6860167667008c3b6f27628d071dc3daaf04
> # good: [1baa43ebca626aa607a03b1c0023ebac5374e62d] octeontx2-af: Fix
> error handling
> git bisect good 1baa43ebca626aa607a03b1c0023ebac5374e62d
> # good: [3845bd336a406cb7c609b515e6ee4c8818053f69] net/sched: act_ife:
> convert comma to semicolon
> git bisect good 3845bd336a406cb7c609b515e6ee4c8818053f69
> # bad: [2901d799a26d949ccf648a6c176a0091a7f1c0ed] ALSA: hda/realtek:
> Fix headset mic for TongFang X6AR55xU
> git bisect bad 2901d799a26d949ccf648a6c176a0091a7f1c0ed
> # bad: [b9b97e6aeb534315f9646b2090d1a5024c6a4e82] procfs: avoid
> fetching build ID while holding VMA lock
> git bisect bad b9b97e6aeb534315f9646b2090d1a5024c6a4e82
> # good: [b8ea101959ab1a46c92be46c238283b0fe60252e] pmdomain: imx:
> gpcv2: Fix the imx8mm gpu hang due to wrong adb400 reset
> git bisect good b8ea101959ab1a46c92be46c238283b0fe60252e
> # good: [dfc3ab6bd64860f8022d69903be299d09be86e11] mm, shmem: prevent
> infinite loop on truncate race
> git bisect good dfc3ab6bd64860f8022d69903be299d09be86e11
> # bad: [9bcc47343ee0ef346aa7b2b460c8ff56bd882fe7] ublk: fix deadlock
> when reading partition table
> git bisect bad 9bcc47343ee0ef346aa7b2b460c8ff56bd882fe7
> # good: [ff48c9312d042bfbe826ca675e98acc6c623211c] KVM: Don't clobber
> irqfd routing type when deassigning irqfd
> git bisect good ff48c9312d042bfbe826ca675e98acc6c623211c
> # bad: [d288ba832d92d16f7db0f6996ffbde2e79190ffe] tools/power
> turbostat: fix GCC9 build regression
> git bisect bad d288ba832d92d16f7db0f6996ffbde2e79190ffe
> # bad: [58130e7ce6cb6e1f73221e412fef6c85ee561425] PCI/ERR: Ensure error
> recoverability at all times
> git bisect bad 58130e7ce6cb6e1f73221e412fef6c85ee561425
> # first bad commit: [58130e7ce6cb6e1f73221e412fef6c85ee561425] PCI/ERR:
> Ensure error recoverability at all times

Hmm, this is an interesting restult as I do not immediately see the
relation. The commit you point out was as well in 6.18.10 and
6.19-rc1, so might you please test as well the kernel in unstable
(6.19.8-1) to see if you can trigger the problem as well?

Seconly: Can you confirm, if you revert this commit specifically on
top of the packaging, it fixes the issue you are facing?

To build a kernel with single patches on top of the current packaging
you can use the debian/bin/test-patches script, cf. https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#id-1.6.6.4

Regards,
Salvatore

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web