Re: using ConnectX card as Ethernet (mlxen)

2014-01-20 Thread John Baldwin
On Monday 20 January 2014 12:08:34 Eggert, Lars wrote: > Hi, > > On 2013-7-9, at 22:08, John Nielsen wrote: > > On Jul 9, 2013, at 9:58 AM, John Baldwin wrote: > >> So this was just fixed (finally) in HEAD in r253048. You can how use the > >> sysctls to change this. > > > > I saw the commit.

Problem updating bootcode on ZFS on root system with MBR

2014-01-20 Thread Thomas Hoffmann
I am running 11.0-CURRENT (r260850) with zfs on root with MBR. After upgrading my 10.0-RELEASE (r260669) system to 11.0-CURRENT (r260850) my zpools reported that they needed to be upgraded. So, I upgraded my zpools and I am attempting to update the bootcode (as required). I managed to get the boot

[head tinderbox] failure on arm/arm

2014-01-20 Thread FreeBSD Tinderbox
TB --- 2014-01-20 15:50:22 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2014-01-20 15:50:22 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2014

Re: panic: mtx_lock_spin: recursed on non-recursive mutex uart_hwmtx...

2014-01-20 Thread David Wolfskill
On Mon, Jan 20, 2014 at 10:33:41AM -0800, David Wolfskill wrote: > ... > On Mon, Jan 20, 2014 at 10:47:12AM -0700, Warner Losh wrote: > > ... > > I have a fix for this. I committed the wrong version of uart_core.c. > > r260911 should fix this. So this is broken from r260890-r260910. > > > >

Re: panic: mtx_lock_spin: recursed on non-recursive mutex uart_hwmtx...

2014-01-20 Thread David Wolfskill
On Mon, Jan 20, 2014 at 06:37:50PM +0200, Konstantin Belousov wrote: > ... > You do not have option WITNESS_SKIPSPIN in your kernel config, do you ? It was a GENERIC kernel for i386; it has WITNESS_SKIPSPIN. On Mon, Jan 20, 2014 at 10:14:08AM -0700, Ian Lepore wrote: > ... > Since you mention ser

Re: panic: mtx_lock_spin: recursed on non-recursive mutex uart_hwmtx...

2014-01-20 Thread Warner Losh
> On Mon, 2014-01-20 at 07:36 -0800, David Wolfskill wrote: >> panic: mtx_lock_spin: recursed on non-recursive mutex uart_hwmtx @ >> /usr/src/sys/dev/uart/uart_cpu.h:94 > > Since you mention serial console, I think r260890 might be a candidate. I have a fix for this. I committed the wrong versi

Re: panic: mtx_lock_spin: recursed on non-recursive mutex uart_hwmtx...

2014-01-20 Thread Warner Losh
On Jan 20, 2014, at 10:14 AM, Ian Lepore wrote: > On Mon, 2014-01-20 at 07:36 -0800, David Wolfskill wrote: >> I saw this on my "build machine" after updating the "head" slice from: >> >> FreeBSD 11.0-CURRENT #1387 r260875M/260877:115: Sun Jan 19 11:57:25 PST >> 2014 r...@freebeast.cat

Re: panic: mtx_lock_spin: recursed on non-recursive mutex uart_hwmtx...

2014-01-20 Thread Ian Lepore
On Mon, 2014-01-20 at 07:36 -0800, David Wolfskill wrote: > I saw this on my "build machine" after updating the "head" slice from: > > FreeBSD 11.0-CURRENT #1387 r260875M/260877:115: Sun Jan 19 11:57:25 PST > 2014 r...@freebeast.catwhisker.org:/common/S4/obj/usr/src/sys/GENERIC > i386

Re: panic: mtx_lock_spin: recursed on non-recursive mutex uart_hwmtx...

2014-01-20 Thread Thomas Hoffmann
On Mon, Jan 20, 2014 at 11:37 AM, Konstantin Belousov wrote: > On Mon, Jan 20, 2014 at 07:36:15AM -0800, David Wolfskill wrote: > > Jan 20 07:02:16 freebeast syslogd: exiting on signal 15 > > Waiting (max 60 seconds) for system process `vnlru' to stop...done > > Waiting (max 60 seconds) for system

Re: panic: mtx_lock_spin: recursed on non-recursive mutex uart_hwmtx...

2014-01-20 Thread Konstantin Belousov
On Mon, Jan 20, 2014 at 07:36:15AM -0800, David Wolfskill wrote: > Jan 20 07:02:16 freebeast syslogd: exiting on signal 15 > Waiting (max 60 seconds) for system process `vnlru' to stop...done > Waiting (max 60 seconds) for system process `syncer' to stop... > Syncing disks, vnodes remaining...2 4 4

panic: mtx_lock_spin: recursed on non-recursive mutex uart_hwmtx...

2014-01-20 Thread David Wolfskill
I saw this on my "build machine" after updating the "head" slice from: FreeBSD 11.0-CURRENT #1387 r260875M/260877:115: Sun Jan 19 11:57:25 PST 2014 r...@freebeast.catwhisker.org:/common/S4/obj/usr/src/sys/GENERIC i386 to FreeBSD 11.0-CURRENT #1388 r260904M/260904:115: Mon Jan 20

Re: using ConnectX card as Ethernet (mlxen)

2014-01-20 Thread Eggert, Lars
Hi, if I leave the mlx4ib device out of the kernel (i.e., only compile in mlxen), doing the sysctl switch to Ethernet mode works fine. Lars On 2014-1-20, at 13:08, Eggert, Lars wrote: > Hi, > > On 2013-7-9, at 22:08, John Nielsen wrote: > On Jul 9, 2013, at 9:58 AM, John Baldwin wrote: >>>

Re: using ConnectX card as Ethernet (mlxen)

2014-01-20 Thread Eggert, Lars
Hi, On 2013-7-9, at 22:08, John Nielsen wrote: On Jul 9, 2013, at 9:58 AM, John Baldwin wrote: >> So this was just fixed (finally) in HEAD in r253048. You can how use the >> sysctls to change this. > > I saw the commit. Thanks! I'll give it a try at some point (whenever my > schedule and hard

Re: vm_reserv.c panic on sparc64 current

2014-01-20 Thread Alan Cox
On 01/19/2014 18:06, Manfred Antar wrote: > vm_reserv.c starting with revision 25 causes panic on sparc64 (netra T1 > 200) > version 259998 works > > backtrace: > Starting apache22. > panic: Bad link elm 0xf8007d4728f8 prev->next != elm > cpuid = 0 > KDB: enter: panic > [ thread pid 1965 t