Date: Sat, 15 Dec 2018 21:17:38 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 234044] graphics/drm-kmod: kernel: Failed to add WC MTRR for [0xe0000000-0xefffffff]: -22; performance may suffer Message-ID: <bug-234044-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234044 Bug ID: 234044 Summary: graphics/drm-kmod: kernel: Failed to add WC MTRR for [0xe0000000-0xefffffff]: -22; performance may suffer Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: jmd@freebsd.org Reporter: phascolarctos@protonmail.ch Assignee: jmd@freebsd.org Flags: maintainer-feedback?(jmd@freebsd.org) I get the following message when loading the i915dms.ko module: kernel: Failed to add WC MTRR for [0xe0000000-0xefffffff]: -22; performance= may suffer Performance do not suffer in a significant manner, however I think there mi= ght be a slight penalty (supertuxkart does not run as smoothly as I would expec= t). This is the relevant part of my system log: kernel: drmn0: <drmn> on vgapci0 kernel: vgapci0: child drmn0 requested pci_enable_io syslogd: last message repeated 1 times kernel: [drm] Memory usable by graphics device =3D 2048M kernel: Failed to add WC MTRR for [0xe0000000-0xefffffff]: -22; performance= may suffer kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). kernel: [drm] Driver supports precise vblank timestamp query. kernel: [drm] Connector LVDS-1: get mode from tunables: kernel: [drm] - kern.vt.fb.modes.LVDS-1 kernel: [drm] - kern.vt.fb.default_mode kernel: [drm] Connector VGA-1: get mode from tunables: kernel: [drm] - kern.vt.fb.modes.VGA-1 kernel: [drm] - kern.vt.fb.default_mode kernel: [drm] Connector HDMI-A-1: get mode from tunables: kernel: [drm] - kern.vt.fb.modes.HDMI-A-1 kernel: [drm] - kern.vt.fb.default_mode kernel: [drm] Connector DP-1: get mode from tunables: kernel: [drm] - kern.vt.fb.modes.DP-1 kernel: [drm] - kern.vt.fb.default_mode kernel: [drm] Initialized i915 1.6.0 20170123 for drmn0 on minor 0 kernel: VT: Replacing driver "efifb" with new "fb". kernel: start FB_INFO: kernel: type=3D11 height=3D768 width=3D1366 depth=3D32 kernel: cmsize=3D16 size=3D4227072 kernel: pbase=3D0xe0236000 vbase=3D0xfffff800e0236000 kernel: name=3Ddrmn0 flags=3D0x0 stride=3D5504 bpp=3D32 kernel: cmap[0]=3D0 cmap[1]=3D7f0000 cmap[2]=3D7f00 cmap[3]=3Dc4a000 kernel: end FB_INFO kernel: drmn0: fb0: inteldrmfb frame buffer device I never had problems with the i915kms.ko module from kernel. However, becau= se of the announce that its code will be removed in 13.0, I made the transitit= ion to the drm-kmod passage. I am on 12.0-RELEASE. The port installed by the metaport is drm-fbsd12.0-kmod-g20181210. The details of my graphic controller can be find here: https://ark.intel.com//products/72061/Intel-Celeron-Processor-1007U-2M-Cach= e-1_50-GHz A similar issue has been discussed in the past here: https://github.com/FreeBSDDesktop/DEPRECATED-freebsd-base-graphics/issues/1= 44 I was unsure if it was better to report the bug here or on github. Finally I thought that a report here was a good idea as it does concern FreeBSD as an= OS; if an issue is opened on github (as it probably should) it can be easily linked. Moreover, this bug report will probably be easier to find, in particular by users not used to github. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-234044-7788>