Re: atomic changes break drm-next-kmod?

On 07/06/2018 03:15, Hans Petter Selasky wrote: On 07/06/18 11:14, Johannes Lundberg wrote: On Fri, Jul 6, 2018 at 9:49 AM Konstantin Belousov wrote: On Fri, Jul 06, 2018 at 09:52:24AM +0200, Niclas Zeising wrote: On 07/06/18 00:02, Warner Losh wrote: On Thu, Jul 5, 2018 at 1:44 PM, Joh

Re: atomic changes break drm-next-kmod?

On 07/06/18 11:14, Johannes Lundberg wrote: On Fri, Jul 6, 2018 at 9:49 AM Konstantin Belousov wrote: On Fri, Jul 06, 2018 at 09:52:24AM +0200, Niclas Zeising wrote: On 07/06/18 00:02, Warner Losh wrote: On Thu, Jul 5, 2018 at 1:44 PM, John Baldwin mailto:j...@freebsd.org>> wrote: On

Re: atomic changes break drm-next-kmod?

On Fri, Jul 6, 2018 at 9:49 AM Konstantin Belousov wrote: > On Fri, Jul 06, 2018 at 09:52:24AM +0200, Niclas Zeising wrote: > > On 07/06/18 00:02, Warner Losh wrote: > > > > > > > > > On Thu, Jul 5, 2018 at 1:44 PM, John Baldwin > > > wrote: > > > > > > On 7/5/18 12:

Re: atomic changes break drm-next-kmod?

On Fri, Jul 06, 2018 at 09:52:24AM +0200, Niclas Zeising wrote: > On 07/06/18 00:02, Warner Losh wrote: > > > > > > On Thu, Jul 5, 2018 at 1:44 PM, John Baldwin > > wrote: > > > > On 7/5/18 12:36 PM, Konstantin Belousov wrote: > > > On Thu, Jul 05, 2018 at 09:1

Re: atomic changes break drm-next-kmod?

On 07/06/18 00:02, Warner Losh wrote: On Thu, Jul 5, 2018 at 1:44 PM, John Baldwin > wrote: On 7/5/18 12:36 PM, Konstantin Belousov wrote: > On Thu, Jul 05, 2018 at 09:12:24PM +0200, Hans Petter Selasky wrote: >> On 07/05/18 20:59, Hans Petter Selasky wr

Re: atomic changes break drm-next-kmod?

On 07/05/2018 12:12, Hans Petter Selasky wrote: On 07/05/18 20:59, Hans Petter Selasky wrote: On 07/05/18 19:48, Pete Wright wrote: On 07/05/2018 10:10, John Baldwin wrote: On 7/3/18 5:10 PM, Pete Wright wrote: On 07/03/2018 15:56, John Baldwin wrote: On 7/3/18 3:34 PM, Pete Wright wrot

Re: atomic changes break drm-next-kmod?

On Thu, Jul 5, 2018 at 1:44 PM, John Baldwin wrote: > On 7/5/18 12:36 PM, Konstantin Belousov wrote: > > On Thu, Jul 05, 2018 at 09:12:24PM +0200, Hans Petter Selasky wrote: > >> On 07/05/18 20:59, Hans Petter Selasky wrote: > >>> On 07/05/18 19:48, Pete Wright wrote: > > > On 07/0

Re: atomic changes break drm-next-kmod?

On 7/5/18 12:36 PM, Konstantin Belousov wrote: > On Thu, Jul 05, 2018 at 09:12:24PM +0200, Hans Petter Selasky wrote: >> On 07/05/18 20:59, Hans Petter Selasky wrote: >>> On 07/05/18 19:48, Pete Wright wrote: On 07/05/2018 10:10, John Baldwin wrote: > On 7/3/18 5:10 PM, Pete Wrig

Re: atomic changes break drm-next-kmod?

On Thu, Jul 05, 2018 at 09:12:24PM +0200, Hans Petter Selasky wrote: > On 07/05/18 20:59, Hans Petter Selasky wrote: > > On 07/05/18 19:48, Pete Wright wrote: > >> > >> > >> On 07/05/2018 10:10, John Baldwin wrote: > >>> On 7/3/18 5:10 PM, Pete Wright wrote: > > On 07/03/2018 15:56, John

Re: atomic changes break drm-next-kmod?

On 07/05/18 20:59, Hans Petter Selasky wrote: On 07/05/18 19:48, Pete Wright wrote: On 07/05/2018 10:10, John Baldwin wrote: On 7/3/18 5:10 PM, Pete Wright wrote: On 07/03/2018 15:56, John Baldwin wrote: On 7/3/18 3:34 PM, Pete Wright wrote: On 07/03/2018 15:29, John Baldwin wrote: That

Re: atomic changes break drm-next-kmod?

On 07/05/18 19:48, Pete Wright wrote: On 07/05/2018 10:10, John Baldwin wrote: On 7/3/18 5:10 PM, Pete Wright wrote: On 07/03/2018 15:56, John Baldwin wrote: On 7/3/18 3:34 PM, Pete Wright wrote: On 07/03/2018 15:29, John Baldwin wrote: That seems like kgdb is looking at the wrong CPU.  C

Re: atomic changes break drm-next-kmod?

On 07/05/2018 10:10, John Baldwin wrote: On 7/3/18 5:10 PM, Pete Wright wrote: On 07/03/2018 15:56, John Baldwin wrote: On 7/3/18 3:34 PM, Pete Wright wrote: 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

Re: atomic changes break drm-next-kmod?

On 7/3/18 5:10 PM, Pete Wright wrote: > > > On 07/03/2018 15:56, John Baldwin wrote: >> On 7/3/18 3:34 PM, Pete Wright wrote: >>> >>> 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 i

Re: atomic changes break drm-next-kmod?

In message <20180703170223.266db...@thor.intern.walstatt.dynvpn.de>, "O. Hartma nn" writes: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Am Tue, 3 Jul 2018 10:19:57 -0400 > Michael Butler schrieb: > > > It seems recent changes (SVN r335873?) may have broken drm-next-kmod .. > > > > --

Re: atomic changes break drm-next-kmod?

In message , Niclas Zeising w rites: > On 07/03/18 17:02, O. Hartmann wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA512 > > > > Am Tue, 3 Jul 2018 10:19:57 -0400 > > Michael Butler schrieb: > > > >> It seems recent changes (SVN r335873?) may have broken drm-next-kmod .. > >> > >> -

Re: atomic changes break drm-next-kmod?

On 07/03/2018 15:56, John Baldwin wrote: On 7/3/18 3:34 PM, Pete Wright wrote: 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 j

Re: atomic changes break drm-next-kmod?

This seems like a clang inline asm bug. Could you try building the port with a recent gcc against an unpatched HEAD? On Tue, Jul 3, 2018 at 15:38 Pete Wright wrote: > > > On 07/03/2018 15:29, John Baldwin wrote: > > That seems like kgdb is looking at the wrong CPU. Can you use > > 'info threads

Re: atomic changes break drm-next-kmod?

On 7/3/18 3:40 PM, Matthew Macy wrote: > This seems like a clang inline asm bug. Could you try building the port with > a recent gcc against an unpatched HEAD? I've already committed the patch to HEAD, but using 'e' is from the GCC docs, not clang docs: https://gcc.gnu.org/onlinedocs/gcc/Machin

Re: atomic changes break drm-next-kmod?

On 7/3/18 3:34 PM, Pete Wright wrote: > > > 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'

Re: atomic changes break drm-next-kmod?

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. s

Re: atomic changes break drm-next-kmod?

On 7/3/18 3:20 PM, Pete Wright wrote: > > > On 07/03/2018 15:12, Pete Wright wrote: >> >> >> On 07/03/2018 14:17, Pete Wright wrote: >>> >>> >>> On 07/03/2018 12:02, John Baldwin wrote: On 7/3/18 11:28 AM, Niclas Zeising wrote: > On 07/03/18 17:02, O. Hartmann wrote: >> -BEGIN PG

Re: atomic changes break drm-next-kmod?

On 07/03/2018 15:12, Pete Wright wrote: On 07/03/2018 14:17, Pete Wright wrote: On 07/03/2018 12:02, John Baldwin wrote: On 7/3/18 11:28 AM, Niclas Zeising wrote: On 07/03/18 17:02, O. Hartmann wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Tue, 3 Jul 2018 10:19:57 -0400 Mic

Re: atomic changes break drm-next-kmod?

On 07/03/2018 14:17, Pete Wright wrote: On 07/03/2018 12:02, John Baldwin wrote: On 7/3/18 11:28 AM, Niclas Zeising wrote: On 07/03/18 17:02, O. Hartmann wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Tue, 3 Jul 2018 10:19:57 -0400 Michael Butler schrieb: It seems recent chan

Re: atomic changes break drm-next-kmod?

On 07/03/2018 12:02, John Baldwin wrote: On 7/3/18 11:28 AM, Niclas Zeising wrote: On 07/03/18 17:02, O. Hartmann wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Tue, 3 Jul 2018 10:19:57 -0400 Michael Butler schrieb: It seems recent changes (SVN r335873?) may have broken drm-nex

Re: atomic changes break drm-next-kmod?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/03/2018 15:23, Jung-uk Kim wrote: > On 07/03/2018 15:02, John Baldwin wrote: >> On 7/3/18 11:28 AM, Niclas Zeising wrote: >>> On 07/03/18 17:02, O. Hartmann wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Tue, 3 Jul 20

Re: atomic changes break drm-next-kmod?

On 07/03/2018 15:02, John Baldwin wrote: > On 7/3/18 11:28 AM, Niclas Zeising wrote: >> On 07/03/18 17:02, O. Hartmann wrote: >>> -BEGIN PGP SIGNED MESSAGE- >>> Hash: SHA512 >>> >>> Am Tue, 3 Jul 2018 10:19:57 -0400 >>> Michael Butler schrieb: >>> It seems recent changes (SVN r335873?

Re: atomic changes break drm-next-kmod?

On 7/3/18 11:28 AM, Niclas Zeising wrote: > On 07/03/18 17:02, O. Hartmann wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA512 >> >> Am Tue, 3 Jul 2018 10:19:57 -0400 >> Michael Butler schrieb: >> >>> It seems recent changes (SVN r335873?) may have broken drm-next-kmod .. >>> >>> --- i915

Re: atomic changes break drm-next-kmod?

On 07/03/18 17:02, O. Hartmann wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Tue, 3 Jul 2018 10:19:57 -0400 Michael Butler schrieb: It seems recent changes (SVN r335873?) may have broken drm-next-kmod .. --- i915_drv.o --- In file included from i915_drv.c:30: In file included fro

Re: atomic changes break drm-next-kmod?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Tue, 3 Jul 2018 10:19:57 -0400 Michael Butler schrieb: > It seems recent changes (SVN r335873?) may have broken drm-next-kmod .. > > --- i915_drv.o --- > In file included from i915_drv.c:30: > In file included from > /usr/ports/graphics/drm-nex

atomic changes break drm-next-kmod?

It seems recent changes (SVN r335873?) may have broken drm-next-kmod .. --- i915_drv.o --- In file included from i915_drv.c:30: In file included from /usr/ports/graphics/drm-next-kmod/work/kms-drm-a753215/linuxkpi/gplv2/include/linux/acpi.h:26: In file included from /usr/ports/graphics/drm-next-km