Re: Change for the worse in rsu wireless driver

from Adrian Chadd: > please bug freebsd-usb@ about flakey usb devices. > I have a couple that i need to chase up hans about. they used to be less > flakey. Flaky USB devices in FreeBSD, also NetBSD, are not limited to wireless adapters. I get console messages about keyboard and mouse l

Jenkins build is back to normal : FreeBSD_HEAD #838

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

Re: netmap(4) transparent mode

On Mon, Jun 9, 2014 at 2:19 PM, Franco Fichtner wrote: > Hi, > > here's a revised version of a patch to address a couple > of issues with the transparent mode of netmap(4), which > doesn't work in current and older stable branches: > > > https://github.com/fichtner/freebsd/commit/b00580b03bf9dd84

netmap(4) transparent mode

Hi, here's a revised version of a patch to address a couple of issues with the transparent mode of netmap(4), which doesn't work in current and older stable branches: https://github.com/fichtner/freebsd/commit/b00580b03bf9dd847e4238dc0faabb349b1852a1.patch Posting this to a wider audience now, s

Re: Change for the worse in rsu wireless driver

Hi, Buy a mini-pcie atheros wifi card. -a On 9 June 2014 03:43, Thomas Mueller wrote: > from Adrian Chadd: > >> please bug freebsd-usb@ about flakey usb devices. > >> I have a couple that i need to chase up hans about. they used to be less >> flakey. > > Flaky USB devices in FreeBSD, also N

[head tinderbox] failure on mips/mips

TB --- 2014-06-09 14:02:38 - tinderbox 2.22 running on freebsd-current.sentex.ca TB --- 2014-06-09 14:02:38 - FreeBSD freebsd-current.sentex.ca 9.2-STABLE FreeBSD 9.2-STABLE #0 r263721: Tue Mar 25 09:27:39 EDT 2014 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2014

[head tinderbox] failure on mips64/mips

TB --- 2014-06-09 14:29:37 - tinderbox 2.22 running on freebsd-current.sentex.ca TB --- 2014-06-09 14:29:37 - FreeBSD freebsd-current.sentex.ca 9.2-STABLE FreeBSD 9.2-STABLE #0 r263721: Tue Mar 25 09:27:39 EDT 2014 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2014

[head tinderbox] failure on ia64/ia64

TB --- 2014-06-09 13:43:03 - tinderbox 2.22 running on freebsd-current.sentex.ca TB --- 2014-06-09 13:43:03 - FreeBSD freebsd-current.sentex.ca 9.2-STABLE FreeBSD 9.2-STABLE #0 r263721: Tue Mar 25 09:27:39 EDT 2014 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2014

[head tinderbox] failure on sparc64/sparc64

TB --- 2014-06-09 15:35:03 - tinderbox 2.22 running on freebsd-current.sentex.ca TB --- 2014-06-09 15:35:03 - FreeBSD freebsd-current.sentex.ca 9.2-STABLE FreeBSD 9.2-STABLE #0 r263721: Tue Mar 25 09:27:39 EDT 2014 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2014

Re: "CPU0: local APIC error 0x40"

On Saturday, June 07, 2014 4:47:39 am Edward Tomasz Napierała wrote: > On 0604T1036, John Baldwin wrote: > > On Monday, June 02, 2014 5:32:13 pm Edward Tomasz Napierała wrote: > > > Some machines, including ThinkPad T61, emit the following error message > > > early during boot: > > > > > > CPU0: l

[head tinderbox] failure on powerpc/powerpc

TB --- 2014-06-09 15:05:40 - tinderbox 2.22 running on freebsd-current.sentex.ca TB --- 2014-06-09 15:05:40 - FreeBSD freebsd-current.sentex.ca 9.2-STABLE FreeBSD 9.2-STABLE #0 r263721: Tue Mar 25 09:27:39 EDT 2014 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2014

[head tinderbox] failure on powerpc64/powerpc

TB --- 2014-06-09 15:34:32 - tinderbox 2.22 running on freebsd-current.sentex.ca TB --- 2014-06-09 15:34:32 - FreeBSD freebsd-current.sentex.ca 9.2-STABLE FreeBSD 9.2-STABLE #0 r263721: Tue Mar 25 09:27:39 EDT 2014 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2014

ohci bricks a amd64 system

I updated my FreeBSD-current system from an April 9th kernel/world (r264280M, which was running fine) to today sources (r267284), and have successfully turned the system into a brick if I include the USB ohci device in my kernel. During the verbose boot process, the brick stops with the message oh

Re: ohci bricks a amd64 system

On 06/09/14 22:34, Steve Kargl wrote: I updated my FreeBSD-current system from an April 9th kernel/world (r264280M, which was running fine) to today sources (r267284), and have successfully turned the system into a brick if I include the USB ohci device in my kernel. During the verbose boot proce

Re: ohci bricks a amd64 system

On Mon, Jun 09, 2014 at 10:37:26PM +0200, Hans Petter Selasky wrote: > On 06/09/14 22:34, Steve Kargl wrote: > > I updated my FreeBSD-current system from an > > April 9th kernel/world (r264280M, which was > > running fine) to today sources (r267284), and > > have successfully turned the system into

WITHOUT_OPENSSL build failure

Hello! When trying to buildworld from 267293 with WITHOUT_OPENSSL I run into a few issues. It seems that the following options currently need to be implied: WITHOUT_LDNS WITHOUT_BSNMP WITHOUT_DMAGENT WITHOUT_PKGBOOTSTRAP WITHOUT_SVNLITE The WITHOUT_BSNMP option also currently needs to enforce WI

Re: Turning TESTS on by default

On Sun, Jun 08, 2014 at 04:36:45PM -0400, Glen Barber wrote: > On Sun, Jun 08, 2014 at 01:33:31PM -0700, Adrian Chadd wrote: > > Now, as for how much bloat it adds to the CD images... > > > > Enough that it will be turned off for the CDs. I wanted to answer that we should split the question into

Re: Turning TESTS on by default

On Tue, Jun 10, 2014 at 02:15:06AM +0300, Konstantin Belousov wrote: > On Sun, Jun 08, 2014 at 04:36:45PM -0400, Glen Barber wrote: > > On Sun, Jun 08, 2014 at 01:33:31PM -0700, Adrian Chadd wrote: > > > Now, as for how much bloat it adds to the CD images... > > > > > > > Enough that it will be t

dhclient sucks cpu usage...

So, after finding out that nc has a stupidly small buffer size (2k even though there is space for 16k), I was still not getting as good as performance using nc between machines, so I decided to generate some flame graphs to try to identify issues... (Thanks to who included a full set of modules, i

clang-tblgen: Too many positional arguments specified!

Hi, I did the following with a tree checked out from HEAD at svn r267307: (1) Did a "make buildworld; make buildkernel; make installkernel; make installworld", with no special settings in /etc/src.conf or /etc/make.conf (2) rebooted (3) Waited for system to come up, and then did the following:

Re: dhclient sucks cpu usage...

Hi, - Original Message - > So, after finding out that nc has a stupidly small buffer size (2k > even though there is space for 16k), I was still not getting as good > as performance using nc between machines, so I decided to generate some > flame graphs to try to identify issues... (Thank