[Bug 249476] graphics/drm-fbsd12.0-kmod i915kms GT2 attach returned 19

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sun Sep 20 08:55:04 UTC 2020


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249476

            Bug ID: 249476
           Summary: graphics/drm-fbsd12.0-kmod i915kms GT2 attach returned
                    19
           Product: Ports & Packages
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: x11 at FreeBSD.org
          Reporter: grarpamp at gmail.com
             Flags: maintainer-feedback?(x11 at FreeBSD.org)
          Assignee: x11 at FreeBSD.org

Intel Haswell GT2 Server HD Graphics P4600 vendor=0x8086,dev=0x041a,revid=0x06
download.freebsd.org: FreeBSD 12.2-BETA1 r365618 GENERIC amd64
pkg.freebsd.org:
FreeBSD:12:amd64/latest/All/drm-fbsd12.0-kmod-4.16.g20200221.txz

Up to date as above.

Modules kldload and kldstat ok...
Loaded /.../i915kms.ko, id=8
i915kms.ko, drm.ko, linuxkpi.ko, linuxkpi_gplv2.ko, debugfs.ko

But the only dmesg output says they are broken...
kernel: anon_inodefs registered
kernel: debugfs registered
kernel: drmn0: <drmn> on vgapci0
kernel: device_attach: drmn0 attach returned 19

Then upon kldunload of i915kms it panics.



The drm shipped in BETA1, and in drm-legacy-kmod-g20200825, both work.

But they do throw some issues...
kernel: info: [drm] Memory usable by graphics device = 2048M
kernel: info: [drm] MTRR allocation failed.  Graphics performance may suffer.
kernel: error: [drm:pidxxx:i915_write32] *ERROR* Unknown unclaimed register
before writing to c5100
...
kernel: error: [drm:pidxxx:drm_mm_takedown] *ERROR* Memory manager not clean.
Delaying takedown
kernel: Warning: memory type drm_sman leaked memory on destroy (4 allocations,
512 bytes leaked).

Intel-ARK says this unit has max 1.7GB video mem shared from dram.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-x11 mailing list