Re: urtwn(4) / rtwn(4) drivers are merged - call for testing (Was: RTL8812AU / RTL8821AU driver)

2016-10-21 Thread Kurt Jaeger
Hi!

> > rtwn(4), urtwn(4) and urtwm (from previous emails) drivers were merged
> > into a
> > single rtwn driver (plus rtwn_usb / rtwn_pci device glue); the code is
> > available on https://github.com/s3erios/rtwn repository. Among bugfixes /
> > code deduplication, there some new features too:
> [...]
> 
> It took a while to test both, the github version as well as the most
> recent version on -CURRENT (r307731) with my RTL8188CE (PCI).

Does this code only work on CURRENT or should it also work on 11.0p1 ?

I've build it on a X220 thinkpad with

none2@pci0:3:0:0:   class=0x028000 card=0x819510ec chip=0x817610ec rev=0x01 
hdr=0x00
vendor = 'Realtek Semiconductor Co., Ltd.'
device = 'RTL8188CE 802.11b/g/n WiFi Adapter'
class  = network
bar   [10] = type I/O Port, range 32, base 0x5000, size 256, enabled
bar   [18] = type Memory, range 64, base 0xf240, size 16384, enabled

and tried to reboot with

if_rtwn_load="YES"
legal.realtek.license_ack=1
rtwn-rtl8192cfwU_load="YES"
rtwn-rtl8192cfwU_B_load="YES"

in /boot/loader.conf. The device was not found/detected.

kldstat finds those (I did a kldload rtwn-* post-boot):

Id Refs AddressSize Name
 1   55 0x8020 1fa7c38  kernel
 21 0x821a9000 30aee8   zfs.ko
 32 0x824b4000 adc8 opensolaris.ko
 41 0x824bf000 21be8geom_eli.ko
 51 0x824e2000 b3f0 aesni.ko
 61 0x824ee000 23ce8if_rtwn.ko
 71 0x82512000 5368 rtwn-rtl8192cfwU.ko
 81 0x8273d000 3980 umodem.ko
 91 0x82741000 53e3 ucom.ko
101 0x82747000 5769 if_cdce.ko
111 0x8274d000 2bf2 uether.ko
121 0x8275 2324fipfw.ko
131 0x82774000 3d84 rtwn-rtl8188eufw.ko
141 0x82778000 4117 rtwn-rtl8192cfwE.ko
151 0x8277d000 4704 rtwn-rtl8192cfwE_B.ko
161 0x82782000 462a rtwn-rtl8192cfwT.ko
171 0x82787000 846b rtwn-rtl8812aufw.ko
181 0x8279 73cb rtwn-rtl8821aufw.ko

Now I need some pointers on what I can do 8-}

-- 
p...@opsec.eu+49 171 3101372 4 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: Recent -CURRENT unable to build numerous ports

2016-10-21 Thread Aryeh Friedman
> This was a side-effect of r307676, which added transformation rules for
> .bco and .llo files (LLVM bytecode in binary and text representation).
>
> Because .SUFFIXES was not updated to match, bmake was actually trying to
> build a ".c.bco" file in the above case...
>
> I committed a fix in r307754.
>
>
Still doesn't work and still corrupts the base system (see output after
portmaster failure) on a fresh from CD install of 11-STABLE (post svlite of
/usr/src and make DESTDIR=/ world kernel):

root@lilith:/usr/src # uname -a
FreeBSD lilith 10.3-STABLE FreeBSD 10.3-STABLE #0 r307759: Sat Oct 22
00:14:55 EDT 2016 aryehl@lilith:/usr/obj/usr/src/sys/GENERIC  amd64


===>   Registering installation for gettext-runtime-0.19.8.1
pkg-static: Unable to access file
/usr/ports/devel/gettext-runtime/work/stage/usr/local/include/autosprintf.h:
No such file or directory
pkg-static: Unable to access file
/usr/ports/devel/gettext-runtime/work/stage/usr/local/lib/libasprintf.a: No
such file or directory
pkg-static: Unable to access file
/usr/ports/devel/gettext-runtime/work/stage/usr/local/lib/libasprintf.so:
No such file or directory
pkg-static: Unable to access file
/usr/ports/devel/gettext-runtime/work/stage/usr/local/lib/libasprintf.so.0:
No such file or directory
pkg-static: Unable to access file
/usr/ports/devel/gettext-runtime/work/stage/usr/local/lib/libasprintf.so.0.0.0:
No such file or directory
*** Error code 74

Stop.
make: stopped in /usr/ports/devel/gettext-runtime

===>>> Installation of gettext-runtime-0.19.8.1 (devel/gettext-runtime)
failed
===>>> Aborting update

===>>> Installation of print/indexinfo (indexinfo-0.2.5) complete


===>>> You can restart from the point of failure with this command line:
   portmaster  devel/gettext-runtime

root@lilith:/usr/ports # cd /usr/src
root@lilith:/usr/src # make DESTDIR=/ world kernel;
--
>>> make world started on Sat Oct 22 00:41:33 EDT 2016
--
--
>>> World build started on Sat Oct 22 00:41:33 EDT 2016
--

--
>>> Rebuilding the temporary build tree
--
rm -rf /usr/obj/usr/src/tmp/legacy/usr/include
rm -f /usr/obj/usr/src/usr.bin/kdump/ioctl.c
rm -f /usr/obj/usr/src/usr.bin/kdump/kdump_subr.c
rm -f /usr/obj/usr/src/usr.bin/truss/ioctl.c
mkdir -p /usr/obj/usr/src/tmp/lib
mkdir -p /usr/obj/usr/src/tmp/usr
mkdir -p /usr/obj/usr/src/tmp/legacy/bin
mkdir -p /usr/obj/usr/src/tmp/legacy/usr
mtree -deU -f /usr/src/etc/mtree/BSD.usr.dist  -p
/usr/obj/usr/src/tmp/legacy/usr >/dev/null
mtree -deU -f /usr/src/etc/mtree/BSD.groff.dist  -p
/usr/obj/usr/src/tmp/legacy/usr >/dev/null
mtree -deU -f /usr/src/etc/mtree/BSD.usr.dist  -p /usr/obj/usr/src/tmp/usr
>/dev/null
mtree -deU -f /usr/src/etc/mtree/BSD.include.dist  -p
/usr/obj/usr/src/tmp/usr/include >/dev/null
ln -sf /usr/src/sys /usr/obj/usr/src/tmp

--
>>> stage 1.1: legacy release compatibility shims
--
cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/usr/src/tmp  INSTALL="sh
/usr/src/tools/install.sh"
PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/legacy/bin:/sbin:/bin:/usr/sbin:/usr/bin
WORLDTMP=/usr/obj/usr/src/tmp  VERSION="FreeBSD 10.3-STABLE amd64 1003509"
MAKEFLAGS="-m /usr/src/tools/build/mk  -m /usr/src/share/mk"
COMPILER_TYPE=clang make  -f Makefile.inc1  DESTDIR=
BOOTSTRAPPING=1003509  SSP_CFLAGS=  -DWITHOUT_HTML -DWITHOUT_INFO -DNO_LINT
-DWITHOUT_MAN  -DNO_PIC -DNO_PROFILE -DNO_SHARED  _BOOTSTRAP_MAKEINFO=yes
-DNO_CPU_CFLAGS -DNO_WARNS -DNO_CTF -DEARLY_BUILD -DNO_TESTS legacy
===> tools/build (obj,includes,depend,all,install)
set -e; cd /usr/src/tools/build; make buildincludes; make installincludes
cc  -O2 -pipe  -I/usr/src/tools/build/../../contrib/libc-pwcache
-I/usr/src/tools/build/../../lib/libc/include -std=gnu99
-I/usr/obj/usr/src/tmp/legacy/usr/include -c
/usr/src/tools/build/../../contrib/libc-pwcache/pwcache.c -o pwcache.o
building static egacy library
ranlib -D libegacy.a
sh /usr/src/tools/install.sh -C -o root -g wheel -m 444   libegacy.a
/usr/obj/usr/src/tmp/legacy/usr/lib

--
>>> stage 1.2: bootstrap tools
--
cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/usr/src/tmp  INSTALL="sh
/usr/src/tools/install.sh"
PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/legacy/bin:/sbin:/bin:/usr/sbin:/usr/bin
WORLDTMP=/usr/obj/usr/src/tmp  VERSION="FreeBSD 10.3-

Jenkins build is back to normal : FreeBSD_HEAD #809

2016-10-21 Thread jenkins-admin
https://jenkins.FreeBSD.org/job/FreeBSD_HEAD/809/
___
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: Recent -CURRENT unable to build numerous ports

2016-10-21 Thread Dimitry Andric
On 21 Oct 2016, at 20:47, Marcus von Appen  wrote:
> 
> -CURRENT as of r307731 seems to have some serious flaw with its build
> tool environment. Many ports fail to build with some error similar to
> the following (devel/apr1):
> 
> cc -emit-llvm -fno-strict-aliasing -pipe -march=native -DLIBICONV_PLUG
>  -fstack-protector -c -o .c.bco
> cc: error: no input files
> *** [.c.bco] Error code 1
> [...]
> 
> Since not all ports are affected, I assume some auto[conf|tool|make]
> issue to be triggered. Hints for getting this one solved are highly
> appreciated.

This was a side-effect of r307676, which added transformation rules for
.bco and .llo files (LLVM bytecode in binary and text representation).

Because .SUFFIXES was not updated to match, bmake was actually trying to
build a ".c.bco" file in the above case...

I committed a fix in r307754.

-Dimitry



signature.asc
Description: Message signed with OpenPGP using GPGMail


Re: Recent -CURRENT unable to build numerous ports

2016-10-21 Thread Marcus von Appen
On, Fri Oct 21, 2016, Marcus von Appen wrote:

> Hi,
>
> -CURRENT as of r307731 seems to have some serious flaw with its build
> tool environment. Many ports fail to build with some error similar to
> the following (devel/apr1):
>
> cc -emit-llvm -fno-strict-aliasing -pipe -march=native -DLIBICONV_PLUG
>   -fstack-protector -c -o .c.bco
> cc: error: no input files
> *** [.c.bco] Error code 1
> [...]
>
> Since not all ports are affected, I assume some auto[conf|tool|make]
> issue to be triggered. Hints for getting this one solved are highly
> appreciated.
>

After some more testing, it seems to relate to our default make.
Switching MAKE to gmake seems to resolve the issue.

A simple test case:
1. create an empty Makefile
2. run make

Cheers
Marcus

signature.asc
Description: PGP signature


Re: urtwn(4) / rtwn(4) drivers are merged - call for testing (Was: RTL8812AU / RTL8821AU driver)

2016-10-21 Thread Marcus von Appen
On, Thu Sep 01, 2016, Andriy Voskoboinyk wrote:

> Hi everyone,
>
> rtwn(4), urtwn(4) and urtwm (from previous emails) drivers were merged
> into a
> single rtwn driver (plus rtwn_usb / rtwn_pci device glue); the code is
> available on https://github.com/s3erios/rtwn repository. Among bugfixes /
> code deduplication, there some new features too:
[...]

It took a while to test both, the github version as well as the most
recent version on -CURRENT (r307731) with my RTL8188CE (PCI).

The github version worked well until 2016-09-05 (commit 580cef).
Throughput was limited to around 400 kbit/s.
The next test from 2016-09-16 (commit a018e741) caused a better throughput,
mostly up to around 1.2 Mbit/s. Its stability was bad, though.
Kernel panics as well as random lockups of the interface struck often.
The version as of r307731 in -CURRENT is just as bad. It feels as if the
stability improvements from r302035 have been reverted.

What can I do to help you to improve the situation?

Cheers
Marcus


signature.asc
Description: PGP signature


r3077XX: LOR in vfs

2016-10-21 Thread O. Hartmann
Since r307157 I'm bugged with sporadic reboots/crashes of all boxes running 
CURRENT. That
is different CPU types (XEON C2D, XEON Haswell, XEON IvyBridge, mobile Haswell 
and
desktop IvyBridge).

Below, you'll finde some messages I gathered from the console. I hope this is 
of any use,
if not: I'm very sorry.

I'm also sorry being incapable of providing you with more informations of the 
crashes. I
do not have any clue how the crashes are related - I try to configure some 
boxes I have
direct access to with debugging options, but unfortunately they all have nvidia 
GPUs and
configured vt() for the UEFI and non UEFI systems - that means, the console is 
wreckage
since there is an unresolved buf as long as the nvidia-mode.ko is loaded. So 
far, the
crashing boxes didn't capture a core.

From the reports I got of the other crashing servers running recent CURRENT, 
last process
in braces is in most cases "(swapper)" or "(pager)" - I got this report via 
phone, sorry.

Anothe observation is that boxes with larger amounts of RAM last longer - a 
workstation
with 32 GB and r3076XX lasted for ~ 32 hours befor it crashed, a server with 16 
GB
takes several hours, sometimes only minutes and another machine with 8 GB goes 
down mor
frequently.

Anyway, try to give some mor infos in case I'm able to capture those. I'm really
surprised that it seems that I'm the only one facing those problems at the 
moment.  

[...]
Oct 21 05:09:59 <0.2> thor kernel: lock order reversal:
Oct 21 05:09:59 <0.2> thor kernel: 1st 0xfe01e98449f8 bufwait (bufwait)
@ /usr/src/sys/kern/vfs_bio.c:3505 Oct 21 05:09:59 <0.2> thor kernel: 2nd
0xf800098c2800 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:281 
Oct 21
05:09:59 <0.2> thor kernel: stack backtrace: Oct 21 05:09:59 <0.2> thor kernel: 
#0
0x80818410 at witness_debugger+0x70 Oct 21 05:09:59 <0.2> thor kernel: 
#1
0x8081830d at witness_checkorder+0xf0d Oct 21 05:09:59 <0.2> thor 
kernel: #2
0x807bbdc2 at _sx_xlock+0x72 Oct 21 05:09:59 <0.2> thor kernel: #3
0x80a8b507 at ufsdirhash_remove+0x37 Oct 21 05:09:59 <0.2> thor kernel: 
#4
0x80a8e760 at ufs_dirremove+0x120 Oct 21 05:09:59 <0.2> thor kernel: #5
0x80a961a8 at ufs_rename+0x14a8 Oct 21 05:09:59 <0.2> thor kernel: #6
0x80b6ce88 at VOP_RENAME_APV+0xe8 Oct 21 05:09:59 <0.2> thor kernel: #7
0x80891fa8 at kern_renameat+0x4a8 Oct 21 05:09:59 <0.2> thor kernel: #8
0x80af6934 at amd64_syscall+0x314 Oct 21 05:09:59 <0.2> thor kernel: #9
0x80ad6f1b at Xfast_syscall+0xfb Oct 21 05:10:00 <3.3> thor nslcd[543]: 
[d0722e]
 no available LDAP server found: Server is unavailable: 
Resource
temporarily unavailable Oct 21 05:10:00 <3.3> thor nslcd[543]: [d0722e]
 no available LDAP server found: Server is unavailable: 
Resource
temporarily unavailable Oct 21 05:10:00 <0.2> thor kernel: acquiring duplicate 
lock of
same type: "os.lock_sx" Oct 21 05:10:00 <0.2> thor kernel: 1st os.lock_sx @
nvidia_os.c:599 Oct 21 05:10:00 <0.2> thor kernel: 2nd os.lock_sx @ 
nvidia_os.c:599 Oct
21 05:10:00 <0.2> thor kernel: stack backtrace: Oct 21 05:10:00 <0.2> thor 
kernel: #0
0x80818410 at witness_debugger+0x70 Oct 21 05:10:00 <0.2> thor kernel: 
#1
0x8081830d at witness_checkorder+0xf0d Oct 21 05:10:00 <0.2> thor 
kernel: #2
0x807bbdc2 at _sx_xlock+0x72 Oct 21 05:10:00 <0.2> thor kernel: #3
0x81e792b2 at os_acquire_mutex+0x32 Oct 21 05:10:00 <0.2> thor kernel: 
#4
0x81e48bc8 at _nv017102rm+0x18 Oct 21 05:10:00 <0.2> thor kernel: 
acquiring
duplicate lock of same type: "os.lock_mtx" Oct 21 05:10:00 <0.2> thor kernel: 
1st
os.lock_mtx @ nvidia_os.c:778 Oct 21 05:10:00 <0.2> thor kernel: 2nd 
os.lock_mtx @
nvidia_os.c:778 Oct 21 05:10:00 <0.2> thor kernel: stack backtrace: Oct 21 
05:10:00 <0.2>
thor kernel: #0 0x80818410 at witness_debugger+0x70 Oct 21 05:10:00 
<0.2> thor
kernel: #1 0x8081830d at witness_checkorder+0xf0d Oct 21 05:10:00 <0.2> 
thor
kernel: #2 0x80792604 at __mtx_lock_flags+0xa4 Oct 21 05:10:00 <0.2> 
thor kernel:
#3 0x81e7962b at os_acquire_spinlock+0x1b Oct 21 05:10:00 <0.2> thor 
kernel: #4
0x81b97705 at _nv011755rm+0x185 Oct 21 05:10:00 <0.6> thor kernel:
nvidia-modeset: Allocated GPU:0 (GPU-85fde95a-7974-9962-f1a4-d7c164413929) @
PCI::01:00.0

[...]

Oct 21 05:23:19 <0.2> thor kernel: lock order reversal:
Oct 21 05:23:19 <0.2> thor kernel: 1st 0xf8017ee32d50 ufs (ufs)
@ /usr/src/sys/kern/vfs_lookup.c:522 Oct 21 05:23:19 <0.2> thor kernel: 2nd
0xfe01ea131fa8 bufwait (bufwait) @ /usr/src/sys/ufs/ffs/ffs_vnops.c:278 Oct 
21
05:23:19 <0.2> thor kernel: 3rd 0xf8017eebe5f0 ufs (ufs)
@ /usr/src/sys/kern/vfs_subr.c:2592 Oct 21 05:23:19 <0.2> thor kernel: stack 
backtrace:
Oct 21 05:23:19 <0.2> thor kernel: #0 0x80818410 at 
witness_debugger+0x70 Oct 21
05:23:19 <0.2> thor kernel: #1 0x8081830d at witness_checkorder+0xf0d 
Oct 21
05:23:19 <0.2> thor kern

Recent -CURRENT unable to build numerous ports

2016-10-21 Thread Marcus von Appen
Hi,

-CURRENT as of r307731 seems to have some serious flaw with its build
tool environment. Many ports fail to build with some error similar to
the following (devel/apr1):

cc -emit-llvm -fno-strict-aliasing -pipe -march=native -DLIBICONV_PLUG
  -fstack-protector -c -o .c.bco
cc: error: no input files
*** [.c.bco] Error code 1
[...]

Since not all ports are affected, I assume some auto[conf|tool|make]
issue to be triggered. Hints for getting this one solved are highly
appreciated.

Cheers
Marcus


signature.asc
Description: PGP signature


Jenkins build is back to normal : FreeBSD_HEAD #804

2016-10-21 Thread jenkins-admin
https://jenkins.FreeBSD.org/job/FreeBSD_HEAD/804/
___
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"