Hi!
On 2019-10-24 01:32, Clay Daniels Jr. wrote:
Niclas, my last working install of 13.0 Current was r353072 of Oct 4th. The
next week's r353427 of Oct 11th did not work and I reverted to r353072 for
a week. Then r353709 of Oct 18th did not work, and when I tried to revert
back to r353072 it
Niclas, my last working install of 13.0 Current was r353072 of Oct 4th. The
next week's r353427 of Oct 11th did not work and I reverted to r353072 for
a week. Then r353709 of Oct 18th did not work, and when I tried to revert
back to r353072 it does not work either. These were install from ports,
On 2019-10-23 21:50, Clay Daniels Jr. wrote:
r353709
Looked promising, but failed:
Loaded r353709
make install drm-kmod, all 3 installed
(drm-devel-kmod, drm-current-kmod, & gpu-firmware-kmod)
set /etc/rc.conf & /boot/loader.conf configs as usual
rebooted and looked good, video tingling
pkg
sorry, should be
all 3 installed
(drm-kmod, drm-current-kmod, & gpu-firmware-kmod)
On Wed, Oct 23, 2019 at 2:50 PM Clay Daniels Jr.
wrote:
> r353709
> Looked promising, but failed:
>
> Loaded r353709
> make install drm-kmod, all 3 installed
> (drm-devel-kmod, drm-current-kmod, &
r353709
Looked promising, but failed:
Loaded r353709
make install drm-kmod, all 3 installed
(drm-devel-kmod, drm-current-kmod, & gpu-firmware-kmod)
set /etc/rc.conf & /boot/loader.conf configs as usual
rebooted and looked good, video tingling
pkg install xorg
rebooted and ran startx
panic:
On 2019-10-21 10:13, Niclas Zeising wrote:
On 2019-10-17 23:05, Mark Johnston wrote:
On Thu, Oct 17, 2019 at 10:31:12PM +0200, Niclas Zeising wrote:
On 2019-10-17 21:53, ma...@freebsd.org wrote:
On Thu, Oct 17, 2019 at 03:03:51PM +0200, Niclas Zeising wrote:
On 2019-10-16 18:57, Neel Chauhan
On 2019-10-21 11:08, Yuri Pankov wrote:
Niclas Zeising wrote:
On 2019-10-20 08:45, Yuri Pankov wrote:
On 10/18/2019 8:01 AM, Xin Li wrote:
Another (semi-fixed!) data point -- I can confirm that with if
(vm_page_sleep_if_busy(page, "linuxkpi"))
-> if (!vm_page_busy_acquire(page,
Niclas Zeising wrote:
On 2019-10-20 08:45, Yuri Pankov wrote:
On 10/18/2019 8:01 AM, Xin Li wrote:
Another (semi-fixed!) data point -- I can confirm that with if
(vm_page_sleep_if_busy(page, "linuxkpi"))
-> if (!vm_page_busy_acquire(page, VM_ALLOC_WAITFAIL)) change and
mjg@'s earlier patch
On 2019-10-17 23:05, Mark Johnston wrote:
On Thu, Oct 17, 2019 at 10:31:12PM +0200, Niclas Zeising wrote:
On 2019-10-17 21:53, ma...@freebsd.org wrote:
On Thu, Oct 17, 2019 at 03:03:51PM +0200, Niclas Zeising wrote:
On 2019-10-16 18:57, Neel Chauhan wrote:
While drm-current-kmod worked for a
On 2019-10-21 09:01, Thomas Mueller wrote:
from Neel Chauhan:
For me, the following code is still necessary for me (HP Spectre x360
2018), which is the remaining parts of the patches not committed if you
are using a recent kernel. I don't know about you all ThinkPad users, it
should still
On 2019-10-20 08:45, Yuri Pankov wrote:
On 10/18/2019 8:01 AM, Xin Li wrote:
Another (semi-fixed!) data point -- I can confirm that with if
(vm_page_sleep_if_busy(page, "linuxkpi"))
-> if (!vm_page_busy_acquire(page, VM_ALLOC_WAITFAIL)) change and
mjg@'s earlier patch at
from Neel Chauhan:
> For me, the following code is still necessary for me (HP Spectre x360
> 2018), which is the remaining parts of the patches not committed if you
> are using a recent kernel. I don't know about you all ThinkPad users, it
> should still apply as it's Intel in general not just
On 10/21/2019 4:14 AM, Neel Chauhan wrote:
For me, the following code is still necessary for me (HP Spectre x360
2018), which is the remaining parts of the patches not committed if you
are using a recent kernel. I don't know about you all ThinkPad users, it
should still apply as it's Intel in
For me, the following code is still necessary for me (HP Spectre x360
2018), which is the remaining parts of the patches not committed if you
are using a recent kernel. I don't know about you all ThinkPad users, it
should still apply as it's Intel in general not just HP or Lenovo.
Without
On 10/18/2019 8:01 AM, Xin Li wrote:
Another (semi-fixed!) data point -- I can confirm that with if
(vm_page_sleep_if_busy(page, "linuxkpi"))
-> if (!vm_page_busy_acquire(page, VM_ALLOC_WAITFAIL)) change and
mjg@'s earlier patch at
https://people.freebsd.org/~mjg/pmap-fict-invl.diff (please
>> Another (semi-fixed!) data point -- I can confirm that with if
>> (vm_page_sleep_if_busy(page, "linuxkpi"))
>> -> if (!vm_page_busy_acquire(page, VM_ALLOC_WAITFAIL)) change and
>> mjg@'s earlier patch at
>> https://people.freebsd.org/~mjg/pmap-fict-invl.diff (please commit it) ,
>> the latest
Have you patched with mjg@'s pmap-fict-invl.diff? The panic seems to be
similar...
Cheers,
On Fri, Oct 18, 2019 at 2:01 AM Neel Chauhan wrote:
> This still panicks for me, but with a different error.
>
> https://i.postimg.cc/K8nxF57G/IMG-20191018-045338.jpg
>
> I really should be sleeping but
> Another (semi-fixed!) data point -- I can confirm that with if
> (vm_page_sleep_if_busy(page, "linuxkpi"))
> -> if (!vm_page_busy_acquire(page, VM_ALLOC_WAITFAIL)) change and
> mjg@'s earlier patch at
> https://people.freebsd.org/~mjg/pmap-fict-invl.diff (please commit it) ,
> the latest
Hey, thanks for the patch and the CC, coincidentally I had some
time to look into this again.
On dj., oct. 17 2019, ma...@freebsd.org wrote:
I believe it was the recent work on the vm page busy state,
r353539
specifically. This patch should fix it; we don't yet have a
__FreeBSD_version
This still panicks for me, but with a different error.
https://i.postimg.cc/K8nxF57G/IMG-20191018-045338.jpg
I really should be sleeping but can't because I have to use an older
kernel to have working graphics. Thanks, Netflix for making my life
harder.
-Neel
On 2019-10-18 01:01, Xin Li
Another (semi-fixed!) data point -- I can confirm that with if
(vm_page_sleep_if_busy(page, "linuxkpi"))
-> if (!vm_page_busy_acquire(page, VM_ALLOC_WAITFAIL)) change and
mjg@'s earlier patch at
https://people.freebsd.org/~mjg/pmap-fict-invl.diff (please commit it) ,
the latest drm-v5.0 branch of
However, the patch to drm-kmod doesn't work for me. I tried both
drm-devel-kmod and drm-current-kmod.
https://i.imgur.com/81JvaOO.jpg
-Neel
===
https://www.neelc.org/
On 2019-10-17 17:35, Eirik Øverby wrote:
On 10/17/19 11:29 PM, Eirik Øverby wrote:
On 10/17/19 10:31 PM, Niclas Zeising
On 10/17/19 11:29 PM, Eirik Øverby wrote:
> On 10/17/19 10:31 PM, Niclas Zeising wrote:
>> On 2019-10-17 21:53, ma...@freebsd.org wrote:
>>> On Thu, Oct 17, 2019 at 03:03:51PM +0200, Niclas Zeising wrote:
..
>>> I believe it was the recent work on the vm page busy state, r353539
>>>
On 10/17/19 10:31 PM, Niclas Zeising wrote:
> On 2019-10-17 21:53, ma...@freebsd.org wrote:
>> On Thu, Oct 17, 2019 at 03:03:51PM +0200, Niclas Zeising wrote:
>>> On 2019-10-16 18:57, Neel Chauhan wrote:
While drm-current-kmod worked for a little while, it broke with r353645.
On Thu, Oct 17, 2019 at 10:31:12PM +0200, Niclas Zeising wrote:
> On 2019-10-17 21:53, ma...@freebsd.org wrote:
> > On Thu, Oct 17, 2019 at 03:03:51PM +0200, Niclas Zeising wrote:
> >> On 2019-10-16 18:57, Neel Chauhan wrote:
> >>> While drm-current-kmod worked for a little while, it broke with
On 2019-10-17 21:53, ma...@freebsd.org wrote:
On Thu, Oct 17, 2019 at 03:03:51PM +0200, Niclas Zeising wrote:
On 2019-10-16 18:57, Neel Chauhan wrote:
While drm-current-kmod worked for a little while, it broke with r353645.
https://i.imgur.com/Q5nYZf2.jpg
I'm using the same HP Spectre that I
On Thu, Oct 17, 2019 at 03:03:51PM +0200, Niclas Zeising wrote:
> On 2019-10-16 18:57, Neel Chauhan wrote:
> > While drm-current-kmod worked for a little while, it broke with r353645.
> >
> > https://i.imgur.com/Q5nYZf2.jpg
> >
> > I'm using the same HP Spectre that I used earlier (where it
On 10/17/19 3:03 PM, Niclas Zeising wrote:> On 2019-10-16 18:57, Neel Chauhan
wrote:
>> While drm-current-kmod worked for a little while, it broke with r353645.
>>
>> https://i.imgur.com/Q5nYZf2.jpg
>>
>> I'm using the same HP Spectre that I used earlier (where it worked and where
>> it
On 2019-10-16 18:57, Neel Chauhan wrote:
While drm-current-kmod worked for a little while, it broke with r353645.
https://i.imgur.com/Q5nYZf2.jpg
I'm using the same HP Spectre that I used earlier (where it worked and
where it panicked).
That commit looks unrelated, it touches the wbwd and
While drm-current-kmod worked for a little while, it broke with r353645.
https://i.imgur.com/Q5nYZf2.jpg
I'm using the same HP Spectre that I used earlier (where it worked and
where it panicked).
-Neel
===
https://www.neelc.org/
On 2019-10-13 10:37, Mateusz Guzik wrote:
On 10/13/19,
On 10/13/19, Evilham wrote:
> Hello,
>
> I somehow had managed to mess up my build system and only
> yesterday got it back to compiling properly.
>
So to be clear, there is an unrelated bug where it seems the module can
decide to abort loading and then it crashes in pseudofs. This can happen
if
Hello,
I somehow had managed to mess up my build system and only
yesterday got it back to compiling properly.
On ds., oct. 12 2019, Mateusz Guzik wrote:
Try this:
https://people.freebsd.org/~mjg/pmap-fict-invl.diff
I tested this patch on top of r353449 and a panic is still
ocurring
The patch doesn't work for me on i915kms on a HP Spectre x360
13-p0043dx. I get a panic
Screenshot:
https://user-images.githubusercontent.com/5403564/66688014-d1a16700-ec52-11e9-9c3b-902f49e311de.png
As of now, I'm using an older kernel.
-Neel
===
https://www.neelc.org/
On 2019-10-11
The patch doesn't work for me on i915kms on a HP Spectre x360
13-p0043dx. I get a panic
Screenshot:
https://user-images.githubusercontent.com/5403564/66688014-d1a16700-ec52-11e9-9c3b-902f49e311de.png
As of now, I'm using an older kernel.
-Neel
===
https://www.neelc.org/
On 2019-10-11
Try this:
https://people.freebsd.org/~mjg/pmap-fict-invl.diff
On 10/12/19, Neel Chauhan wrote:
> The patch doesn't work for me on i915kms on a HP Spectre x360
> 13-p0043dx. I get a panic
>
> Screenshot:
>
On 2019-10-10 13:44, Mateusz Guzik wrote:
> 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
>
That patch worked for me also. The patch applied clean when I used
'wget' to retrieve
On 19. 10. 10., Mateusz Guzik wrote:
> 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
This patch fixed a similar problem for me. FYI, I am using
drm-devel-kmod for "AMD Ryzen 5
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 wrote:
> On 2019-10-10 12:21, Mateusz Guzik wrote:
>> Try this:
>>
>> http://dpaste.com/0P2MXF6
>>
>> if it still
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
Try this:
http://dpaste.com/0P2MXF6
if it still fails, provide the panic info + the first debug line(the
one with "pv_table").
On 10/10/19, Thomas Laus wrote:
> List:
>
> I am still getting kernel panics on my laptop after the recent changes
> made to /sys/amd64/amd64/pmap.c.
>
> The updated
List:
I am still getting kernel panics on my laptop after the recent changes
made to /sys/amd64/amd64/pmap.c.
The updated pmap.c works on my Skylake build machine but panics on my
laptop. I always build on the faster computer and perform a
installkernel and installworld from a nfs share. The
41 matches
Mail list logo
