While on the subject INTRNG - does anybody know the status of handling GPIO
interrupts with queue/kevent?
There were some patches before INTRNG, but they require some work.
Peter
> On 23 Feb 2018, at 07:25, Jon Brawn wrote:
>
> Wotcha Gang!
>
> In my travels through the arm64 GENERIC config
Dear all,
Please CC me as I am not subscribed.
On behalf of the FreeBSDDesktop team and thanks to the tireless efforts
of Johannes Lundberg and Hans Petter Selasky (hselasky), I am pleased to
report that the graphics/drm-next-kmod port just received an update to
Linux level 4.11 KMS/DRM for amdgp
∴sudo iocage activate zroot
∴sudo iocage list
+-+--+---+-+-+
| JID | NAME | STATE | RELEASE | IP4 |
+=+==+===+=+=+
+-+--+---+-+-+
∴sudo iocage create -r 11.1-RELEASE
Fetching: 11.1-RELEASE
Downloading : MANIFEST [#
On Sun, Feb 25, 2018 at 3:50 PM, Eitan Adler wrote:
> ∴sudo iocage activate zroot
> ∴sudo iocage list
> +-+--+---+-+-+
> | JID | NAME | STATE | RELEASE | IP4 |
> +=+==+===+=+=+
> +-+--+---+-+-+
> ∴sudo iocage create -r 11.1-R
On 25 February 2018 at 15:15, Alan Somers wrote:
> On Sun, Feb 25, 2018 at 3:50 PM, Eitan Adler wrote:
>> What should I do from here?
>>
>
> It's a well-known problem. You need to patch your copy of py-libzfs.
> Unfortunately, the patch hasn't been picked up by upstream because the port
> maint
Wotcha!
So, I’ve been using FreeBSD 12-CURRENT at various svn releases for a while now,
and I get quite a few “lock order reversal” dumps. The one I’ve got on my
screen at the moment is for ufs / bufwait / ufs:
root@brax:/usr/src/stand # lock order reversal:
1st 0xfd0003ec17e8 ufs (ufs) @
On 26/02/2018 07:18, Jon Brawn wrote:
> Wotcha!
>
> So, I’ve been using FreeBSD 12-CURRENT at various svn releases for a while
> now, and I get quite a few “lock order reversal” dumps. The one I’ve got on
> my screen at the moment is for ufs / bufwait / ufs:
>
> root@brax:/usr/src/stand # lock
