Date: Tue, 3 Jul 2018 15:34:24 -0700 From: Pete Wright <pete@nomadlogic.org> To: John Baldwin <jhb@FreeBSD.org>, Niclas Zeising <zeising+freebsd@daemonic.se>, "O. Hartmann" <ohartmann@walstatt.org>, FreeBSD Current <freebsd-current@FreeBSD.org> Subject: Re: atomic changes break drm-next-kmod? Message-ID: <0bf8e57b-fdb4-4c1a-3d0d-a734f8187ca8@nomadlogic.org> In-Reply-To: <063ae5c3-0584-1284-dd9d-ab8b5790baf1@FreeBSD.org> References: <c640afcd-1fa4-a43e-5f36-f0bd11aad63d@protected-networks.net> <20180703170223.266dbf5b@thor.intern.walstatt.dynvpn.de> <cbd2d2f2-8ce4-871a-9aaf-75738d6c465b@daemonic.se> <ee0f7fce-7ce3-3784-f9e8-0f6862d59303@FreeBSD.org> <c7a3b447-00e9-8501-0484-841a371cfd62@nomadlogic.org> <bb2cac77-4bcd-c87c-9bc9-ce5f8ce1c726@nomadlogic.org> <845aca10-8c01-fa3b-087f-f957df4e7531@nomadlogic.org> <063ae5c3-0584-1284-dd9d-ab8b5790baf1@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0bf8e57b-fdb4-4c1a-3d0d-a734f8187ca8>