From owner-freebsd-current@freebsd.org Tue Jul 3 22:34:32 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 76BE7102F568 for ; Tue, 3 Jul 2018 22:34:32 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (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 DB78F74A20; Tue, 3 Jul 2018 22:34:31 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.106] (cpe-75-82-194-8.socal.res.rr.com [75.82.194.8]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 63fc6e69 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Tue, 3 Jul 2018 15:34:29 -0700 (PDT) Subject: Re: atomic changes break drm-next-kmod? To: John Baldwin , Niclas Zeising , "O. Hartmann" , FreeBSD Current References: <20180703170223.266dbf5b@thor.intern.walstatt.dynvpn.de> <845aca10-8c01-fa3b-087f-f957df4e7531@nomadlogic.org> <063ae5c3-0584-1284-dd9d-ab8b5790baf1@FreeBSD.org> From: Pete Wright Message-ID: <0bf8e57b-fdb4-4c1a-3d0d-a734f8187ca8@nomadlogic.org> Date: Tue, 3 Jul 2018 15:34:24 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <063ae5c3-0584-1284-dd9d-ab8b5790baf1@FreeBSD.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 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, 03 Jul 2018 22:34:32 -0000 On 07/03/2018 15:29, John Baldwin wrote: > That seems like kgdb is looking at the wrong CPU. Can you use > 'info threads' and look for threads not stopped in 'sched_switch' > and get their backtraces? You could also just do 'thread apply > all bt' and put that file at a URL if that is easiest. > sure thing John - here's a gist of "thread apply all bt" https://gist.github.com/gem-pete/d8d7ab220dc8781f0827f965f09d43ed cheers! -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA