From nobody Sat Jun 15 15:02:07 2024 X-Original-To: x11@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4W1fWR0Lv2z5NwVy for ; Sat, 15 Jun 2024 15:02:11 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4W1fWQ71T2z4P5l; Sat, 15 Jun 2024 15:02:10 +0000 (UTC) (envelope-from jbeich@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1718463731; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=1oEgYeYVK+BSZ5AuPy+W8QyRt1AQXYZhN265y9obDR4=; b=yr4KT/8EvGSZolCbEfR0q/Ly/kXo+rG2mr4Ox7gRiL+9+lcLWy9bqFhNJKFBrsWSLnYrmL gmWVwiqpLDFQPgXa/MEpWhOle7/Di6gJa0zUfae0EKEXycoOhCfF3hEJSOQ9Y7d+37jOcz XDOJS/RszZ4AM541DhmRaoY2nbNYKH3+sJDdDzXURyz6z+XL3cYhYw7w85TPwit/4m7Zq/ GxIpOjuAEjnVSbAmGLrnsrtfVG+J9pzSLm56IQn19sOY+obvppMtP3iJnOVfPY+9E1+olY lNV0Az8ldBXEQwW70dfRoOvg2pzNPyK+yrGNQZdsC79zZPscQHMwHnMWqqyegA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1718463731; a=rsa-sha256; cv=none; b=wskCZ2g0DECn4jhfvTNVaQmoNOxB3LgFSIJX8PeUhGA6uPD2KKtXAR/TNs4SiSeePwHU2N M1wgDZc7T4nXdcuR2F2uNkfApE3DOX7jlJp8IBv3sXKFQoMcOp2z6zNSCHTRUz8RxsZfo3 es9hbUvnA0Zw94711nUuyAhOYaHBrnTMewCCVZVG6JHImz1onfpn7D6uPrGeDnB41AIlnS UTzQDbA2ZLsYkXklc4DcMnASg/7s66m0X+kSL7DoADqtsi9jBZyoabzKMqO9lWjXOYQqTx cU5oLYBKEiQU3OV7gEnCsL34ZOnt0X6OAD8IP+DUQqgBsaDB6u2ai16GrFMvkA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1718463731; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=1oEgYeYVK+BSZ5AuPy+W8QyRt1AQXYZhN265y9obDR4=; b=FWjcbCekMzAaNcLOaAHh7l/fd4wuQa7D3pyXFjbr1DhSX3UnAxqIG9zNlbHX6o1NBc8CKH wCLc2FeI5EIAvlwsuS6/E7yQ0T7a4pLQwqgu2aEH2qFJ8skek7DTiP/hLMSv2M6oVySuHT NpH1tavhqwAWw9PxYj7QvVilq+tsjcE740uopI4y8SIGY2R3mkLe8dM++lpy31TmS5i7Qr MNcmUpsT41GsXSnugeWFXdWlGU6Q60hzWzdfutqbGOJpoo/c3DQl3bTrQrTrCIH0+2CT4W NNZIxzF60AJ03MIdF0N029CUJrlvxKahgjzvv5R1gdTf4rI7QqQlSgWmAgFIiw== Received: by freefall.freebsd.org (Postfix, from userid 1354) id E0CC914FB8; Sat, 15 Jun 2024 15:02:10 +0000 (UTC) From: Jan Beich To: cenhj Cc: x11@FreeBSD.org Subject: Re: Hyprland crash at start since 0.41.1 In-Reply-To: <9f8d671b-e48d-470b-9eb0-1a4d5c405476@zju.edu.cn> (cenhj@zju.edu.cn's message of "Sat, 15 Jun 2024 14:39:45 +0800") References: <9f8d671b-e48d-470b-9eb0-1a4d5c405476@zju.edu.cn> Date: Sat, 15 Jun 2024 17:02:07 +0200 Message-ID: <4j9u-5jww-wny@FreeBSD.org> List-Id: X11 List-Archive: https://lists.freebsd.org/archives/freebsd-x11 List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-x11@freebsd.org Sender: owner-freebsd-x11@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain (CC'ing x11@ list to let other users chime in if it's common) cenhj writes: > Hello, > > Since the port hyprland updated to 0.41.1, I can't run it at > start. The situation > is the same with 0.41.1_1. The system is FreeBSD 14.1-RELEASE, and > other ports are > up to date. What GPU and drm-*-kmod version? I use drm-515-kmod with Ubuntu fixups as described in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274770#c5 with Intel Skylake GT2 on -CURRENT where hyprland-0.41.1_1 appears to work fine. Maybe try https://cgit.FreeBSD.org/ports/commit/?id=a81bdbc5d906 but it's unlikely to be related to your kernel crash. > Every time entering `Hyprland` in TTY, the screen seems to get power > off and the system > is going to restart. Tried to get the crash log, but it is empty. I > can only attain info from When Hyprland itself crashes seat usually restores VT terminal. If the screen is blank switching VT tends to restore it, after which you can restart Hyprland. Does Hyprland also crash kernel if started under Sway? It's supposed to spawn a window which can be used for debugging or initial configuration. > dmesg: > > Fatal trap 9: general protection fault while in kernel mode > cpuid = 4; apic id = 04 > instruction pointer = 0x20:0xffffffff80629154 > stack pointer = 0x0:0xfffffe0192585aa0 > frame pointer = 0x0:0xfffffe0192585aa0 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 97492 (Hyprland) > rdi: 75e3ba3d79a3ba51 rsi: 0000000000000010 rdx: 0000000000000400 > rcx: 0000000000000002 r8: fffffe0192585c00 r9: fffffe0192585c18 > rax: 0000000000000000 rbx: fffffe00054a1b80 rbp: fffffe0192585aa0 > r10: 0000558f9f3a6fff r11: 00002a705ff55680 r12: 75e3ba3d79a3ba51 > r13: 0000000000000001 r14: 0000000000000010 r15: 75e3ba3d79a3ba39 > trap number = 9 > panic: general protection fault > cpuid = 4 > time = 1718432663 > Uptime: 20h1m37s > ------ > > Please help me to solve the problem, thank you. Panic messages are rarely enough. At bare minimum you need to provide kernel backtrace to get a clue where in the code the crash occurs. After that report on drm-kmod repo, preferably with empty or minimal Hyprland config that can reproduce the crash. https://docs.freebsd.org/en/books/developers-handbook/kerneldebug/ https://github.com/freebsd/drm-kmod/issues/