From owner-freebsd-current@freebsd.org Tue Mar 9 08:45:32 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9572F56F3BA; Tue, 9 Mar 2021 08:45:32 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Dvpgw3D4bz3KXF; Tue, 9 Mar 2021 08:45:31 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2020.home.selasky.org (unknown [178.17.145.105]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id EA3AB260201; Tue, 9 Mar 2021 09:45:22 +0100 (CET) Subject: Re: panic in drm or vt or deadlock on mutex or ... To: Alastair Hogge Cc: Emmanuel Vadot , Steve Kargl , Andriy Gapon , freebsd-current@freebsd.org, freebsd-x11@freebsd.org References: <20210203050828.GA21823@troutmask.apl.washington.edu> <4581b83f-e048-fb8b-edfe-44332d3dc460@FreeBSD.org> <20210203160324.GA23963@troutmask.apl.washington.edu> <20210204105029.5fc11bed5df0e4283f983fbf@bidouilliste.com> <36a5927f9992ec828a0fe1e9bf480ce3@riseup.net> <942bb6f5190e5300492120c3aecdf874@riseup.net> From: Hans Petter Selasky Message-ID: <08876514-e12d-dcc1-29de-184207bb8278@selasky.org> Date: Tue, 9 Mar 2021 09:45:06 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0 MIME-Version: 1.0 In-Reply-To: <942bb6f5190e5300492120c3aecdf874@riseup.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Dvpgw3D4bz3KXF X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 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, 09 Mar 2021 08:45:32 -0000 On 3/9/21 9:31 AM, Alastair Hogge wrote: > On 2021-02-08 21:01, Hans Petter Selasky wrote: >> On 2/8/21 1:53 PM, Alastair Hogge wrote: >>> Boot to multi-user; login (getty): >>> $ doas kldload /boot/modules/amdgpu.ko >>> $ sysctl >>> [panic] >>> >>> ..is a guaranteed way to panic my system. >> >> Hi, >> >> Maybe you could do a hack and edit the sysctl source code: >> >> 1) print the sysctl before it is queried. >> 2) sleep 1 second between print and query. >> >> Should be easy to nail this down! > > Always panics at: > $ /tmp/sysctl-with-delay -a > [...] > p1003_1b.mapped_files: 200112 > p1003_1b.memlock: 0 > p1003_1b.memlock_range: 0 > p1003_1b.memory_protection: 0 > p1003_1b.message_passing: 0 > p1003_1b.prioritized_io: 0 > p1003_1b.priority_scheduling: 200112 > p1003_1b.realtime_signals: 200112 > p1003_1b.semaphores: 0 > p1003_1b.fsync: 200112 > p1003_1b.shared_memory_objects: 200112 > p1003_1b.synchronized_io: 0 > p1003_1b.timers: 200112 > p1003_1b.aio_listio_max: 256 > p1003_1b.aio_max: 1024 > p1003_1b.aio_prio_delta_max: 0 > p1003_1b.delaytimer_max: 2147483647 > p1003_1b.mq_open_max: 0 > p1003_1b.pagesize: 4096 > p1003_1b.rtsig_max: 62 > p1003_1b.sem_nsems_max: 0 > p1003_1b.sem_value_max: 0 > p1003_1b.sigqueue_max: 128 > p1003_1b.timer_max: 32 > Hi, On my system: p1003_1b.timer_max: 32 sys.class.drm.card0-HDMI-A-1.modes: 1680x1050 1600x1200 1280x1024 1440x900 1280x960 1024x768 800x600 640x480 720x400 So that means some modes sysctl is causing the panic. Emmanuel: Do you want to debug this? --HPS