Hello,
I'm getting this panic every time trying to build rust in poudriere.
Until the recent time I was able to build rust successfully on
13-CURRENT, but now I'm getting out of space and the panic.
My system is 13.0-CURRENT r340723 amd64. It's on laptop with i5 GPU (2nd
Generation) and 12GB RAM. Any suggestions what I can do with that?
smsh-zfs% pkg info | grep drm
drm-devel-kmod-4.16.g20181119 DRM modules for the linuxkpi-based KMS
components (development version)
drm-kmod-g20180930 Metaport of DRM modules for the
linuxkpi-based KMS components
from dmesg:
swap_pager_getswapspace(19): failed
swap_pager_getswapspace(12): failed
WARNING !drm_modeset_is_locked(>mutex) failed at
/wrkdirs/usr/ports/graphics/drm-devel-kmod/work/kms-drm-5f3b167/drivers/gpu/drm/drm_atomic_helper.c:577
WARNING !drm_modeset_is_locked(>mutex) failed at
/wrkdirs/usr/ports/graphics/drm-devel-kmod/work/kms-drm-5f3b167/drivers/gpu/drm/drm_atomic_helper.c:577
WARNING !drm_modeset_is_locked(>mode_config.connection_mutex)
failed at
/wrkdirs/usr/ports/graphics/drm-devel-kmod/work/kms-drm-5f3b167/drivers/gpu/drm/drm_atomic_helper.c:622
WARNING !drm_modeset_is_locked(>mode_config.connection_mutex)
failed at
/wrkdirs/usr/ports/graphics/drm-devel-kmod/work/kms-drm-5f3b167/drivers/gpu/drm/drm_atomic_helper.c:622
WARN_ON(!drm_modeset_is_locked(>dev->mode_config.connection_mutex))
WARNING !drm_modeset_is_locked(>mutex) failed at
/wrkdirs/usr/ports/graphics/drm-devel-kmod/work/kms-drm-5f3b167/drivers/gpu/drm/drm_atomic_helper.c:821
WARNING !drm_modeset_is_locked(>mutex) failed at
/wrkdirs/usr/ports/graphics/drm-devel-kmod/work/kms-drm-5f3b167/drivers/gpu/drm/drm_atomic_helper.c:821
WARNING !drm_modeset_is_locked(>mutex) failed at
/wrkdirs/usr/ports/graphics/drm-devel-kmod/work/kms-drm-5f3b167/drivers/gpu/drm/drm_atomic_helper.c:821
WARNING !drm_modeset_is_locked(>mutex) failed at
/wrkdirs/usr/ports/graphics/drm-devel-kmod/work/kms-drm-5f3b167/drivers/gpu/drm/drm_atomic_helper.c:821
WARNING !drm_modeset_is_locked(>mutex) failed at
/wrkdirs/usr/ports/graphics/drm-devel-kmod/work/kms-drm-5f3b167/drivers/gpu/drm/drm_atomic_helper.c:821
WARNING !drm_modeset_is_locked(>mutex) failed at
/wrkdirs/usr/ports/graphics/drm-devel-kmod/work/kms-drm-5f3b167/drivers/gpu/drm/drm_atomic_helper.c:821
WARN_ON(!drm_modeset_is_locked(>dev->mode_config.connection_mutex))WARN_ON(!drm_modeset_is_locked(>dev->mode_config.connection_mutex))WARN_ON(!drm_modeset_is_locked(>dev->mode_config.connection_mutex))WARN_ON(!drm_modeset_is_locked(>dev->mode_config.connection_mutex))WARN_ON(!mutex_is_locked(>struct_mutex))WARN_ON(!mutex_is_locked(>struct_mutex))
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x28
fault code = supervisor write data, page not present
instruction pointer = 0x20:0x80bad254
stack pointer = 0x28:0xfe59ccd0
frame pointer = 0x28:0xfe59cd00
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= resume, IOPL = 0
current process = 24 (laundry: dom0)
trap number = 12
panic: page fault
cpuid = 0
time = 1543321280
KDB: stack backtrace:
#0 0x80ba05f7 at kdb_backtrace+0x67
#1 0x80b5ab83 at vpanic+0x1a3
#2 0x80b5a9d3 at panic+0x43
#3 0x80ff66ff at trap_fatal+0x35f
#4 0x80ff6759 at trap_pfault+0x49
#5 0x80ff5e13 at trap+0x2a3
#6 0x80fd1f67 at calltrap+0x8
#7 0x829e1905 at linux_add_to_sleepqueue+0x35
#8 0x829e1779 at linux_wait_event_common+0x109
#9 0x8299f9cf at drm_wait_one_vblank+0x22f
#10 0x82891f97 at ironlake_crtc_enable+0xe17
#11 0x8289d294 at intel_update_crtc+0x94
#12 0x82896615 at intel_update_crtcs+0x55
#13 0x828a17c4 at intel_atomic_commit_tail+0x724
#14 0x8289ecfc at intel_atomic_commit+0x2cc
#15 0x82980566 at restore_fbdev_mode_atomic+0x1b6
#16 0x8297c83e at drm_fb_helper_restore_fbdev_mode_unlocked+0x7e
#17 0x829a2205 at vt_kms_postswitch+0x125
Uptime: 4h43m45s
I also have this in dmesg. It may be related to my experiments with
suspend/resume in recent past:
[drm] Unable to create a private tmpfs mount, hugepage support will be
disabled(-19).
__pm_runtime_resume not implemented -- see your local kernel hacker
Failed to add WC MTRR for [0xb000-0xbfff]: -22; performance may
suffer
[drm] Got stolen memory base 0xada0, size 0x200
[drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[drm] Driver supports precise vblank timestamp query.
[drm] Connector LVDS-1: get mode from tunables:
[drm] - kern.vt.fb.modes.LVDS-1
[drm] - kern.vt.fb.default_mode
pm_runtime_mark_last_busy not implemented -- see your local kernel hacker
__pm_runtime_suspend not implemented --
