Re: VirtualBox network connectivity broken on recent -CURRENT

Em 04/06/2016 23:04, Randy Westlund escreveu: On Fri, Jun 03, 2016 at 05:11:24PM -0700, Don Lewis wrote: It looks like something changed in -CURRENT to break network connectivity to VirtualBox guests. This was last known to work with r299139 (May 6th) and is definitely broken with r301229.

Re: Date formatting with en_US locale

Em 26/05/2016 11:49, Baptiste Daroussin escreveu: On Thu, May 26, 2016 at 09:44:25AM -0500, Eric van Gyzen wrote: Baptiste and -current, I noticed two annoyances with date formatting on head, and I wonder how we can fix them. I have these settings: LC_ALL=en_US.ISO8859-1

Re: (beagleboneblack/urtwn) Kernel page fault with the following non-sleepable locks held [ssh on rpi2 comparison]

Em 21/06/2016 19:45, Keith White escreveu: On Tue, 21 Jun 2016, Ian Lepore wrote: On Tue, 2016-06-21 at 08:11 -0300, Otacílio wrote: Em 21/06/2016 07:33, Keith White escreveu: In an earlier message Ian said that he thought he knew what the problem was... Here the problem occurs when using

Re: (beagleboneblack/urtwn) Kernel page fault with the following non-sleepable locks held [ssh on rpi2 comparison]

Em 21/06/2016 07:33, Keith White escreveu: In an earlier message Ian said that he thought he knew what the problem was... Here the problem occurs when using wifi. I do not have tested wired because I don't have a cable here. []'s -Otacilio

Re: (beagleboneblack/urtwn) Kernel page fault with the following non-sleepable locks held

Em 19/06/2016 18:47, Otacílio escreveu: Em 19/06/2016 18:40, Otacílio escreveu: I was installing netperf on a fresh FreeBSD-ALPHA3 FreeBSD beaglebone 11.0-ALPHA3 FreeBSD 11.0-ALPHA3 #0 r301846: Mon Jun 13 19:54:27 BRT 2016 ota@nostromo:/root/crochet/work/obj/arm.armv6/usr/src/sys/BEAGLEBONE

Re: Restarting rtwn(0)-based interface causes reproducible kernel panics

Em 27/06/2016 14:14, Marcus von Appen escreveu: Hi, restarting the network interface for my rtwn(0)-based RTL8188CE card causes a reproducible kernel panic: # service netif restart [...] panic: Memory modified after free 0xf80005c22800(2048) val=8018 @ 0xf80005c22800 [...] Unread

Re: Bad rtwn(0) performance with RTL8188CE on -CURRENT after r302035

from anywhere. Let me know, what information is necessary to isolate and correct that issue. I'll gladly test it. :-) Cheers Marcus I have helped doing some tests with the urtwn. You can try creating the interface with -ht parameter. Here this improves performance. []'s -Otacílio

Re: Bad rtwn(0) performance with RTL8188CE on -CURRENT after r302035

Em 27/06/2016 15:34, Marcus von Appen escreveu: On, Mon Jun 27, 2016, Adrian Chadd wrote: Heh, there isn't any 11n support in rtwn (and won't be until I unify rtwn and urtwn post-11.) I do not know about that. My experience from pre-r302035 were 1-2 Mbit/s downstream from some servers, but

Re: Multicast routing on FreeBSD 11 current

Em 24/01/2016 07:24, Olivier Cochard-Labbé escreveu: On Sun, Jan 24, 2016 at 9:41 AM, Ben Woods wrote: Hi everyone, Could someone running FreeBSD current on a test machine try loading the ip_mroute driver on their machine? ​Hi, no problem here: root@lame5 # uname -a

WIFI urtwn possibly broken on 297561

this log is for the follow adapter but for the next one the behavior is the same urtwn0: on usbus1 urtwn0: MAC/BB RTL8192CU, RF 6052 2T2R urtwn0: on usbus1 urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R Someone knows whats going on? Thanks a lot

Re: WIFI urtwn possibly broken on 297561

4 ttl=64 time=19.729 ms 64 bytes from 192.168.0.26: icmp_seq=35 ttl=64 time=7.052 ms []'s -Otacilio Em 08/04/2016 16:55, Adrian Chadd escreveu: hi, try 'ifconfig wlan0 -ff -amsdu' and try again -a On 8 April 2016 at 12:35, Otacílio <otacilio.n...@bsd.com.br> wrote: Dears I'm te

Re: WIFI urtwn possibly broken on 297561

in 2 cwmax 3 aifs 2 txopLimit 47 -acm media: IEEE 802.11 Wireless Ethernet MCS mode 11ng status: associated nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> === If you need more test I can do. Send me the re

Re: Heads up

ning without problems and with full stress. The Beaglebone is compiling kernel and the amd64 have compiled freebsd to beaglebone. If exists some tests that I can made to help please let me know. []'s -Otacílio ___ freebsd-current@freebsd.org mailing list http

Re: New rc.d scripts on current

d.org" I'm receiving eval: disk: not found eval: disk: not found on beaglebone black also. r298522 []'s -Otacílio ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send an

type of vm.stats.vm.v_vnodepgsin vm.stats.vm.v_swappgsin, vm.stats.vm.v_vnodepgsout vm.stats.vm.v_swappgsout on AMD64 r320730

. Is this behavior correct? []'s -Otacílio ___ 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: type of vm.stats.vm.v_vnodepgsin vm.stats.vm.v_swappgsin, vm.stats.vm.v_vnodepgsout vm.stats.vm.v_swappgsout on AMD64 r320730

Em 10/07/2017 06:49, Konstantin Belousov escreveu: On Mon, Jul 10, 2017 at 06:45:28PM +0900, Tomoaki AOKI wrote: Hm, for example, sysutils/lsof (userspace app) depends on kernel source, and I thought the one Otacilio mentioned is something like it. lsof purpose is to dig into a kernel memory

Re: dmesg: can't reuse a leaf (ixl_rx_miss_bufs)!

Em qui, 26 de mai de 2016 06:01, Juan Ramón Molina Menor escreveu: > Hi! > > In three different machines running HEAD I have this message in the very > first lines of the dmesg output: > > can't reuse a leaf (ixl_rx_miss_bufs)! > > I don’t remember seeing it before and I have not

Fwd: WIFI urtwn possibly broken on 297561

Em seg, 11 de abr de 2016 06:05, Anton Shterenlikht escreveu: > > > >Hi! > > > >this is because we don't have A-MPDU RX aging on by default. So, if > >there are holes in the sequence number space, FreeBSD's reordering > >logic doesn't flush frames up until it's received /all/

Re: Heads up

Em seg, 25 de abr de 2016 01:55, Otacílio <otacilio.n...@bsd.com.br> escreveu: > Em 24/04/2016 14:49, Ivan Klymenko escreveu: > > On Fri, 15 Apr 2016 11:44:43 +0300 > > Ivan Klymenko <fi...@ukr.net> wrote: > > > >> On Thu, 14 Apr 2016 16:42:33 -060