Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 10 Oct 2019 19:44:17 +0200
From:      Mateusz Guzik <mjguzik@gmail.com>
To:        lausts@acm.org
Cc:        FreeBSD Current <freebsd-current@freebsd.org>
Subject:   Re: DRM-current-kmod is still a problem at r353339
Message-ID:  <CAGudoHE755ig7KGuzq8uNY01K2Jcf-MKBjCp8kbpJAoiHdbQMA@mail.gmail.com>
In-Reply-To: <7ca3b30a-81f6-f79d-1486-7fd29765646f@acm.org>
References:  <c2566b4b-7b4b-78ba-b8b1-2a13e653ddd7@acm.org> <CAGudoHG_aAcqOfSi0GCW5-yw=6RcEXB0dz72mkgdJoz0guJMHA@mail.gmail.com> <7ca3b30a-81f6-f79d-1486-7fd29765646f@acm.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Probably whitespace issues from copypasting. I used dpaste since
people.freebsd.org was down.

It's up, so:
https://people.freebsd.org/~mjg/pmap-fict3.diff


On 10/10/19, Thomas Laus <lausts@acm.org> wrote:
> On 2019-10-10 12:21, Mateusz Guzik wrote:
>> Try this:
>>
>> http://dpaste.com/0P2MXF6
>>
>> if it still fails, provide the panic info + the first debug line(the
>> one with "pv_table").
>>
> This patch did not apply cleanly to my source tree checked out today.
> My pmap.c version is r353311.  I saved the file to filename pmap.diff
> and ran the patch utility with the command "patch -i pmap.diff" from the
> /sys/amd64/amd64 directory.  Should I be using a different utility to
> patch this file?  The FreeBSD patch utility has always worked for me in
> the past.
>
> Tom
>
> --
> Public Keys:
> PGP KeyID = 0x5F22FDC1
> GnuPG KeyID = 0x620836CF
>


-- 
Mateusz Guzik <mjguzik gmail.com>



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