Date: Tue, 9 Mar 2021 09:45:06 +0100 From: Hans Petter Selasky <hps@selasky.org> To: Alastair Hogge <agh@riseup.net> Cc: Emmanuel Vadot <manu@bidouilliste.com>, Steve Kargl <sgk@troutmask.apl.washington.edu>, Andriy Gapon <avg@freebsd.org>, freebsd-current@freebsd.org, freebsd-x11@freebsd.org Subject: Re: panic in drm or vt or deadlock on mutex or ... Message-ID: <08876514-e12d-dcc1-29de-184207bb8278@selasky.org> In-Reply-To: <942bb6f5190e5300492120c3aecdf874@riseup.net> 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> <fea61694-367d-7161-e071-4a8f77810a68@selasky.org> <942bb6f5190e5300492120c3aecdf874@riseup.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?08876514-e12d-dcc1-29de-184207bb8278>