I re-installed the user land in my jail after re-compiling the sources and
from that point I don't have the issue anymore. Seems like some libraries
were not properly updated or something like that (maybe libva).
In any case if it happens again I'll try to generate a test video with
ffmpeg and try
On 2020-08-16 22:23, Alexandre Levy wrote:
Any suggestions ?
Are there any simple steps to reproduce this?
--HPS
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
For reference, below is the backtrace then further down I printed the
structures I could access :
#0 __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55
#1 doadump (textdump=0) at /usr/src/sys/kern/kern_shutdown.c:394
#2 0x8049c26a in db_dump (dummy=,
dummy2=, dummy3=, dummy4=) a
On 2020-08-16 22:23, Alexandre Levy wrote:
(kgdb) p *m
$2 = {plinks = {q = {tqe_next = 0x578491b51dd60510, tqe_prev =
0xd78c11bd9dde8518}, s = {ss = {sle_next = 0x578491b51dd60510}}, memguard =
{p = 6306325585301210384,
v = 15531808720989095192}, uma = {slab = 0x578491b51dd60510, zone =
0x
"m" is not NULL :
(kgdb) frame 16
#16 0x80ec23ed in vm_page_busy_acquire (m=0xfe00040ff9e8,
allocflags=16) at /usr/src/sys/vm/vm_page.c:884
(kgdb) p *m
$2 = {plinks = {q = {tqe_next = 0x578491b51dd60510, tqe_prev =
0xd78c11bd9dde8518}, s = {ss = {sle_next = 0x578491b51dd60510}}, memgua
On 2020-08-16 17:28, Alexandre Levy wrote:
Now at intel_freebsd.c:193 (frame #17) the driver calls
vm_page_busy_acquire(m, VM_ALLOC_WAITFAIL). 'm' is the page grabbed from
vm_obj of the calling frame.
Can you check if "m" is NULL at this point?
--HPS
___
Hi,
I looked at the crash dump and the code more closely:
#18 0x82be1c5f in i915_gem_fault (dummy=,
vmf=)
at
/usr/ports/graphics/drm-devel-kmod/work/drm-kmod-drm_v5.3_4/drivers/gpu/drm/i915/gem/i915_gem_mman.c:367
(kgdb) p area->vm_obj->lock
$43 = {lock_object = {lo_name = 0x8
Hi,
I could finally generate a crash dump even with a black screen, I had to
guess I was in the crash handler and I type "dump" and enter which worked.
The driver logs "[drm] Cannot find any crtc or sizes" which I guess is the
reason why I couldn't see anything on my screen.
Back to the initial p
Hi,
On 2020-08-10 12:59, Alexandre Levy wrote:
Looking at the code, the error happens during the call to VM_OBJECT_WLOCK
(memory page locking for write ?) in the intel_freebsd.c (see [1] below).
I'm out for a few days but I'll try to dig more into it when I'm back next
weekend although I have no
On 2020-08-10 12:59, Alexandre Levy wrote:
I could reproduce with GENERIC kernel and i915 kms compiled with DEBUG and
I got this additional info (still no crash dump though) :
If you have the debugger enabled, you will need to type "dump" in the
crash handler to get the core-dump.
--HPS
I could reproduce with GENERIC kernel and i915 kms compiled with DEBUG and
I got this additional info (still no crash dump though) :
Kernel page fault with the following non-sleepable locks held:
kernel: exclusive rw vm object (vm object) r = 0 (0xf8037533bc60)
locked @
/usr/ports/graphics/drm
Ah thanks, I was doing a make config-recursive and that didn't show the
DEBUG option. It's recompiling the module with DEBUG now.
Le lun. 10 août 2020 à 09:43, Hans Petter Selasky a
écrit :
> On 2020-08-10 10:41, Alexandre Levy wrote:
> > I'm recompiling the kernel using GENERIC at the moment bu
On 2020-08-10 10:41, Alexandre Levy wrote:
I'm recompiling the kernel using GENERIC at the moment but I'm not sure how
to enable debugging in i915 kms, there is no compile option for that, am I
missing something ?
Type:
make config
Before building the i915kms port, then there should be a DEBU
I'm recompiling the kernel using GENERIC at the moment but I'm not sure how
to enable debugging in i915 kms, there is no compile option for that, am I
missing something ?
Le lun. 10 août 2020 à 08:44, Hans Petter Selasky a
écrit :
> Hi,
>
> On 2020-08-10 00:19, Alexandre Levy wrote:
> > Hi,
> >
Hi,
On 2020-08-10 00:19, Alexandre Levy wrote:
Hi,
I installed the port drm-devel-kmod for Plex to be able to transcode videos
using the integrated GPU of my Intel Celeron G5900.
I'm running r364031 and the kernel is compiled with GENERIC-NODEBUG profile.
Transcoding has been working fine for
Hi,
I installed the port drm-devel-kmod for Plex to be able to transcode videos
using the integrated GPU of my Intel Celeron G5900.
I'm running r364031 and the kernel is compiled with GENERIC-NODEBUG profile.
Transcoding has been working fine for quite a while now but one video
transcoding is ca
16 matches
Mail list logo
