Re: Compilation failure of the kernel for drm-next

2018-02-26 Thread Pete Wright 



On 02/26/2018 17:17, Mylan Connolly wrote:

Hello all,

I'm not sure if this is the best place to send this, but it looks like the 
issue tracker in Github is a bit dead.


there may not be much traffic on it recently, but people are def still 
actively working on the repository and will see when new issues are 
reported.


as of now your best to to use or test out the drm-next bits is to run a 
recent 12-CURRENT with no patches applied.  then you can build the port 
or package via the ports tree under graphics/drm-next-kmod.  it 
currently runs on my end under 12-CURRENT and 11-STABLE.


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"

Compilation failure of the kernel for drm-next

2018-02-26 Thread Mylan Connolly 
Hello all,

I'm not sure if this is the best place to send this, but it looks like the 
issue tracker in Github is a bit dead.

I have been trying to compile it for the past few weeks after downloading the 
latest code about once a week and it looks like this issue hasn't resolved 
itself.

When I try to compile the kernel (using the command `make kernel`) I get the 
following error. Let me know if there's anything else I can do to assist.

/usr/local/bin/ccache cc -target x86_64-unknown-freebsd12.0 
--sysroot=/usr/obj/usr/src/amd64.amd64/tmp 
-B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin  -O2 -pipe 
'-DKBUILD_MODNAME="i915kms"' -include /usr/src/sys/dev/drm/drm_os_config.h 
-march=skylake  -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc  
-I/usr/src/sys/compat/linuxkpi/dummy/include 
-I/usr/src/sys/compat/linuxkpi/gplv2/include 
-I/usr/src/sys/compat/linuxkpi/common/include 
-I/usr/src/sys/compat/linuxkpi/common/include/uapi -DHAVE_KERNEL_OPTION_HEADERS 
-include /usr/obj/usr/src/amd64.amd64/sys/GENERIC/opt_global.h -I. 
-I/usr/src/sys -fno-common -g -fno-omit-frame-pointer 
-mno-omit-leaf-frame-pointer -I/usr/obj/usr/src/amd64.amd64/sys/GENERIC   -MD  
-MF.depend.intel_freebsd.o -MTintel_freebsd.o -mcmodel=kernel -mno-red-zone 
-mno-mmx -mno-sse -msoft-float  -fno-asynchronous-unwind-tables -ffreestanding 
-fwrapv -fstack-protector -gdwarf-2 -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes -Wmissing-prototype
 s -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign 
-D__printf__=__freebsd_kprintf__ -Wmissing-include-dirs 
-fdiagnostics-show-option -Wno-unknown-pragmas -Wno-error-tautological-compare 
-Wno-error-empty-body -Wno-error-parentheses-equality 
-Wno-error-unused-function -Wno-error-pointer-sign 
-Wno-error-shift-negative-value -Wno-error-address-of-packed-member 
-Wno-pointer-arith -Wno-format  -mno-aes -mno-avx  -std=iso9899:1999 -c 
/usr/src/sys/dev/drm/i915/intel_freebsd.c -o intel_freebsd.o

/usr/src/sys/dev/drm/i915/intel_freebsd.c:203:5: error: use of undeclared 
identifier 'VM_WAIT'; did you mean 'VM_LAST'?

VM_WAIT;

^~~

VM_LAST

/usr/src/sys/sys/systm.h:81:50: note: 'VM_LAST' declared here

VM_GUEST_VMWARE, VM_GUEST_KVM, VM_GUEST_BHYVE, VM_LAST };

   ^

/usr/src/sys/dev/drm/i915/intel_freebsd.c:203:5: error: expression result 
unused [-Werror,-Wunused-value]

VM_WAIT;

^~~

2 errors generated.

*** [intel_freebsd.o] Error code 1

make[6]: stopped in /usr/src/sys/modules/drm/i915/i915kms

1 error

make[6]: stopped in /usr/src/sys/modules/drm/i915/i915kms

*** [all_subdir_drm/i915/i915kms] Error code 2

make[5]: stopped in /usr/src/sys/modules/drm/i915

1 error

make[5]: stopped in /usr/src/sys/modules/drm/i915

*** [all_subdir_drm/i915] Error code 2

make[4]: stopped in /usr/src/sys/modules/drm

1 error

make[4]: stopped in /usr/src/sys/modules/drm

*** [all_subdir_drm] Error code 2

make[3]: stopped in /usr/src/sys/modules

1 error

make[3]: stopped in /usr/src/sys/modules

*** [modules-all] Error code 2

make[2]: stopped in /usr/obj/usr/src/amd64.amd64/sys/GENERIC

1 error

make[2]: stopped in /usr/obj/usr/src/amd64.amd64/sys/GENERIC

*** [buildkernel] Error code 2

make[1]: stopped in /usr/src

1 error

make[1]: stopped in /usr/src

*** [buildkernel] Error code 2

make: stopped in /usr/src

1 error

make: stopped in /usr/src

Mylan
___
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: update of graphics/drm-next-kmod to Linux 4.11 level for recent CURRENT and 11-STABLE

2018-02-26 Thread Ronald Klop 
On Sun, 25 Feb 2018 16:48:44 +0100, Johannes M Dieterich   
wrote:



Dear all,

Please CC me as I am not subscribed.

On behalf of the FreeBSDDesktop team and thanks to the tireless efforts
of Johannes Lundberg and Hans Petter Selasky (hselasky), I am pleased to
report that the graphics/drm-next-kmod port just received an update to
Linux level 4.11 KMS/DRM for amdgpu, radeon, and i915 for both recent
CURRENT and 11-STABLE.

We have tested this on a range of hardware ourselves:
* Haswell
* Broadwell
* Skylake
* Evergreen
* Kaveri (both radeon and amgpu KMS)
* Carrizo
* Polaris

Needless to say, the possible space of hardware this could run on is
significantly larger. Hence, if you find issues and/or want to propose
patches, please do so at our development github:

https://github.com/FreeBSDDesktop/kms-drm

We absolutely do welcome contributions!

Johannes



Nice work. It might be nice to edit the linux 4,9 reference from pkg-descr.

Regards,
Ronald.
___
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: Errors compiling LLVM on RPi3 at 330019

2018-02-26 Thread Dimitry Andric 
On 26 Feb 2018, at 16:23, bob prohaska  wrote:
> 
> At revision 330019 -DNO_CLEAN buildworld stops with
> 
> --- Target/X86/X86ISelDAGToDAG.o ---
> /usr/src/contrib/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:2463:7: error: use 
> of undeclared identifier 'SelectCode'
>  SelectCode(ZextTarget.getNode());
>  ^
> /usr/src/contrib/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:2464:7: error: use 
> of undeclared identifier 'SelectCode'
>  SelectCode(Brind.getNode());
>  ^
> /usr/src/contrib/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:2480:5: error: use 
> of undeclared identifier 'SelectCode'
>SelectCode(VSelect.getNode());
>^
> /usr/src/contrib/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:3072:3: error: use 
> of undeclared identifier 'SelectCode'
>  SelectCode(Node);
> 
> Should I wait for an update, or run cleandir? This is on a Pi3.

From which revision were you upgrading?  It looks like your .inc files
were not regenerated properly by llvm-tblgen, maybe timestamps out of
whack?  I would indeed try a clean build.

-Dimitry



signature.asc
Description: Message signed with OpenPGP

Errors compiling LLVM on RPi3 at 330019

2018-02-26 Thread bob prohaska 
At revision 330019 -DNO_CLEAN buildworld stops with

--- Target/X86/X86ISelDAGToDAG.o ---
/usr/src/contrib/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:2463:7: error: use of 
undeclared identifier 'SelectCode'
  SelectCode(ZextTarget.getNode());
  ^
/usr/src/contrib/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:2464:7: error: use of 
undeclared identifier 'SelectCode'
  SelectCode(Brind.getNode());
  ^
/usr/src/contrib/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:2480:5: error: use of 
undeclared identifier 'SelectCode'
SelectCode(VSelect.getNode());
^
/usr/src/contrib/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:3072:3: error: use of 
undeclared identifier 'SelectCode'
  SelectCode(Node);

Should I wait for an update, or run cleandir? This is on a Pi3.

Thanks for reading,

bob prohaska

___
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: lock order reversal

2018-02-26 Thread Chris H 

On Mon, 26 Feb 2018 08:42:14 +0200 "Andriy Gapon"  said


On 26/02/2018 07:18, Jon Brawn wrote:
> Wotcha!
> 
> So, I’ve been using FreeBSD 12-CURRENT at various svn releases for a while

> now, and I get quite a few “lock order reversal” dumps. The one I’ve got
> on my screen at the moment is for ufs / bufwait / ufs:
> 
> root@brax:/usr/src/stand # lock order reversal:

>  1st 0xfd0003ec17e8 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2602
>  2nd 0x410efa20 bufwait (bufwait) @
>  /usr/src/sys/ufs/ffs/ffs_vnops.c:282
>  3rd 0xfd00b83ca7e8 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2602
> stack backtrace:
> #0 0x003b59d4 at witness_debugger+0x64
> #1 0x0032bd34 at __lockmgr_args+0x6ac
> #2 0x005c6af0 at ffs_lock+0x88
> #3 0x00679eb0 at VOP_LOCK1_APV+0xac
> #4 0x00426fa8 at _vn_lock+0x64
> #5 0x00417550 at vget+0x78
> #6 0x00409fdc at vfs_hash_get+0xec
> #7 0x005c2b94 at ffs_vgetf+0x44
> #8 0x005b96a8 at softdep_sync_buf+0x9f4
> #9 0x005c7834 at ffs_syncvnode+0x26c
> #10 0x005a1b5c at ffs_truncate+0x6b0
> #11 0x005ce3cc at ufs_direnter+0x778
> #12 0x005d64bc at ufs_makeinode+0x4b8
> #13 0x005d2b90 at ufs_create+0x38
> #14 0x00677168 at VOP_CREATE_APV+0xac
> #15 0x0042691c at vn_open_cred+0x264
> #16 0x0041fc84 at kern_openat+0x208
> #17 0x0064b59c at do_el0_sync+0x8bc
> 
> Is there something I should be doing to help debug these?


IMO, no. Please ignore LORs involving "bufwait", "filedesc structure",
"syncer"
unless you experience any real problem (like a lock up).

Or build a kernel without WITNESS (and FULL_BUF_TRACKING?) :-)

--Chris


--
Andriy Gapon
___
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"