Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 1 Nov 2018 11:53:46 -0500
From:      "Matthew D. Fuller" <fullermd@over-yonder.net>
To:        Johannes Lundberg <johalun0@gmail.com>
Cc:        Steve Kargl <sgk@troutmask.apl.washington.edu>, x11-list freebsd <freebsd-x11@freebsd.org>, Niclas Zeising <zeising@freebsd.org>
Subject:   Re: drm2 again
Message-ID:  <20181101165346.GI78336@over-yonder.net>
In-Reply-To: <CAECmPwvi-H4QfxWpTvXGAzY0ciPPUU7K4XDM0YmCUV%2BKs%2BG_KQ@mail.gmail.com>
References:  <CAECmPwu3ndCzQa0S2hQHmyOoXQaZRAwaUjGGcApPEX3dZXH%2Byw@mail.gmail.com> <20181031194726.GA957@troutmask.apl.washington.edu> <CAECmPwsPzF-bhF0AR9PjLUJoMD7xNF=usJEa3cpnFCSvuEJkuA@mail.gmail.com> <20181031201319.GA896@troutmask.apl.washington.edu> <CAECmPwusuHsEqPArj0uYh%2B4kiEKzsFXDaiZzgcv4pmvE0WhVSw@mail.gmail.com> <f28a9824-c263-4d10-107c-5ec7983dae4d@freebsd.org> <20181031223253.GA915@troutmask.apl.washington.edu> <CAECmPwu7tVWTD-UAC0F%2BVJw92UW5uODE5QB44Yp2B%2BpHWXgOaA@mail.gmail.com> <20181101145749.GB6969@troutmask.apl.washington.edu> <CAECmPwvi-H4QfxWpTvXGAzY0ciPPUU7K4XDM0YmCUV%2BKs%2BG_KQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 01, 2018 at 03:04:09PM +0000 I heard the voice of
Johannes Lundberg, and lo! it spake thus:
>
> There are also reports in the ML from someone using -stable or
> -devel on the same hardware as you. Maybe that was -devel?

% pkg info -x 'drm-.*-kmod'
drm-next-kmod-4.11.g20181027    # though it's got a couple months
                                # uptime, so it's _running_ an older
                                # version ATM...

% kldstat -v | grep radeonkms
 4    1 0xffffffff82819000 158851   radeonkms.ko (/boot/modules/radeonkms.ko)

% dmesg | grep initializing
[drm] initializing kernel modesetting (CAICOS 0x1002:0x6779 0x1682:0x3207 0x00).

% grep Chipset /var/log/Xorg.0.log
[    48.378] (--) RADEON(0): Chipset: "CAICOS" (ChipID = 0x6779)


It ran fine back in ~early summer with -stable as well.  I got
occasional bursts of the fence_wait errors Steve talked about, but
they never seemed to have much impact on the running.  Haven't seen
once since switching [back] to -devel.


-- 
Matthew Fuller     (MF4839)   |  fullermd@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
           On the Internet, nobody can hear you scream.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20181101165346.GI78336>