[Bug 289647] graphics/drm-61-kmod: X11 with nvidia-drm-61-kmod fails to start after commit ac934345a14f

[email protected]
Newsgroups gmane.os.freebsd.devel.x11
Message-ID <[email protected]/bugzilla/>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289647

--- Comment #61 from [email protected] ---
A commit in branch stable/14 references this bug:

URL:
https://cgit.FreeBSD.org/src/commit/?id=2f4700c4dc1598c1b99996412a932764d5cbac45

commit 2f4700c4dc1598c1b99996412a932764d5cbac45
Author:     Bjoern A. Zeeb <[email protected]>
AuthorDate: 2025-09-04 20:22:00 +0000
Commit:     Bjoern A. Zeeb <[email protected]>
CommitDate: 2026-01-16 19:37:50 +0000

    LinuxKPI: pci: allocate entire pci_dev hiereachy up to root port on attach

    In linux_pci_attach_device() allocate a LinuxKPI pci_dev for each device in
    the hierarchy up to the root port[1] as we cannot do that later on demand
    as we may be in a context where we may not sleep.

    Take special care of DRM as there is a non-PCI device in the chain which
    needs to be skipped.

    iwlwifi(4) can hit this case called from a callout.

    While here leave a comment as the cleanup order of
    linux_pci_attach_device() needs correction seperately.

    Sponsored by:   The FreeBSD Foundation (initially)
    PR:             283027
    PR:             289647
    Suggested by:   jhb [1]
    Reviewed by:    dumbbell
    Differential Revision:  https://reviews.freebsd.org/D52069

    (cherry picked from commit bbeeb585315645db20118ef349a4e3dc83b148cc)
    (cherry picked from commit 3860afe99ec39b9942967941181f28f27f3fc548)
    (cherry picked from commit 123c2dc6e15a62ceba3469caf0f1a6801214a7d3)
    (cherry picked from commit d8972ad2f6e7113d779d4ec975ce32552030b2a3)

 sys/compat/linuxkpi/common/src/linux_pci.c | 47 +++++++++++++++++++++++++-----
 1 file changed, 40 insertions(+), 7 deletions(-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.