Date: Sat, 20 Feb 2021 05:45:23 -0500 From: Steven Friedrich <FreeBSD@twc.com> To: freebsd-questions@freebsd.org Subject: Re: [drm] Got stolen memory base 0x8a800000, size 0x2000000 Message-ID: <3029859.bT80LyP3VS@freebsd> In-Reply-To: <4840868.YNO7O01DYZ@freebsd> References: <16988477.sFgvYJuXru@freebsd> <4301c070-a85d-9951-eff7-91e49740b678@nomadlogic.org> <4840868.YNO7O01DYZ@freebsd>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, 19 February 2021 21:54:08 EST Steven Friedrich wrote:
> On Friday, 19 February 2021 13:27:49 EST Pete Wright wrote:
> > On 2/19/21 2:23 AM, Steven Friedrich wrote:
> > > How can I fix or avoid this?
> > >
> > > I do see some odd graphic corruption overlayed on my consoles.
> > >
> > > What will I lose if I turn DRM off by not using :
> > > drm-fbsd12.0-kmod-4.16.g20201016_1 DRM modules for the linuxkpi-based
> > > KMS
> > > components
> > > drm-kmod-g20190710_1 Metaport of DRM modules for the
> > > linuxkpi-based KMS components
> > > drm_info-2.2.0_1 Small utility to dump info about DRM
> > > devices
> > > libdrm-2.4.104,1 Userspace interface to kernel Direct
> > > Rendering Module services
> > > s
> >
> > You will not have hardware accelerated graphics is using Xorg if the
> > drm-kmod is not present, which may or may be an issue depending on your
> > use-case. It may also effect power management as well, for example on
> > my laptop if I don't load the kmod for my Nvidia GPU I get much worse
> > battery life. So that would be something to look out for.
> >
> > To help you fix this it would be helpful to provide the following:
> > 1. FreeBSD release (uname -a)
> > 2. Graphics hardware (Intel i915 vs AMD)
> > 3. Additional logging/debugging information. For example if you can
> > provide more context of the error in your logs, and if there are repro
> > steps.
> >
> > Cheers,
> > -pete
>
> Thanks for the reply, Pete.
> After I sent that email, I figured out how to make my signature reflect my
> uname output.
> I have a i7-8700 with integrated UHD-630 graphics.
> I have no idea where t look, beyond dmesg, for ,re info regarding this
> "stolen" memory. It happens everytime I boot. No logs in /var/log by drm.
>
> root@FreeBSD(pts/1):/var/log # grep -i stolen *
> dmesg.today:[drm] Got stolen memory base 0x8a800000, size 0x2000000
> dmesg.yesterday:[drm] Got stolen memory base 0x8a800000, size 0x2000000
> dmesg.yesterday:[drm] Got stolen memory base 0x8a800000, size 0x2000000
> messages:Feb 19 06:00:17 FreeBSD kernel: [drm] Got stolen memory base
> 0x8a800000, size 0x2000000
> messages:Feb 19 05:04:41 FreeBSD kernel: [drm] Got stolen memory base
> 0x8a800000, size 0x2000000
> messages:Feb 19 16:42:41 FreeBSD kernel: [drm] Got stolen memory base
> 0x8a800000, size 0x2000000
> messages:Feb 19 16:59:01 FreeBSD kernel: [drm] Got stolen memory base
> 0x8a800000, size 0x2000000
> messages:Feb 19 18:23:36 FreeBSD kernel: [drm] Got stolen memory base
> 0x8a800000, size 0x2000000
Here's a better version of the original report:
real memory = 17179869184 (16384 MB)
avail memory = 16294457344 (15539 MB)
unknown: memory range not supported
pci0: <memory, RAM> at device 20.2 (no driver attached)
[drm] Got stolen memory base 0x8a800000, size 0x2000000
Here's the device as reported by pciconf -lv:
none1@pci0:0:20:2: class=0x050000 card=0x72708086 chip=0xa36f8086
rev=0x10 hdr=0x00
vendor = 'Intel Corporation'
device = 'Cannon Lake PCH Shared SRAM'
class = memory
subclass = RAM
After I invoke sddm, and start a plasma5 session, upon exiting sddm, my
consoles have corruption at the top of the screens. It doesn't scrolll off.
Remains until reboot. Another X11 session causes it to recur.
--
FreeBSD FreeBSD 12.2-RELEASE-p3 FreeBSD 12.2-RELEASE-p3 r369283 Special amd64
HP-Slimline 290-p0014 Desktop
Using integrated UHD Graphics 630
Built drm from /usr/ports/drm-kmod
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3029859.bT80LyP3VS>