From owner-freebsd-current@freebsd.org Tue Nov 27 12:42:42 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 54995114A441 for ; Tue, 27 Nov 2018 12:42:42 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward100j.mail.yandex.net (forward100j.mail.yandex.net [IPv6:2a02:6b8:0:801:2::100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0ACCC77A4D for ; Tue, 27 Nov 2018 12:42:40 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from mxback5o.mail.yandex.net (mxback5o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::1f]) by forward100j.mail.yandex.net (Yandex) with ESMTP id 824672080827 for ; Tue, 27 Nov 2018 15:42:30 +0300 (MSK) Received: from smtp3p.mail.yandex.net (smtp3p.mail.yandex.net [2a02:6b8:0:1472:2741:0:8b6:8]) by mxback5o.mail.yandex.net (nwsmtp/Yandex) with ESMTP id roI4rPHh8u-gUxeg4mQ; Tue, 27 Nov 2018 15:42:30 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1543322550; bh=QgU+mzJIu4v/XcdGJWzWxjg2KmmXKMDaBRJ/bB6qEDE=; h=To:From:Subject:Message-ID:Date; b=mkzTRjwVvYc8bKyP4+PsMj9FXRHUcdJpYmrgXACD9FVZ+lvNfJY5GXNa3552DZwQ4 3itFNRWH8Ph5vK6qTm0Ip1SMLJuZvBVxf3ce43QRkqIkJHCEIX6wYopKZR/42M4LfV qivzVgLlb+27YptmtXKd5PTR8jKowe0is9GVzcRY= Received: by smtp3p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id JPV9aGl0FE-gTpCjra3; Tue, 27 Nov 2018 15:42:29 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1543322549; bh=QgU+mzJIu4v/XcdGJWzWxjg2KmmXKMDaBRJ/bB6qEDE=; h=To:From:Subject:Message-ID:Date; b=nfkHCez4uCbSXDblw7LkJU54wxlF2dG+MXNymAchQcEASh+q1vnEEpxqPZaFU1HJP Nt39Gy39PqkZbc3ec+zKlVrAAIrYNyMPFBfzhJBcoea48ptZvAi8wZoR1hb3EvfQto 3L7LfkABHOhylTalDCFHgVFXz/M3PrE4VwFjMbFI= Authentication-Results: smtp3p.mail.yandex.net; dkim=pass header.i=@yandex.ru To: FreeBSD Current From: Ruslan Makhmatkhanov Subject: drm kmod kernel panic Message-ID: <854beb67-941e-e3d6-1bab-e45cd0b39447@yandex.ru> Date: Tue, 27 Nov 2018 15:36:19 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 0ACCC77A4D X-Spamd-Result: default: False [-5.83 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[yandex.ru]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a02:6b8:0::/52]; FREEMAIL_FROM(0.00)[yandex.ru]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[4]; RCVD_TLS_LAST(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[yandex.ru:+]; DMARC_POLICY_ALLOW(-0.50)[yandex.ru,none]; MX_GOOD(-0.01)[mx.yandex.ru,mx.yandex.ru,mx.yandex.ru,mx.yandex.ru,mx.yandex.ru]; TO_MATCH_ENVRCPT_ALL(0.00)[]; IP_SCORE(-1.72)[ipnet: 2a02:6b8::/32(-4.81), asn: 13238(-3.82), country: RU(0.01)]; NEURAL_HAM_SHORT(-1.00)[-0.995,0]; RCVD_IN_DNSWL_LOW(-0.10)[0.0.1.0.0.0.0.0.0.0.0.0.2.0.0.0.1.0.8.0.0.0.0.0.8.b.6.0.2.0.a.2.list.dnswl.org : 127.0.5.1]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[yandex.ru]; ASN(0.00)[asn:13238, ipnet:2a02:6b8::/32, country:RU]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Server: mx1.freebsd.org X-Mailman-Approved-At: Tue, 27 Nov 2018 12:49:30 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Nov 2018 12:42:42 -0000 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(&crtc->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(&crtc->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(&dev->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(&dev->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(&s->dev->mode_config.connection_mutex)) WARNING !drm_modeset_is_locked(&plane->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(&plane->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(&plane->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(&plane->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(&plane->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(&plane->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(&s->dev->mode_config.connection_mutex))WARN_ON(!drm_modeset_is_locked(&s->dev->mode_config.connection_mutex))WARN_ON(!drm_modeset_is_locked(&s->dev->mode_config.connection_mutex))WARN_ON(!drm_modeset_is_locked(&s->dev->mode_config.connection_mutex))WARN_ON(!mutex_is_locked(&dev->struct_mutex))WARN_ON(!mutex_is_locked(&dev->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:0xffffffff80bad254 stack pointer = 0x28:0xfffffe000059ccd0 frame pointer = 0x28:0xfffffe000059cd00 code segment = base 0x0, limit 0xfffff, 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 0xffffffff80ba05f7 at kdb_backtrace+0x67 #1 0xffffffff80b5ab83 at vpanic+0x1a3 #2 0xffffffff80b5a9d3 at panic+0x43 #3 0xffffffff80ff66ff at trap_fatal+0x35f #4 0xffffffff80ff6759 at trap_pfault+0x49 #5 0xffffffff80ff5e13 at trap+0x2a3 #6 0xffffffff80fd1f67 at calltrap+0x8 #7 0xffffffff829e1905 at linux_add_to_sleepqueue+0x35 #8 0xffffffff829e1779 at linux_wait_event_common+0x109 #9 0xffffffff8299f9cf at drm_wait_one_vblank+0x22f #10 0xffffffff82891f97 at ironlake_crtc_enable+0xe17 #11 0xffffffff8289d294 at intel_update_crtc+0x94 #12 0xffffffff82896615 at intel_update_crtcs+0x55 #13 0xffffffff828a17c4 at intel_atomic_commit_tail+0x724 #14 0xffffffff8289ecfc at intel_atomic_commit+0x2cc #15 0xffffffff82980566 at restore_fbdev_mode_atomic+0x1b6 #16 0xffffffff8297c83e at drm_fb_helper_restore_fbdev_mode_unlocked+0x7e #17 0xffffffff829a2205 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 [0xb0000000-0xbfffffff]: -22; performance may suffer [drm] Got stolen memory base 0xada00000, size 0x2000000 [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 -- see your local kernel hacker [drm] Connector VGA-1: get mode from tunables: [drm] - kern.vt.fb.modes.VGA-1 [drm] - kern.vt.fb.default_mode [drm] Connector HDMI-A-1: get mode from tunables: [drm] - kern.vt.fb.modes.HDMI-A-1 [drm] - kern.vt.fb.default_mode [drm] Connector DP-1: get mode from tunables: [drm] - kern.vt.fb.modes.DP-1 [drm] - kern.vt.fb.default_mode pm_runtime_get_if_in_use not implemented -- see your local kernel hacker sched_setscheduler_nocheck not implemented -- see your local kernel hacker sched_setscheduler_nocheck not implemented -- see your local kernel hacker register_oom_notifier not implemented -- see your local kernel hacker acpi_lid_notifier_register not implemented -- see your local kernel hacker [drm] Initialized i915 1.6.0 20171222 for drmn0 on minor 0 register_acpi_notifier not implemented -- see your local kernel hacker async_schedule is dodgy -- see your local kernel hacker pm_runtime_set_autosuspend_delay not implemented -- see your local kernel hacker async_synchronize_cookie not implemented -- see your local kernel hacker __pm_runtime_use_autosuspend not implemented -- see your local kernel hacker VT: Replacing driver "vga" with new "fb". -- Regards, Ruslan T.O.S. Of Reality