atomic changes break drm-next-kmod?

2018-07-03 Thread Michael Butler 
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-kmod/work/kms-drm-a753215/linuxkpi/gplv2/include/linux/device.h:4:
In file included from
/usr/src/sys/compat/linuxkpi/common/include/linux/device.h:35:
In file included from
/usr/src/sys/compat/linuxkpi/common/include/linux/types.h:37:
In file included from /usr/src/sys/sys/systm.h:44:
./machine/atomic.h:450:29: error: invalid operand for instruction
ATOMIC_ASM(clear,long,  "andq %1,%0",  "ir", ~v);
^
:1:7: note: instantiated into assembly here
andq $9223372036854775807,40672(%r14)
 ^
1 error generated.
*** [i915_drv.o] Error code 1

make[3]: stopped in
/usr/ports/graphics/drm-next-kmod/work/kms-drm-a753215/i915
--- i915_gem.o ---
In file included from i915_gem.c:28:
In file included from
/usr/ports/graphics/drm-next-kmod/work/kms-drm-a753215/include/drm/drmP.h:38:
In file included from /usr/src/sys/sys/malloc.h:42:
In file included from /usr/src/sys/sys/systm.h:44:
./machine/atomic.h:449:29: error: invalid operand for instruction
ATOMIC_ASM(set,  long,  "orq %1,%0",   "ir",  v);
^
:1:6: note: instantiated into assembly here
orq $-9223372036854775808,40672(%r14)
^~
1 error generated.
*** [i915_gem.o] Error code 1

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: atomic changes break drm-next-kmod?

2018-07-03 Thread O. Hartmann 
-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-next-kmod/work/kms-drm-a753215/linuxkpi/gplv2/include/linux/acpi.h:26:
> In file included from
> /usr/ports/graphics/drm-next-kmod/work/kms-drm-a753215/linuxkpi/gplv2/include/linux/device.h:4:
> In file included from
> /usr/src/sys/compat/linuxkpi/common/include/linux/device.h:35:
> In file included from
> /usr/src/sys/compat/linuxkpi/common/include/linux/types.h:37:
> In file included from /usr/src/sys/sys/systm.h:44:
> ./machine/atomic.h:450:29: error: invalid operand for instruction
> ATOMIC_ASM(clear,long,  "andq %1,%0",  "ir", ~v);
> ^
> :1:7: note: instantiated into assembly here
> andq $9223372036854775807,40672(%r14)
>  ^
> 1 error generated.
> *** [i915_drv.o] Error code 1
> 
> make[3]: stopped in
> /usr/ports/graphics/drm-next-kmod/work/kms-drm-a753215/i915
> --- i915_gem.o ---
> In file included from i915_gem.c:28:
> In file included from
> /usr/ports/graphics/drm-next-kmod/work/kms-drm-a753215/include/drm/drmP.h:38:
> In file included from /usr/src/sys/sys/malloc.h:42:
> In file included from /usr/src/sys/sys/systm.h:44:
> ./machine/atomic.h:449:29: error: invalid operand for instruction
> ATOMIC_ASM(set,  long,  "orq %1,%0",   "ir",  v);
> ^
> :1:6: note: instantiated into assembly here
> orq $-9223372036854775808,40672(%r14)
> ^~
> 1 error generated.
> *** [i915_gem.o] Error code 1
> 
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


It breaks also graphics/drm-stable-kmod (see PR 229484,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229484, same error as you 
described
above) and also emulators/virtualbox-ose-kmod. As long as CURRENT revision is < 
r335873,
those kmod compile well.
- -- 
O. Hartmann

Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).
-BEGIN PGP SIGNATURE-

iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWzuQGgAKCRDS528fyFhY
lKHnAf0fIVHnw1xBVHzogeQQo4v+he17R2ln6l25lNR/pUE1AZOsFzPDamAkqbY+
f1+Usr+P5o7jn26Bh4ob3UmIj25DAf4tJZpeZS4iGZ374lrCAemYFb53+MJ1fClW
aBLI6DVOiBiOt/UpLXZf1whl/dtQvo5yd1xywfYOwi9Jh8teHcNW
=mtMH
-END PGP SIGNATURE-
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: svn commit: r335879 - in head/sys: conf kern sys [ broke ci.freebsd.org's FreeBSD-head-amd64-build ]

2018-07-03 Thread Bryan Drewery 
On 7/2/2018 10:46 PM, Mark Millard wrote:
> -r335879 broke ci.freebsd.org's FreeBSD-head-amd64-build :
> 
> https://ci.freebsd.org/job/FreeBSD-head-amd64-build/
> 
> shows:
> 
> --- ia32_genassym.o ---
> In file included from /usr/src/sys/compat/ia32/ia32_genassym.c:6:
> In file included from /usr/src/sys/sys/systm.h:113:
> /usr/src/sys/sys/kpilite.h:33:10: fatal error: 'offset.inc' file not found
> #include "offset.inc"
>  ^~~~
> 1 error generated.
> *** [ia32_genassym.o] Error code 1
> 
> Later builds ( -r335880 , -r335881 , -r335882 ) get the same.
> 
> FreeBSD-head-i386-LINT also fails for such reasons.
> 

r335884 should fix this.


-- 
Regards,
Bryan Drewery



signature.asc
Description: OpenPGP digital signature

Re: svn commit: r335879 - in head/sys: conf kern sys [ broke ci.freebsd.org's FreeBSD-head-amd64-build ]

2018-07-03 Thread Li-Wen Hsu 
On Tue, Jul 3, 2018 at 5:30 PM Bryan Drewery  wrote:
>
> On 7/2/2018 10:46 PM, Mark Millard wrote:
> > -r335879 broke ci.freebsd.org's FreeBSD-head-amd64-build :
> >
> > https://ci.freebsd.org/job/FreeBSD-head-amd64-build/
> >
> > shows:
> >
> > --- ia32_genassym.o ---
> > In file included from /usr/src/sys/compat/ia32/ia32_genassym.c:6:
> > In file included from /usr/src/sys/sys/systm.h:113:
> > /usr/src/sys/sys/kpilite.h:33:10: fatal error: 'offset.inc' file not found
> > #include "offset.inc"
> >  ^~~~
> > 1 error generated.
> > *** [ia32_genassym.o] Error code 1
> >
> > Later builds ( -r335880 , -r335881 , -r335882 ) get the same.
> >
> > FreeBSD-head-i386-LINT also fails for such reasons.
> >
>
> r335884 should fix this.

It seems that amd64 and i386 LINT are still failing.

-- 
Li-Wen Hsu 
https://lwhsu.org
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

em0 link fail

2018-07-03 Thread Michael Butler 
On June 1st, I was able to do my monthly laptop ZFS snap-shot/back-up
(using "zfs snapshot -r zroot@backup; zfs send -R >nfs-filesys"). Now I
can't without the em0 interface stalling :-(

On a guess, I tried reverting SVN r335303 but that didn't help.

em0:  port 0xf080-0xf09f mem
0xf7e0-0xf7e1,0xf7e39000-0xf7e39fff irq 20 at device 25.0 on pci0
em0: attach_pre capping queues at 1
em0: using 1024 tx descriptors and 1024 rx descriptors
em0: msix_init qsets capped at 1
em0: PCIY_MSIX capability not found; or rid 0 == 0.
em0: Using an MSI interrupt
em0: allocated for 1 tx_queues
em0: allocated for 1 rx_queues
em0: Ethernet address: f0:1f:af:66:95:7e
em0: netmap queues/slots: TX 1/1024, RX 1/1024
em0: link state changed to UP

 [ initiate "zfs send" ]

em0: TX(0) desc avail = 41, pidx = 172
em0: link state changed to DOWN
em0: TX(0) desc avail = 1024, pidx = 0
em0: TX(0) desc avail = 1024, pidx = 0

 .. ad nauseum ..

"ifconfig em0 down; ifconfig em0 up" doesn't help.

Any hints?

imb

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: svn commit: r335879 - in head/sys: conf kern sys [ broke ci.freebsd.org's FreeBSD-head-amd64-build ]

2018-07-03 Thread Mark Millard 



On 2018-Jul-3, at 10:06 AM, Li-Wen Hsu  wrote:

> On Tue, Jul 3, 2018 at 5:30 PM Bryan Drewery  wrote:
>> 
>> On 7/2/2018 10:46 PM, Mark Millard wrote:
>>> -r335879 broke ci.freebsd.org's FreeBSD-head-amd64-build :
>>> 
>>> https://ci.freebsd.org/job/FreeBSD-head-amd64-build/
>>> 
>>> shows:
>>> 
>>> --- ia32_genassym.o ---
>>> In file included from /usr/src/sys/compat/ia32/ia32_genassym.c:6:
>>> In file included from /usr/src/sys/sys/systm.h:113:
>>> /usr/src/sys/sys/kpilite.h:33:10: fatal error: 'offset.inc' file not found
>>> #include "offset.inc"
>>> ^~~~
>>> 1 error generated.
>>> *** [ia32_genassym.o] Error code 1
>>> 
>>> Later builds ( -r335880 , -r335881 , -r335882 ) get the same.
>>> 
>>> FreeBSD-head-i386-LINT also fails for such reasons.
>>> 
>> 
>> r335884 should fix this.
> 
> It seems that amd64 and i386 LINT are still failing.

https://ci.freebsd.org/job/FreeBSD-head-amd64-build/ shows that
#9303 (-r335884) and later for amd64 are building successfully.

But https://ci.freebsd.org/job/FreeBSD-head-i386-LINT/ shows
that -r335884 (#6934) and later ( -r335892 so far ) for i386's
LINT are still failing with:

--- linux_genassym.o ---
In file included from /workspace/src/sys/i386/linux/linux_genassym.c:6:
In file included from /workspace/src/sys/sys/systm.h:113:
/workspace/src/sys/sys/kpilite.h:33:10: fatal error: 'offset.inc' file not found
#include "offset.inc"
 ^~~~
1 error generated.
*** [linux_genassym.o] Error code 1



===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: em0 link fail

2018-07-03 Thread Kurt Jaeger 
Hi!

> On June 1st, I was able to do my monthly laptop ZFS snap-shot/back-up
> (using "zfs snapshot -r zroot@backup; zfs send -R >nfs-filesys"). Now I
> can't without the em0 interface stalling :-(

I had a similar case on a current r334918 and saw this in the kern syslog:

  Jun 30 15:40:34 fc kernel: em0: TX(0) desc avail = 1024, pidx = 0

A reboot was necessary to get this fixed.

-- 
p...@opsec.eu+49 171 31013722 years to go !
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: atomic changes break drm-next-kmod?

2018-07-03 Thread Niclas Zeising 

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 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-kmod/work/kms-drm-a753215/linuxkpi/gplv2/include/linux/device.h:4:
In file included from
/usr/src/sys/compat/linuxkpi/common/include/linux/device.h:35:
In file included from
/usr/src/sys/compat/linuxkpi/common/include/linux/types.h:37:
In file included from /usr/src/sys/sys/systm.h:44:
./machine/atomic.h:450:29: error: invalid operand for instruction
ATOMIC_ASM(clear,long,  "andq %1,%0",  "ir", ~v);
 ^
:1:7: note: instantiated into assembly here
 andq $9223372036854775807,40672(%r14)
  ^
1 error generated.
*** [i915_drv.o] Error code 1

make[3]: stopped in
/usr/ports/graphics/drm-next-kmod/work/kms-drm-a753215/i915
--- i915_gem.o ---
In file included from i915_gem.c:28:
In file included from
/usr/ports/graphics/drm-next-kmod/work/kms-drm-a753215/include/drm/drmP.h:38:
In file included from /usr/src/sys/sys/malloc.h:42:
In file included from /usr/src/sys/sys/systm.h:44:
./machine/atomic.h:449:29: error: invalid operand for instruction
ATOMIC_ASM(set,  long,  "orq %1,%0",   "ir",  v);
 ^
:1:6: note: instantiated into assembly here
 orq $-9223372036854775808,40672(%r14)
 ^~
1 error generated.
*** [i915_gem.o] Error code 1

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"



It breaks also graphics/drm-stable-kmod (see PR 229484,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229484, same error as you 
described
above) and also emulators/virtualbox-ose-kmod. As long as CURRENT revision is < 
r335873,
those kmod compile well.


We are looking into why both the drm ports fail.
Regards
--
Niclas

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: em0 link fail

2018-07-03 Thread Sean Bruno 


On 07/03/18 11:47, Michael Butler wrote:
> On June 1st, I was able to do my monthly laptop ZFS snap-shot/back-up
> (using "zfs snapshot -r zroot@backup; zfs send -R >nfs-filesys"). Now I
> can't without the em0 interface stalling :-(
> 

Can you tell what version of FreeBSD SVN was in use on "June 1st" ?

sean

> On a guess, I tried reverting SVN r335303 but that didn't help.
> 
> em0:  port 0xf080-0xf09f mem
> 0xf7e0-0xf7e1,0xf7e39000-0xf7e39fff irq 20 at device 25.0 on pci0
> em0: attach_pre capping queues at 1
> em0: using 1024 tx descriptors and 1024 rx descriptors
> em0: msix_init qsets capped at 1
> em0: PCIY_MSIX capability not found; or rid 0 == 0.
> em0: Using an MSI interrupt
> em0: allocated for 1 tx_queues
> em0: allocated for 1 rx_queues
> em0: Ethernet address: f0:1f:af:66:95:7e
> em0: netmap queues/slots: TX 1/1024, RX 1/1024
> em0: link state changed to UP
> 
>  [ initiate "zfs send" ]
> 
> em0: TX(0) desc avail = 41, pidx = 172
> em0: link state changed to DOWN
> em0: TX(0) desc avail = 1024, pidx = 0
> em0: TX(0) desc avail = 1024, pidx = 0
> 
>  .. ad nauseum ..
> 
> "ifconfig em0 down; ifconfig em0 up" doesn't help.
> 
> Any hints?
> 
>   imb
> 
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> 



signature.asc
Description: OpenPGP digital signature

Re: em0 link fail

2018-07-03 Thread Michael Butler 
On 07/03/18 14:31, Sean Bruno wrote:
> 
> 
> On 07/03/18 11:47, Michael Butler wrote:
>> On June 1st, I was able to do my monthly laptop ZFS snap-shot/back-up
>> (using "zfs snapshot -r zroot@backup; zfs send -R >nfs-filesys"). Now I
>> can't without the em0 interface stalling :-(
>>
> 
> Can you tell what version of FreeBSD SVN was in use on "June 1st" ?
> 
> sean

That would've been ..

Jun  1 09:56:15 toshi kernel: FreeBSD 12.0-CURRENT #35 r334484: Fri Jun
1 08:25:58 EDT 2018

I'm going to build one with SVN r334862 reverted to see if that works,

imb


> 
>> On a guess, I tried reverting SVN r335303 but that didn't help.
>>
>> em0:  port 0xf080-0xf09f mem
>> 0xf7e0-0xf7e1,0xf7e39000-0xf7e39fff irq 20 at device 25.0 on pci0
>> em0: attach_pre capping queues at 1
>> em0: using 1024 tx descriptors and 1024 rx descriptors
>> em0: msix_init qsets capped at 1
>> em0: PCIY_MSIX capability not found; or rid 0 == 0.
>> em0: Using an MSI interrupt
>> em0: allocated for 1 tx_queues
>> em0: allocated for 1 rx_queues
>> em0: Ethernet address: f0:1f:af:66:95:7e
>> em0: netmap queues/slots: TX 1/1024, RX 1/1024
>> em0: link state changed to UP
>>
>>  [ initiate "zfs send" ]
>>
>> em0: TX(0) desc avail = 41, pidx = 172
>> em0: link state changed to DOWN
>> em0: TX(0) desc avail = 1024, pidx = 0
>> em0: TX(0) desc avail = 1024, pidx = 0
>>
>>  .. ad nauseum ..
>>
>> "ifconfig em0 down; ifconfig em0 up" doesn't help.
>>
>> Any hints?
>>
>>  imb
>>
>> ___
>> freebsd-current@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>>
> 

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: atomic changes break drm-next-kmod?

2018-07-03 Thread John Baldwin 
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_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-kmod/work/kms-drm-a753215/linuxkpi/gplv2/include/linux/device.h:4:
>>> In file included from
>>> /usr/src/sys/compat/linuxkpi/common/include/linux/device.h:35:
>>> In file included from
>>> /usr/src/sys/compat/linuxkpi/common/include/linux/types.h:37:
>>> In file included from /usr/src/sys/sys/systm.h:44:
>>> ./machine/atomic.h:450:29: error: invalid operand for instruction
>>> ATOMIC_ASM(clear,long,  "andq %1,%0",  "ir", ~v);
>>>  ^
>>> :1:7: note: instantiated into assembly here
>>>  andq $9223372036854775807,40672(%r14)
>>>   ^
>>> 1 error generated.
>>> *** [i915_drv.o] Error code 1
>>>
>>> make[3]: stopped in
>>> /usr/ports/graphics/drm-next-kmod/work/kms-drm-a753215/i915
>>> --- i915_gem.o ---
>>> In file included from i915_gem.c:28:
>>> In file included from
>>> /usr/ports/graphics/drm-next-kmod/work/kms-drm-a753215/include/drm/drmP.h:38:
>>> In file included from /usr/src/sys/sys/malloc.h:42:
>>> In file included from /usr/src/sys/sys/systm.h:44:
>>> ./machine/atomic.h:449:29: error: invalid operand for instruction
>>> ATOMIC_ASM(set,  long,  "orq %1,%0",   "ir",  v);
>>>  ^
>>> :1:6: note: instantiated into assembly here
>>>  orq $-9223372036854775808,40672(%r14)
>>>  ^~
>>> 1 error generated.
>>> *** [i915_gem.o] Error code 1
>>>
>>> ___
>>> freebsd-current@freebsd.org mailing list
>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>>> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>>
>>
>> It breaks also graphics/drm-stable-kmod (see PR 229484,
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229484, same error as you 
>> described
>> above) and also emulators/virtualbox-ose-kmod. As long as CURRENT revision 
>> is < r335873,
>> those kmod compile well.
> 
> We are looking into why both the drm ports fail.
> Regards
> 

I haven't yet tested an amd64 kernel with this, but I think this change to 
sys/amd64/include/atomic.h
might fix it:

Index: atomic.h
===
--- atomic.h(revision 335896)
+++ atomic.h(working copy)
@@ -446,10 +446,10 @@ ATOMIC_ASM(clear,int,   "andl %1,%0",  "ir", ~
 ATOMIC_ASM(add, int,   "addl %1,%0",  "ir",  v);
 ATOMIC_ASM(subtract, int,   "subl %1,%0",  "ir",  v);
 
-ATOMIC_ASM(set, long,  "orq %1,%0",   "ir",  v);
-ATOMIC_ASM(clear,long,  "andq %1,%0",  "ir", ~v);
-ATOMIC_ASM(add, long,  "addq %1,%0",  "ir",  v);
-ATOMIC_ASM(subtract, long,  "subq %1,%0",  "ir",  v);
+ATOMIC_ASM(set, long,  "orq %1,%0",   "er",  v);
+ATOMIC_ASM(clear,long,  "andq %1,%0",  "er", ~v);
+ATOMIC_ASM(add, long,  "addq %1,%0",  "er",  v);
+ATOMIC_ASM(subtract, long,  "subq %1,%0",  "er",  v);
 
 #defineATOMIC_LOADSTORE(TYPE)  \
ATOMIC_LOAD(TYPE);  \


-- 
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: em0 link fail

2018-07-03 Thread Michael Butler 
On 7/3/18 14:47, I wrote:
> On 07/03/18 14:31, Sean Bruno wrote:
>>
>>
>> On 07/03/18 11:47, Michael Butler wrote:
>>> On June 1st, I was able to do my monthly laptop ZFS snap-shot/back-up
>>> (using "zfs snapshot -r zroot@backup; zfs send -R >nfs-filesys"). Now I
>>> can't without the em0 interface stalling :-(
>>>
>>
>> Can you tell what version of FreeBSD SVN was in use on "June 1st" ?
>>
>> sean
> 
> That would've been ..
> 
> Jun  1 09:56:15 toshi kernel: FreeBSD 12.0-CURRENT #35 r334484: Fri Jun
> 1 08:25:58 EDT 2018
> 
> I'm going to build one with SVN r334862 reverted to see if that works,

Sadly, no :-(

> 
>>
>>> On a guess, I tried reverting SVN r335303 but that didn't help.
>>>
>>> em0:  port 0xf080-0xf09f mem
>>> 0xf7e0-0xf7e1,0xf7e39000-0xf7e39fff irq 20 at device 25.0 on pci0
>>> em0: attach_pre capping queues at 1
>>> em0: using 1024 tx descriptors and 1024 rx descriptors
>>> em0: msix_init qsets capped at 1
>>> em0: PCIY_MSIX capability not found; or rid 0 == 0.
>>> em0: Using an MSI interrupt
>>> em0: allocated for 1 tx_queues
>>> em0: allocated for 1 rx_queues
>>> em0: Ethernet address: f0:1f:af:66:95:7e
>>> em0: netmap queues/slots: TX 1/1024, RX 1/1024
>>> em0: link state changed to UP
>>>
>>>  [ initiate "zfs send" ]
>>>
>>> em0: TX(0) desc avail = 41, pidx = 172
>>> em0: link state changed to DOWN
>>> em0: TX(0) desc avail = 1024, pidx = 0
>>> em0: TX(0) desc avail = 1024, pidx = 0
>>>
>>>  .. ad nauseum ..
>>>
>>> "ifconfig em0 down; ifconfig em0 up" doesn't help.
>>>
>>> Any hints?
>>>
>>> imb
>>>
>>> ___
>>> freebsd-current@freebsd.org mailing list
>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>>> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>>>
>>
> 
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> 

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: atomic changes break drm-next-kmod?

2018-07-03 Thread Jung-uk Kim 
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?) 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-kmod/work/kms-drm-a753215/linuxkpi/gplv2/include/linux/device.h:4:
 In file included from
 /usr/src/sys/compat/linuxkpi/common/include/linux/device.h:35:
 In file included from
 /usr/src/sys/compat/linuxkpi/common/include/linux/types.h:37:
 In file included from /usr/src/sys/sys/systm.h:44:
 ./machine/atomic.h:450:29: error: invalid operand for instruction
 ATOMIC_ASM(clear,long,  "andq %1,%0",  "ir", ~v);
  ^
 :1:7: note: instantiated into assembly here
  andq $9223372036854775807,40672(%r14)
   ^
 1 error generated.
 *** [i915_drv.o] Error code 1

 make[3]: stopped in
 /usr/ports/graphics/drm-next-kmod/work/kms-drm-a753215/i915
 --- i915_gem.o ---
 In file included from i915_gem.c:28:
 In file included from
 /usr/ports/graphics/drm-next-kmod/work/kms-drm-a753215/include/drm/drmP.h:38:
 In file included from /usr/src/sys/sys/malloc.h:42:
 In file included from /usr/src/sys/sys/systm.h:44:
 ./machine/atomic.h:449:29: error: invalid operand for instruction
 ATOMIC_ASM(set,  long,  "orq %1,%0",   "ir",  v);
  ^
 :1:6: note: instantiated into assembly here
  orq $-9223372036854775808,40672(%r14)
  ^~
 1 error generated.
 *** [i915_gem.o] Error code 1

 ___
 freebsd-current@freebsd.org mailing list
 https://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>>>
>>>
>>> It breaks also graphics/drm-stable-kmod (see PR 229484,
>>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229484, same error as you 
>>> described
>>> above) and also emulators/virtualbox-ose-kmod. As long as CURRENT revision 
>>> is < r335873,
>>> those kmod compile well.
>>
>> We are looking into why both the drm ports fail.
>> Regards
>>
> 
> I haven't yet tested an amd64 kernel with this, but I think this change to 
> sys/amd64/include/atomic.h
> might fix it:
> 
> Index: atomic.h
> ===
> --- atomic.h  (revision 335896)
> +++ atomic.h  (working copy)
> @@ -446,10 +446,10 @@ ATOMIC_ASM(clear,int,   "andl %1,%0",  "ir", ~
>  ATOMIC_ASM(add,   int,   "addl %1,%0",  "ir",  v);
>  ATOMIC_ASM(subtract, int,   "subl %1,%0",  "ir",  v);
>  
> -ATOMIC_ASM(set,   long,  "orq %1,%0",   "ir",  v);
> -ATOMIC_ASM(clear,long,  "andq %1,%0",  "ir", ~v);
> -ATOMIC_ASM(add,   long,  "addq %1,%0",  "ir",  v);
> -ATOMIC_ASM(subtract, long,  "subq %1,%0",  "ir",  v);
> +ATOMIC_ASM(set,   long,  "orq %1,%0",   "er",  v);
> +ATOMIC_ASM(clear,long,  "andq %1,%0",  "er", ~v);
> +ATOMIC_ASM(add,   long,  "addq %1,%0",  "er",  v);
> +ATOMIC_ASM(subtract, long,  "subq %1,%0",  "er",  v);
>  
>  #define  ATOMIC_LOADSTORE(TYPE)  \
>   ATOMIC_LOAD(TYPE);  \

Isn't "Z" better than "e" in this case?

Jung-uk Kim



signature.asc
Description: OpenPGP digital signature

Re: atomic changes break drm-next-kmod?

2018-07-03 Thread Jung-uk Kim 
-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 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-next-kmod/work/kms-drm-a753215/linuxkpi/gp
lv2/include/linux/acpi.h:26:
>
>
> 
In file included from
> /usr/ports/graphics/drm-next-kmod/work/kms-drm-a753215/linuxkpi/gp
lv2/include/linux/device.h:4:
>
>
> 
In file included from
> /usr/src/sys/compat/linuxkpi/common/include/linux/device.h:35:
>
>
> 
In file included from
> /usr/src/sys/compat/linuxkpi/common/include/linux/types.h:37:
>
>
> 
In file included from /usr/src/sys/sys/systm.h:44:
> ./machine/atomic.h:450:29: error: invalid operand for 
> instruction ATOMIC_ASM(clear,long,  "andq %1,%0", "ir",
> ~v); ^ :1:7: note: instantiated into assembly
> here andq $9223372036854775807,40672(%r14) 
> ^ 1 error generated. *** [i915_drv.o] 
> Error code 1
> 
> make[3]: stopped in 
> /usr/ports/graphics/drm-next-kmod/work/kms-drm-a753215/i915
>
>
> 
- --- i915_gem.o ---
> In file included from i915_gem.c:28: In file included from
>  
> /usr/ports/graphics/drm-next-kmod/work/kms-drm-a753215/include/drm
/drmP.h:38:
>
>
> 
In file included from /usr/src/sys/sys/malloc.h:42:
> In file included from /usr/src/sys/sys/systm.h:44: 
> ./machine/atomic.h:449:29: error: invalid operand for 
> instruction ATOMIC_ASM(set,  long,  "orq %1,%0", "ir",
> v); ^ :1:6: note: instantiated into assembly
> here orq $-9223372036854775808,40672(%r14) 
> ^~ 1 error generated. *** [i915_gem.o] 
> Error code 1
> 
> ___ 
> freebsd-current@freebsd.org mailing list 
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>  To unsubscribe, send any mail to 
> "freebsd-current-unsubscr...@freebsd.org"
 
 
 It breaks also graphics/drm-stable-kmod (see PR 229484, 
 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229484, 
 same error as you described above) and also 
 emulators/virtualbox-ose-kmod. As long as CURRENT revision
 is < r335873, those kmod compile well.
>>> 
>>> We are looking into why both the drm ports fail. Regards
>>> 
>> 
>> I haven't yet tested an amd64 kernel with this, but I think this 
>> change to sys/amd64/include/atomic.h might fix it:
>> 
>> Index: atomic.h 
>> ===
>>
>>
>> 
- --- atomic.h  (revision 335896)
>> +++ atomic.h (working copy) @@ -446,10 +446,10 @@ 
>> ATOMIC_ASM(clear,int,   "andl %1,%0",  "ir", ~ 
>> ATOMIC_ASM(add,   int,   "addl %1,%0",  "ir",  v); 
>> ATOMIC_ASM(subtract, int,   "subl %1,%0",  "ir",  v);
>> 
>> -ATOMIC_ASM(set,  long,  "orq %1,%0",   "ir",  v); 
>> -ATOMIC_ASM(clear,long,  "andq %1,%0",  "ir", ~v); 
>> -ATOMIC_ASM(add,  long,  "addq %1,%0",  "ir",  v); 
>> -ATOMIC_ASM(subtract, long,  "subq %1,%0",  "ir",  v); 
>> +ATOMIC_ASM(set,  long,  "orq %1,%0",   "er",  v); 
>> +ATOMIC_ASM(clear,long,  "andq %1,%0",  "er", ~v); 
>> +ATOMIC_ASM(add,  long,  "addq %1,%0",  "er",  v); 
>> +ATOMIC_ASM(subtract, long,  "subq %1,%0",  "er",  v);
>> 
>> #define  ATOMIC_LOADSTORE(TYPE)  \ 
>> ATOMIC_LOAD(TYPE);\
> 
> Isn't "Z" better than "e" in this case?

Never mind, brain fart.  These instructions are sign-extended.

Sorry for the noise.

Jung-uk Kim
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEl1bqgKaRyqfWXu/CfJ+WJvzb8UYFAls7zy8ACgkQfJ+WJvzb
8UYiOgf+PSb+Mv7UGCTUlftCiRmYYOW6ElMZSdr4tPinMocn4b/V9KJDqKOgO1SX
B2KCQHgSYt4Y+STiSrcCdhIkqCeIxdqJGHdTNpnpiUm7C+B50MrKgZo6n1xnlcCM
d4thqf0T/ZMaVaVEkZ42FTnmdXFo0L3jHNCHHYrpnXXXfRLJF6j5Q5Uetr1GEUJX
rpV2NIXMdk308qy4EvagLd0DEtT85QAjuG124nKh5FoSFD+5wBGFVrQWk4v4LVyd
rzBNM55JbTlEIFASlFjpiWJVhGvDzNVwN9XRxacYVgfEv23AMEibqhK12V48Lto/
X1/qHA0T9HC+gu/Eol+53AtU/P8ZyQ==
=cHxX
-END PGP SIGNATURE-
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

[regression] The USB WiFi card stopped working: if_run doesn't create the 'run0' interface any more

2018-07-03 Thread Yuri 
I updated the laptop to r335884 last night, and 'service wpa_supplicant 
start wlan0' doesn't succeed any more.


kernel is supposed to create the network interface 'run0', but it 
doesn't. This is the immediate reason why wpa_supplicant fails.


The non-creation of 'run0' is a regression. I don't know of any workaround.


The steps 'mergemaster -p' and 'mergemaster' were done during the 
upgrade, so /etc is updated.



Yuri


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: [regression] The USB WiFi card stopped working: if_run doesn't create the 'run0' interface any more

2018-07-03 Thread Lev Serebryakov 
On 03.07.2018 22:45, Yuri wrote:

> I updated the laptop to r335884 last night, and 'service wpa_supplicant
> start wlan0' doesn't succeed any more.
> 
> kernel is supposed to create the network interface 'run0', but it
> doesn't. This is the immediate reason why wpa_supplicant fails.
> 
> The non-creation of 'run0' is a regression. I don't know of any workaround.
 No, it isn't.

 https://lists.freebsd.org/pipermail/freebsd-wireless/2016-October/007232.html

 I don't know, why is it not mentioned in UPDATING :-(


-- 
// Lev Serebryakov



signature.asc
Description: OpenPGP digital signature

Re: [regression] The USB WiFi card stopped working: if_run doesn't create the 'run0' interface any more

2018-07-03 Thread Yuri 

On 07/03/18 12:50, Lev Serebryakov wrote:

  No, it isn't.

  https://lists.freebsd.org/pipermail/freebsd-wireless/2016-October/007232.html

  I don't know, why is it not mentioned in UPDATING:-(



I may be mistaken about the interface creation.

But regardless of the cause, WiFi doesn't work any more. :-(


Yuri


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: [regression] The USB WiFi card stopped working: if_run doesn't create the 'run0' interface any more

2018-07-03 Thread Sean Bruno 


On 07/03/18 13:53, Yuri wrote:
> On 07/03/18 12:50, Lev Serebryakov wrote:
>>   No, it isn't.
>>
>>  
>> https://lists.freebsd.org/pipermail/freebsd-wireless/2016-October/007232.html
>>
>>
>>   I don't know, why is it not mentioned in UPDATING:-(
> 
> 
> I may be mistaken about the interface creation.
> 
> But regardless of the cause, WiFi doesn't work any more. :-(
> 
> 
> Yuri
> 
> 
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> 


Yuri:

If you're still having trouble, dump your rc.conf entries for your
wireless.  Mine looks like this at the moment with iwn(4):

wlans_iwn0="wlan0"
ifconfig_wlan0="WPA DHCP"

seam




signature.asc
Description: OpenPGP digital signature

Re: atomic changes break drm-next-kmod?

2018-07-03 Thread Pete Wright 



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-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-kmod/work/kms-drm-a753215/linuxkpi/gplv2/include/linux/device.h:4:
In file included from
/usr/src/sys/compat/linuxkpi/common/include/linux/device.h:35:
In file included from
/usr/src/sys/compat/linuxkpi/common/include/linux/types.h:37:
In file included from /usr/src/sys/sys/systm.h:44:
./machine/atomic.h:450:29: error: invalid operand for instruction
ATOMIC_ASM(clear,long,  "andq %1,%0",  "ir", ~v);
  ^
:1:7: note: instantiated into assembly here
  andq $9223372036854775807,40672(%r14)
   ^
1 error generated.
*** [i915_drv.o] Error code 1

make[3]: stopped in
/usr/ports/graphics/drm-next-kmod/work/kms-drm-a753215/i915
--- i915_gem.o ---
In file included from i915_gem.c:28:
In file included from
/usr/ports/graphics/drm-next-kmod/work/kms-drm-a753215/include/drm/drmP.h:38:
In file included from /usr/src/sys/sys/malloc.h:42:
In file included from /usr/src/sys/sys/systm.h:44:
./machine/atomic.h:449:29: error: invalid operand for instruction
ATOMIC_ASM(set,  long,  "orq %1,%0",   "ir",  v);
  ^
:1:6: note: instantiated into assembly here
  orq $-9223372036854775808,40672(%r14)
  ^~
1 error generated.
*** [i915_gem.o] Error code 1

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


It breaks also graphics/drm-stable-kmod (see PR 229484,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229484, same error as you 
described
above) and also emulators/virtualbox-ose-kmod. As long as CURRENT revision is < 
r335873,
those kmod compile well.

We are looking into why both the drm ports fail.
Regards


I haven't yet tested an amd64 kernel with this, but I think this change to 
sys/amd64/include/atomic.h
might fix it:

Index: atomic.h
===
--- atomic.h(revision 335896)
+++ atomic.h(working copy)
@@ -446,10 +446,10 @@ ATOMIC_ASM(clear,int,   "andl %1,%0",  "ir", ~
  ATOMIC_ASM(add,int,   "addl %1,%0",  "ir",  v);
  ATOMIC_ASM(subtract, int,   "subl %1,%0",  "ir",  v);
  
-ATOMIC_ASM(set,	 long,  "orq %1,%0",   "ir",  v);

-ATOMIC_ASM(clear,long,  "andq %1,%0",  "ir", ~v);
-ATOMIC_ASM(add, long,  "addq %1,%0",  "ir",  v);
-ATOMIC_ASM(subtract, long,  "subq %1,%0",  "ir",  v);
+ATOMIC_ASM(set, long,  "orq %1,%0",   "er",  v);
+ATOMIC_ASM(clear,long,  "andq %1,%0",  "er", ~v);
+ATOMIC_ASM(add, long,  "addq %1,%0",  "er",  v);
+ATOMIC_ASM(subtract, long,  "subq %1,%0",  "er",  v);
  
  #define	ATOMIC_LOADSTORE(TYPE)	\

ATOMIC_LOAD(TYPE);  \




i've just built a kernel with this patch applied, rebooted into it and 
was able to build the drm-next-kmod port.  i am also running X without 
issues so far with this configuration.


cheers,
-pete


--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: [regression] The USB WiFi card stopped working: if_run doesn't create the 'run0' interface any more

2018-07-03 Thread Yuri 

On 07/03/18 13:54, Sean Bruno wrote:

Yuri:

If you're still having trouble, dump your rc.conf entries for your
wireless.  Mine looks like this at the moment with iwn(4):

wlans_iwn0="wlan0"
ifconfig_wlan0="WPA DHCP"

seam



Thank you, Sean!


rc.conf has:

wlans_iwn0="wlan0"

ifconfig_wlan0="WPA DHCP"

wpa_supplicant_enable="YES"

wpa_supplicant_program="/usr/local/sbin/wpa_supplicant"


This worked before, and the only thing that has changed is that the system was 
updated.

The interface run0 exists.
After I run this command manually: ifconfig wlan0 create wlandev run0
wpa_supplicant works. But before this happened automatically, now it doesn't 
happen, and wpa_supplicant just fails.

Something in the system update affected the interoperability with 
wpa_supplicant.


Yuri

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: [regression] The USB WiFi card stopped working: if_run doesn't create the 'run0' interface any more

2018-07-03 Thread Yuri 

On 07/03/18 14:32, Yuri wrote:



rc.conf has:

wlans_iwn0="wlan0"

ifconfig_wlan0="WPA DHCP"

wpa_supplicant_enable="YES"

wpa_supplicant_program="/usr/local/sbin/wpa_supplicant"



This got mixed up.

rc.conf has:

wlans_run0="wlan0"
ifconfig_wlan0="WPA SYNCDHCP"
wpa_supplicant_enable="YES"
wpa_supplicant_program="/usr/local/sbin/wpa_supplicant"


Yuri


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: atomic changes break drm-next-kmod?

2018-07-03 Thread Pete Wright 



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 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-kmod/work/kms-drm-a753215/linuxkpi/gplv2/include/linux/device.h:4: 


In file included from
/usr/src/sys/compat/linuxkpi/common/include/linux/device.h:35:
In file included from
/usr/src/sys/compat/linuxkpi/common/include/linux/types.h:37:
In file included from /usr/src/sys/sys/systm.h:44:
./machine/atomic.h:450:29: error: invalid operand for instruction
ATOMIC_ASM(clear,    long,  "andq %1,%0",  "ir", ~v);
  ^
:1:7: note: instantiated into assembly here
  andq $9223372036854775807,40672(%r14)
   ^
1 error generated.
*** [i915_drv.o] Error code 1

make[3]: stopped in
/usr/ports/graphics/drm-next-kmod/work/kms-drm-a753215/i915
--- i915_gem.o ---
In file included from i915_gem.c:28:
In file included from
/usr/ports/graphics/drm-next-kmod/work/kms-drm-a753215/include/drm/drmP.h:38: 


In file included from /usr/src/sys/sys/malloc.h:42:
In file included from /usr/src/sys/sys/systm.h:44:
./machine/atomic.h:449:29: error: invalid operand for instruction
ATOMIC_ASM(set,  long,  "orq %1,%0",   "ir",  v);
  ^
:1:6: note: instantiated into assembly here
  orq $-9223372036854775808,40672(%r14)
  ^~
1 error generated.
*** [i915_gem.o] Error code 1

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to 
"freebsd-current-unsubscr...@freebsd.org"


It breaks also graphics/drm-stable-kmod (see PR 229484,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229484, same 
error as you described
above) and also emulators/virtualbox-ose-kmod. As long as CURRENT 
revision is < r335873,

those kmod compile well.

We are looking into why both the drm ports fail.
Regards

I haven't yet tested an amd64 kernel with this, but I think this 
change to sys/amd64/include/atomic.h

might fix it:

Index: atomic.h
===
--- atomic.h    (revision 335896)
+++ atomic.h    (working copy)
@@ -446,10 +446,10 @@ ATOMIC_ASM(clear,    int,   "andl %1,%0", "ir", ~
  ATOMIC_ASM(add, int,   "addl %1,%0",  "ir",  v);
  ATOMIC_ASM(subtract, int,   "subl %1,%0",  "ir",  v);
  -ATOMIC_ASM(set, long,  "orq %1,%0",   "ir",  v);
-ATOMIC_ASM(clear,    long,  "andq %1,%0",  "ir", ~v);
-ATOMIC_ASM(add, long,  "addq %1,%0",  "ir",  v);
-ATOMIC_ASM(subtract, long,  "subq %1,%0",  "ir",  v);
+ATOMIC_ASM(set, long,  "orq %1,%0",   "er",  v);
+ATOMIC_ASM(clear,    long,  "andq %1,%0",  "er", ~v);
+ATOMIC_ASM(add, long,  "addq %1,%0",  "er",  v);
+ATOMIC_ASM(subtract, long,  "subq %1,%0",  "er",  v);
    #define    ATOMIC_LOADSTORE(TYPE)    \
  ATOMIC_LOAD(TYPE);    \




i've just built a kernel with this patch applied, rebooted into it and 
was able to build the drm-next-kmod port.  i am also running X without 
issues so far with this configuration.





oh neat - looks like this may have triggered a kernel panic. fortunately 
i was able to savecore.  here's the output of my info file:


info:
  Version String: FreeBSD 12.0-CURRENT #7 d7ac1268f3a(master)-dirty: 
Tue Jul  3 13:53:50 PDT 2018

pete@duke:/usr/obj/usr/home/pete/git/freebsd/amd64.amd64/sys/GENERIC-EVDEV
  Panic String: Duplicate free of 0xf8010ac59000 from zone 
0xf800340935a0(i915_gem_request) slab 0xf8010ac43af0(0)


i didn't build a kernel.debug file unfortunately, but here's the output 
of my core.txt file, not sure how helpful it is:


BFD: /bootpool/boot/kernel/kernel: invalid relocation type 37
BFD: BFD 2.17.50 [FreeBSD] 2007-07-03 assertion fail 
/usr/home/pete/git/freebsd/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/elf64-x86-64.c:276

BFD: /bootpool/boot/kernel/kernel: invalid relocation type 37
BFD: BFD 2.17.50 [FreeBSD] 2007-07-03 assertion fail 
/usr/home/pete/git/freebsd/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/elf64-x86-64.c:276

/dev/stdin:1: Error in sourced command file:
Cannot access memory at address 0x65657246
BFD: /bootpool/boot/kernel/kernel: invalid relocation type 37
BFD: BFD 2.17.50 [FreeBSD] 2007-07-03 assertion fail 
/usr/home/pete/git/freebsd/gnu/usr.bin/binutils/libbfd/../../../../contrib/binutils/bfd/elf64-x86-64.c:276

BFD: /bootpool/boot/kernel/kernel: invalid

Re: atomic changes break drm-next-kmod?

2018-07-03 Thread Pete Wright 



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
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-next-kmod/work/kms-drm-a753215/linuxkpi/gplv2/include/linux/acpi.h:26: 


In file included from
/usr/ports/graphics/drm-next-kmod/work/kms-drm-a753215/linuxkpi/gplv2/include/linux/device.h:4: 


In file included from
/usr/src/sys/compat/linuxkpi/common/include/linux/device.h:35:
In file included from
/usr/src/sys/compat/linuxkpi/common/include/linux/types.h:37:
In file included from /usr/src/sys/sys/systm.h:44:
./machine/atomic.h:450:29: error: invalid operand for instruction
ATOMIC_ASM(clear,    long,  "andq %1,%0",  "ir", ~v);
  ^
:1:7: note: instantiated into assembly here
  andq $9223372036854775807,40672(%r14)
   ^
1 error generated.
*** [i915_drv.o] Error code 1

make[3]: stopped in
/usr/ports/graphics/drm-next-kmod/work/kms-drm-a753215/i915
--- i915_gem.o ---
In file included from i915_gem.c:28:
In file included from
/usr/ports/graphics/drm-next-kmod/work/kms-drm-a753215/include/drm/drmP.h:38: 


In file included from /usr/src/sys/sys/malloc.h:42:
In file included from /usr/src/sys/sys/systm.h:44:
./machine/atomic.h:449:29: error: invalid operand for instruction
ATOMIC_ASM(set,  long,  "orq %1,%0",   "ir",  v);
  ^
:1:6: note: instantiated into assembly here
  orq $-9223372036854775808,40672(%r14)
  ^~
1 error generated.
*** [i915_gem.o] Error code 1

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to 
"freebsd-current-unsubscr...@freebsd.org"


It breaks also graphics/drm-stable-kmod (see PR 229484,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229484, same 
error as you described
above) and also emulators/virtualbox-ose-kmod. As long as CURRENT 
revision is < r335873,

those kmod compile well.

We are looking into why both the drm ports fail.
Regards

I haven't yet tested an amd64 kernel with this, but I think this 
change to sys/amd64/include/atomic.h

might fix it:

Index: atomic.h
===
--- atomic.h    (revision 335896)
+++ atomic.h    (working copy)
@@ -446,10 +446,10 @@ ATOMIC_ASM(clear,    int,   "andl %1,%0", "ir", ~
  ATOMIC_ASM(add, int,   "addl %1,%0",  "ir",  v);
  ATOMIC_ASM(subtract, int,   "subl %1,%0",  "ir",  v);
  -ATOMIC_ASM(set, long,  "orq %1,%0",   "ir",  v);
-ATOMIC_ASM(clear,    long,  "andq %1,%0",  "ir", ~v);
-ATOMIC_ASM(add, long,  "addq %1,%0",  "ir",  v);
-ATOMIC_ASM(subtract, long,  "subq %1,%0",  "ir",  v);
+ATOMIC_ASM(set, long,  "orq %1,%0",   "er",  v);
+ATOMIC_ASM(clear,    long,  "andq %1,%0",  "er", ~v);
+ATOMIC_ASM(add, long,  "addq %1,%0",  "er",  v);
+ATOMIC_ASM(subtract, long,  "subq %1,%0",  "er",  v);
    #define    ATOMIC_LOADSTORE(TYPE)    \
  ATOMIC_LOAD(TYPE);    \




i've just built a kernel with this patch applied, rebooted into it 
and was able to build the drm-next-kmod port.  i am also running X 
without issues so far with this configuration.





oh neat - looks like this may have triggered a kernel panic. 
fortunately i was able to savecore.  here's the output of my info file:


info:
  Version String: FreeBSD 12.0-CURRENT #7 d7ac1268f3a(master)-dirty: 
Tue Jul  3 13:53:50 PDT 2018
pete@duke:/usr/obj/usr/home/pete/git/freebsd/amd64.amd64/sys/GENERIC-EVDEV 

  Panic String: Duplicate free of 0xf8010ac59000 from zone 
0xf800340935a0(i915_gem_request) slab 0xf8010ac43af0(0)


i didn't build a kernel.debug file unfortunately, but here's the 
output of my core.txt file, not sure how helpful it is:


darn, hit send too soon - i was looking in wrong place for debug kernel 
- here is some hopefully more helpful info:


$ sudo kgdb /usr/lib/debug/boot/kernel/kernel.debug /var/crash/vmcore.1
Unread portion of the kernel message buffer:
WARNING !state->acquire_ctx failed at drm_atomic.c:634
WARNING !state->acquire_ctx failed at drm_atomic.c:270
WARNING !state->acquire_ctx failed at drm_atomic.c:634
WARNING !state->acquire_ctx failed at drm_atomic.c:634
WARNING !state->acquire_ctx failed at drm_atomic.c:634
WARNING !state->acquire_ctx failed at drm_atomic.c:270
WARNING !state->acquire_ctx failed at drm_atomic.c:634
WARNING !state->acquire_ctx failed at drm_atomic.c:270
WARNING !state->acquire_ctx failed at drm_atomic.c:270
WARNING !state->acquire_ctx

Re: [regression] The USB WiFi card stopped working: if_run doesn't create the 'run0' interface any more

2018-07-03 Thread Rodney W. Grimes 
> On 07/03/18 14:32, Yuri wrote:
> >
> >
> > rc.conf has:
> >
> > wlans_iwn0="wlan0"
> >
> > ifconfig_wlan0="WPA DHCP"
> >
> > wpa_supplicant_enable="YES"
> >
> > wpa_supplicant_program="/usr/local/sbin/wpa_supplicant"
^^

What wpa_supplicant is this?
The normal system one lives in /sbin.

> 
> This got mixed up.
> 
> rc.conf has:
> 
> wlans_run0="wlan0"
> ifconfig_wlan0="WPA SYNCDHCP"
> wpa_supplicant_enable="YES"
> wpa_supplicant_program="/usr/local/sbin/wpa_supplicant"
> 
> 
> Yuri
> 
> 
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> 

-- 
Rod Grimes rgri...@freebsd.org
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: atomic changes break drm-next-kmod?

2018-07-03 Thread John Baldwin 
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 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-next-kmod/work/kms-drm-a753215/linuxkpi/gplv2/include/linux/acpi.h:26:
>>>  
>>>
>>> In file included from
>>> /usr/ports/graphics/drm-next-kmod/work/kms-drm-a753215/linuxkpi/gplv2/include/linux/device.h:4:
>>>  
>>>
>>> In file included from
>>> /usr/src/sys/compat/linuxkpi/common/include/linux/device.h:35:
>>> In file included from
>>> /usr/src/sys/compat/linuxkpi/common/include/linux/types.h:37:
>>> In file included from /usr/src/sys/sys/systm.h:44:
>>> ./machine/atomic.h:450:29: error: invalid operand for instruction
>>> ATOMIC_ASM(clear,    long,  "andq %1,%0",  "ir", ~v);
>>>   ^
>>> :1:7: note: instantiated into assembly here
>>>   andq $9223372036854775807,40672(%r14)
>>>    ^
>>> 1 error generated.
>>> *** [i915_drv.o] Error code 1
>>>
>>> make[3]: stopped in
>>> /usr/ports/graphics/drm-next-kmod/work/kms-drm-a753215/i915
>>> --- i915_gem.o ---
>>> In file included from i915_gem.c:28:
>>> In file included from
>>> /usr/ports/graphics/drm-next-kmod/work/kms-drm-a753215/include/drm/drmP.h:38:
>>>  
>>>
>>> In file included from /usr/src/sys/sys/malloc.h:42:
>>> In file included from /usr/src/sys/sys/systm.h:44:
>>> ./machine/atomic.h:449:29: error: invalid operand for instruction
>>> ATOMIC_ASM(set,  long,  "orq %1,%0",   "ir",  v);
>>>   ^
>>> :1:6: note: instantiated into assembly here
>>>   orq $-9223372036854775808,40672(%r14)
>>>   ^~
>>> 1 error generated.
>>> *** [i915_gem.o] Error code 1
>>>
>>> ___
>>> freebsd-current@freebsd.org mailing list
>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>>> To unsubscribe, send any mail to 
>>> "freebsd-current-unsubscr...@freebsd.org"
>>
>> It breaks also graphics/drm-stable-kmod (see PR 229484,
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229484, same 
>> error as you described
>> above) and also emulators/virtualbox-ose-kmod. As long as CURRENT 
>> revision is < r335873,
>> those kmod compile well.
> We are looking into why both the drm ports fail.
> Regards
>
 I haven't yet tested an amd64 kernel with this, but I think this 
 change to sys/amd64/include/atomic.h
 might fix it:

 Index: atomic.h
 ===
 --- atomic.h    (revision 335896)
 +++ atomic.h    (working copy)
 @@ -446,10 +446,10 @@ ATOMIC_ASM(clear,    int,   "andl %1,%0", "ir", ~
   ATOMIC_ASM(add, int,   "addl %1,%0",  "ir",  v);
   ATOMIC_ASM(subtract, int,   "subl %1,%0",  "ir",  v);
   -ATOMIC_ASM(set, long,  "orq %1,%0",   "ir",  v);
 -ATOMIC_ASM(clear,    long,  "andq %1,%0",  "ir", ~v);
 -ATOMIC_ASM(add, long,  "addq %1,%0",  "ir",  v);
 -ATOMIC_ASM(subtract, long,  "subq %1,%0",  "ir",  v);
 +ATOMIC_ASM(set, long,  "orq %1,%0",   "er",  v);
 +ATOMIC_ASM(clear,    long,  "andq %1,%0",  "er", ~v);
 +ATOMIC_ASM(add, long,  "addq %1,%0",  "er",  v);
 +ATOMIC_ASM(subtract, long,  "subq %1,%0",  "er",  v);
     #define    ATOMIC_LOADSTORE(TYPE)    \
   ATOMIC_LOAD(TYPE);    \


>>>
>>> i've just built a kernel with this patch applied, rebooted into it 
>>> and was able to build the drm-next-kmod port.  i am also running X 
>>> without issues so far with this configuration.
>>>
>>
>>
>> oh neat - looks like this may have triggered a kernel panic. 
>> fortunately i was able to savecore.  here's the output of my info file:
>>
>> info:
>>   Version String: FreeBSD 12.0-CURRENT #7 d7ac1268f3a(master)-dirty: 
>> Tue Jul  3 13:53:50 PDT 2018
>> pete@duke:/usr/obj/usr/home/pete/git/freebsd/amd64.amd64/sys/GENERIC-EVDEV 
>>
>>   Panic String: Duplicate free of 0xf8010ac59000 from zone 
>> 0xf800340935a0(i915_gem_request) slab 0xf8010ac43af0(0)
>>
>> i didn't build a kernel.debug file unfortunately, but here's the 
>> output of my core.txt file, not sure how helpful it is:
> 
> darn, hit send too soon

Re: atomic changes break drm-next-kmod?

2018-07-03 Thread Pete Wright 




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
p...@nomadlogic.org
@nomadlogicLA

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: [regression] The USB WiFi card stopped working: if_run doesn't create the 'run0' interface any more

2018-07-03 Thread Yuri 

On 07/03/18 15:29, Rodney W. Grimes wrote:

wpa_supplicant_program="/usr/local/sbin/wpa_supplicant"

 ^^

What wpa_supplicant is this?
The normal system one lives in /sbin.


It's installed by the package wpa_supplicant-2.6_2 from 
security/wpa_supplicant.
It is supposed to be the most recent version of the same project where 
system wpa_supplicant comes from.



Yuri

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: atomic changes break drm-next-kmod?

2018-07-03 Thread John Baldwin 
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' 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

That doesn't look right at all.  Are you sure the kernel matches the
vmcore?  Also, which kgdb version are you using?

-- 
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: atomic changes break drm-next-kmod?

2018-07-03 Thread John Baldwin 
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/Machine-Constraints.html#Machine-Constraints

The disassembly of one of the functions from the kmod using one of the affected 
atomic ops would
show if it is working correctly (there should now be a mov with a 64-bit 
immediate into a register
followed by the atomic op using a register operand).  You could also try using 
just 'r' to always
force the use of a register.  It would be less optimal than "er" but should 
function correctly.

> 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' 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
> p...@nomadlogic.org 
> @nomadlogicLA
> 
> ___
> freebsd-current@freebsd.org  mailing 
> list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org 
> "
> 


-- 
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: atomic changes break drm-next-kmod?

2018-07-03 Thread Matthew Macy 
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' 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
> p...@nomadlogic.org
> @nomadlogicLA
>
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: atomic changes break drm-next-kmod?

2018-07-03 Thread Pete Wright 



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

That doesn't look right at all.  Are you sure the kernel matches the
vmcore?  Also, which kgdb version are you using?



yea i agree that doesn't look right at all.  here is my setup:

$ which kgdb
/usr/bin/kgdb
$ kgdb
GNU gdb 6.1.1 [FreeBSD]
$ ls -lh /var/crash/vmcore.1
-rw---  1 root  wheel   1.6G Jul  3 15:03 /var/crash/vmcore.1
$ ls -l /usr/lib/debug/boot/kernel/kernel.debug
-r-xr-xr-x  1 root  wheel  87840496 Jul  3 13:54 
/usr/lib/debug/boot/kernel/kernel.debug


and i invoke kgdb like so:
$ sudo kgdb /usr/lib/debug/boot/kernel/kernel.debug /var/crash/vmcore.1

here's a gist of my full gdb session:
http://termbin.com/krsn

dunno - maybe i have a bad core dump?  regardless, more than happy to 
help so let me know if i should try anything else or patches etc..


-pete

--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: [regression] The USB WiFi card stopped working: if_run doesn't create the 'run0' interface any more

2018-07-03 Thread Rodney W. Grimes 
[ Charset UTF-8 unsupported, converting... ]
> On 07/03/18 15:29, Rodney W. Grimes wrote:
> >>> wpa_supplicant_program="/usr/local/sbin/wpa_supplicant"
> >  ^^
> >
> > What wpa_supplicant is this?
> > The normal system one lives in /sbin.
> 
> It's installed by the package wpa_supplicant-2.6_2 from 
> security/wpa_supplicant.
> It is supposed to be the most recent version of the same project where 
> system wpa_supplicant comes from.

Do you get the same failure condition if you use the
wpa_supplicant from the base system?

-- 
Rod Grimes rgri...@freebsd.org
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: atomic changes break drm-next-kmod?

2018-07-03 Thread Cy Schubert 
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 ..
> >>
> >> --- 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/incl
> ude/linux/acpi.h:26:
> >> In file included from
> >> /usr/ports/graphics/drm-next-kmod/work/kms-drm-a753215/linuxkpi/gplv2/incl
> ude/linux/device.h:4:
> >> In file included from
> >> /usr/src/sys/compat/linuxkpi/common/include/linux/device.h:35:
> >> In file included from
> >> /usr/src/sys/compat/linuxkpi/common/include/linux/types.h:37:
> >> In file included from /usr/src/sys/sys/systm.h:44:
> >> ./machine/atomic.h:450:29: error: invalid operand for instruction
> >> ATOMIC_ASM(clear,long,  "andq %1,%0",  "ir", ~v);
> >>  ^
> >> :1:7: note: instantiated into assembly here
> >>  andq $9223372036854775807,40672(%r14)
> >>   ^
> >> 1 error generated.
> >> *** [i915_drv.o] Error code 1
> >>
> >> make[3]: stopped in
> >> /usr/ports/graphics/drm-next-kmod/work/kms-drm-a753215/i915
> >> --- i915_gem.o ---
> >> In file included from i915_gem.c:28:
> >> In file included from
> >> /usr/ports/graphics/drm-next-kmod/work/kms-drm-a753215/include/drm/drmP.h:
> 38:
> >> In file included from /usr/src/sys/sys/malloc.h:42:
> >> In file included from /usr/src/sys/sys/systm.h:44:
> >> ./machine/atomic.h:449:29: error: invalid operand for instruction
> >> ATOMIC_ASM(set,  long,  "orq %1,%0",   "ir",  v);
> >>  ^
> >> :1:6: note: instantiated into assembly here
> >>  orq $-9223372036854775808,40672(%r14)
> >>  ^~
> >> 1 error generated.
> >> *** [i915_gem.o] Error code 1
> >>
> >> ___
> >> freebsd-current@freebsd.org mailing list
> >> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> >> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> > 
> > 
> > It breaks also graphics/drm-stable-kmod (see PR 229484,
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229484, same error as you
>  described
> > above) and also emulators/virtualbox-ose-kmod. As long as CURRENT revision 
> is < r335873,
> > those kmod compile well.

The vbox issue looks like namespace pollution.


-- 
Cheers,
Cy Schubert 
FreeBSD UNIX: Web:  http://www.FreeBSD.org

The need of the many outweighs the greed of the few.


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"