Re: Native Encryption for ZFS on FreeBSD CFT

[Outback Dingo]

of course interesting work, but unfortunately, and as you know me,
what would i say next

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
-I/usr/src/sys/cddl/compat/opensolaris
-I/usr/src/cddl/compat/opensolaris/include
-I/usr/src/cddl/compat/opensolaris/lib/libumem
-I/usr/src/cddl/contrib/opensolaris/lib/libzpool/common
-I/usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs
-I/usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/lua
-I/usr/src/sys/cddl/contrib/opensolaris/common/zfs
-I/usr/src/sys/cddl/contrib/opensolaris/uts/common
-I/usr/src/cddl/contrib/opensolaris/head
-I/usr/src/cddl/contrib/opensolaris/lib/libnvpair
-I/usr/src/cddl/contrib/opensolaris/lib/libcmdutils
-DWANTS_MUTEX_OWNED -I/usr/src/lib/libpthread/thread
-I/usr/src/lib/libpthread/sys -I/usr/src/lib/libthr/arch/amd64/include
-g -DDEBUG=1 -DZFS_DEBUG=1   -DNEED_SOLARIS_BOOLEAN -g -MD
-MF.depend.freebsd_crypto.o -MTfreebsd_crypto.o -std=iso9899:1999
-fstack-protector-strong -Wno-pointer-sign -Wno-unknown-pragmas
-Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable
-Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality
-Wno-unused-function -Wno-enum-conversion -Wno-unused-local-typedef
-Wno-address-of-packed-member -Wno-switch -Wno-switch-enum
-Wno-knr-promoted-parameter -Wno-parentheses  -Qunused-arguments  -c
/usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/freebsd_crypto.c
-o freebsd_crypto.o
/usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/freebsd_crypto.c:62:19:
warning: tentative definition of variable with internal linkage has
incomplete non-array type 'struct mtx'
[-Wtentative-definition-incomplete-type]
static struct mtx freebsd_crypto_mutex;
  ^
/usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/freebsd_crypto.c:62:15:
note: forward declaration of 'struct mtx'
static struct mtx freebsd_crypto_mutex;
  ^
/usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/freebsd_crypto.c:63:35:
error: expected identifier
MTX_SYSINIT(freebsd_crypto_mutex, _crypto_mutex, "FreeBSD ZFS
Crypto mutex", MTX_DEF);
  ^
/usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/freebsd_crypto.c:63:1:
warning: type specifier missing, defaults to 'int' [-Wimplicit-int]
MTX_SYSINIT(freebsd_crypto_mutex, _crypto_mutex, "FreeBSD ZFS
Crypto mutex", MTX_DEF);
^
/usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/freebsd_crypto.c:62:19:
error: tentative definition has type 'struct mtx' that is never
completed
static struct mtx freebsd_crypto_mutex;
  ^
/usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/freebsd_crypto.c:62:15:
note: forward declaration of 'struct mtx'
static struct mtx freebsd_crypto_mutex;
  ^
2 warnings and 2 errors generated.
*** Error code 1
On Wed, Aug 22, 2018 at 4:28 AM Matthew Macy  wrote:
>
> On Tue, Aug 21, 2018 at 6:55 PM Matthew Macy  wrote:
>
> > To anyone with an interest in native encryption in ZFS please test the
> > projects/zfs-crypto-merge-0820 branch in my freebsd repo:
> > https://github.com/mattmacy/networking.git
> >
> >
> Oh and I neglected to state that this work is being supported by iX Systems
> and the tree is all built on work done by Sean Fagan at iX Systems. Please
> keep him in the loop on any problems encountered.
> Thanks.
>
>
>
> > ( git clone  https://github.com/mattmacy/networking.git -b
> > projects/zfs-crypto-merge-0820 )
> >
> > The UI is quite close to the Oracle Solaris ZFS crypto with minor
> > differences for specifying key location.
> >
> > Please note that once a feature is enabled on a pool it can't be
> > disabled. This means that if you enable encryption support on a pool
> > you will never be able to import it in to a ZFS without encryption
> > support. For this reason I would strongly advise against using this on
> > any pool that can't be easily replaced until this change has made its
> > way in to HEAD after the freeze has been lifted.
> >
> >
> > By way of background the original ZoL commit can be found at:
> >
> > https://github.com/zfsonlinux/zfs/pull/5769/commits/5aef9bedc801830264428c64cd2242d1b786fd49
> >
> > Thanks in advance.
> > -M
> >
> ___
> 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"

Status - ClearFOG PRO

[Outback Dingo]

Can someone comment on the status on the ClearFOG PRO?? Ive seen recent commits
going into the tree that mention it specifically in the DTS file, Is
an image buildable? What
is working now, what is not? I have two that need some FreeBSD love.
___
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: [CFT] ypldap testing against OpenLDAP and Microsoft Active Directory

[Outback Dingo]

On Wed, Jun 15, 2016 at 10:15 PM, Marcelo Araujo 
wrote:

> No worries Nikolai! If one day I will do it, will be on 12-RELEASE.
>
> Br,
>
> 2016-06-15 20:03 GMT+08:00 Nikolai Lifanov :
>
> > On 06/14/2016 21:05, Marcelo Araujo wrote:
> > > 2016-06-15 8:17 GMT+08:00 Chris H :
> > >
> > >> On Thu, 9 Jun 2016 17:55:58 +0800 Marcelo Araujo <
> > araujobsdp...@gmail.com>
> > >> wrote
> > >>
> > >>> Hey,
> > >>>
> > >>> Thanks for the CFT Craig.
> > >>>
> > >>> 2016-06-09 14:41 GMT+08:00 Xin Li :
> > >>>
> > 
> > 
> >  On 6/8/16 23:10, Craig Rodrigues wrote:
> > > Hi,
> > >
> > > I have worked with Marcelo Araujo to port OpenBSD's ypldap to
> FreeBSD
> > > current.
> > >
> > > In latest current, it should be possible to put in /etc/rc.conf:
> > >
> > > nis_ypldap_enable="YES"
> > > to activate the ypldap daemon.
> > >
> > > When set up properly, it should be possible to log into FreeBSD,
> and
> > >> have
> > > the backend password database come from an LDAP database such
> > > as OpenLDAP
> > >
> > > There is some documentation for setting this up, but it is OpenBSD
> >  specific:
> > >
> > > http://obfuscurity.com/2009/08/OpenBSD-as-an-LDAP-Client
> > > http://puffysecurity.com/wiki/ypldap.html#2
> > >
> > > I did not bother porting the OpenBSD LDAP server to FreeBSD, so
> that
> > > information
> > > does not apply.  I figure that openldap from ports should work
> fine.
> > >
> > > I was wondering if there is someone out there familiar enough with
> > >> LDAP
> > > and has a setup they can test this stuff out with, provide
> feedback,
> > >> and
> > > help
> > > improve the documentation for FreeBSD?
> > 
> >  Looks like it would be a fun weekend project.  I've cc'ed a
> potential
> >  person who may be interested in this as well.
> > 
> >  But will this worth the effort? (I think the current implementation
> >  would do everything with plaintext protocol over wire, so while it
> >  extends life for legacy applications that are still using NIS/YP, it
> >  doesn't seem to be something that we should recommend end user to
> > use?)
> > 
> > >>>
> > >>> I can see two good point to use ypldap that would be basically for
> > users
> > >>> that needs to migrate from NIS to LDAP or need to make some
> integration
> > >>> between legacy(NIS) and LDAP during a transition period to LDAP.
> > >>>
> > >>> As mentioned, NIS is 'plain text' not safe by its nature, however
> there
> > >> are
> > >>> still lots of people out there using NIS, and ypldap(8) is a good
> tool
> > to
> > >>> help these people migrate to a more safe tool like LDAP.
> > >>>
> > >>>
> > 
> > > I would also be interested in hearing from someone who can see if
> > > ypldap can work against a Microsoft Active Directory setup?
> > 
> >  Cheers,
> > 
> > 
> > >>> All my tests were using OpenLDAP, I used the OpenBSD documentation to
> > >> setup
> > >>> everything, and the file share/examples/ypldap/ypldap.conf can be a
> > good
> > >>> start to anybody that wants to start to work with ypldap(8).
> > >>>
> > >>> Would be nice hear from other users how was their experience using
> > ypldap
> > >>> with MS Active Directory and perhaps some HOWTO how they made all the
> > >> setup
> > >>> would be amazing to have.
> > >>>
> > >>> Also, would be useful to know who are still using NIS and what kind
> of
> > >>> setup(user case), maybe even the reason why they are still using it.
> > >>
> > >> Honestly, I think the best way to motivate people to do the right
> > thing(tm)
> > >> Would be to remove Yellow Pages from the tree, entirely. :-)
> > >> It's been dead for *years*, and as you say, isn't safe, anyway..
> > >>
> > >
> > > Yes, I have a plan for that, but I don't believe it will happens before
> > > FreeBSD 12-RELEASE.
> > >
> >
> > Please don't, at least for now. NIS is fast, simple, reliable, and works
> > on first boot without additional software. I have passwords in
> > Kerberos, so the usual cons doesn't apply. This is very valuable to me.
> >
> > It's not hurting anyone. What's the motivation behind removing it?
>


Removing NIS is a BAD idea, there are still plenty of people that use it,
and plenty of businesses rely on it, I still hear people asking for it



> >
> > >
> > >>
> > >> --Chris
> > >>>
> > >>>
> > >>> Best,
> > >>> --
> > >>>
> > >>> --
> > >>> Marcelo Araujo(__)ara...@freebsd.org
> > >>> \\\'',)http://www.FreeBSD.org    \/  \ ^
> > >>> Power To Server. .\. /_)
> > >>> ___
> > >>> freebsd-current@freebsd.org mailing list
> > >>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > >>> To unsubscribe, send any mail to "
> > >> 

CURRENT BROKEN fatal error: 'config_local.h' file not found

[Outback Dingo]

seems current is broken due to a missing file
/usr/src/usr.sbin/amd/libamu/../include/config.h:12:10: fatal error:
'config_local.h' file not found


CC='cc' mkdep -f .depend -a
   -I/usr/src/usr.bin/elfcopy/../../contrib/elftoolchain/libelftc
-I/usr/src/usr.bin/elfcopy/../../contrib/elftoolchain/libpe
-I/usr/src/usr.bin
/elfcopy/../../contrib/elftoolchain/common -DWITH_PE=1 -std=gnu99
   /usr/src/usr.bin/elfcopy/../../contrib/elftoolchain/elfcopy/archive.c
/usr/src/usr.bin/elfcopy/../../co
ntrib/elftoolchain/elfcopy/ascii.c
/usr/src/usr.bin/elfcopy/../../contrib/elftoolchain/elfcopy/binary.c
/usr/src/usr.bin/elfcopy/../../contrib/elftoolchain/elfcopy/main.c /
usr/src/usr.bin/elfcopy/../../contrib/elftoolchain/elfcopy/pe.c
/usr/src/usr.bin/elfcopy/../../contrib/elftoolchain/elfcopy/sections.c
/usr/src/usr.bin/elfcopy/../../contri
b/elftoolchain/elfcopy/segments.c
/usr/src/usr.bin/elfcopy/../../contrib/elftoolchain/elfcopy/symbols.c
--- depend_subdir_usr.sbin ---
1 error generated.
In file included from
/usr/src/usr.sbin/amd/libamu/../../../contrib/amd/conf/mtab/mtab_bsd.c:51:
/usr/src/usr.sbin/amd/libamu/../include/config.h:12:10: fatal error:
'config_local.h' file not found
#include "config_local.h"
^
1 error generated.
In file included from
/usr/src/usr.sbin/amd/libamu/../../../contrib/amd/conf/umount/umount_bsd44.c:49:

/usr/src/usr.sbin/amd/libamu/../include/config.h:12:10: fatal error:
'config_local.h' file not found
#include "config_local.h"
^
1 error generated.
In file included from xdr_func_%undef.c:48:
/usr/src/usr.sbin/amd/libamu/../include/config.h:12:10: fatal error:
'config_local.h' file not found
#include "config_local.h"
^
1 error generated.
mkdep: compile failed
*** [.depend] Error code 1

make[5]: stopped in /usr/src/usr.sbin/amd/libamu
1 error
___
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: CURRENT: buildworld failure due to nvmecontrol source error

[Outback Dingo]

On Sat, Jan 30, 2016 at 12:39 PM, O. Hartmann 
wrote:

> Buildworld (r295070) fails in building nvmecontrol patches correctly:
>
> [...]
> (cd /usr/src/lib/libc/tests/gen &&  DEPENDFILE=.depend.raise_test
> NO_SUBDIR=1 make
> -f /usr/src/lib/libc/tests/gen/Makefile _RECURSING_PROGS=t
> PROG=raise_test ) ---
> all_subdir_share --- ===> share/i18n/csmapper/APPLE (all)
> --- all_subdir_usr.sbin ---
> ===> usr.sbin/acpi/iasl (all)
> --- all_subdir_sbin ---
> /usr/src/sbin/nvmecontrol/power.c:44:16: error: invalid application of
> 'sizeof' to an
> incomplete type 'struct nvme_power_state' _Static_assert(sizeof(struct
> nvme_power_state)
> == 256 / NBBY, ^ ~
> /usr/src/sbin/nvmecontrol/power.c:44:30: note: forward declaration of
> 'struct
> nvme_power_state' _Static_assert(sizeof(struct nvme_power_state) == 256 /
> NBBY,
>  ^
> /usr/src/sbin/nvmecontrol/power.c:60:14: error: incomplete definition of
> type 'struct
> nvme_power_state' mpower = nps->mp;
>  ~~~^
> /usr/src/sbin/nvmecontrol/power.c:44:30: note: forward declaration of
> 'struct
> nvme_power_state' _Static_assert(sizeof(struct nvme_power_state) == 256 /
> NBBY,
>  ^
> /usr/src/sbin/nvmecontrol/power.c:61:9: error: incomplete definition of
> type 'struct
> nvme_power_state' if (nps->mps == 0)
>
>
> regards
>


same here to confirm
cc  -pg  -O2 -pipe
-I/backup/freebsd/kerberos5/lib/libroken/../../../crypto/heimdal/lib/roken
-I.   -DHAVE_CONFIG_H
-I/backup/freebsd/kerberos5/lib/libroken/../../include -std=gnu99 -fstack
-protector-strong-Qunused-arguments -c
/backup/freebsd/kerberos5/lib/libroken/../../../crypto/heimdal/lib/roken/eread.c
-o eread.po
--- all_subdir_secure ---
cc  -pg  -O2 -pipe
  -I/backup/freebsd/secure/lib/libcrypto/../../../crypto/openssl -DTERMIOS
-DANSI_SOURCE -DOPENSSL_THREADS -DDSO_DLFCN -DHAVE_DLFCN_H -DL_ENDIAN
-DOPENSSL_IA32_SSE2 -DAES
_ASM -DBSAES_ASM -DVPAES_ASM -DECP_NISTZ256_ASM -DOPENSSL_BN_ASM_MONT
-DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DMD5_ASM -DGHASH_ASM
-DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DWHIRLPOOL_ASM
-I/usr/obj/backup/freebsd/secure/lib/libcrypto
-I/backup/freebsd/secure/lib/libcrypto/../../../crypto/openssl/crypto
-I/backup/freebsd/secure/lib/libcrypto/../../../crypto/openssl/crypto/a
sn1
-I/backup/freebsd/secure/lib/libcrypto/../../../crypto/openssl/crypto/evp
-I/backup/freebsd/secure/lib/libcrypto/../../../crypto/openssl/crypto/modes
-std=gnu89 -fstack-protector-strong
-Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int
-Wno-unused-const-variable -Wno-tautological-compare -Wno-unused-value
-Wno-parentheses-equality -Wno-unused-function -Wno-enum-conve
rsion -Wno-unused-local-typedef -Wno-switch -Wno-switch-enum
-Wno-knr-promoted-parameter -Wno-parentheses  -Qunused-arguments -c
/backup/freebsd/secure/lib/libcrypto/../../../crypto/openssl
/crypto/evp/m_md5.c -o m_md5.po
--- all_subdir_sbin ---
/backup/freebsd/sbin/nvmecontrol/power.c:44:16: error: invalid application
of 'sizeof' to an incomplete type 'struct nvme_power_state'
_Static_assert(sizeof(struct nvme_power_state) == 256 / NBBY,
  ^ ~
/backup/freebsd/sbin/nvmecontrol/power.c:44:30: note: forward declaration
of 'struct nvme_power_state'
_Static_assert(sizeof(struct nvme_power_state) == 256 / NBBY,
^
/backup/freebsd/sbin/nvmecontrol/power.c:60:14: error: incomplete
definition of type 'struct nvme_power_state'
   mpower = nps->mp;
~~~^
/backup/freebsd/sbin/nvmecontrol/power.c:44:30: note: forward declaration
of 'struct nvme_power_state'
_Static_assert(sizeof(struct nvme_power_state) == 256 / NBBY,
^
/backup/freebsd/sbin/nvmecontrol/power.c:61:9: error: incomplete definition
of type 'struct nvme_power_state'
   if (nps->mps == 0)
   ~~~^
/backup/freebsd/sbin/nvmecontrol/power.c:44:30: note: forward declaration
of 'struct nvme_power_state'
_Static_assert(sizeof(struct nvme_power_state) == 256 / NBBY,
^
/backup/freebsd/sbin/nvmecontrol/power.c:63:14: error: incomplete
definition of type 'struct nvme_power_state'
   ipower = nps->idlp;
~~~^
/backup/freebsd/sbin/nvmecontrol/power.c:44:30: note: forward declaration
of 'struct nvme_power_state'
_Static_assert(sizeof(struct nvme_power_state) == 256 / NBBY,
^
/backup/freebsd/sbin/nvmecontrol/power.c:64:9: error: incomplete definition
of type 'struct nvme_power_state'
   if (nps->ips == 1)
   ~~~^
/backup/freebsd/sbin/nvmecontrol/power.c:44:30: note: forward declaration
of 'struct nvme_power_state'
_Static_assert(sizeof(struct nvme_power_state) == 256 / NBBY,
^
/backup/freebsd/sbin/nvmecontrol/power.c:66:14: error: incomplete
definition of type 'struct nvme_power_state'
--- all_subdir_rescue ---
--- dhclient_make ---
--- packet.o ---
--- 

Re: Is NextBSD safe for bhyve?

[Outback Dingo]

On Thu, Aug 27, 2015 at 5:15 PM, Russell Haley russ.ha...@gmail.com wrote:

 Is NextBSD safe for bhyve?

 Thanks


Consider that everything CURRENT, can be somewhat volatile at times, I
wouldnt recommend it for a production business case.
However that being said I do have XEN/NextBSD running as a dom0 quite well,
iocage, behyve and others are being reveiwed
for use cases, at this state of flux your mileage may vary depending on
exactly what your using it for, localized testing and
running a few vms, Ive accomplished that much with XEN so far. But again,
it is based on CURRENT with alot of additions
being merged in and worked on daily.



 Russ
 ___
 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

Re: AMD64 disk1.iso dont create /home (/usr/home)

[Outback Dingo]

On Fri, Aug 21, 2015 at 3:57 PM, Kevin Lo ke...@freebsd.org wrote:

 I hit this and poked bapt@ two weeks ago, he said he couldn't reproduce
 this problem...

 Kevin



Well seems three people just confirmed it exists might be a corner
case



 On Thu, Aug 20, 2015 at 08:29:32PM -0700, Adrian Chadd wrote:
 
  I just hit this; i'll hit up gjb@ about it.
 
 
  -a
 
 
  On 20 August 2015 at 19:04, Outback Dingo outbackdi...@gmail.com
 wrote:
   On Fri, Aug 21, 2015 at 11:30 AM, Allan Jude allanj...@freebsd.org
 wrote:
  
   On 2015-08-20 21:04, Keynes Augusto wrote:
   
   
   
The ISO (r286893/r284969) does not create the folder / home or
 /usr/home
   and the user created during installation disappears.
   
All files em skel disappears too.
   
Sorry my english, i use Google for translate.
   
Keynes Deus
   
   
___
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
   
  
   Did you use UFS or ZFS?
  
   Normally the /home symlink is not created until you add the first
 user.
  
  
   and it still fails even then if you create a user during install
  
  
  
   --
   Allan Jude
  
  
   ___
   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
 

___
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: AMD64 disk1.iso dont create /home (/usr/home)

[Outback Dingo]

On Fri, Aug 21, 2015 at 11:30 AM, Allan Jude allanj...@freebsd.org wrote:

 On 2015-08-20 21:04, Keynes Augusto wrote:
 
 
 
  The ISO (r286893/r284969) does not create the folder / home or /usr/home
 and the user created during installation disappears.
 
  All files em skel disappears too.
 
  Sorry my english, i use Google for translate.
 
  Keynes Deus
 
 
  ___
  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
 

 Did you use UFS or ZFS?

 Normally the /home symlink is not created until you add the first user.


and it still fails even then if you create a user during install



 --
 Allan Jude


___
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: FreeBSD 10 and zfsd

[Outback Dingo]

On Thu, Dec 19, 2013 at 6:32 PM, asom...@gmail.com wrote:

 On Wed, Dec 18, 2013 at 2:40 PM, Outback Dingo outbackdi...@gmail.com
 wrote:
 
 
 
  On Wed, Dec 18, 2013 at 4:40 PM, Alan Somers asom...@freebsd.org
 wrote:
 
  On Wed, Dec 18, 2013 at 11:47 AM, Outback Dingo outbackdi...@gmail.com
 
  wrote:
  
  
   On Wed, Dec 18, 2013 at 12:39 PM, Mark Felder f...@freebsd.org
 wrote:
  
   On Thu, Oct 10, 2013, at 11:26, Alan Somers wrote:
   
Due to popular demand, I have located a round toit.  I'm currently
working on rebasing the zfsd project branch to head, after which
 I'll
push SpectraLogic's recent changes.
   
  
   Just thought I'd ping the list about the situation here... would love
   to
   see this in HEAD soon :)
  
  
  
   Id love to see an updated patch from the zfsd tree against head itself
   so we
   could continue using and testing it
 
  Coming up ...
 
 
  Sweet..!!!

 Sorry, but I'm running into nontrivial merge conflicts.  It's going to
 take a few more days.

 -Alan



Has any progress been made on an updated patch set ??



 
 
 
  
  
   ___
   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
  
  
 
 

___
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: FreeBSD 10 and zfsd

[Outback Dingo]

On Wed, Dec 18, 2013 at 12:39 PM, Mark Felder f...@freebsd.org wrote:

 On Thu, Oct 10, 2013, at 11:26, Alan Somers wrote:
 
  Due to popular demand, I have located a round toit.  I'm currently
  working on rebasing the zfsd project branch to head, after which I'll
  push SpectraLogic's recent changes.
 

 Just thought I'd ping the list about the situation here... would love to
 see this in HEAD soon :)



Id love to see an updated patch from the zfsd tree against head itself so
we could continue using and testing it


 ___
 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

___
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: FreeBSD 10 and zfsd

[Outback Dingo]

On Wed, Dec 18, 2013 at 4:40 PM, Alan Somers asom...@freebsd.org wrote:

 On Wed, Dec 18, 2013 at 11:47 AM, Outback Dingo outbackdi...@gmail.com
 wrote:
 
 
  On Wed, Dec 18, 2013 at 12:39 PM, Mark Felder f...@freebsd.org wrote:
 
  On Thu, Oct 10, 2013, at 11:26, Alan Somers wrote:
  
   Due to popular demand, I have located a round toit.  I'm currently
   working on rebasing the zfsd project branch to head, after which I'll
   push SpectraLogic's recent changes.
  
 
  Just thought I'd ping the list about the situation here... would love to
  see this in HEAD soon :)
 
 
 
  Id love to see an updated patch from the zfsd tree against head itself
 so we
  could continue using and testing it

 Coming up ...


Sweet..!!!



 
 
  ___
  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
 
 

___
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

FreeBSD CURRENT Build breakage

[Outback Dingo]

Heads up, seems compiling a kernel as of tonights broken

CC='cc ' mkdep -f .depend -a   -nostdinc -D_KERNEL -DKLD_MODULE
-DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq
-I/usr/obj/usr/src/sys/GENERIC -std=iso9899:1999
/usr/src/sys/modules/cpufreq/../../dev/cpufreq/ichss.c
/usr/src/sys/modules/cpufreq/../../x86/cpufreq/est.c
/usr/src/sys/modules/cpufreq/../../x86/cpufreq/hwpstate.c
/usr/src/sys/modules/cpufreq/../../x86/cpufreq/p4tcc.c
/usr/src/sys/modules/cpufreq/../../x86/cpufreq/powernow.c
=== crypto (depend)
@ - /usr/src/sys
awk -f @/tools/makeobjops.awk @/opencrypto/cryptodev_if.m -c
make[4]: don't know how to make deflate.c. Stop

make[4]: stopped in /usr/src/sys/modules/crypto
*** Error code 2

Stop.
___
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

CURRENT 11.0 ZFS as of Today

[Outback Dingo]

Just came across this error...

zfs -mm master errors with

Assertion failed: (tq-tq_freelist != NULL), file
/master/src/cddl/lib/libzpool/../../../cddl/contrib/opensolaris/lib/libzpool/common/taskq.c,
line 289.
Abort (core dumped)
___
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: CURRENT 11.0 ZFS as of Today

[Outback Dingo]

2a000   spacemap242   free
 5.70M
On-disk histogram:
metaslab 85   offset2a800   spacemap228   free
 2.94M
On-disk histogram:
metaslab 86   offset2b000   spacemap243   free
 2.31M
On-disk histogram:
metaslab 87   offset2b800   spacemap244   free
 2.69M
On-disk histogram:
metaslab 88   offset2c000   spacemap245   free
 3.56M
On-disk histogram:
metaslab 89   offset2c800   spacemap246   free
 4.05M
On-disk histogram:
metaslab 90   offset2d000   spacemap247   free
 8.32M
On-disk histogram:
metaslab 91   offset2d800   spacemap248   free
 49.5M
On-disk histogram:
metaslab 92   offset2e000   spacemap249   free
 4.20M
On-disk histogram:
metaslab 93   offset2e800   spacemap250   free
 29.0M
On-disk histogram:
metaslab 94   offset2f000   spacemap251   free
 1.14M
On-disk histogram:
metaslab 95   offset2f800   spacemap252   free
114M
On-disk histogram:
metaslab 96   offset3   spacemap253   free
 85.3M
On-disk histogram:
metaslab 97   offset30800   spacemap254   free
 7.11M
On-disk histogram:
metaslab 98   offset31000   spacemap255   free
 23.4M
On-disk histogram:
metaslab 99   offset31800   spacemap256   free
 38.7M
On-disk histogram:
metaslab100   offset32000   spacemap260   free
101M
On-disk histogram:
 12: 13 *
 13:  6 **
 14: 12 
 15: 13 *
 16: 18 **
 17:  1 *
 18:  0
 19:  0
 20:  0
 21:  0
 22:  0
 23:  0
 24:  2 **
 25:  1 *
metaslab101   offset32800   spacemap224   free
9.8M
On-disk histogram:
metaslab102   offset33000   spacemap258   free
128M
On-disk histogram:



On Sat, Nov 30, 2013 at 11:04 PM, Glen Barber g...@freebsd.org wrote:

 On Sat, Nov 30, 2013 at 10:51:56PM -0500, Outback Dingo wrote:
  Just came across this error...
 
  zfs -mm master errors with
 
  Assertion failed: (tq-tq_freelist != NULL), file
 
 /master/src/cddl/lib/libzpool/../../../cddl/contrib/opensolaris/lib/libzpool/common/taskq.c,
  line 289.
  Abort (core dumped)

 What should it to?

 % zfs -mm master
 unrecognized command '-mm'

 Glen


___
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: pkg install on CURRENT ?

[Outback Dingo]

On Fri, Nov 15, 2013 at 3:12 AM, Baptiste Daroussin b...@freebsd.orgwrote:

 On Thu, Nov 14, 2013 at 10:13:58PM -0500, Outback Dingo wrote:
  anyway to resolve this ??? id like to pkg install a few things or is my
  only option ports
 
  Checking integrity... done
  [1/16] Installing expat-2.0.1_2...pkg: wrong architecture:
  freebsd:10:x86:64 instead of freebsd:11:x86:64

 pkg -vv, uname -a and file /bin/sh please

 regards,
 Bapt



Nevermind I got it, needed to modify  packagesite:
http://pkg.FreeBSD.org/freebsd:11:x86:64/latest
___
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: pkg install on CURRENT ?

[Outback Dingo]

On Fri, Nov 15, 2013 at 10:02 AM, Sergey V. Dyatko
sergey.dya...@gmail.comwrote:

 On Fri, 15 Nov 2013 08:29:10 -0500
 Outback Dingo outbackdi...@gmail.com wrote:

  On Fri, Nov 15, 2013 at 3:12 AM, Baptiste Daroussin
  b...@freebsd.orgwrote:
 
   On Thu, Nov 14, 2013 at 10:13:58PM -0500, Outback Dingo wrote:
anyway to resolve this ??? id like to pkg install a few things or
is my only option ports
   
Checking integrity... done
[1/16] Installing expat-2.0.1_2...pkg: wrong architecture:
freebsd:10:x86:64 instead of freebsd:11:x86:64
  
   pkg -vv, uname -a and file /bin/sh please
  
   regards,
   Bapt
  
 
 
  Nevermind I got it, needed to modify  packagesite:
  http://pkg.FreeBSD.org/freebsd:11:x86:64/latest

 http://pkg.freebsd.org/${ABI}/latest



thanks for that now im golden...




 --
 wbr, tiger
 ___
 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

___
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

pkg install on CURRENT ?

[Outback Dingo]

anyway to resolve this ??? id like to pkg install a few things or is my
only option ports

Checking integrity... done
[1/16] Installing expat-2.0.1_2...pkg: wrong architecture:
freebsd:10:x86:64 instead of freebsd:11:x86:64
___
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: CUURENT kernel build broken - make[2]: exec(aicasm) failed (No such file or directory)

[Outback Dingo]

On Tue, Nov 5, 2013 at 2:01 AM, Gleb Smirnoff gleb...@freebsd.org wrote:

 On Mon, Nov 04, 2013 at 10:09:54PM -0700, Ian Lepore wrote:
 I   /usr/src/sys/dev/aic7xxx/aic7xxx.seq
 Imake[2]: exec(aicasm) failed (No such file or directory)
 I*** Error code 1
 I   
 IStop.
 Imake[2]: stopped in /usr/obj/usr/src/sys/GENERIC
 I*** Error code 1
 I   
 IStop.
 Imake[1]: stopped in /usr/src
 I  
 I   Did you update your source and then make buildkernel without
 I   buildworld?  If so, a make kernel-toolchain should create the
 aicasm
 I   tool and get you back on track.
 I  
 I 
 I  really odd as i built a kernel this morning no problem, then updated
 the
 I  tree and went to build another kernel and got that.
 I  working through it, thanks for the input..
 I 
 I
 I You were just unlucky that your updates bracketed my checkin that
 I changed the build process for the aicasm tool so that it gets built as
 I part of the toolchain rather than as part of the kernel now.

 Before this change, the toolchain was not required for kernel build if you
 aren't cross building. And now it is. This breaks the kernel build
 procedure
 documented in handbook for years, and brings a lot of discomfort to
 developers.

 Now to test a trivial change to kernel I need first to compile clang.


I concur, I feel this is a bit invasive and unneccesary, as custom build
scripts now also fail, what has worked for years
without issue is now completely broken, it makes no sense to me to have to
build a toolchain just to build a kernel
everytime.


 --
 Totus tuus, Glebius.

___
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

CUURENT kernel build broken - make[2]: exec(aicasm) failed (No such file or directory)

[Outback Dingo]

cc  -c -O2 -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls
-Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith
-Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions
-Wmissing-include-dirs -fdiagnostics-show-option
-Wno-error-tautological-compare -Wno-error-empty-body
-Wno-error-parentheses-equality -nostdinc -I. -I/usr/src/sys
-I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter
-I/usr/src/sys/dev/ath -I/usr/src/sys/dev/ath/ath_hal
-I/usr/src/sys/contrib/dev/ath/ath_hal -I/usr/src/sys/contrib/ngatm
-I/usr/src/sys/dev/twa -I/usr/src/sys/dev/cxgb -I/usr/src/sys/dev/cxgbe
-I/usr/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS
-include opt_global.h -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
-mno-aes -mno-avx -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse
-msoft-float -fno-asynchronous-unwind-tables -ffreestanding
-fstack-protector /usr/src/sys/amd64/amd64/genassym.c
NM='nm' sh /usr/src/sys/kern/genassym.sh genassym.o  assym.s
awk -f /usr/src/sys/tools/vnode_if.awk /usr/src/sys/kern/vnode_if.src -p
awk -f /usr/src/sys/tools/vnode_if.awk /usr/src/sys/kern/vnode_if.src -q
awk -f /usr/src/sys/tools/vnode_if.awk /usr/src/sys/kern/vnode_if.src -h
awk -f /usr/src/sys/tools/acpi_quirks2h.awk
/usr/src/sys/dev/acpica/acpi_quirks
aicasm -nostdinc  -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq
-I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/dev/ath
-I/usr/src/sys/dev/ath/ath_hal -I/usr/src/sys/contrib/dev/ath/ath_hal
-I/usr/src/sys/contrib/ngatm -I/usr/src/sys/dev/twa -I/usr/src/sys/dev/cxgb
-I/usr/src/sys/dev/cxgbe -I/usr/src/sys/contrib/libfdt
-I/usr/src/sys/cam/scsi -I/usr/src/sys/dev/aic7xxx -o aic7xxx_seq.h -r
aic7xxx_reg.h -p aic7xxx_reg_print.c -i
/usr/src/sys/dev/aic7xxx/aic7xxx_osm.h /usr/src/sys/dev/aic7xxx/aic7xxx.seq
make[2]: exec(aicasm) failed (No such file or directory)
*** Error code 1

Stop.
make[2]: stopped in /usr/obj/usr/src/sys/GENERIC
*** Error code 1

Stop.
make[1]: stopped in /usr/src
___
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: CUURENT kernel build broken - make[2]: exec(aicasm) failed (No such file or directory)

[Outback Dingo]

On Mon, Nov 4, 2013 at 7:36 PM, Ian Lepore i...@freebsd.org wrote:

 On Mon, 2013-11-04 at 19:25 -0500, Outback Dingo wrote:
  cc  -c -O2 -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls
  -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith
  -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions
  -Wmissing-include-dirs -fdiagnostics-show-option
  -Wno-error-tautological-compare -Wno-error-empty-body
  -Wno-error-parentheses-equality -nostdinc -I. -I/usr/src/sys
  -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter
  -I/usr/src/sys/dev/ath -I/usr/src/sys/dev/ath/ath_hal
  -I/usr/src/sys/contrib/dev/ath/ath_hal -I/usr/src/sys/contrib/ngatm
  -I/usr/src/sys/dev/twa -I/usr/src/sys/dev/cxgb -I/usr/src/sys/dev/cxgbe
  -I/usr/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS
  -include opt_global.h -fno-omit-frame-pointer
 -mno-omit-leaf-frame-pointer
  -mno-aes -mno-avx -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse
  -msoft-float -fno-asynchronous-unwind-tables -ffreestanding
  -fstack-protector /usr/src/sys/amd64/amd64/genassym.c
  NM='nm' sh /usr/src/sys/kern/genassym.sh genassym.o  assym.s
  awk -f /usr/src/sys/tools/vnode_if.awk /usr/src/sys/kern/vnode_if.src -p
  awk -f /usr/src/sys/tools/vnode_if.awk /usr/src/sys/kern/vnode_if.src -q
  awk -f /usr/src/sys/tools/vnode_if.awk /usr/src/sys/kern/vnode_if.src -h
  awk -f /usr/src/sys/tools/acpi_quirks2h.awk
  /usr/src/sys/dev/acpica/acpi_quirks
  aicasm -nostdinc  -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq
  -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/dev/ath
  -I/usr/src/sys/dev/ath/ath_hal -I/usr/src/sys/contrib/dev/ath/ath_hal
  -I/usr/src/sys/contrib/ngatm -I/usr/src/sys/dev/twa
 -I/usr/src/sys/dev/cxgb
  -I/usr/src/sys/dev/cxgbe -I/usr/src/sys/contrib/libfdt
  -I/usr/src/sys/cam/scsi -I/usr/src/sys/dev/aic7xxx -o aic7xxx_seq.h -r
  aic7xxx_reg.h -p aic7xxx_reg_print.c -i
  /usr/src/sys/dev/aic7xxx/aic7xxx_osm.h
 /usr/src/sys/dev/aic7xxx/aic7xxx.seq
  make[2]: exec(aicasm) failed (No such file or directory)
  *** Error code 1
 
  Stop.
  make[2]: stopped in /usr/obj/usr/src/sys/GENERIC
  *** Error code 1
 
  Stop.
  make[1]: stopped in /usr/src

 Did you update your source and then make buildkernel without
 buildworld?  If so, a make kernel-toolchain should create the aicasm
 tool and get you back on track.


really odd as i built a kernel this morning no problem, then updated the
tree and went to build another kernel and got that.
working through it, thanks for the input..



 -- Ian



___
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: [CFT] bsdinstall and zfsboot enhancements

[Outback Dingo]

On Sat, Nov 2, 2013 at 1:59 PM, Teske, Devin devin.te...@fisglobal.comwrote:

 Hi all,

 Another Call For Testing...
 This one is for bsdinstall.

 Two patchsets are required for this CFT:

 http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_debug/
 http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/

 The enhancements are:

 + Add a `-D FILE command-line option for overriding the
 path to the bsdinstall log file (BSDINSTALL_LOG env var).

 + Document new `-D FILE' in the man page for bsdinstall.

 + If FILE in `-D FILE' begins with a +, debug output goes to
 stdout (interleaved between dialog(1) invocations/output) as
 well as to FILE (minus the leading + of course).

 + If BSDINSTALL_LOG cannot be written, then debugging is
 disabled (except in the case of a leading + in the pathname,
 wherein debug will still be printed to stdout).

 + Update source code format to approximate a future shstyle(9)

 + Fix a dangling participle (Begun ... - Began ...)

 + Rewrite the docsinstall script (was necessary to abate direct
 dependency on BSDINSTALL_LOG (instead, use fault-tolerant
 bsdconfig framework which displays appropriate errors for
 package management).

 + Add additional debug output for dhclient/rtsol/wpa_cliscan

 + Display script errors in a textbox rather than just on stdout

 + Update many coments.

 + Add new f_show_err() API call (like f_show_msg but changes
 the dialog title to Error)(see bsdconfig's `common.subr').

 + Add new f_eval_catch() API call for executing a command via
 eval but not before logging the command to debug. Several
 example cases documented in API header for function in
 bsdconfig's `common.subr'.

 + Fix dialog auto-sizing when launched as an rvalue to a pipe
 for indirected scripts (previously would default to 80x24 sizing
 in this case, now it can autosize to full size even when in a pipe
 chain).

 + Fix a bug in f_snprintf wherein if the $format argument began
 with a - or -- it would be misinterpreted as a flag to printf. (this
 is in bsdcofig's strings.subr)

 + Add accompanying f_sprintf() and f_vsprintf() to go along with
 already existing f_snprintf() and f_vsnprintf() (see bsdconfig's
 strings.subr).

 + Update bsdinstall's config script to adjust ttyu* entries in
 /etc/ttys when it is determined that we are in-fact doing an install
 over serial (e.g. bhyve).

 + Remove some unnecessary default ZFS datasets from the
 automatic zfsboot script. Such as: /usr/ports/distfiles
 /usr/ports/packages /usr/obj /var/db /var/empty /var/mail and
 /var/run (these can all be created as-needed once the system is
 installed).

 + Remove setuid=off for /usr/home (as discussed with others from
 last round of CFT).

 + Fix some i18n string violations in zfsboot

 + Bolster debugging output in zfsboot

 + Fix some string quoting issues in zfsboot

 + Fix some variable scope issues in zfsboot

 + Only display the ZFS vdev type selection menu when running
 interactively (duh).

 + Change Create to Install in zfsboot main menu

 + Increase pedantic error checking in zfsboot (type-check
 arguments and such).

 + Add a call to graid destroy to kill automatic metadata (part of
 the series of pedantic destructions we do when bootstrapping
 a new/naked disk).

 + Make judicious use of new f_eval_catch() in zfsboot

 + More comments (zfsboot).

 + Fixup some variable names for consistency (zfsboot).


nice work, looks good, patched the bootloader also, seems to function well,
love the kernel selection variable


 --
 Devin

 _
 The information contained in this message is proprietary and/or
 confidential. If you are not the intended recipient, please: (i) delete the
 message and all copies; (ii) do not disclose, distribute or use the message
 in any manner; and (iii) notify the sender immediately. In addition, please
 be aware that any message addressed to our domain is subject to archiving
 and review by persons other than the intended recipient. Thank you.

___
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: [CFT] Kernel-Selection Enhancemnt to Boot Menu

[Outback Dingo]

On Sat, Nov 2, 2013 at 12:47 PM, Teske, Devin devin.te...@fisglobal.comwrote:


 On Nov 2, 2013, at 1:45 AM, Sam Fourman Jr. wrote:

 
 
 
  On Sat, Nov 2, 2013 at 7:09 AM, Teske, Devin devin.te...@fisglobal.com
 wrote:
  Hi all,
 
  Here's a chance to test out the kernel selection menu enhancements
  to the boot loader menu before they go into HEAD.
 
  Discussion welcome, feedback desired.
 
  No recompile needed, just drop the new forth files onto a HEAD or
  stable/9 box and reboot.
  --
  Cheers,
  Devin
 
  where are the forth files in question?
 

 D'Oh!

 Here they are:

 http://druidbsd.cvs.sf.net/viewvc/druidbsd/forth_zfs/

 Supplied as patches to either stable/9 or head.


patched the bootloader, seems to function well, love the kernel selection
variable

 --
 Devin

 _
 The information contained in this message is proprietary and/or
 confidential. If you are not the intended recipient, please: (i) delete the
 message and all copies; (ii) do not disclose, distribute or use the message
 in any manner; and (iii) notify the sender immediately. In addition, please
 be aware that any message addressed to our domain is subject to archiving
 and review by persons other than the intended recipient. Thank you.

___
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

CURRENT issue with /dev/cs

[Outback Dingo]

cc  -c -O2 -pipe -fno-strict-aliasing  -std=c99 -g -Wall -Wredundant-decls
-Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith
-Winline -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions
 -Wmissing-include-dirs -fdiagnostics-show-option
 -Wno-error-tautological-compare -Wno-error-empty-body
 -Wno-error-parentheses-equality  -nostdinc  -I. -I/usr/src/sys
-I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/libfdt -D_KERNEL
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h  -fno-omit-frame-pointer
-mno-omit-leaf-frame-pointer -mno-aes -mno-avx -mcmodel=kernel
-mno-red-zone -mno-mmx -mno-sse -msoft-float
 -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror
 /usr/src/sys/dev/cs/if_cs.c
ctfconvert -L VERSION -g if_cs.o
cc  -c -O2 -pipe -fno-strict-aliasing  -std=c99 -g -Wall -Wredundant-decls
-Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith
-Winline -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions
 -Wmissing-include-dirs -fdiagnostics-show-option
 -Wno-error-tautological-compare -Wno-error-empty-body
 -Wno-error-parentheses-equality  -nostdinc  -I. -I/usr/src/sys
-I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/libfdt -D_KERNEL
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h  -fno-omit-frame-pointer
-mno-omit-leaf-frame-pointer -mno-aes -mno-avx -mcmodel=kernel
-mno-red-zone -mno-mmx -mno-sse -msoft-float
 -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror
 /usr/src/sys/dev/cs/if_cs_isa.c
In file included from /usr/src/sys/dev/cs/if_cs_isa.c:48:
/usr/src/sys/dev/cs/if_csvar.h:68:17: error: field has incomplete type
'struct callout'
struct callout timer;
   ^
/usr/src/sys/dev/cs/if_csvar.h:68:9: note: forward declaration of 'struct
callout'
struct callout timer;
   ^
1 error generated.
*** Error code 1

Stop.
bmake[2]: stopped in /usr/obj/usr/src/sys/GENERIC
___
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

CUURENT kernel build broken - /usr/src/sys/dev/xen/netback/netback.c

[Outback Dingo]

cc  -c -O2 -pipe -fno-strict-aliasing  -std=c99 -g -Wall -Wredundant-decls
-Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith
-Winline -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions
 -Wmissing-include-dirs -fdiagnostics-show-option
 -Wno-error-tautological-compare -Wno-error-empty-body
 -Wno-error-parentheses-equality  -nostdinc  -I. -I/usr/src/sys
-I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/libfdt -D_KERNEL
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h  -fno-omit-frame-pointer
-mno-omit-leaf-frame-pointer -mno-aes -mno-avx -mcmodel=kernel
-mno-red-zone -mno-mmx -mno-sse -msoft-float
 -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror
 /usr/src/sys/dev/xen/control/control.c
ctfconvert -L VERSION -g control.o
cc  -c -O2 -pipe -fno-strict-aliasing  -std=c99 -g -Wall -Wredundant-decls
-Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith
-Winline -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions
 -Wmissing-include-dirs -fdiagnostics-show-option
 -Wno-error-tautological-compare -Wno-error-empty-body
 -Wno-error-parentheses-equality  -nostdinc  -I. -I/usr/src/sys
-I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/libfdt -D_KERNEL
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h  -fno-omit-frame-pointer
-mno-omit-leaf-frame-pointer -mno-aes -mno-avx -mcmodel=kernel
-mno-red-zone -mno-mmx -mno-sse -msoft-float
 -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror
 /usr/src/sys/dev/xen/netback/netback.c
/usr/src/sys/dev/xen/netback/netback.c:588:7: error: incomplete definition
of type 'struct mbuf'
if (m-m_flags  M_PKTHDR) {
~^
/usr/src/sys/net/ethernet.h:367:8: note: forward declaration of 'struct
mbuf'
struct mbuf;
   ^
/usr/src/sys/dev/xen/netback/netback.c:588:19: error: use of undeclared
identifier 'M_PKTHDR'
if (m-m_flags  M_PKTHDR) {
 ^
/usr/src/sys/dev/xen/netback/netback.c:591:11: error: incomplete definition
of type 'struct mbuf'
   m-m_pkthdr.flowid, (int)m-m_pkthdr.csum_flags,
   ~^
/usr/src/sys/net/ethernet.h:367:8: note: forward declaration of 'struct
mbuf'
struct mbuf;
   ^
/usr/src/sys/dev/xen/netback/netback.c:594:11: error: incomplete definition
of type 'struct mbuf'
   m-m_pkthdr.rcvif, m-m_pkthdr.len);
   ~^
/usr/src/sys/net/ethernet.h:367:8: note: forward declaration of 'struct
mbuf'
struct mbuf;
   ^
/usr/src/sys/dev/xen/netback/netback.c:597:10: error: incomplete definition
of type 'struct mbuf'
   m-m_next, m-m_nextpkt, m-m_data);
   ~^
/usr/src/sys/net/ethernet.h:367:8: note: forward declaration of 'struct
mbuf'
struct mbuf;
   ^
/usr/src/sys/dev/xen/netback/netback.c:599:10: error: incomplete definition
of type 'struct mbuf'
   m-m_len, m-m_flags, m-m_type);
   ~^
/usr/src/sys/net/ethernet.h:367:8: note: forward declaration of 'struct
mbuf'
struct mbuf;
   ^
/usr/src/sys/dev/xen/netback/netback.c:601:9: error: incomplete definition
of type 'struct mbuf'
len = m-m_len;
  ~^
/usr/src/sys/net/ethernet.h:367:8: note: forward declaration of 'struct
mbuf'
struct mbuf;
   ^
/usr/src/sys/dev/xen/netback/netback.c:602:6: error: implicit declaration
of function 'mtod' is invalid in C99
[-Werror,-Wimplicit-function-declaration]
d = mtod(m, uint8_t*);
^
/usr/src/sys/dev/xen/netback/netback.c:602:14: error: unexpected type name
'uint8_t': expected expression
d = mtod(m, uint8_t*);
^
/usr/src/sys/dev/xen/netback/netback.c:602:22: error: expected expression
d = mtod(m, uint8_t*);
^
/usr/src/sys/dev/xen/netback/netback.c:1071:3: error: implicit declaration
of function 'if_free' is invalid in C99
[-Werror,-Wimplicit-function-declaration]
if_free(xnb-xnb_ifp);
^
/usr/src/sys/dev/xen/netback/netback.c:1213:24: error: implicit declaration
of function 'if_alloc' is invalid in C99
[-Werror,-Wimplicit-function-declaration]
ifp = xnb-xnb_ifp = if_alloc(IFT_ETHER);
 ^
/usr/src/sys/dev/xen/netback/netback.c:1213:22: error: incompatible integer
to pointer conversion assigning to 'struct ifnet *' from 'int'
[-Werror,-Wint-conversion]
ifp = xnb-xnb_ifp = if_alloc(IFT_ETHER);
   ^ ~~~
/usr/src/sys/dev/xen/netback/netback.c:1214:6: error: incomplete definition
of type 'struct ifnet'
ifp-if_softc = xnb;
~~~^
/usr/src/sys/net/if_arp.h:106:10: note: forward declaration of 'struct
ifnet'
struct  ifnet *ac_ifp;  /* network-visible interface */
^
/usr/src/sys/dev/xen/netback/netback.c:1215:3: error: implicit declaration
of function 'if_initname' is invalid in C99

Re: CURRENT issue with /dev/cs

[Outback Dingo]

On Mon, Oct 28, 2013 at 12:27 PM, Sean Bruno sean_br...@yahoo.com wrote:

 On Mon, 2013-10-28 at 10:27 -0400, Outback Dingo wrote:
  cc  -c -O2 -pipe -fno-strict-aliasing  -std=c99 -g -Wall
 -Wredundant-decls
  -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes
 -Wpointer-arith
  -Winline -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions
   -Wmissing-include-dirs -fdiagnostics-show-option
   -Wno-error-tautological-compare -Wno-error-empty-body
   -Wno-error-parentheses-equality  -nostdinc  -I. -I/usr/src/sys
  -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/libfdt -D_KERNEL
  -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h
  -fno-omit-frame-pointer
  -mno-omit-leaf-frame-pointer -mno-aes -mno-avx -mcmodel=kernel
  -mno-red-zone -mno-mmx -mno-sse -msoft-float
   -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror
   /usr/src/sys/dev/cs/if_cs.c
  ctfconvert -L VERSION -g if_cs.o
  cc  -c -O2 -pipe -fno-strict-aliasing  -std=c99 -g -Wall
 -Wredundant-decls
  -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes
 -Wpointer-arith
  -Winline -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions
   -Wmissing-include-dirs -fdiagnostics-show-option
   -Wno-error-tautological-compare -Wno-error-empty-body
   -Wno-error-parentheses-equality  -nostdinc  -I. -I/usr/src/sys
  -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/libfdt -D_KERNEL
  -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h
  -fno-omit-frame-pointer
  -mno-omit-leaf-frame-pointer -mno-aes -mno-avx -mcmodel=kernel
  -mno-red-zone -mno-mmx -mno-sse -msoft-float
   -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror
   /usr/src/sys/dev/cs/if_cs_isa.c
  In file included from /usr/src/sys/dev/cs/if_cs_isa.c:48:
  /usr/src/sys/dev/cs/if_csvar.h:68:17: error: field has incomplete type
  'struct callout'
  struct callout timer;
 ^
  /usr/src/sys/dev/cs/if_csvar.h:68:9: note: forward declaration of 'struct
  callout'
  struct callout timer;
 ^
  1 error generated.
  *** Error code 1
 
  Stop.
  bmake[2]: stopped in /usr/obj/usr/src/sys/GENERIC
  ___
  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


 thanks for catching this.  I've committed a fix for this at svn R257262


great thanks though seems now xen netback broken even worse :P ill quit for
the day and update tomorrow


 sean

___
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: CUREENT issue with ballon.c

[Outback Dingo]

On Thu, Oct 24, 2013 at 6:16 AM, Roger Pau Monné roger@citrix.comwrote:

 On 24/10/13 03:02, Outback Dingo wrote:
  --- trap 0, rip = 0, rsp = 0xfe2c6b70, rbp = 0 ---
  uma_zalloc_arg: zone 16 with the following non-sleepable locks held:
  exclusive sleep mutex balloon_lock (balloon_lock) r = 0
  (0x816e9c58) locked @ /usr/src/sys/dev/xen/balloon/balloon.c:339
  exclusive sleep mutex balloon_mutex (balloon_mutex) r = 0
  (0x816e9c38) locked @ /usr/src/sys/dev/xen/balloon/balloon.c:373
  KDB: stack backtrace:
  db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
  0xfe2c67c0
  kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe2c6870
  witness_warn() at witness_warn+0x4a8/frame 0xfe2c6930
  uma_zalloc_arg() at uma_zalloc_arg+0x3b/frame 0xfe2c69a0
  malloc() at malloc+0x101/frame 0xfe2c69f0
  balloon_process() at balloon_process+0x44a/frame 0xfe2c6a70
  fork_exit() at fork_exit+0x84/frame 0xfe2c6ab0
  fork_trampoline() at fork_trampoline+0xe/frame 0xfe2c6ab0
  --- trap 0, rip = 0, rsp = 0xfe2c6b70, rbp = 0 ---
  uma_zalloc_arg: zone 16 with the following non-sleepable locks held:
  exclusive sleep mutex balloon_lock (balloon_lock) r = 0
  (0x816e9c58) locked @ /usr/src/sys/dev/xen/balloon/balloon.c:339
  exclusive sleep mutex balloon_mutex (balloon_mutex) r = 0
  (0x816e9c38) locked @ /usr/src/sys/dev/xen/balloon/balloon.c:373
  KDB: stack backtrace:
  db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
  0xfe2c67c0
  kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe2c6870
  witness_warn() at witness_warn+0x4a8/frame 0xfe2c6930
  uma_zalloc_arg() at uma_zalloc_arg+0x3b/frame 0xfe2c69a0
  malloc() at malloc+0x101/frame 0xfe2c69f0
  balloon_process() at balloon_process+0x44a/frame 0xfe2c6a70
  fork_exit() at fork_exit+0x84/frame 0xfe2c6ab0
  fork_trampoline() at fork_trampoline+0xe/frame 0xfe2c6ab0
  --- trap 0, rip = 0, rsp = 0xfe2c6b70, rbp = 0 ---
  uma_zalloc_arg: zone 16 with the following non-sleepable locks held:

 Did you do anything specific to trigger the crash? Can you explain the
 steps needed to reproduce it?


just recompiled a kernel, and booted it scrolls continuously across the
screen
doesnt seem to ever stop.
___
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: CUREENT issue with ballon.c

[Outback Dingo]

On Thu, Oct 24, 2013 at 6:17 PM, Roger Pau Monné roger@citrix.comwrote:

 On 24/10/13 22:15, Konstantin Belousov wrote:
  On Thu, Oct 24, 2013 at 09:45:20PM +0100, Roger Pau Monn? wrote:
  On 24/10/13 13:01, Outback Dingo wrote:
 
 
  On Thu, Oct 24, 2013 at 6:16 AM, Roger Pau Monn? roger@citrix.com
  mailto:roger@citrix.com wrote:
 
  On 24/10/13 03:02, Outback Dingo wrote:
   --- trap 0, rip = 0, rsp = 0xfe2c6b70, rbp = 0 ---
   uma_zalloc_arg: zone 16 with the following non-sleepable locks
 held:
   exclusive sleep mutex balloon_lock (balloon_lock) r = 0
   (0x816e9c58) locked @
  /usr/src/sys/dev/xen/balloon/balloon.c:339
   exclusive sleep mutex balloon_mutex (balloon_mutex) r = 0
   (0x816e9c38) locked @
  /usr/src/sys/dev/xen/balloon/balloon.c:373
   KDB: stack backtrace:
   db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
   0xfe2c67c0
   kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe2c6870
   witness_warn() at witness_warn+0x4a8/frame 0xfe2c6930
   uma_zalloc_arg() at uma_zalloc_arg+0x3b/frame 0xfe2c69a0
   malloc() at malloc+0x101/frame 0xfe2c69f0
   balloon_process() at balloon_process+0x44a/frame
 0xfe2c6a70
   fork_exit() at fork_exit+0x84/frame 0xfe2c6ab0
   fork_trampoline() at fork_trampoline+0xe/frame 0xfe2c6ab0
   --- trap 0, rip = 0, rsp = 0xfe2c6b70, rbp = 0 ---
   uma_zalloc_arg: zone 16 with the following non-sleepable locks
 held:
   exclusive sleep mutex balloon_lock (balloon_lock) r = 0
   (0x816e9c58) locked @
  /usr/src/sys/dev/xen/balloon/balloon.c:339
   exclusive sleep mutex balloon_mutex (balloon_mutex) r = 0
   (0x816e9c38) locked @
  /usr/src/sys/dev/xen/balloon/balloon.c:373
   KDB: stack backtrace:
   db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
   0xfe2c67c0
   kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe2c6870
   witness_warn() at witness_warn+0x4a8/frame 0xfe2c6930
   uma_zalloc_arg() at uma_zalloc_arg+0x3b/frame 0xfe2c69a0
   malloc() at malloc+0x101/frame 0xfe2c69f0
   balloon_process() at balloon_process+0x44a/frame
 0xfe2c6a70
   fork_exit() at fork_exit+0x84/frame 0xfe2c6ab0
   fork_trampoline() at fork_trampoline+0xe/frame 0xfe2c6ab0
   --- trap 0, rip = 0, rsp = 0xfe2c6b70, rbp = 0 ---
   uma_zalloc_arg: zone 16 with the following non-sleepable locks
 held:
 
  Did you do anything specific to trigger the crash? Can you explain
 the
  steps needed to reproduce it?
 
 
  just recompiled a kernel, and booted it scrolls continuously across the
  screen
  doesnt seem to ever stop.
 
  I've tried r257051 and it seems to work fine, could you please post your
  Xen version, the config file used to launch the VM and the toolstack
 used?
 
  Do you have witness enabled in your kernel config ?

 Yes, but I'm not touching balloon memory target.

  There is an obvious case of calling malloc(M_WAITOK) while holding both
  balloon_lock and balloon_mutex:
  ballon_process-decrease_reservation-balloon_append.

 Yes, I'm aware of that, it's just that it shouldn't happen unless you
 actually trigger a balloon memory decrease, which should not happen
 automatically AFAIK, that's why I was asking if this was happening
 without the user specifically requesting it.

 Anyway, this should be clearly fixed and pulled into 10 no matter what
 triggered it. I will send a patch as soon as possible.


Yes, WITNESS was enabled, im using Kubuntu / XEN kernel / and
virt-manager it was fine running Current, until i ran updates this week
then encountered this. Ive since disabled WITNESS with a recompile, but the
VM still apears more sluggish then before.

root@M14xR2:/home/dingo# xm info
host   : M14xR2
release: 3.11.0-12-generic
version: #19-Ubuntu SMP Wed Oct 9 16:20:46 UTC 2013
machine: x86_64
nr_cpus: 4
nr_nodes   : 1
cores_per_socket   : 2
threads_per_core   : 2
cpu_mhz: 2494
xen:/// capabilities:
capabilities

  host
cpu
  archx86_64/arch
  features
pae/
  /features
/cpu
power_management
  suspend_mem/
  suspend_disk/
  suspend_hybrid/
/power_management
migration_features
  live/
  uri_transports
uri_transportxenmigr/uri_transport
  /uri_transports
/migration_features
  /host

  guest
os_typexen/os_type
arch name='x86_64'
  wordsize64/wordsize
  emulatorqemu-dm/emulator
  machinexenpv/machine
  domain type='xen'
  /domain
/arch
  /guest

  guest
os_typexen/os_type
arch name='i686'
  wordsize32/wordsize
  emulatorqemu-dm/emulator
  machinexenpv/machine

Re: CUREENT issue with ballon.c

[Outback Dingo]

On Thu, Oct 24, 2013 at 6:24 PM, Outback Dingo outbackdi...@gmail.comwrote:




 On Thu, Oct 24, 2013 at 6:17 PM, Roger Pau Monné roger@citrix.comwrote:

 On 24/10/13 22:15, Konstantin Belousov wrote:
  On Thu, Oct 24, 2013 at 09:45:20PM +0100, Roger Pau Monn? wrote:
  On 24/10/13 13:01, Outback Dingo wrote:
 
 
  On Thu, Oct 24, 2013 at 6:16 AM, Roger Pau Monn? 
 roger@citrix.com
  mailto:roger@citrix.com wrote:
 
  On 24/10/13 03:02, Outback Dingo wrote:
   --- trap 0, rip = 0, rsp = 0xfe2c6b70, rbp = 0 ---
   uma_zalloc_arg: zone 16 with the following non-sleepable
 locks held:
   exclusive sleep mutex balloon_lock (balloon_lock) r = 0
   (0x816e9c58) locked @
  /usr/src/sys/dev/xen/balloon/balloon.c:339
   exclusive sleep mutex balloon_mutex (balloon_mutex) r = 0
   (0x816e9c38) locked @
  /usr/src/sys/dev/xen/balloon/balloon.c:373
   KDB: stack backtrace:
   db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
   0xfe2c67c0
   kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe2c6870
   witness_warn() at witness_warn+0x4a8/frame 0xfe2c6930
   uma_zalloc_arg() at uma_zalloc_arg+0x3b/frame 0xfe2c69a0
   malloc() at malloc+0x101/frame 0xfe2c69f0
   balloon_process() at balloon_process+0x44a/frame
 0xfe2c6a70
   fork_exit() at fork_exit+0x84/frame 0xfe2c6ab0
   fork_trampoline() at fork_trampoline+0xe/frame
 0xfe2c6ab0
   --- trap 0, rip = 0, rsp = 0xfe2c6b70, rbp = 0 ---
   uma_zalloc_arg: zone 16 with the following non-sleepable
 locks held:
   exclusive sleep mutex balloon_lock (balloon_lock) r = 0
   (0x816e9c58) locked @
  /usr/src/sys/dev/xen/balloon/balloon.c:339
   exclusive sleep mutex balloon_mutex (balloon_mutex) r = 0
   (0x816e9c38) locked @
  /usr/src/sys/dev/xen/balloon/balloon.c:373
   KDB: stack backtrace:
   db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
   0xfe2c67c0
   kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe2c6870
   witness_warn() at witness_warn+0x4a8/frame 0xfe2c6930
   uma_zalloc_arg() at uma_zalloc_arg+0x3b/frame 0xfe2c69a0
   malloc() at malloc+0x101/frame 0xfe2c69f0
   balloon_process() at balloon_process+0x44a/frame
 0xfe2c6a70
   fork_exit() at fork_exit+0x84/frame 0xfe2c6ab0
   fork_trampoline() at fork_trampoline+0xe/frame
 0xfe2c6ab0
   --- trap 0, rip = 0, rsp = 0xfe2c6b70, rbp = 0 ---
   uma_zalloc_arg: zone 16 with the following non-sleepable
 locks held:
 
  Did you do anything specific to trigger the crash? Can you
 explain the
  steps needed to reproduce it?
 
 
  just recompiled a kernel, and booted it scrolls continuously across
 the
  screen
  doesnt seem to ever stop.
 
  I've tried r257051 and it seems to work fine, could you please post
 your
  Xen version, the config file used to launch the VM and the toolstack
 used?
 
  Do you have witness enabled in your kernel config ?

 Yes, but I'm not touching balloon memory target.

  There is an obvious case of calling malloc(M_WAITOK) while holding both
  balloon_lock and balloon_mutex:
  ballon_process-decrease_reservation-balloon_append.

 Yes, I'm aware of that, it's just that it shouldn't happen unless you
 actually trigger a balloon memory decrease, which should not happen
 automatically AFAIK, that's why I was asking if this was happening
 without the user specifically requesting it.

 Anyway, this should be clearly fixed and pulled into 10 no matter what
 triggered it. I will send a patch as soon as possible.


 Yes, WITNESS was enabled, im using Kubuntu / XEN kernel / and
 virt-manager it was fine running Current, until i ran updates this week
 then encountered this. Ive since disabled WITNESS with a recompile, but the
 VM still apears more sluggish then before.

 root@M14xR2:/home/dingo# xm info
 host   : M14xR2
 release: 3.11.0-12-generic
 version: #19-Ubuntu SMP Wed Oct 9 16:20:46 UTC 2013
 machine: x86_64
 nr_cpus: 4
 nr_nodes   : 1
 cores_per_socket   : 2
 threads_per_core   : 2
 cpu_mhz: 2494
 xen:/// capabilities:
 capabilities

   host
 cpu
   archx86_64/arch
   features
 pae/
   /features
 /cpu
 power_management
   suspend_mem/
   suspend_disk/
   suspend_hybrid/
 /power_management
 migration_features
   live/
   uri_transports
 uri_transportxenmigr/uri_transport
   /uri_transports
 /migration_features
   /host

   guest
 os_typexen/os_type
 arch name='x86_64'
   wordsize64/wordsize
   emulatorqemu-dm/emulator
   machinexenpv/machine
   domain type='xen'
   /domain
 /arch
   /guest

   guest

CUREENT issue with ballon.c

[Outback Dingo]

--- trap 0, rip = 0, rsp = 0xfe2c6b70, rbp = 0 ---
uma_zalloc_arg: zone 16 with the following non-sleepable locks held:
exclusive sleep mutex balloon_lock (balloon_lock) r = 0
(0x816e9c58) locked @ /usr/src/sys/dev/xen/balloon/balloon.c:339
exclusive sleep mutex balloon_mutex (balloon_mutex) r = 0
(0x816e9c38) locked @ /usr/src/sys/dev/xen/balloon/balloon.c:373
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
0xfe2c67c0
kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe2c6870
witness_warn() at witness_warn+0x4a8/frame 0xfe2c6930
uma_zalloc_arg() at uma_zalloc_arg+0x3b/frame 0xfe2c69a0
malloc() at malloc+0x101/frame 0xfe2c69f0
balloon_process() at balloon_process+0x44a/frame 0xfe2c6a70
fork_exit() at fork_exit+0x84/frame 0xfe2c6ab0
fork_trampoline() at fork_trampoline+0xe/frame 0xfe2c6ab0
--- trap 0, rip = 0, rsp = 0xfe2c6b70, rbp = 0 ---
uma_zalloc_arg: zone 16 with the following non-sleepable locks held:
exclusive sleep mutex balloon_lock (balloon_lock) r = 0
(0x816e9c58) locked @ /usr/src/sys/dev/xen/balloon/balloon.c:339
exclusive sleep mutex balloon_mutex (balloon_mutex) r = 0
(0x816e9c38) locked @ /usr/src/sys/dev/xen/balloon/balloon.c:373
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
0xfe2c67c0
kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe2c6870
witness_warn() at witness_warn+0x4a8/frame 0xfe2c6930
uma_zalloc_arg() at uma_zalloc_arg+0x3b/frame 0xfe2c69a0
malloc() at malloc+0x101/frame 0xfe2c69f0
balloon_process() at balloon_process+0x44a/frame 0xfe2c6a70
fork_exit() at fork_exit+0x84/frame 0xfe2c6ab0
fork_trampoline() at fork_trampoline+0xe/frame 0xfe2c6ab0
--- trap 0, rip = 0, rsp = 0xfe2c6b70, rbp = 0 ---
uma_zalloc_arg: zone 16 with the following non-sleepable locks held:
___
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: [SOLVED] Re: Can't start iscsid - kldload: can't load iscsi: Exec format error - FreeBSD 10 Alpha 2

[Outback Dingo]

On Fri, Oct 11, 2013 at 11:52 PM, Miguel C. miguelmcl...@gmail.com wrote:

 I updated to alpha5 it is indeed removed.

 Thanks


 Edward Tomasz Napierała tr...@freebsd.org wrote:
 Dnia 11 paź 2013 o godz. 13:15 Mike C. miguelmcl...@gmail.com
 napisał(a):
 
 
  On 10/11/13 09:24, Edward Tomasz Napierała wrote:
  Wiadomość napisana przez Mike C. w dniu 10 paź 2013, o godz. 23:41:
  Hi,
 
  I'm running Alpha-2 and wanted to test with iscsi but it seems I
 can't
  start iscsid.
 
 
  $ sudo service iscsid onerestart
  kldload: can't load iscsi: Exec format error
  /etc/rc.d/iscsid: WARNING: Unable to load kernel module iscsi
  /etc/rc.d/iscsid: WARNING: failed precmd routine for iscsid
 
 
  dmesg shows:
  interface icl.1 already present in the KLD 'kernel'!
  linker_load_file: Unsupported file type
 
  Do you have device ctl in your kernel config?  If so,
  either remove it (ctl.ko module is automatically loaded
  by ctladm), or add device iscsi.
 
  device  ctl # CAM Target Layer
 
  Seems that GENERIC has it by default! I'll remove and recompile!
 
 Actually, it got removed from GENERIC in 10 some time ago.


Ive actually noticed what i feel is an anomaly with ctladm... i can
literally
run ctladm create -b block -o file=/luns/LUN0 numerous times.. and
create a new LUN
every time, using the same file.

ctladm devlist
LUN Backend   Size (Blocks)   BS Serial NumberDevice ID
san: ~ # ctladm create -b block -o file=/mnt/extent6
LUN created successfully
backend:   block
device type:   0
LUN size:  10485760 bytes
blocksize  512 bytes
LUN ID:0
Serial Number: MYSERIAL   0
Device ID; MYDEVID   0
san: ~ # ctladm create -b block -o file=/mnt/extent6
LUN created successfully
backend:   block
device type:   0
LUN size:  10485760 bytes
blocksize  512 bytes
LUN ID:1
Serial Number: MYSERIAL   1
Device ID; MYDEVID   1
san: ~ # ctladm create -b block -o file=/mnt/extent6
LUN created successfully
backend:   block
device type:   0
LUN size:  10485760 bytes
blocksize  512 bytes
LUN ID:2
Serial Number: MYSERIAL   2
Device ID; MYDEVID   2
san: ~ # ctladm create -b block -o file=/mnt/extent6
LUN created successfully
backend:   block
device type:   0
LUN size:  10485760 bytes
blocksize  512 bytes
LUN ID:3
Serial Number: MYSERIAL   3
Device ID; MYDEVID   3
san: ~ # ctladm create -b block -o file=/mnt/extent6
LUN created successfully
backend:   block
device type:   0
LUN size:  10485760 bytes
blocksize  512 bytes
LUN ID:4
Serial Number: MYSERIAL   4
Device ID; MYDEVID   4
san: ~ # ctladm devlist -v
LUN Backend   Size (Blocks)   BS Serial NumberDevice ID
  0 block 20480  512 MYSERIAL   0 MYDEVID   0
  lun_type=0
  num_threads=14
  file=/mnt/extent6
  1 block 20480  512 MYSERIAL   1 MYDEVID   1
  lun_type=0
  num_threads=14
  file=/mnt/extent6
  2 block 20480  512 MYSERIAL   2 MYDEVID   2
  lun_type=0
  num_threads=14
  file=/mnt/extent6
  3 block 20480  512 MYSERIAL   3 MYDEVID   3
  lun_type=0
  num_threads=14
  file=/mnt/extent6
  4 block 20480  512 MYSERIAL   4 MYDEVID   4
  lun_type=0
  num_threads=14
  file=/mnt/extent6

notice the same file is used for each LUN.. it appears that ctladm
never checks for a LUN using the same file. or zpool for that
matter... anyway we can correct said behavior ??



 --
 Sent from my Android device with K-9 Mail. Please excuse my brevity.
 ___
 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

___
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: New iSCSI stack.

[Outback Dingo]

On Wed, Sep 11, 2013 at 5:14 PM, Edward Tomasz Napierała
tr...@freebsd.orgwrote:

 I'm working on last few minor nits to get this into the tree.  Give me few
 days,
 I'll prepare a patch against 9-STABLE.



Quick question, is there a specific reason why ctld doesnt create the file
/ device for iscsi, or fc ?
the previous iscsi would read the config file and create the file / device
... it now appears to be a
manual process.
___
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: FreeBSD 10 and zfsd.

[Outback Dingo]

On Fri, Oct 11, 2013 at 10:16 AM, Allan Jude free...@allanjude.com wrote:

 On 2013-10-11 04:27, O. Hartmann wrote:
  On Fri, 11 Oct 2013 03:24:51 -0400
  Allan Jude free...@allanjude.com wrote:
 
  On 2013-10-11 03:02, Johan Hendriks wrote:
  Johan Hendriks wrote:
  When i started using ZFS on FreeBSD I quickly found out that hot
  spares are not possible on FreeBSD.
  I was told that with zfsd it should be possible and that it would
  be included in FreeBSD 10.
 
  Is there some info about the zfsd function and how it could be
  used?
 
  regards
  Johan Hendriks
 
  Thanks all for the explanation and your time
  A notice in the handbook may be a good thing to let new FreeBSD
  users know that you can add spares, but that it is not a hot spare.
  So human action is required to activate the spare.
 
  regards
  Johan Hendriks
  ___
  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
  That bit is in the zfs handbook project branch, it just isn't
  published yet
 
  ... so it isn't visible to the normal users.
 
  I would also appreciate a hint in the man page of zpool(8). Like
  Be aware: A spare declared vdev is not (yet) automatically replacing a
  faulty rendered drive. Human action is still required.
 
  It could save some trouble in prevention.
 
  Oliver
 Lyndon Nerenberg attached a patch for the man page earlier in the
 thread, and I have forwarded that to the docs team


I was under the impression rc_setvar was dropped from rc.d scripts

i believe it should be


rcvar=`zfsd`

for /etc/rc.d/zfsd


 --
 Allan Jude

 ___
 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

___
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: FreeBSD 10 and zfsd.

[Outback Dingo]

On Fri, Oct 11, 2013 at 4:27 PM, Alan Somers asom...@freebsd.org wrote:

 On Fri, Oct 11, 2013 at 1:57 PM, Outback Dingo outbackdi...@gmail.com
 wrote:
  On Fri, Oct 11, 2013 at 10:16 AM, Allan Jude free...@allanjude.com
 wrote:
 
  On 2013-10-11 04:27, O. Hartmann wrote:
   On Fri, 11 Oct 2013 03:24:51 -0400
   Allan Jude free...@allanjude.com wrote:
  
   On 2013-10-11 03:02, Johan Hendriks wrote:
   Johan Hendriks wrote:
   When i started using ZFS on FreeBSD I quickly found out that hot
   spares are not possible on FreeBSD.
   I was told that with zfsd it should be possible and that it would
   be included in FreeBSD 10.
  
   Is there some info about the zfsd function and how it could be
   used?
  
   regards
   Johan Hendriks
  
   Thanks all for the explanation and your time
   A notice in the handbook may be a good thing to let new FreeBSD
   users know that you can add spares, but that it is not a hot spare.
   So human action is required to activate the spare.
  
   regards
   Johan Hendriks
   ___
   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
   That bit is in the zfs handbook project branch, it just isn't
   published yet
  
   ... so it isn't visible to the normal users.
  
   I would also appreciate a hint in the man page of zpool(8). Like
   Be aware: A spare declared vdev is not (yet) automatically replacing
 a
   faulty rendered drive. Human action is still required.
  
   It could save some trouble in prevention.
  
   Oliver
  Lyndon Nerenberg attached a patch for the man page earlier in the
  thread, and I have forwarded that to the docs team
 
 
  I was under the impression rc_setvar was dropped from rc.d scripts
 
  i believe it should be
 
 
  rcvar=`zfsd`
 
  for /etc/rc.d/zfsd

 Good catch.  I obviously still have a lot of merging to do.


also in my diff against CURRENT from your updated SVN, i found the patch
created a /usr/src/rc.d/zfsd instead of /usr/src/etc/rc.d a bit odd
and /usr/src/sbin/zfsd instead of /usr/src/cddl/sbin ... however the
Makefiles were correctly patched for both in the proper locations... though
IMHO i was tired... might have been me i moved them to the proper
places when i realized they were built on the first make world kernel :P
might want to double check. for others sanity


 
 
  --
  Allan Jude
 
  ___
  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
 
  ___
  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

___
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: rcs

[Outback Dingo]

On Thu, Oct 10, 2013 at 6:42 PM, Jakub Lach jakub_l...@mailplus.pl wrote:

 I have similar views. There is abundance of be-everything-for-everybody
 Linuxes
 and not enough lean and mean Unix-style kits...




however did we neglect to realize that even some ports need rcs


= clog-1.6.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
= Attempting to fetch
http://ftp.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/obrien/clog-1.6.tar.gz
clog-1.6.tar.gz   100% of   17 kB   59 kBps
00m00s
=== Fetching all distfiles required by clog-1.6 for building
===  Extracting for clog-1.6
= SHA256 Checksum OK for clog-1.6.tar.gz.
===  Patching for clog-1.6
===  Applying FreeBSD patches for clog-1.6
rcsdiff: not found
patch:  can't check out file clog.c: differs from default RCS version
= Patch patch-clog.c failed to apply cleanly.
*** Error code 1

Stop.
uname -a
FreeBSD zfsroot.xxx.com 10.0-ALPHA5 FreeBSD 10.0-ALPHA5 #0: Fri Oct 11
22:41:25 EDT 2013 m...@zfsroot.xxx.com:/usr/obj/usr/src/sys/GENERIC
 amd64






 --
 View this message in context:
 http://freebsd.1045724.n5.nabble.com/rcs-tp5850096p5850951.html
 Sent from the freebsd-current mailing list archive at Nabble.com.
 ___
 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

___
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: rcs

[Outback Dingo]

On Fri, Oct 11, 2013 at 11:52 PM, Glen Barber g...@freebsd.org wrote:

 On Fri, Oct 11, 2013 at 11:49:15PM -0400, Outback Dingo wrote:
  On Thu, Oct 10, 2013 at 6:42 PM, Jakub Lach jakub_l...@mailplus.pl
 wrote:
 
   I have similar views. There is abundance of be-everything-for-everybody
   Linuxes
   and not enough lean and mean Unix-style kits...
  
  
  
  
  however did we neglect to realize that even some ports need rcs
 
 
  = clog-1.6.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
  = Attempting to fetch
 
 http://ftp.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/obrien/clog-1.6.tar.gz
  clog-1.6.tar.gz   100% of   17 kB   59 kBps
  00m00s
  === Fetching all distfiles required by clog-1.6 for building
  ===  Extracting for clog-1.6
  = SHA256 Checksum OK for clog-1.6.tar.gz.
  ===  Patching for clog-1.6
  ===  Applying FreeBSD patches for clog-1.6
  rcsdiff: not found

 gjb@nucleus:~ % make -C /usr/ports/net-mgmt/clog -V PATCH_DEPENDS
 rcsdiff:/usr/ports/devel/rcs


Yupp just found it, i got it done, but thanks


 Glen


___
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: FreeBSD 10 and zfsd

[Outback Dingo]

On Thu, Oct 10, 2013 at 11:24 AM, Alan Somers asom...@freebsd.org wrote:

 On Thu, Oct 10, 2013 at 8:19 AM, Johan Hendriks joh.hendr...@gmail.com
 wrote:
  When i started using ZFS on FreeBSD I quickly found out that hot spares
 are
  not possible on FreeBSD.
  I was told that with zfsd it should be possible and that it would be
  included in FreeBSD 10.
 
  Is there some info about the zfsd function and how it could be used?

 zfsd is currently not in FreeBSD/head and won't make it into 10, but
 you can still get the source code from its project branch.  It's being
 used in production by at least two companies.

 http://svnweb.freebsd.org/base/projects/zfsd/head/


might be easier to just cut a diff of it, as it 2+ months behind CURRENT as
it is in this branch, be
nice to review and do some testing on, but getting a diff from that to
CURRENT might prove a bit difficult
unless the branch was updated


 
  regards
  Johan Hendriks
 
  ___
  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
 ___
 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

___
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: FreeBSD 10 and zfsd

[Outback Dingo]

On Thu, Oct 10, 2013 at 1:26 PM, Alan Somers asom...@freebsd.org wrote:

 On Thu, Oct 10, 2013 at 11:24 AM, Allan Jude free...@allanjude.com
 wrote:
  On 2013-10-10 12:13, Mark Felder wrote:
  On Thu, Oct 10, 2013, at 10:24, Alan Somers wrote:
  On Thu, Oct 10, 2013 at 8:19 AM, Johan Hendriks 
 joh.hendr...@gmail.com
  wrote:
  When i started using ZFS on FreeBSD I quickly found out that hot
 spares are
  not possible on FreeBSD.
  I was told that with zfsd it should be possible and that it would be
  included in FreeBSD 10.
 
  Is there some info about the zfsd function and how it could be used?
  zfsd is currently not in FreeBSD/head and won't make it into 10, but
  you can still get the source code from its project branch.  It's being
  used in production by at least two companies.
 
  So FreeBSD is going to have inferior ZFS management compared to
  Solaris/Illumos/etc for another 2+ years? Why are things like this
  allowed to miss releases?
  ___
  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
  ZFSd was a big topic of discussion at the EuroBSDCon 2013 dev summit (3
  weeks ago). There is a lot of collaboration going on, to bring in some
  work done by vendors like SpectraLogics. This is the type of feature
  that can be assed in 10.1, it won't have to wait for 11.
 
  You can see Robert Watsons talk How FreeBSD Works to see why releases
  are based on date, rather than on feature completion (because things are
  never finished)
 
 
 
  --
  Allan Jude
 
  ___
  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

 Due to popular demand, I have located a round toit.  I'm currently
 working on rebasing the zfsd project branch to head, after which I'll
 push SpectraLogic's recent changes.


Sweet... something to play with the next few days and see how
stable it is.


 ___
 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

___
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: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI

[Outback Dingo]

On Tue, Oct 8, 2013 at 5:21 AM, Teske, Devin devin.te...@fisglobal.comwrote:


 On Oct 7, 2013, at 10:48 PM, Allan Jude wrote:

  On 2013-10-08 01:11, Teske, Devin wrote:
  On Oct 7, 2013, at 10:07 PM, Allan Jude wrote:
 
  On 2013-10-07 15:59, Allan Jude wrote:
  Devin Teske and I have been working on a big patch to bsdinstall to
  implement installing on a ZFS pool. It supports both GPT and MBR, the
 4k
  sector gnop trick, and optional GELI encryption. We would like to
 commit
  this in time for 10.0-BETA1 so it needs some testing to work out any
  obvious bugs before we send it off to re@ to get it committed.
 
  It includes a single configuration menu that allows you to select all
 of
  the required details, including which drives to use (gets details from
  camcontrol, also includes an inspection utility that presents the
  detailed output of camcontrol inquiry/identify, and gpart show), what
  ZFS RAID level to use (taking in to consideration the selected number
 of
  drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc.
 
 
  Additional, it includes some other changes to bsdinstall:
  1. Change the default to the 'non-standard keyboard mapping' prompt
 to no
  2. Replace the 3 separate dialogs to configure an ipv4 address with
 just 1
  3. Remove the dialog asking if you wish to enable crash dumps, this
  feature has been combined into the regular 'services to enable' dialog
  and enabled by default
 
 
  You can browse the patches here:
  http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/
 
  I've built a bootonly.iso (10.0-ALPHA4) to make testing easier,
  available compressed (48 MB) or uncompressed (211 MB):
 
  http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz
 
  http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso
 
 
  We look forward to your feedback
 
  I've generated a new version of the ISO incorporating all of todays
  changes and moving up to 10.0-ALPHA5
  It includes 2 patches from Warren Block, improving the keymap menu and
  indicating which network interfaces are wireless
 
  Excellent.
 
  However, I have to say... you opened a can of worms by touching keymap.
 
  Eventually I plan to rewrite all of the scripts to the same format that
 zfsboot
  is using. I've already started rewriting keymap to the new format. Of
 course,
  this opened up another can of worms... the simple things like:
 
  DIALOG_OK
  DIALOG_CANCEL
  DIALOG_ESC
 
  Yeah, after having them, I felt a bit naked not having all of those
  'constants' defined.
 

 The constants are now where they belong... `dialog.subr'
 I also went through bsdconfig(8) with a fine-tooth comb and made use of the
 new constants everywhere.

 I think it's a definite improvement.



  Originally, all I had done was add --defaultno to the dialog command,
  but Warren's patch makes a lot of sense, allow the user to 'try' the new
  keymap before trying to do the rest of the install based on it.
 

 I rewrote warren's code into the stateful design and cleaned it up.



  I feel would be much better off in the `dialog.subr' module. So,...
 I've started
  peppering their usage everywhere in bsdconfig to make them proper.
 
  That means they will just be transparent from including `dialog.subr'.
 
 
  This is definately something that I think is a good idea, but my focus
  is on improving the usability and functionality of the installer in time
  for 10.0. Unifying everything to the bsdconfig style is slightly lower
  priority. Admittedly, the `bsdconfig networking` stuff is quite nice
 

 *nods*

 I took a look at the bsdinstall networking stuff, and I wanted to run away.

 Let's push that into the future.

 It wasn't too hard to get those global exit codes deployed, so I did that,
 but like you say... I agree we should minimize extra work that will be
 eventually slated for a future release.
 --
 Devin



Just noticed that when trying to install root-on-zfs under xen it doesn't
recognize the xbd0 virtual block device attached as ada0 so it skips the
install screen and goes to configure networking




  http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz
 
  http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso
 
  Excellent, thanks!
 
 
  --
  Allan Jude
 
  ___
  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

 _
 The information contained in this message is proprietary and/or
 confidential. If you are not the intended recipient, please: (i) delete the
 message and all copies; (ii) do not disclose, distribute or use the message
 in any manner; and (iii) notify the sender immediately. In addition, please
 be aware that any message addressed to our domain is subject to archiving
 and review by persons other than the intended recipient. Thank you.
 ___
 freebsd-current@freebsd.org 

Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI

[Outback Dingo]

On Tue, Oct 8, 2013 at 7:13 PM, Allan Jude free...@allanjude.com wrote:

 On 2013-10-08 16:17, Nathan Whitehorn wrote:
  On 10/07/13 21:59, Allan Jude wrote:
  Devin Teske and I have been working on a big patch to bsdinstall to
  implement installing on a ZFS pool. It supports both GPT and MBR, the 4k
  sector gnop trick, and optional GELI encryption. We would like to commit
  this in time for 10.0-BETA1 so it needs some testing to work out any
  obvious bugs before we send it off to re@ to get it committed.
 
  It includes a single configuration menu that allows you to select all of
  the required details, including which drives to use (gets details from
  camcontrol, also includes an inspection utility that presents the
  detailed output of camcontrol inquiry/identify, and gpart show), what
  ZFS RAID level to use (taking in to consideration the selected number of
  drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc.
 
 
  Additional, it includes some other changes to bsdinstall:
  1. Change the default to the 'non-standard keyboard mapping' prompt to
 no
  2. Replace the 3 separate dialogs to configure an ipv4 address with
 just 1
  3. Remove the dialog asking if you wish to enable crash dumps, this
  feature has been combined into the regular 'services to enable' dialog
  and enabled by default
 
 
  You can browse the patches here:
  http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/
 
  I've built a bootonly.iso (10.0-ALPHA4) to make testing easier,
  available compressed (48 MB) or uncompressed (211 MB):
 
  http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz
 
  http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso
 
 
  We look forward to your feedback
 
  Thanks for doing this! I had a few comments:
  1. ZFS is not bootable on all architectures. Could you adjust that menu
  item to only display for i386, amd64, and (I think?) sparc64. Use uname
  -m, not -p, for this.
 I had not considered that, I'll make that change

  1a. The script is broken on sparc64 in any case, which uses VTOC8
  instead of GPT.
 I'll disable sparc64 as well

  2. Why are you using camcontrol? That is guaranteed not to work on
  non-CAM systems. You should use the GEOM ident string if you need an ID.
 The GEOM ident string doesn't do enough to help the user identify which
 drive is which.
 More data is not exposed anywhere that I could find

 What we really need, is dev.ada.0.desc% like we have for network
 interfaces and a slew of other devices. GEOM data is great, but it is
 not exposed in a shell friendly way any place that I could find, other
 than the sysctl with DOT and XML data.

  3. Any plans to integrate this into the regular partition editor? ZFS
  support is important enough that I will definitely not get in the way,
  even as a bolt-on, but it would be a shame for it to stay that way. The
  editor is also designed for ZFS to be added.
 I am a sysadmin, not a programmer. I can't write C. Most people
 deploying servers can't write C. I agree with Devin Teske, if everything
 was in shell it would be a lot more usable for non-developers, who
 probably make up the majority of people who deploy FreeBSD.

  4. What is this gnop stuff for?
 yeah, we align the partitions and the blocks to ensure optimal
 performance on 'advanced format' drives, there is no real downside for
 older drives, and it saves you from headaches in the future.

  5. I think some substantial part of the MBR code will blow up if you are
  reinitalizing a previously formatted disk (the bsdlabel will be retasted
  and come back from the dead).
 We try to do what we can here, including creating a fresh GPT and MBR
 and blowing them away to ensure that anything left over is really dead.
 We also use zpool labelclear, which doesn't check if there ever was a
 ZFS label, it just blindly overwrites the spots where the label would go.
 I'll add some additional napalm to ensure there are no zombie partitions.

  -Nathan


I can now confirm with the latest patches from 1.5 hours ago applied i can
now install and boot
into a zfs-on-root system under XEN.. now you seriously ROCK! great
work ... and thanks

dmesg
Copyright (c) 1992-2013 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 10.0-ALPHA5 #1 r256169M: Wed Oct  9 01:03:43 EDT 2013
di...@current.optimcloud.com:/usr/obj/usr/src/sys/GENERIC amd64
FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610
XEN: Hypervisor version 4.3 detected.
CPU: Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz (2494.38-MHz K8-class CPU)
  Origin = GenuineIntel  Id = 0x306a9  Family = 0x6  Model = 0x3a
 Stepping = 9

Features=0x1783fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE,SSE2,HTT

Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI

[Outback Dingo]

On Tue, Oct 8, 2013 at 10:30 PM, Outback Dingo outbackdi...@gmail.comwrote:




 On Tue, Oct 8, 2013 at 7:13 PM, Allan Jude free...@allanjude.com wrote:

 On 2013-10-08 16:17, Nathan Whitehorn wrote:
  On 10/07/13 21:59, Allan Jude wrote:
  Devin Teske and I have been working on a big patch to bsdinstall to
  implement installing on a ZFS pool. It supports both GPT and MBR, the
 4k
  sector gnop trick, and optional GELI encryption. We would like to
 commit
  this in time for 10.0-BETA1 so it needs some testing to work out any
  obvious bugs before we send it off to re@ to get it committed.
 
  It includes a single configuration menu that allows you to select all
 of
  the required details, including which drives to use (gets details from
  camcontrol, also includes an inspection utility that presents the
  detailed output of camcontrol inquiry/identify, and gpart show), what
  ZFS RAID level to use (taking in to consideration the selected number
 of
  drives), GPT/mbr, 4k YES/no, GELI yes/NO, pool name, etc.
 
 
  Additional, it includes some other changes to bsdinstall:
  1. Change the default to the 'non-standard keyboard mapping' prompt to
 no
  2. Replace the 3 separate dialogs to configure an ipv4 address with
 just 1
  3. Remove the dialog asking if you wish to enable crash dumps, this
  feature has been combined into the regular 'services to enable' dialog
  and enabled by default
 
 
  You can browse the patches here:
  http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_zfs/
 
  I've built a bootonly.iso (10.0-ALPHA4) to make testing easier,
  available compressed (48 MB) or uncompressed (211 MB):
 
  http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso.xz
 
  http://www.allanjude.com/bsd/zfsbootonly_2013-10-06.iso
 
 
  We look forward to your feedback
 
  Thanks for doing this! I had a few comments:
  1. ZFS is not bootable on all architectures. Could you adjust that menu
  item to only display for i386, amd64, and (I think?) sparc64. Use uname
  -m, not -p, for this.
 I had not considered that, I'll make that change

  1a. The script is broken on sparc64 in any case, which uses VTOC8
  instead of GPT.
 I'll disable sparc64 as well

  2. Why are you using camcontrol? That is guaranteed not to work on
  non-CAM systems. You should use the GEOM ident string if you need an ID.
 The GEOM ident string doesn't do enough to help the user identify which
 drive is which.
 More data is not exposed anywhere that I could find

 What we really need, is dev.ada.0.desc% like we have for network
 interfaces and a slew of other devices. GEOM data is great, but it is
 not exposed in a shell friendly way any place that I could find, other
 than the sysctl with DOT and XML data.

  3. Any plans to integrate this into the regular partition editor? ZFS
  support is important enough that I will definitely not get in the way,
  even as a bolt-on, but it would be a shame for it to stay that way. The
  editor is also designed for ZFS to be added.
 I am a sysadmin, not a programmer. I can't write C. Most people
 deploying servers can't write C. I agree with Devin Teske, if everything
 was in shell it would be a lot more usable for non-developers, who
 probably make up the majority of people who deploy FreeBSD.

  4. What is this gnop stuff for?
 yeah, we align the partitions and the blocks to ensure optimal
 performance on 'advanced format' drives, there is no real downside for
 older drives, and it saves you from headaches in the future.

  5. I think some substantial part of the MBR code will blow up if you are
  reinitalizing a previously formatted disk (the bsdlabel will be retasted
  and come back from the dead).
 We try to do what we can here, including creating a fresh GPT and MBR
 and blowing them away to ensure that anything left over is really dead.
 We also use zpool labelclear, which doesn't check if there ever was a
 ZFS label, it just blindly overwrites the spots where the label would go.
 I'll add some additional napalm to ensure there are no zombie partitions.

  -Nathan


 I can now confirm with the latest patches from 1.5 hours ago applied i can
 now install and boot
 into a zfs-on-root system under XEN.. now you seriously ROCK! great
 work ... and thanks

 dmesg
 Copyright (c) 1992-2013 The FreeBSD Project.
 Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
 The Regents of the University of California. All rights reserved.
 FreeBSD is a registered trademark of The FreeBSD Foundation.
 FreeBSD 10.0-ALPHA5 #1 r256169M: Wed Oct  9 01:03:43 EDT 2013
 di...@current.optimcloud.com:/usr/obj/usr/src/sys/GENERIC amd64
 FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610
 XEN: Hypervisor version 4.3 detected.
 CPU: Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz (2494.38-MHz K8-class CPU)
   Origin = GenuineIntel  Id = 0x306a9  Family = 0x6  Model = 0x3a
  Stepping = 9

 Features=0x1783fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT

CURRENT BUILD FAILURE sys/modules/cxgbe

[Outback Dingo]

cc  -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc
 -I/usr/src/sys/modules/cxgbe/if_cxgbe/../../../dev/cxgbe
-DHAVE_KERNEL_OPTION_HEADERS -include
/usr/obj/usr/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq
-fno-common -g -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
-I/usr/obj/usr/src/sys/GENERIC  -mno-aes -mno-avx -mcmodel=kernel
-mno-red-zone -mno-mmx -mno-sse -msoft-float
 -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector
-std=iso9899:1999 -Qunused-arguments -fstack-protector -Wall
-Wredundant-decls -Wnested-externs -Wstrict-prototypes
 -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef
-Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs
-fdiagnostics-show-option  -Wno-error-tautological-compare
-Wno-error-empty-body  -Wno-error-parentheses-equality  -c
/usr/src/sys/modules/cxgbe/if_cxgbe/../../../dev/cxgbe/t4_sge.c
/usr/src/sys/modules/cxgbe/if_cxgbe/../../../dev/cxgbe/t4_sge.c:228:12:
error: use of undeclared identifier 'cpu_clflush_line_size'
pad = max(cpu_clflush_line_size, 16);
  ^
/usr/src/sys/modules/cxgbe/if_cxgbe/../../../dev/cxgbe/t4_sge.c:273:9:
error: use of undeclared identifier 'cpu_clflush_line_size'
len = cpu_clflush_line_size  64 ? 128 : 64;
  ^
2 errors generated.
___
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: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI

[Outback Dingo]

On Mon, Oct 7, 2013 at 4:54 PM, Allan Jude free...@allanjude.com wrote:

 On 2013-10-07 16:43, Warren Block wrote:
  On Mon, 7 Oct 2013, Allan Jude wrote:
 
  Additional, it includes some other changes to bsdinstall:
  1. Change the default to the 'non-standard keyboard mapping' prompt
  to no
 
  Please see http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/162175 .
  ___
  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
 That is a good idea, I'll add that

 I've also hit this:

 http://lists.freebsd.org/pipermail/freebsd-sysinstall/2013-September/000949.html
 and plan to throw in a fix for that.
 Which makes more sense, blindly 'killall dhclient' before we try to
 acquire a new lease, or detect that dhclient is running and try to use
 the IP that has already been assigned?



jeez after i just updated and patched my source tree to do a build, you
go and fix things :P
anyway you can just generate a master diff against the tree that we can
apply, seems not ive to
revert the patches and reapply all the newest ones.



 --
 Allan Jude

 ___
 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

___
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: CURRENT BUILD FAILURE sys/modules/cxgbe

[Outback Dingo]

On Mon, Oct 7, 2013 at 5:00 PM, Ian Lepore i...@freebsd.org wrote:

 On Mon, 2013-10-07 at 16:52 -0400, Outback Dingo wrote:
  cc  -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE
 -nostdinc
   -I/usr/src/sys/modules/cxgbe/if_cxgbe/../../../dev/cxgbe
  -DHAVE_KERNEL_OPTION_HEADERS -include
  /usr/obj/usr/src/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq
  -fno-common -g -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
  -I/usr/obj/usr/src/sys/GENERIC  -mno-aes -mno-avx -mcmodel=kernel
  -mno-red-zone -mno-mmx -mno-sse -msoft-float
   -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector
  -std=iso9899:1999 -Qunused-arguments -fstack-protector -Wall
  -Wredundant-decls -Wnested-externs -Wstrict-prototypes
   -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef
  -Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs
  -fdiagnostics-show-option  -Wno-error-tautological-compare
  -Wno-error-empty-body  -Wno-error-parentheses-equality  -c
  /usr/src/sys/modules/cxgbe/if_cxgbe/../../../dev/cxgbe/t4_sge.c
  /usr/src/sys/modules/cxgbe/if_cxgbe/../../../dev/cxgbe/t4_sge.c:228:12:
  error: use of undeclared identifier 'cpu_clflush_line_size'
  pad = max(cpu_clflush_line_size, 16);
^
  /usr/src/sys/modules/cxgbe/if_cxgbe/../../../dev/cxgbe/t4_sge.c:273:9:
  error: use of undeclared identifier 'cpu_clflush_line_size'
  len = cpu_clflush_line_size  64 ? 128 : 64;
^
  2 errors generated.

 Fixed in r256118.


odd i show that commit in my svn log however, kernel build still fails

 
r256120 | eadler | 2013-10-07 15:22:53 -0400 (Mon, 07 Oct 2013) | 4 lines

This regenerates src.conf.5 for both the RCS removal as well as r255784.

Approved by:re (glebius)


r256119 | dim | 2013-10-07 12:57:48 -0400 (Mon, 07 Oct 2013) | 6 lines

Remove redundant declarations of szsigcode and sigcode in
sys/i386/ibcs2/ibcs2_sysvec.c, to silence two gcc warnings.

Approved by:re (gjb)
MFC after:  3 days


r256118 | dim | 2013-10-07 12:56:56 -0400 (Mon, 07 Oct 2013) | 6 lines

Remove redundant declaration of cpu_clflush_line_size in
sys/dev/cxgbe/t4_sge.c, to silence a gcc warning.

Approved by:re (gjb)
MFC after:  3 days


r256117 | dim | 2013-10-07 12:55:34 -0400 (Mon, 07 Oct 2013) | 6 lines

Initialize a variable in sys/dev/xen/control/control.c, to silence a gcc
warning.

Approved by:re (gjb)


 -- Ian



___
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: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI

[Outback Dingo]

On Mon, Oct 7, 2013 at 5:49 PM, Teske, Devin devin.te...@fisglobal.comwrote:


 On Oct 7, 2013, at 2:47 PM, Allan Jude wrote:

  On 2013-10-07 17:00, Outback Dingo wrote:
  On Mon, Oct 7, 2013 at 4:54 PM, Allan Jude free...@allanjude.com
 wrote:
 
  On 2013-10-07 16:43, Warren Block wrote:
  On Mon, 7 Oct 2013, Allan Jude wrote:
 
  Additional, it includes some other changes to bsdinstall:
  1. Change the default to the 'non-standard keyboard mapping' prompt
  to no
  Please see http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/162175 .
  ___
  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
  That is a good idea, I'll add that
 
  I've also hit this:
 
 
 http://lists.freebsd.org/pipermail/freebsd-sysinstall/2013-September/000949.html
  and plan to throw in a fix for that.
  Which makes more sense, blindly 'killall dhclient' before we try to
  acquire a new lease, or detect that dhclient is running and try to use
  the IP that has already been assigned?
 
 
 
  jeez after i just updated and patched my source tree to do a build,
 you
  go and fix things :P
  anyway you can just generate a master diff against the tree that we can
  apply, seems not ive to
  revert the patches and reapply all the newest ones.
 
 
  --
  Allan Jude
 
  ___
  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
 
  ___
  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
 
  Attached find the patch from last night against a fresh HEAD
 
  I am working on incorporating Warren's patch now
 

 ... and I'm working to review and validate what Allan is writing ;D

 A couple of big patches to incorporate within the hour (next 15 minutes).


okies dokies guess ill revert it all and wait till you guys give the green
light to try again


 --
 Devin

 _
 The information contained in this message is proprietary and/or
 confidential. If you are not the intended recipient, please: (i) delete the
 message and all copies; (ii) do not disclose, distribute or use the message
 in any manner; and (iii) notify the sender immediately. In addition, please
 be aware that any message addressed to our domain is subject to archiving
 and review by persons other than the intended recipient. Thank you.
 ___
 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

___
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: Committing PEFS to CURRENT

[Outback Dingo]

On Mon, Oct 7, 2013 at 9:42 PM, Gleb Kurtsou gleb.kurt...@gmail.com wrote:

 On Mon, Oct 7, 2013 at 6:24 PM, John-Mark Gurney j...@funkthat.com wrote:
 
  But will the work get done to clean it up after the freeze is over?  What
  happens if it doesn't, will it get removed before 10.1 or will we have
  to live w/ the code?

 I still hope not to get hit by bus any time soon..


well, i think we all hope you dont get hit by a bus. ever



 ___
 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

___
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: Committing PEFS to CURRENT

[Outback Dingo]

On Mon, Oct 7, 2013 at 9:42 PM, Gleb Kurtsou gleb.kurt...@gmail.com wrote:

 On Mon, Oct 7, 2013 at 6:24 PM, John-Mark Gurney j...@funkthat.com wrote:
 
  But will the work get done to clean it up after the freeze is over?  What
  happens if it doesn't, will it get removed before 10.1 or will we have
  to live w/ the code?

 I still hope not to get hit by bus any time soon..


on a side note, i applied the patch to stable/9 out of curiosity and the
kernel failed to build the module
however i could install fine from ports.


 ___
 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

___
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: 10-stable does not boot on Dell E1505 any more

[Outback Dingo]

On Sat, Sep 14, 2013 at 1:37 PM, Warren Block wbl...@wonkity.com wrote:

 This is an older Dell E1505, Core 2 but does not have AHCI.

 r255569 does not find /dev/ada0s2a and ? at the mountroot prompt shows
 no devices.

 r255451 from September 10 boots fine.

 Also possibly relevant is that after successfully building and installing
 world and kernel, /boot/kernel.old is not being replaced. This is good at
 present because the old kernel still works, but shouldn't kernel.old be
 replaced on installkernel?


Yeah, i just got nicked by it in a XEN host same error i booted
kernel.old and made a copy of kernel.old - kernel.good just to get it to
boot again. guess it sits till someone fixes/resolves/reverts the naughty
code. :)


 __**_
 freebsd-current@freebsd.org mailing list
 http://lists.freebsd.org/**mailman/listinfo/freebsd-**currenthttp://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to freebsd-current-unsubscribe@**
 freebsd.org freebsd-current-unsubscr...@freebsd.org

___
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: 10-stable does not boot on Dell E1505 any more

[Outback Dingo]

On Sat, Sep 14, 2013 at 2:37 PM, Jan Kokemüller
jan.kokemuel...@gmail.comwrote:

  r255569 does not find /dev/ada0s2a and ? at the mountroot prompt
  shows no devices.

 I've had the same problem after I updated my kernel today. I tracked it
 down to the hyperv drivers that were added in r255524. Without the device
 hyperv line in my kernconf the system boots fine again.


i can confirm removing device hyperv does also work for me under XEN

 ___
 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

___
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: New iSCSI stack.

[Outback Dingo]

On Sun, Sep 8, 2013 at 9:32 AM, Outback Dingo outbackdi...@gmail.comwrote:




 On Sun, Sep 8, 2013 at 6:29 AM, Edward Tomasz Napierała tr...@freebsd.org
  wrote:

 Wiadomość napisana przez Alfred Perlstein bri...@mu.org w dniu 6 wrz
 2013, o godz. 20:18:
  On 9/5/13 3:27 AM, Edward Tomasz Napierała wrote:
  Hello.  At http://people.freebsd.org/~trasz/cfiscsi-20130904.diffyou'll 
  find
  a patch which adds the new iSCSI initiator and target, against
 10-CURRENT.
  To use the new initiator, start with man iscsictl.  For the target -
 man
  ctld.
 
  All feedback is welcome.  If nothing unexpected comes up, I'll commit
 it
  in a few days from now.  Note that it's still not optimized; at this
 point
  I'm focusing more on reliability and interoperability.
 
  This work is being sponsored by FreeBSD Foundation.
 
  ___
  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
 
  Edward, this is really exciting!
 
  Is there an easy way to use the userland iscsi configuration files?

 Which iSCSI userland configuration files, the ctl.conf(5)?  If you need
 an ability to parse it and modify from a shell scripts, see confctl
 utility
 (sysutils/confctl, https://github.com/trasz/confctl/).

  We would love to quickly backport and ship this with FreeNAS as an
 option for our users, having the config files be the same OR having a very
 good converter would really make that much easier for us.

 Porting to 9 should be quite easy - there are Capsicum API differences;
 you might also want to compare CTL between 10 and 9 to see if there are
 any changes which need to be merged.  Taking a look at the code searching
 for possible security issues would be also very welcome :-)

 As for the config files - writing a converter should be quite easy.  Which
 configuration files you need to support, ctl.conf(5) and istgt
 configuration?


 I was i belive quite close to having it working on the last patch, however
 could never seem to get the ctl kernel module to function,
 And feel im a bit further away with this latest patch retracing my steps,
 from previous... quite easy to backport maybe for you, or other
 but yes, I also would like to integrate the work to stable/9 in the lab
 for some benchmarks



Still trying to tackle this.. any ideas?? I think if i can get past the
few errors im encountering i can get a patch against stable/9 for others to
test

clang -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE
-nostdinc   -DHAVE_KERNEL_OPTION_HEADERS -include
/usr/obj/usr/home/dingo/devel/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq
-fno-common -g -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
-I/usr/obj/usr/home/dingo/devel/sys/GENERIC  -mno-aes -mno-avx
-mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float
 -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector
-std=iso9899:1999 -Qunused-arguments -fstack-protector -Wall
-Wredundant-decls -Wnested-externs -Wstrict-prototypes
 -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef
-Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs
-fdiagnostics-show-option  -Wno-error-tautological-compare
-Wno-error-empty-body  -Wno-error-parentheses-equality -c
/usr/home/dingo/devel/sys/modules/ctl/../../cam/ctl/ctl_frontend_cam_sim.c
ctfconvert -L VERSION -g ctl_frontend_cam_sim.o
clang -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE
-nostdinc   -DHAVE_KERNEL_OPTION_HEADERS -include
/usr/obj/usr/home/dingo/devel/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq
-fno-common -g -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
-I/usr/obj/usr/home/dingo/devel/sys/GENERIC  -mno-aes -mno-avx
-mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float
 -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector
-std=iso9899:1999 -Qunused-arguments -fstack-protector -Wall
-Wredundant-decls -Wnested-externs -Wstrict-prototypes
 -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef
-Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs
-fdiagnostics-show-option  -Wno-error-tautological-compare
-Wno-error-empty-body  -Wno-error-parentheses-equality -c
/usr/home/dingo/devel/sys/modules/ctl/../../cam/ctl/ctl_frontend_internal.c
ctfconvert -L VERSION -g ctl_frontend_internal.o
clang -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE
-nostdinc   -DHAVE_KERNEL_OPTION_HEADERS -include
/usr/obj/usr/home/dingo/devel/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq
-fno-common -g -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
-I/usr/obj/usr/home/dingo/devel/sys/GENERIC  -mno-aes -mno-avx
-mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float
 -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector
-std=iso9899:1999 -Qunused-arguments -fstack-protector -Wall
-Wredundant-decls -Wnested-externs

Re: New iSCSI stack.

[Outback Dingo]

On Wed, Sep 11, 2013 at 11:06 AM, Outback Dingo outbackdi...@gmail.comwrote:




 On Sun, Sep 8, 2013 at 9:32 AM, Outback Dingo outbackdi...@gmail.comwrote:




 On Sun, Sep 8, 2013 at 6:29 AM, Edward Tomasz Napierała 
 tr...@freebsd.org wrote:

 Wiadomość napisana przez Alfred Perlstein bri...@mu.org w dniu 6 wrz
 2013, o godz. 20:18:
  On 9/5/13 3:27 AM, Edward Tomasz Napierała wrote:
  Hello.  At http://people.freebsd.org/~trasz/cfiscsi-20130904.diffyou'll 
  find
  a patch which adds the new iSCSI initiator and target, against
 10-CURRENT.
  To use the new initiator, start with man iscsictl.  For the target
 - man
  ctld.
 
  All feedback is welcome.  If nothing unexpected comes up, I'll commit
 it
  in a few days from now.  Note that it's still not optimized; at this
 point
  I'm focusing more on reliability and interoperability.
 
  This work is being sponsored by FreeBSD Foundation.
 
  ___
  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
 
  Edward, this is really exciting!
 
  Is there an easy way to use the userland iscsi configuration files?

 Which iSCSI userland configuration files, the ctl.conf(5)?  If you need
 an ability to parse it and modify from a shell scripts, see confctl
 utility
 (sysutils/confctl, https://github.com/trasz/confctl/).

  We would love to quickly backport and ship this with FreeNAS as an
 option for our users, having the config files be the same OR having a very
 good converter would really make that much easier for us.

 Porting to 9 should be quite easy - there are Capsicum API differences;
 you might also want to compare CTL between 10 and 9 to see if there are
 any changes which need to be merged.  Taking a look at the code searching
 for possible security issues would be also very welcome :-)

 As for the config files - writing a converter should be quite easy.
  Which
 configuration files you need to support, ctl.conf(5) and istgt
 configuration?


 I was i belive quite close to having it working on the last patch,
 however could never seem to get the ctl kernel module to function,
 And feel im a bit further away with this latest patch retracing my steps,
 from previous... quite easy to backport maybe for you, or other
 but yes, I also would like to integrate the work to stable/9 in the lab
 for some benchmarks



 Still trying to tackle this.. any ideas?? I think if i can get past
 the few errors im encountering i can get a patch against stable/9 for
 others to test
 Negate the last posted error, Ive worked past it. I think if i can get
 past this capsicum issue, ill have a kernel

 === iscsi (all)
 clang -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE
 -nostdinc  -I/usr/home/dingo/devel/sys/modules/iscsi/../../ofed/include
 -DHAVE_KERNEL_OPTION_HEADERS -include
 /usr/obj/usr/home/dingo/devel/sys/GENERIC/opt_global.h -I. -I@ 
 -I@/contrib/altq
 -fno-common -g -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
 -I/usr/obj/usr/home/dingo/devel/sys/GENERIC  -mno-aes -mno-avx
 -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float
  -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector
 -std=iso9899:1999 -Qunused-arguments -fstack-protector -Wall
 -Wredundant-decls -Wnested-externs -Wstrict-prototypes
  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef
 -Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs
 -fdiagnostics-show-option  -Wno-error-tautological-compare
 -Wno-error-empty-body  -Wno-error-parentheses-equality -c
 /usr/home/dingo/devel/sys/modules/iscsi/../../dev/iscsi//icl.c
 /usr/home/dingo/devel/sys/modules/iscsi/../../dev/iscsi//icl.c:1098:26:
 error: use of undeclared identifier 'CAP_SOCK_CLIENT'
 cap_rights(rights, CAP_SOCK_CLIENT), fp);
 ^
 1 error generated.
 *** [icl.o] Error code 1

 Stop in /usr/home/dingo/devel/sys/modules/iscsi.


  ___
 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




___
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: New iSCSI stack.

[Outback Dingo]

On Wed, Sep 11, 2013 at 1:09 PM, Outback Dingo outbackdi...@gmail.comwrote:




 On Wed, Sep 11, 2013 at 11:06 AM, Outback Dingo outbackdi...@gmail.comwrote:




 On Sun, Sep 8, 2013 at 9:32 AM, Outback Dingo outbackdi...@gmail.comwrote:




 On Sun, Sep 8, 2013 at 6:29 AM, Edward Tomasz Napierała 
 tr...@freebsd.org wrote:

 Wiadomość napisana przez Alfred Perlstein bri...@mu.org w dniu 6 wrz
 2013, o godz. 20:18:
  On 9/5/13 3:27 AM, Edward Tomasz Napierała wrote:
  Hello.  At http://people.freebsd.org/~trasz/cfiscsi-20130904.diffyou'll 
  find
  a patch which adds the new iSCSI initiator and target, against
 10-CURRENT.
  To use the new initiator, start with man iscsictl.  For the target
 - man
  ctld.
 
  All feedback is welcome.  If nothing unexpected comes up, I'll
 commit it
  in a few days from now.  Note that it's still not optimized; at this
 point
  I'm focusing more on reliability and interoperability.
 
  This work is being sponsored by FreeBSD Foundation.
 
  ___
  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
 
  Edward, this is really exciting!
 
  Is there an easy way to use the userland iscsi configuration files?

 Which iSCSI userland configuration files, the ctl.conf(5)?  If you need
 an ability to parse it and modify from a shell scripts, see confctl
 utility
 (sysutils/confctl, https://github.com/trasz/confctl/).

  We would love to quickly backport and ship this with FreeNAS as an
 option for our users, having the config files be the same OR having a very
 good converter would really make that much easier for us.

 Porting to 9 should be quite easy - there are Capsicum API differences;
 you might also want to compare CTL between 10 and 9 to see if there are
 any changes which need to be merged.  Taking a look at the code
 searching
 for possible security issues would be also very welcome :-)

 As for the config files - writing a converter should be quite easy.
  Which
 configuration files you need to support, ctl.conf(5) and istgt
 configuration?


 I was i belive quite close to having it working on the last patch,
 however could never seem to get the ctl kernel module to function,
 And feel im a bit further away with this latest patch retracing my
 steps, from previous... quite easy to backport maybe for you, or other
 but yes, I also would like to integrate the work to stable/9 in the lab
 for some benchmarks



 Still trying to tackle this.. any ideas?? I think if i can get past
 the few errors im encountering i can get a patch against stable/9 for
 others to test
 Negate the last posted error, Ive worked past it. I think if i can
 get past this capsicum issue, ill have a kernel

 === iscsi (all)
 clang -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE
 -nostdinc  -I/usr/home/dingo/devel/sys/modules/iscsi/../../ofed/include
 -DHAVE_KERNEL_OPTION_HEADERS -include
 /usr/obj/usr/home/dingo/devel/sys/GENERIC/opt_global.h -I. -I@ 
 -I@/contrib/altq
 -fno-common -g -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
 -I/usr/obj/usr/home/dingo/devel/sys/GENERIC  -mno-aes -mno-avx
 -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float
  -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector
 -std=iso9899:1999 -Qunused-arguments -fstack-protector -Wall
 -Wredundant-decls -Wnested-externs -Wstrict-prototypes
  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef
 -Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs
 -fdiagnostics-show-option  -Wno-error-tautological-compare
 -Wno-error-empty-body  -Wno-error-parentheses-equality -c
 /usr/home/dingo/devel/sys/modules/iscsi/../../dev/iscsi//icl.c
 /usr/home/dingo/devel/sys/modules/iscsi/../../dev/iscsi//icl.c:1098:26:
 error: use of undeclared identifier 'CAP_SOCK_CLIENT'
 cap_rights(rights, CAP_SOCK_CLIENT), fp);
 ^
 1 error generated.
 *** [icl.o] Error code 1

 Stop in /usr/home/dingo/devel/sys/modules/iscsi.


and i guess, icl needs to be upgraded ?

KLD ctl.ko: depends on icl - not available or version mismatch




  ___
 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





___
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: New iSCSI stack.

[Outback Dingo]

On Sun, Sep 8, 2013 at 6:29 AM, Edward Tomasz Napierała
tr...@freebsd.orgwrote:

 Wiadomość napisana przez Alfred Perlstein bri...@mu.org w dniu 6 wrz
 2013, o godz. 20:18:
  On 9/5/13 3:27 AM, Edward Tomasz Napierała wrote:
  Hello.  At http://people.freebsd.org/~trasz/cfiscsi-20130904.diffyou'll 
  find
  a patch which adds the new iSCSI initiator and target, against
 10-CURRENT.
  To use the new initiator, start with man iscsictl.  For the target -
 man
  ctld.
 
  All feedback is welcome.  If nothing unexpected comes up, I'll commit it
  in a few days from now.  Note that it's still not optimized; at this
 point
  I'm focusing more on reliability and interoperability.
 
  This work is being sponsored by FreeBSD Foundation.
 
  ___
  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
 
  Edward, this is really exciting!
 
  Is there an easy way to use the userland iscsi configuration files?

 Which iSCSI userland configuration files, the ctl.conf(5)?  If you need
 an ability to parse it and modify from a shell scripts, see confctl utility
 (sysutils/confctl, https://github.com/trasz/confctl/).

  We would love to quickly backport and ship this with FreeNAS as an
 option for our users, having the config files be the same OR having a very
 good converter would really make that much easier for us.

 Porting to 9 should be quite easy - there are Capsicum API differences;
 you might also want to compare CTL between 10 and 9 to see if there are
 any changes which need to be merged.  Taking a look at the code searching
 for possible security issues would be also very welcome :-)

 As for the config files - writing a converter should be quite easy.  Which
 configuration files you need to support, ctl.conf(5) and istgt
 configuration?


I was i belive quite close to having it working on the last patch, however
could never seem to get the ctl kernel module to function,
And feel im a bit further away with this latest patch retracing my steps,
from previous... quite easy to backport maybe for you, or other
but yes, I also would like to integrate the work to stable/9 in the lab for
some benchmarks


 ___
 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

___
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: New iSCSI stack.

[Outback Dingo]

On Fri, Sep 6, 2013 at 1:50 AM, Edward Tomasz Napierała
tr...@freebsd.orgwrote:

 New patch, updated for Capsicum changes, is here:

 http://people.freebsd.org/~trasz/cfiscsi-20130906.diff


Bravo patched, compiled successfully and tested a lun using ctld

cfiscsi_ioctl_handoff: new connection from
iqn.1993-08.org.debian:01:7a3a657cdd11 (192.168.122.1) to
iqn.2012-06.com.example:target2
(0:2:0:0): MAINTENANCE (IN). CDB: a3 0c 01 12 00 00 00 00 02 00 00 00
(0:2:0:0): Tag: 0x0011, Type: 1
(0:2:0:0): CTL Status: SCSI Error
(0:2:0:0): SCSI Status: Check Condition
(0:2:0:0): SCSI sense: ILLEGAL REQUEST asc:24,0 (Invalid field in CDB)
(0:2:0:0): Command byte 1 bit 4 is invalid

it was mounted. partitioned, formatted ext4 and data copied to/from a linux
host
___
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: New iSCSI stack.

[Outback Dingo]

On Fri, Sep 6, 2013 at 2:18 PM, Alfred Perlstein bri...@mu.org wrote:

 On 9/5/13 3:27 AM, Edward Tomasz Napierała wrote:

 Hello.  At 
 http://people.freebsd.org/~**trasz/cfiscsi-20130904.diffhttp://people.freebsd.org/~trasz/cfiscsi-20130904.diffyou'll
  find
 a patch which adds the new iSCSI initiator and target, against 10-CURRENT.
 To use the new initiator, start with man iscsictl.  For the target -
 man
 ctld.

 All feedback is welcome.  If nothing unexpected comes up, I'll commit it
 in a few days from now.  Note that it's still not optimized; at this point
 I'm focusing more on reliability and interoperability.

 This work is being sponsored by FreeBSD Foundation.

 __**_
 freebsd-current@freebsd.org mailing list
 http://lists.freebsd.org/**mailman/listinfo/freebsd-**currenthttp://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to freebsd-current-unsubscribe@**
 freebsd.org freebsd-current-unsubscr...@freebsd.org

  Edward, this is really exciting!

 Is there an easy way to use the userland iscsi configuration files?

 We would love to quickly backport and ship this with FreeNAS as an option
 for our users, having the config files be the same OR having a very good
 converter would really make that much easier for us.


 your going to have to backport more then just this as capsicum and the ICL
stuff is iSCSI Common Layer, we went to try but kept getting caught up in
the ICL breakage also, but removal of all references in the patch to
capsicum, it was 4-6 files i belive, will get at least ctld and iscsi to
build, now you need the new cam which needs better eyes then mine to fix in
a back port due to icl version differences in 9 and 10.




 --
 Alfred Perlstein


 __**_
 freebsd-current@freebsd.org mailing list
 http://lists.freebsd.org/**mailman/listinfo/freebsd-**currenthttp://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to freebsd-current-unsubscribe@**
 freebsd.org freebsd-current-unsubscr...@freebsd.org

___
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: New iSCSI stack.

[Outback Dingo]

On Fri, Sep 6, 2013 at 4:03 PM, Outback Dingo outbackdi...@gmail.comwrote:




 On Fri, Sep 6, 2013 at 2:18 PM, Alfred Perlstein bri...@mu.org wrote:

 On 9/5/13 3:27 AM, Edward Tomasz Napierała wrote:

 Hello.  At 
 http://people.freebsd.org/~**trasz/cfiscsi-20130904.diffhttp://people.freebsd.org/~trasz/cfiscsi-20130904.diffyou'll
  find
 a patch which adds the new iSCSI initiator and target, against
 10-CURRENT.
 To use the new initiator, start with man iscsictl.  For the target -
 man
 ctld.

 All feedback is welcome.  If nothing unexpected comes up, I'll commit it
 in a few days from now.  Note that it's still not optimized; at this
 point
 I'm focusing more on reliability and interoperability.

 This work is being sponsored by FreeBSD Foundation.

 __**_
 freebsd-current@freebsd.org mailing list
 http://lists.freebsd.org/**mailman/listinfo/freebsd-**currenthttp://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to freebsd-current-unsubscribe@**
 freebsd.org freebsd-current-unsubscr...@freebsd.org

  Edward, this is really exciting!

 Is there an easy way to use the userland iscsi configuration files?

 We would love to quickly backport and ship this with FreeNAS as an option
 for our users, having the config files be the same OR having a very good
 converter would really make that much easier for us.


 your going to have to backport more then just this as capsicum and the
 ICL stuff is iSCSI Common Layer, we went to try but kept getting caught up
 in the ICL breakage also, but removal of all references in the patch to
 capsicum, it was 4-6 files i belive, will get at least ctld and iscsi to
 build, now you need the new cam which needs better eyes then mine to fix in
 a back port due to icl version differences in 9 and 10.




And i used this config as a simple test ctld.conf
 cat /etc/ctl.conf
 pidfile /var/run/ctld.pid

# auth-group example2 {
# chap-mutual user secret mutualuser22 mutualsecret
# chap-mutual user2 secret2 mutualuser22 mutualsecret
# }

 portal-group example2 {
 discovery-auth-group no-authentication
 listen 127.0.0.1
 listen 0.0.0.0:3261
 listen [::]:3261
 }

 target iqn.2012-06.com.example:target0 {
 auth-group no-authentication
 portal-group example2
 lun 0 {
 path /home/dingo/example_0
 blocksize 4096
 size 4G
 }
 }

 target iqn.2012-06.com.example:target3 {
 auth-group no-authentication
 portal-group example2
 lun 0 {
 path /home/dingo/example_3
 blocksize 4096
 size 4G
 }
 }

 target iqn.2012-06.com.example:target2 {
 auth-group no-authentication
 portal-group example2
 lun 0 {
 path /home/dingo/example2_0
 blocksize 4096
 size 4G
 }
 lun 1 {
 path /home/dingo/example2_1
 blocksize 4096
 size 4G
 }
 }

so your 9.x config mileage might vary



 --
 Alfred Perlstein


 __**_
 freebsd-current@freebsd.org mailing list
 http://lists.freebsd.org/**mailman/listinfo/freebsd-**currenthttp://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to freebsd-current-unsubscribe@**
 freebsd.org freebsd-current-unsubscr...@freebsd.org



___
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: New iSCSI stack.

[Outback Dingo]

On Thu, Sep 5, 2013 at 8:02 AM, Ivan Voras ivo...@freebsd.org wrote:

 On 5 September 2013 14:00, Edward Tomasz Napierała tr...@freebsd.org
 wrote:
  Wiadomość napisana przez Ivan Voras ivo...@freebsd.org w dniu 5 wrz
 2013, o godz. 13:18:
  On 05/09/2013 12:27, Edward Tomasz Napierała wrote:
  Hello.  At http://people.freebsd.org/~trasz/cfiscsi-20130904.diffyou'll 
  find
  a patch which adds the new iSCSI initiator and target, against
 10-CURRENT.
  To use the new initiator, start with man iscsictl.  For the target -
 man
  ctld.
 
  Just a naming question: ctld could mean anything, I'd parse it as a
  control deamon or something like that. Could you name it something
  which reminds the user of iscsi? Like iscsictld?
 
  As the man page says, ctld is CAM Target Layer / iSCSI target daemon.
  Sure, right now it's pretty iSCSI-specific, but it doesn't need to be -
 it can
  be extended to just manage CTL configuration (e.g. for Fibre Channel),
  or to support other CTL-backed storage protocols, such as FCoE.
 
  It's just a helper daemon for ctl(4) - thus, ctld(8).  And in case
 someone
  does man -k iscsi, there is the iSCSI target in the manual page
 title.

 Thanks, you're right!


Is it me, or is this patch mangled and does not apply cleanly to CURRENT


 ___
 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

___
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: New iSCSI stack.

[Outback Dingo]

On Thu, Sep 5, 2013 at 2:47 PM, Miroslav Lachman 000.f...@quip.cz wrote:

 Edward Tomasz Napierała wrote:

 Wiadomość napisana przez Ivan Vorasivo...@freebsd.org  w dniu 5 wrz
 2013, o godz. 13:18:

 On 05/09/2013 12:27, Edward Tomasz Napierała wrote:

 Hello.  At 
 http://people.freebsd.org/~**trasz/cfiscsi-20130904.diffhttp://people.freebsd.org/~trasz/cfiscsi-20130904.diffyou'll
  find
 a patch which adds the new iSCSI initiator and target, against
 10-CURRENT.
 To use the new initiator, start with man iscsictl.  For the target -
 man
 ctld.


 Just a naming question: ctld could mean anything, I'd parse it as a
 control deamon or something like that. Could you name it something
 which reminds the user of iscsi? Like iscsictld?


 As the man page says, ctld is CAM Target Layer / iSCSI target daemon.
 Sure, right now it's pretty iSCSI-specific, but it doesn't need to be -
 it can
 be extended to just manage CTL configuration (e.g. for Fibre Channel),
 or to support other CTL-backed storage protocols, such as FCoE.

 It's just a helper daemon for ctl(4) - thus, ctld(8).  And in case someone
 does man -k iscsi, there is the iSCSI target in the manual page title.


 I understand your explanation, but still thinking rc.conf variables are
 really confusing and unintuitive:

 iscsid_enable
 iscsictl_enable
 ctld_enable

 I cannot tell what they control just by their names and the same apply for
 services names.

 If I want to restart iscsi target, should I use 'service iscsid restart'
 or 'service iscsictl restart'? ... oh wait, it should be 'service ctld
 restart'

 I think it should be more user friendly. Something as Apache 2.2.x has
 httpd and httpd.conf, but users are using 'service apache22 restart' and
 'apache22_enable=YES', because there can be more http daemons.

 My $0.02


Just an FYI 10_CURRENT svn info
Path: .
Working Copy Root Path: /usr/src
URL: http://svn.freebsd.org/base/head
Relative URL: ^/head
Repository Root: http://svn.freebsd.org/base
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 255253
Node Kind: directory
Schedule: normal
Last Changed Author: sjg
Last Changed Rev: 255253
Last Changed Date: 2013-09-05 11:57:26 -0400 (Thu, 05 Sep 2013)


cc  -O2 -pipe  -I/usr/src/usr.sbin/ctld -I/usr/src/usr.sbin/ctld/../../sys
-I/usr/src/usr.sbin/ctld/../../sys/cam/ctl
-I/usr/src/usr.sbin/ctld/../../sys/dev/iscsi -std=gnu99 -Qunused-arguments
-fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W
-Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes
-Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow
-Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs
-Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-empty-body
-Wno-string-plus-int -c /usr/src/usr.sbin/ctld/ctld.c
cc  -O2 -pipe  -I/usr/src/usr.sbin/ctld -I/usr/src/usr.sbin/ctld/../../sys
-I/usr/src/usr.sbin/ctld/../../sys/cam/ctl
-I/usr/src/usr.sbin/ctld/../../sys/dev/iscsi -std=gnu99 -Qunused-arguments
-fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W
-Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes
-Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow
-Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs
-Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-empty-body
-Wno-string-plus-int -c /usr/src/usr.sbin/ctld/discovery.c
cc  -O2 -pipe  -I/usr/src/usr.sbin/ctld -I/usr/src/usr.sbin/ctld/../../sys
-I/usr/src/usr.sbin/ctld/../../sys/cam/ctl
-I/usr/src/usr.sbin/ctld/../../sys/dev/iscsi -std=gnu99 -Qunused-arguments
-fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W
-Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes
-Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow
-Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs
-Wredundant-decls -Wold-style-definition -Wno-pointer-sign -Wno-empty-body
-Wno-string-plus-int -c /usr/src/usr.sbin/ctld/kernel.c
/usr/src/usr.sbin/ctld/kernel.c:762:35: error: incompatible integer to
pointer conversion passing 'unsigned long long' to parameter of type 'const
cap_rights_t *' (aka 'const struct cap_rights *') [-Werror,-Wint-conversion]
error = cap_rights_limit(ctl_fd, CAP_IOCTL);
 ^
/usr/src/usr.sbin/ctld/../../sys/sys/capability.h:197:20: note: expanded
from macro 'CAP_IOCTL'
#define CAP_IOCTL   CAPRIGHT(1, 0x0080ULL)
^~
/usr/src/usr.sbin/ctld/../../sys/sys/capability.h:53:28: note: expanded
from macro 'CAPRIGHT'
#define CAPRIGHT(idx, bit)  ((1ULL  (57 + (idx))) | (bit))
^~~~
/usr/src/usr.sbin/ctld/../../sys/sys/capability.h:327:50: note: passing
argument to parameter 'rights' here
int cap_rights_limit(int fd, const cap_rights_t *rights);
   

Re: New iSCSI stack.

[Outback Dingo]

On Thu, Sep 5, 2013 at 1:55 PM, Outback Dingo outbackdi...@gmail.comwrote:




 On Thu, Sep 5, 2013 at 8:02 AM, Ivan Voras ivo...@freebsd.org wrote:

 On 5 September 2013 14:00, Edward Tomasz Napierała tr...@freebsd.org
 wrote:
  Wiadomość napisana przez Ivan Voras ivo...@freebsd.org w dniu 5 wrz
 2013, o godz. 13:18:
  On 05/09/2013 12:27, Edward Tomasz Napierała wrote:
  Hello.  At http://people.freebsd.org/~trasz/cfiscsi-20130904.diffyou'll 
  find
  a patch which adds the new iSCSI initiator and target, against
 10-CURRENT.
  To use the new initiator, start with man iscsictl.  For the target
 - man
  ctld.
 
  Just a naming question: ctld could mean anything, I'd parse it as a
  control deamon or something like that. Could you name it something
  which reminds the user of iscsi? Like iscsictld?
 
  As the man page says, ctld is CAM Target Layer / iSCSI target daemon.
  Sure, right now it's pretty iSCSI-specific, but it doesn't need to be -
 it can
  be extended to just manage CTL configuration (e.g. for Fibre Channel),
  or to support other CTL-backed storage protocols, such as FCoE.
 
  It's just a helper daemon for ctl(4) - thus, ctld(8).  And in case
 someone
  does man -k iscsi, there is the iSCSI target in the manual page
 title.

 Thanks, you're right!



Nevermind


 Is it me, or is this patch mangled and does not apply cleanly to CURRENT




 ___
 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
 



___
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: New iSCSI stack.

[Outback Dingo]

On Thu, Sep 5, 2013 at 5:09 PM, O. Hartmann ohart...@zedat.fu-berlin.dewrote:

 On Thu, 5 Sep 2013 16:03:31 -0400
 Outback Dingo outbackdi...@gmail.com wrote:

  On Thu, Sep 5, 2013 at 2:47 PM, Miroslav Lachman 000.f...@quip.cz
  wrote:
 
   Edward Tomasz Napierała wrote:
  
   Wiadomość napisana przez Ivan Vorasivo...@freebsd.org  w dniu 5
   wrz 2013, o godz. 13:18:
  
   On 05/09/2013 12:27, Edward Tomasz Napierała wrote:
  
   Hello.  At
   http://people.freebsd.org/~**trasz/cfiscsi-20130904.diff
 http://people.freebsd.org/~trasz/cfiscsi-20130904.diffyou'll
   find a patch which adds the new iSCSI initiator and target,
   against 10-CURRENT. To use the new initiator, start with man
   iscsictl.  For the target - man
   ctld.
  
  
   Just a naming question: ctld could mean anything, I'd parse it
   as a control deamon or something like that. Could you name it
   something which reminds the user of iscsi? Like iscsictld?
  
  
   As the man page says, ctld is CAM Target Layer / iSCSI target
   daemon. Sure, right now it's pretty iSCSI-specific, but it
   doesn't need to be - it can
   be extended to just manage CTL configuration (e.g. for Fibre
   Channel), or to support other CTL-backed storage protocols, such
   as FCoE.
  
   It's just a helper daemon for ctl(4) - thus, ctld(8).  And in case
   someone does man -k iscsi, there is the iSCSI target in the
   manual page title.
  
  
   I understand your explanation, but still thinking rc.conf variables
   are really confusing and unintuitive:
  
   iscsid_enable
   iscsictl_enable
   ctld_enable
  
   I cannot tell what they control just by their names and the same
   apply for services names.
  
   If I want to restart iscsi target, should I use 'service iscsid
   restart' or 'service iscsictl restart'? ... oh wait, it should be
   'service ctld restart'
  
   I think it should be more user friendly. Something as Apache 2.2.x
   has httpd and httpd.conf, but users are using 'service apache22
   restart' and 'apache22_enable=YES', because there can be more
   http daemons.
  
   My $0.02
  
  
  Just an FYI 10_CURRENT svn info
  Path: .
  Working Copy Root Path: /usr/src
  URL: http://svn.freebsd.org/base/head
  Relative URL: ^/head
  Repository Root: http://svn.freebsd.org/base
  Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
  Revision: 255253
  Node Kind: directory
  Schedule: normal
  Last Changed Author: sjg
  Last Changed Rev: 255253
  Last Changed Date: 2013-09-05 11:57:26 -0400 (Thu, 05 Sep 2013)
 
 
  cc  -O2 -pipe  -I/usr/src/usr.sbin/ctld
  -I/usr/src/usr.sbin/ctld/../../sys
  -I/usr/src/usr.sbin/ctld/../../sys/cam/ctl
  -I/usr/src/usr.sbin/ctld/../../sys/dev/iscsi -std=gnu99
  -Qunused-arguments -fstack-protector -Wsystem-headers -Werror -Wall
  -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes
  -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual
  -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align
  -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls
  -Wold-style-definition -Wno-pointer-sign -Wno-empty-body
  -Wno-string-plus-int -c /usr/src/usr.sbin/ctld/ctld.c cc  -O2 -pipe
  -I/usr/src/usr.sbin/ctld -I/usr/src/usr.sbin/ctld/../../sys
  -I/usr/src/usr.sbin/ctld/../../sys/cam/ctl
  -I/usr/src/usr.sbin/ctld/../../sys/dev/iscsi -std=gnu99
  -Qunused-arguments -fstack-protector -Wsystem-headers -Werror -Wall
  -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes
  -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual
  -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align
  -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls
  -Wold-style-definition -Wno-pointer-sign -Wno-empty-body
  -Wno-string-plus-int -c /usr/src/usr.sbin/ctld/discovery.c cc  -O2
  -pipe  -I/usr/src/usr.sbin/ctld -I/usr/src/usr.sbin/ctld/../../sys
  -I/usr/src/usr.sbin/ctld/../../sys/cam/ctl
  -I/usr/src/usr.sbin/ctld/../../sys/dev/iscsi -std=gnu99
  -Qunused-arguments -fstack-protector -Wsystem-headers -Werror -Wall
  -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes
  -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual
  -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align
  -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls
  -Wold-style-definition -Wno-pointer-sign -Wno-empty-body
  -Wno-string-plus-int
  -c /usr/src/usr.sbin/ctld/kernel.c
 /usr/src/usr.sbin/ctld/kernel.c:762:35:
  error: incompatible integer to pointer conversion passing 'unsigned
  long long' to parameter of type 'const cap_rights_t *' (aka 'const
  struct cap_rights *') [-Werror,-Wint-conversion] error =
  cap_rights_limit(ctl_fd, CAP_IOCTL);
  ^ /usr/src/usr.sbin/ctld/../../sys/sys/capability.h:197:20:
  note: expanded from macro 'CAP_IOCTL' #define CAP_IOCTL
  CAPRIGHT(1, 0x0080ULL)
  ^~
 /usr/src/usr.sbin/ctld/../../sys/sys/capability.h:53:28:
  note: expanded from macro 'CAPRIGHT' #define CAPRIGHT(idx

Re: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking

[Outback Dingo]

On Tue, Sep 3, 2013 at 9:42 AM, Jeremie Le Hen j...@freebsd.org wrote:

 On Mon, Sep 02, 2013 at 11:49:33AM +0300, Alexander Motin wrote:
  Hi.
 
  I would like to invite more people to review and test my patches for
  improving CAM and GEOM scalability, that for last six months you could
  see developing in project/camlock SVN branch. Full diff of that branch
  against present head (r255131) can be found here:
  http://people.freebsd.org/~mav/camlock_patches/camlock_20130902.patch

 I'm building my kernel right now.


Can anyone confirm how well tested/stable this patch set might be?? if
theres positive input i have a zoo of dev machines i could load it on, to
help further it.
Just checking to see how widely its been tested,


 --
 Jeremie Le Hen

 Scientists say the world is made up of Protons, Neutrons and Electrons.
 They forgot to mention Morons.
 ___
 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

___
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: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking

[Outback Dingo]

On Tue, Sep 3, 2013 at 5:48 PM, Olivier Cochard-Labbé oliv...@cochard.mewrote:

 On Tue, Sep 3, 2013 at 8:10 PM, Outback Dingo outbackdi...@gmail.com
 wrote:
  Can anyone confirm how well tested/stable this patch set might be?? if
  theres positive input i have a zoo of dev machines i could load it on, to
  help further it.
  Just checking to see how widely its been tested,

 I've installed this patch on 3 differents machines there status after
 about 12hours:
 - SUN FIRE X4170 M2 (amd64: r255178) with 6 SAS harddrives in one big
 zraid (LSI MegaSAS Gen2 controller): Used for generating package with
 poudriere… no probleme since;
 - HAL/Fujitsu SPARC64-V (sparc64: r255178) with two SCSI-3 disks in
 gmirror: Used for generating package with poudriere too… no probleme
 since;
 - HP EliteBook 8460p (amd64: r255188) with DVD replaced by a second
 hardrive (where fbsd is installed): It crash just after the message
 GEOM: new disk ada1 during boot

 screenshot of the crash screen:
 http://goo.gl/tW1VIx

 A little more information:
 addr2line -e /boot/kernel/kernel.symbols 0x8083abd3
 /usr/src/sys/geom/geom_io.c:129

 Regards,

 Olivier


Be nice if it was backported to 9/stable. not sure how feasible it is
though... patch fails in a few places.
___
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: patch to improve AES-NI performance

[Outback Dingo]

On Sun, Aug 25, 2013 at 10:19 AM, Ollivier Robert robe...@keltia.freenix.fr
 wrote:

 According to Ollivier Robert:
  You are right, I wanted to say r226837 which is the code one.

 FYI I've finally merged r226837,r226839 as r254856 in stable/9 as it is a
 prerequesite to apply jmg's patch.  I've asked re@ whether they would
 consider this for 9.2.  It is very late in the 9.2 release circle but that
 patch has been in 10 for more than a year now...


So this patch can now be applied to STABLE/9 for testing on a local system
since these 3 revisions are now in??


 --
 Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=-
 robe...@keltia.freenix.fr
 In memoriam to Ondine : http://ondine.keltia.net/
 ___
 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

___
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: [HEADSUP] No more pkg_install on HEAD by default

[Outback Dingo]

On Sat, Jul 13, 2013 at 7:59 AM, Baptiste Daroussin b...@freebsd.orgwrote:

 On Sat, Jul 13, 2013 at 06:11:11AM -0500, Mark Linimon wrote:
  fwiw, nanobsd also is still on pkg_*, but I intend to come up with
  patches for that if someone else has not already done so.
 
  mcl

 There are lots of patches available everyone to have nanobsd using pkgng

 I didn't commit any, because I do find the nanobsd dev a bit weird, lots of
 different version everywhere, lots of different patches etc.


would someone like to forward their patches for pkg on nanobsd to the list


 regards,
 Bapt

___
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: SOLVED: Re: Skype in head (r250588)

[Outback Dingo]

On Sun, May 19, 2013 at 10:49 AM, Matthias Apitz g...@unixarea.de wrote:

 El día Friday, May 17, 2013 a las 12:08:17PM +, Matthias Apitz
 escribió:

 
  Hello,
 
  I have updated my laptop today to /head r250588, the ports are also from
  SVN as of April 1;
 
  cuse4bsd-kmod-0.1.27
  webcamd-3.9.0.5
  skype-2.1.0.81_1,1
  libv4l-0.8.8_1
  v4l_compat-1.0.20120501_1
  linux-f10-libv4l-0.6.2
 
  The laptop has a built-in cam and I have attached another via USB,
  both are working fine with pwcview(1);
 

 After a lot of tests and debugging it turned out that only the local
 test view and the local own view in calls were not working; the problem
 reduced that way to a local X11 issue; I deleted in xorg.conf the
 entries about

 # Virtual   2944 2944

 in all Display sections and after it the local picture in Skype was
 working too; don't know what the relationship between this in the
 overlay in Skype is.


So ... wait skype now works in FreeBSD ?? And with cams?



 matthias
 --
 Matthias Apitz   |  /\ ASCII Ribbon Campaign:
 www.asciiribbon.org
 E-mail: g...@unixarea.de |  \ / - No HTML/RTF in E-mail
 WWW: http://www.unixarea.de/ |   X  - No proprietary attachments
 phone: +49-170-4527211   |  / \ - Respect for open standards
 ___
 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

___
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

Commit r250812 breaks buildworld

[Outback Dingo]

r250812 | markj | 2013-05-19 17:14:36 + (Sun, 19 May 2013) | 11 lines

Re-introduce another part of r249367. This commit fixes a register leak in
dt_cg_ptrsize() and generally cleans up some of the error handling around
register allocation.

This change corresponds to part of illumos-gate commit e5803b76927480:
  3025 register leak in D code generation

Reviewed by:pfg
Obtained from:  illumos
MFC after:  1 month


produces

/root/builder/FreeBSD/src/tmp/usr/lib/libdtrace.so: undefined reference to
`dt_cg_xlate_expand'
*** [dtrace] Error code 1
___
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

FreeBSD CURRENT LSI mps timeouts

[Outback Dingo]

Im getting a ton of times outs while trying to simply compile ports on
CURRENT, on a zpool
using multipath.

FreeBSD  10.0-CURRENT FreeBSD 10.0-CURRENT #3 r250692M: Thu May 16 04:17:59
UTC 2013 root@:/usr/obj/usr/src/sys/GENERIC  amd64

mps1: mpssas_alloc_tm freezing simq
mps1: timedout cm 0xff800111d680 allocated tm 0xff80010fb9c0
(da58:mps1:0:38:0): WRITE(6). CDB: 0a 00 79 a0 e8 00 length 118784 SMID 456
completed timedout cm 0xff800111d680 ccb 0xfe01c4101000 during
recovery ioc 8048 scsi 0 state c xfer 0
(noperiph:mps1:0:38:0): SMID 44 abort TaskMID 456 status 0x4a code 0x0
count 1
(noperiph:mps1:0:38:0): SMID 44 finished recovery after aborting TaskMID
456
mps1: mpssas_free_tm releasing simq
(da58:mps1:0:38:0): WRITE(6). CDB: 0a 00 79 a0 e8 00
(da58:mps1:0:38:0): CAM status: Command timeout
(da58:mps1:0:38:0): Retrying command
mps1: mpssas_scsiio_timeout checking sc 0xff80010e5000 cm
0xff800111a0b0
(da58:mps1:0:38:0): WRITE(6). CDB: 0a 00 78 a0 f0 00 length 122880 SMID 415
command timeout cm 0xff800111a0b0 ccb 0xfe01c40fd000
mps1: mpssas_alloc_tm freezing simq
mps1: timedout cm 0xff800111a0b0 allocated tm 0xff80010fbb10
(da58:mps1:0:38:0): WRITE(6). CDB: 0a 00 78 a0 f0 00 length 122880 SMID 415
completed timedout cm 0xff800111a0b0 ccb 0xfe01c40fd000 during
recovery ioc 8048 scsi 0 state c xfer 0
(noperiph:mps1:0:38:0): SMID 45 abort TaskMID 415 status 0x4a code 0x0
count 1
(noperiph:mps1:0:38:0): SMID 45 finished recovery after aborting TaskMID 415
mps1: mpssas_free_tm releasing simq
(da58:mps1:0:38:0): WRITE(6). CDB: 0a 00 78 a0 f0 00
(da58:mps1:0:38:0): CAM status: Command timeout
(da58:mps1:0:38:0): Error 5, Retries exhausted
GEOM_MULTIPATH: Error 5, da58 in SATA_LUN06 marked FAIL
GEOM_MULTIPATH: all paths in SATA_LUN06 were marked FAIL, restore da5
GEOM_MULTIPATH: da5 is now active path in SATA_LUN06
mps1: mpssas_scsiio_timeout checking sc 0xff80010e5000 cm
0xff800112c560
(da58:mps1:0:38:0): READ(10). CDB: 28 00 17 49 ec 10 00 00 10 00 length
8192 SMID 638 command timeout cm 0xff800112c560 ccb 0xfe01c4142800
mps1: mpssas_alloc_tm freezing simq
mps1: timedout cm 0xff800112c560 allocated tm 0xff80010fa760
(da58:mps1:0:38:0): READ(10). CDB: 28 00 17 49 ec 10 00 00 10 00 length
8192 SMID 638 completed timedout cm 0xff800112c560 ccb
0xfe01c4142800 during recovery ioc 8048 scsi 0 state c
x(noperiph:mps1:0:38:0): SMID 30 abort TaskMID 638 status 0x4a code 0x0
count 1
(noperiph:mps1:0:38:0): SMID 30 finished recovery after aborting TaskMID 638
mps1: mpssas_free_tm releasing simq
(da58:mps1:0:38:0): READ(10). CDB: 28 00 17 49 ec 10 00 00 10 00
(da58:mps1:0:38:0): CAM status: Command timeout
(da58:mps1:0:38:0): Error 5, Retries exhausted
mps1: mpssas_scsiio_timeout checking sc 0xff80010e5000 cm
0xff8001133250
(da58:mps1:0:38:0): READ(10). CDB: 28 00 17 49 ee 10 00 00 10 00 length
8192 SMID 721 command timeout cm 0xff8001133250 ccb 0xfe01c40fe000
mps1: mpssas_alloc_tm freezing simq
mps1: timedout cm 0xff8001133250 allocated tm 0xff80010fb9c0
(da58:mps1:0:38:0): READ(10). CDB: 28 00 17 49 ee 10 00 00 10 00 length
8192 SMID 721 completed timedout cm 0xff8001133250 ccb
0xfe01c40fe000 during recovery ioc 8048 scsi 0 state c
x(noperiph:mps1:0:38:0): SMID 44 abort TaskMID 721 status 0x4a code 0x0
count 1
(noperiph:mps1:0:38:0): SMID 44 finished recovery after aborting TaskMID 721
mps1: mpssas_free_tm releasing simq
(da58:mps1:0:38:0): READ(10). CDB: 28 00 17 49 ee 10 00 00 10 00
(da58:mps1:0:38:0): CAM status: Command timeout
(da58:mps1:0:38:0): Error 5, Retries exhausted
mps0: mpssas_scsiio_timeout checking sc 0xff8000dae000 cm
0xff8000eb6520
(da5:mps0:0:16:0): READ(10). CDB: 28 00 17 49 ec 10 00 00 10 00 length 8192
SMID 138 command timeout cm 0xff8000eb6520 ccb 0xfe01aceed000
mps0: mpssas_alloc_tm freezing simq
mps0: timedout cm 0xff8000eb6520 allocated tm 0xff8000eacb90
mps0: mpssas_scsiio_timeout checking sc 0xff8000dae000 cm
0xff8000ed7a00
(da5:mps0:0:16:0): READ(6). CDB: 08 00 02 10 10 00 length 8192 SMID 544
command timeout cm 0xff8000ed7a00 ccb 0xfe01c400e000
mps0: queued timedout cm 0xff8000ed7a00 for processing by tm
0xff8000eacb90
mps0: mpssas_scsiio_timeout checking sc 0xff8000dae000 cm
0xff8000eb1900
(da5:mps0:0:16:0): READ(10). CDB: 28 00 17 49 f1 ae 00 00 01 00 length 512
SMID 80 command timeout cm 0xff8000eb1900 ccb 0xfe01c40c3000
mps0: queued timedout cm 0xff8000eb1900 for processing by tm
0xff8000eacb90
mps0: mpssas_scsiio_timeout checking sc 0xff8000dae000 cm
0xff8000eb8740
(da5:mps0:0:16:0): READ(10). CDB: 28 00 17 49 ee 10 00 00 10 00 length 8192
SMID 164 command timeout cm 0xff8000eb8740 ccb 0xfe01acf11000
mps0: queued timedout cm 0xff8000eb8740 for processing by tm
0xff8000eacb90
(da5:mps0:0:16:0): READ(10). CDB: 28 00 17 49 ec 10 00 00 10 00 length 8192
SMID 138 completed timedout 

Re: FreeBSD Quarterly Status Report, January-March 2013

[Outback Dingo]

 __


 FreeNAS

URL: http://www.FreeNAS.org/

Contact: Alfred Perlstein alf...@freebsd.org
Contact: Josh Paetzel jpaet...@freebsd.org

FreeNAS 8.3.1-RELEASE-p2 will hit Sourceforge the second week of April,
and should end up as the last FreeNAS release based on FreeBSD 8.X It's
currently the only Free Open Source NAS product available with any form
of ZFS encryption (provided by GELI).

 Open tasks:

 1. The team is hard at work on getting a FreeBSD 9.X-based release of
FreeNAS ready. Currently there are several nightly snapshots
available.
 2. Add HAST to the webinterface.
 3. Migrate to NFSv4.
 4. Integrate foundation sponsored kernel iSCSI target.



Uhmm WHAT??? FreeNAS is not the only Free Open Source NAS product
available with any form
   of ZFS encryption (provided by GELI). NAS4Free has been doing it.
___
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

Infiniband OFED CLANG failing

[Outback Dingo]

svn info
Path: .
Working Copy Root Path: /usr/src
URL: http://svn.freebsd.org/base/head
Repository Root: http://svn.freebsd.org/base
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 250012
Node Kind: directory
Schedule: normal
Last Changed Author: eadler
Last Changed Rev: 250012
Last Changed Date: 2013-04-28 02:23:39 + (Sun, 28 Apr 2013)


cc -O2 -pipe
 -I/usr/src/contrib/ofed/usr.bin/opensm/../../include/infiniband
-I/usr/src/contrib/ofed/usr.bin/opensm/../../management/opensm/include/
-pthread -DVENDOR_RMPP_SUPPORT -DDUAL_SIDED_RMPP
-I/usr/src/contrib/ofed/usr.bin/opensm/../../include/infiniband
-I/usr/src/contrib/ofed/usr.bin/opensm/../../management/opensm/include/
-std=gnu99 -Qunused-arguments -fstack-protector -Wsystem-headers -Werror
-Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int
-Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality
-Wno-unused-function -Wno-conversion -Wno-switch -Wno-switch-enum
-Wno-knr-promoted-parameter -Wno-parentheses -c
/usr/src/contrib/ofed/usr.bin/opensm/../../management/opensm/opensm/osm_console.c
/usr/src/contrib/ofed/usr.bin/opensm/../../management/opensm/opensm/osm_console.c:70:1:
error: use of GNU old-style field designator extension
[-Werror,-Wgnu-designator]
on: 0, delay_s: 2, loop_function:NULL};
^~~
.on =
/usr/src/contrib/ofed/usr.bin/opensm/../../management/opensm/opensm/osm_console.c:70:8:
error: use of GNU old-style field designator extension
[-Werror,-Wgnu-designator]
on: 0, delay_s: 2, loop_function:NULL};
   ^~~~
   .delay_s =
/usr/src/contrib/ofed/usr.bin/opensm/../../management/opensm/opensm/osm_console.c:70:20:
error: use of GNU old-style field designator extension
[-Werror,-Wgnu-designator]
on: 0, delay_s: 2, loop_function:NULL};
   ^~
   .loop_function =
3 errors generated.
*** [osm_console.o] Error code 1

Stop in /usr/src/contrib/ofed/usr.bin/opensm.
___
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

Last commit to HEAD

[Outback Dingo]

Okay I must be loosing it since the change over to svn, and loosing cvsup

where can i find the last commit to HEAD ?

and is it correct to use

svn co http://svn.freebsd.org/base/head/ for 10.0-CURRENT srcs

making the last commit rev  249529

and as for 9.x i thought releng was what brought updates to the 9 tree

so why stable look like theres more current work, or is that going to
become
the life of 9.2 

trying to refresh my memory here!
___
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: Last commit to HEAD

[Outback Dingo]

On Mon, Apr 15, 2013 at 10:17 PM, David Wolfskill da...@catwhisker.orgwrote:

 On Mon, Apr 15, 2013 at 09:48:20PM -0400, Outback Dingo wrote:
  Okay I must be loosing it since the change over to svn, and loosing cvsup
 
  where can i find the last commit to HEAD ?

 A couple of Web-oriented sources of information:

 * http://docs.freebsd.org/mail/current/svn-src-head.html, which (as of
   this writing) refers to Apr 15 Andrey V. Elsukov   svn commit:
   r249528 - head/sys/netinet6.

 * http://svnweb.freebsd.org/base/head/, which (again, as of this
   writing) mentions Directory revision:249528 (of 249529).

  and is it correct to use
 
  svn co http://svn.freebsd.org/base/head/ for 10.0-CURRENT srcs

 Mostly, though we now have some official mirrors, as well; you might want
 to consider using one of those.  And per
 
 http://www.freebsd.org/doc/en/articles/committers-guide/article.html#subversion-primer
 ,
 https is recommended for anonymous checkout, e.g.:
 svn co https://svn0.us-west.FreeBSD.org/base/head /usr/src

  making the last commit rev  249529

 As of this writing, that was the last commit to the src repository.
 However, that commit was to the user part of the repo, not to head.
 (Ref. http://svnweb.freebsd.org/base/.)

  and as for 9.x i thought releng was what brought updates to the 9 tree

 releng/* is equivalent to the old RELENG_* CVS branches -- that is,
 RELEASE_* + patches/commits to address security advisories.

 This is *not* what you want for new features (such as support for a
 device that wasn't supported in RELEASE).

  so why stable look like theres more current work, or is that going to
  become
  the life of 9.2 

 That's exactly the same as it was under CVS: stable/* is a development
 branch, and that *does* get new features (ideally, all MFCed from
 head), and (as of this writing) stable/9 is where code is committed that
 will eventually become release/9.2.0, then releng/9.2.

  trying to refresh my memory here!

 I hope that helps a bit.

 Peace,
 david


Yupp Thanks for the refresher, im good now!


 --
 David H. Wolfskill  da...@catwhisker.org
 Taliban: Evil men with guns afraid of truth from a 14-year old girl.

 See http://www.catwhisker.org/~david/publickey.gpg for my public key.

___
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: FreeBSD 10 prognostication...

[Outback Dingo]

On Wed, May 16, 2012 at 5:44 PM, Thomas Mueller muelle...@insightbb.com wrote:
 Umm, it's about as factual as The Onion, except not as funny.  FreeBSD
 never had to jettison two thirds of its code base and start from
 scratch.  Apple is not involved in FreeBSD development.  No Mac OS X or
 Darwin version includes FreeBSD.  FreeBSD and Mac OS X will never
 merge.  FreeBSD was never acquired by WinDriver Systems or by anyone
 else, although a company named WindRiver Systems (makers of the embedded
 operating system VxWorks, not of Windows video drivers) did at one point
 acquire BSDI, which had previously acquired Walnut Creek CD-ROM, which
 was heavily involved in the early history of both FreeBSD and Slackware
 Linux.  The remains of Walnut Creek CD-ROM and BSDI are now known as
 FreeBSD Mall and iXsystems (of PC-BSD and FreeNAS fame).

 DES
 --
 Dag-Erling Smørgrav - d...@des.no

 I was a long-time subscriber to Slackware going back to Walnut Creek CDROM 
 days (Slackware 96 to the best of my memory, but  3.0).

 I believe FreeBSD Mall and Slackware (store.slackware.com) are connected.  I 
 had a difficult time terminating my Slackware subscription, customer service 
 ignoring me, thought I was going to have to have my credit card number 
 changed to jilt Slackware.  I noticed the similarity in subscription 
 arrangement between FreeBSD Mall and store.slackware.com.

 Slackware package system is geared to binary packages rather than building 
 from source, and there is no tracking of dependencies.  A package can be 
 installed even if dependencies are missing, and that even happened in 
 Slackware releases, as I found when I tried unsuccessfully to run gnumeric 
 many releases ago, got the message of missing library.  Seeing the better 
 package managers in FreeBSD (ports), NetBSD (pkgsrc, and ported to other 
 (quasi-)Unix OSes), and several Linux distributions is what made me not want 
 to go further with Slackware.  Multimedia files failing to play may have been 
 due to lack of proper package management.

 Tom

Guess his next claim will be that the kernel was forked from minix,
and userland came from QNX... some people are just plain
(biting my tongue)

 ___
 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
___
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

FYI clang fails to build ports argp-standalone

[Outback Dingo]

build on CURRENT Not sure if its appropriate here, but when trying to
get through a new glusterfs FYI clang fails to build ports
argp-standalone on CURRENT
___
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

FYI FreeBSD clang build fails on new import of sort

[Outback Dingo]

trying to rerun a clang build of FreeBSD CURRENT fails on new import of sort,

cat /etc/src.conf
WITH_CLANG_IS_CC=1
make world
-SNIP---
clang -O2 -pipe  -DSORT_THREADS -std=gnu99 -Qunused-arguments
-fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W
-Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes
-Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch
-Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline
-Wnested-externs -Wredundant-decls -Wold-style-definition
-Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -c
/usr/src/usr.bin/sort/coll.c
clang -O2 -pipe  -DSORT_THREADS -std=gnu99 -Qunused-arguments
-fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W
-Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes
-Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch
-Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline
-Wnested-externs -Wredundant-decls -Wold-style-definition
-Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -c
/usr/src/usr.bin/sort/file.c
/usr/src/usr.bin/sort/file.c:601:12: error: format string is not a
string literal (potentially insecure) [-Werror,-Wformat-security]
err(2, getstr(7));
   ^
/usr/src/usr.bin/sort/sort.h:52:20: note: expanded from macro 'getstr'
#define getstr(n)catgets(catalog, 1, n, nlsstr[n])
 ^
/usr/src/usr.bin/sort/file.c:942:11: error: format string is not a
string literal (potentially insecure) [-Werror,-Wformat-security]
err(2, getstr(8));
   ^
/usr/src/usr.bin/sort/sort.h:52:20: note: expanded from macro 'getstr'
#define getstr(n)catgets(catalog, 1, n, nlsstr[n])
 ^
/usr/src/usr.bin/sort/file.c:1279:10: error: format string is not a
string literal (potentially insecure) [-Werror,-Wformat-security]
err(2, getstr(9));
   ^
/usr/src/usr.bin/sort/sort.h:52:20: note: expanded from macro 'getstr'
#define getstr(n)catgets(catalog, 1, n, nlsstr[n])
 ^
/usr/src/usr.bin/sort/file.c:1295:12: error: format string is not a
string literal (potentially insecure) [-Werror,-Wformat-security]
errx(2, getstr(10));
^~
/usr/src/usr.bin/sort/sort.h:52:20: note: expanded from macro 'getstr'
#define getstr(n)catgets(catalog, 1, n, nlsstr[n])
 ^
4 errors generated.
*** [file.o] Error code 1

Stop in /usr/src/usr.bin/sort.
___
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

CURRENT as of 5/8/2012 make release

[Outback Dingo]

Ive noticed trying a make release on CURRENT that it appears to be
looping deeper and deeper,
does this appear normal to anyone else???

a 
usr/src/release/dist/usr/src/release/dist/usr/src/release/dist/usr/src/sys/dev/malo/if_malohal.h
a 
usr/src/release/dist/usr/src/release/dist/usr/src/release/dist/usr/src/sys/dev/malo/if_malo.h
a 
usr/src/release/dist/usr/src/release/dist/usr/src/release/dist/usr/src/sys/dev/twa/tw_osl_freebsd.c
a 
usr/src/release/dist/usr/src/release/dist/usr/src/release/dist/usr/src/sys/dev/twa/tw_cl_misc.c
a 
usr/src/release/dist/usr/src/release/dist/usr/src/release/dist/usr/src/sys/dev/twa/tw_osl_externs.h
a 
usr/src/release/dist/usr/src/release/dist/usr/src/release/dist/usr/src/sys/dev/twa/tw_cl_io.c
___
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: ctfmerge core dump

[Outback Dingo]

On Sat, May 5, 2012 at 8:26 PM, Outback Dingo outbackdi...@gmail.com wrote:
 On Sat, May 5, 2012 at 7:54 PM, David Xu listlog2...@gmail.com wrote:
 On 2012/5/6 5:08, b. f. wrote:

 On 5/5/12, Steve Willsswi...@freebsd.org  wrote:

 On 05/05/12 15:43, b. f. wrote:

 Steve Wills wrote:

 After updating from -CURRENT as of April 5 to one built today, I now
 get
 a core dump running ctfmerge on libc:

 ctfmerge -L VERSION -g -o libc.so.7 syscall.So fork.So..
 Bus error (core dumped)
 *** [libc.so.7] Error code 138

 Anyone else seeing this or have any idea how to avoid it?

 Yes, I'm also seeing such problems when attempting to build a r235052
 amd64 kernel on r235035 amd64. (This problem did not occur when
 building a r235035 amd64 world and kernel on r234854 amd64.)  ctfmerge
 succeeds for several kernel modules but fails with kgssapi.ko.debug,
 linux.ko.debug, or kernel.debug. I'm not yet sure which change has
 caused this, or how to avoid it.

 Thanks for the info. I took a look at the dump and see this:

 % sudo gdb /usr/bin/ctfmerge ctfmerge.core
 [GDB will not be able to debug user-mode threads: Undefined symbol
 td_thr_getxmmregs]
 GNU gdb 6.1.1 [FreeBSD]
 Copyright 2004 Free Software Foundation, Inc.
 GDB is free software, covered by the GNU General Public License, and you
 are
 welcome to change it and/or distribute copies of it under certain
 conditions.
 Type show copying to see the conditions.
 There is absolutely no warranty for GDB.  Type show warranty for
 details.
 This GDB was configured as amd64-marcel-freebsd...
 Core was generated by `ctfmerge'.
 Program terminated with signal 10, Bus error.
 Reading symbols from /lib/libctf.so.2...done.
 Loaded symbols for /lib/libctf.so.2
 Reading symbols from /usr/lib/libdwarf.so.3...done.
 Loaded symbols for /usr/lib/libdwarf.so.3
 Reading symbols from /usr/lib/libelf.so.1...done.
 Loaded symbols for /usr/lib/libelf.so.1
 Reading symbols from /lib/libz.so.6...done.
 Loaded symbols for /lib/libz.so.6
 Reading symbols from /lib/libthr.so.3...done.
 Loaded symbols for /lib/libthr.so.3
 Reading symbols from /lib/libc.so.7...done.
 Loaded symbols for /lib/libc.so.7
 Reading symbols from /libexec/ld-elf.so.1...done.
 Loaded symbols for /libexec/ld-elf.so.1
 #0  0x004064b0 in fifo_len (f=0x801c29070) at

 /usr/src/cddl/usr.bin/ctfmerge/../../../cddl/contrib/opensolaris/tools/ctf/cvt/fifo.c:128
 128             for (i = 0, fn = f-f_head; fn; fn = fn-fn_next, i++);
 (gdb) bt
 #0  0x004064b0 in fifo_len (f=0x801c29070) at

 /usr/src/cddl/usr.bin/ctfmerge/../../../cddl/contrib/opensolaris/tools/ctf/cvt/fifo.c:128
 #1  0x0040622c in worker_thread (wq=0x610ee0) at

 /usr/src/cddl/usr.bin/ctfmerge/../../../cddl/contrib/opensolaris/tools/ctf/cvt/ctfmerge.c:329
 #2  0x000801078da9 in thread_start (curthread=0x801c0f800) at
 /usr/src/lib/libthr/thread/thr_create.c:284
 #3  0x in ?? ()
 Cannot access memory at address 0x7f5fb000
 (gdb)

 After reverting the recent libthr changes in r234947, I am no longer
 encountering this problem.

 b.

 I have fixed it in r235068.

 hopefully itll fix kernel compilations also halting with signal 10

well seems to be okay now i did successfully get a kernel compiled





 ___
 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
___
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: ctfmerge core dump

[Outback Dingo]

On Sat, May 5, 2012 at 7:54 PM, David Xu listlog2...@gmail.com wrote:
 On 2012/5/6 5:08, b. f. wrote:

 On 5/5/12, Steve Willsswi...@freebsd.org  wrote:

 On 05/05/12 15:43, b. f. wrote:

 Steve Wills wrote:

 After updating from -CURRENT as of April 5 to one built today, I now
 get
 a core dump running ctfmerge on libc:

 ctfmerge -L VERSION -g -o libc.so.7 syscall.So fork.So..
 Bus error (core dumped)
 *** [libc.so.7] Error code 138

 Anyone else seeing this or have any idea how to avoid it?

 Yes, I'm also seeing such problems when attempting to build a r235052
 amd64 kernel on r235035 amd64. (This problem did not occur when
 building a r235035 amd64 world and kernel on r234854 amd64.)  ctfmerge
 succeeds for several kernel modules but fails with kgssapi.ko.debug,
 linux.ko.debug, or kernel.debug. I'm not yet sure which change has
 caused this, or how to avoid it.

 Thanks for the info. I took a look at the dump and see this:

 % sudo gdb /usr/bin/ctfmerge ctfmerge.core
 [GDB will not be able to debug user-mode threads: Undefined symbol
 td_thr_getxmmregs]
 GNU gdb 6.1.1 [FreeBSD]
 Copyright 2004 Free Software Foundation, Inc.
 GDB is free software, covered by the GNU General Public License, and you
 are
 welcome to change it and/or distribute copies of it under certain
 conditions.
 Type show copying to see the conditions.
 There is absolutely no warranty for GDB.  Type show warranty for
 details.
 This GDB was configured as amd64-marcel-freebsd...
 Core was generated by `ctfmerge'.
 Program terminated with signal 10, Bus error.
 Reading symbols from /lib/libctf.so.2...done.
 Loaded symbols for /lib/libctf.so.2
 Reading symbols from /usr/lib/libdwarf.so.3...done.
 Loaded symbols for /usr/lib/libdwarf.so.3
 Reading symbols from /usr/lib/libelf.so.1...done.
 Loaded symbols for /usr/lib/libelf.so.1
 Reading symbols from /lib/libz.so.6...done.
 Loaded symbols for /lib/libz.so.6
 Reading symbols from /lib/libthr.so.3...done.
 Loaded symbols for /lib/libthr.so.3
 Reading symbols from /lib/libc.so.7...done.
 Loaded symbols for /lib/libc.so.7
 Reading symbols from /libexec/ld-elf.so.1...done.
 Loaded symbols for /libexec/ld-elf.so.1
 #0  0x004064b0 in fifo_len (f=0x801c29070) at

 /usr/src/cddl/usr.bin/ctfmerge/../../../cddl/contrib/opensolaris/tools/ctf/cvt/fifo.c:128
 128             for (i = 0, fn = f-f_head; fn; fn = fn-fn_next, i++);
 (gdb) bt
 #0  0x004064b0 in fifo_len (f=0x801c29070) at

 /usr/src/cddl/usr.bin/ctfmerge/../../../cddl/contrib/opensolaris/tools/ctf/cvt/fifo.c:128
 #1  0x0040622c in worker_thread (wq=0x610ee0) at

 /usr/src/cddl/usr.bin/ctfmerge/../../../cddl/contrib/opensolaris/tools/ctf/cvt/ctfmerge.c:329
 #2  0x000801078da9 in thread_start (curthread=0x801c0f800) at
 /usr/src/lib/libthr/thread/thr_create.c:284
 #3  0x in ?? ()
 Cannot access memory at address 0x7f5fb000
 (gdb)

 After reverting the recent libthr changes in r234947, I am no longer
 encountering this problem.

 b.

 I have fixed it in r235068.

hopefully itll fix kernel compilations also halting with signal 10




 ___
 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
___
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

make kernel build fails

[Outback Dingo]

uname -a
FreeBSD  10.0-CURRENT FreeBSD 10.0-CURRENT #4: Fri Apr 20 11:58:36 UTC
2012 root@:/usr/obj/usr/src/sys/GENERIC  amd64

when trying a make kernel it errors out with

jemalloc: 
/usr/src/lib/libc/../../contrib/jemalloc/include/jemalloc/internal/arena.h:650:
Failed assertion: ((uintptr_t)ptr - ((uintptr_t)run +
(uintptr_t)bin_info-reg0_offset)) % bin_info-reg_interval == 0
*** [kernel.debug] Signal 6

or


uest.o scif_sas_task_request_state_handlers.o
scif_sas_task_request_states.o scif_sas_timer.o syscons_isa.o
vga_isa.o kern_clocksource.o link_elf_obj.o ia32_reg.o  ia32_signal.o
ia32_sigtramp.o ia32_syscall.o ia32_misc.o  freebsd32_ioctl.o
freebsd32_misc.o freebsd32_syscalls.o  freebsd32_sysent.o
ia32_sysvec.o imgact_elf32.o memmove.o  memset.o x86bios.o x86emu.o
OsdEnvironment.o acpi_apm.o madt.o  srat.o powernow.o est.o hwpstate.o
p4tcc.o atrtc.o clock.o isa.o  isa_dma.o nmi.o orm.o pci_bus.o qpi.o
busdma_machdep.o  dump_machdep.o intr_machdep.o io_apic.o legacy.o
local_apic.o  mca.o msi.o nexus.o tsc.o config.o env.o hints.o
vnode_if.o hack.So vers.o
*** [kernel.debug] Signal 10

Stop in /usr/obj/usr/src/sys/GENERIC.
*** [buildkernel] Error code 1

Stop in /usr/src.
*** [buildkernel] Error code 1

Stop in /usr/src.
___
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: VM images for FreeBSD

[Outback Dingo]

On Tue, Dec 20, 2011 at 6:52 PM, Alexander Yerenkow yeren...@gmail.com wrote:
 2011/12/21 Baptiste Daroussin b...@freebsd.org

 On Mon, Dec 19, 2011 at 10:31:51PM +0200, Alexander Yerenkow wrote:
  2011/12/19 Adrian Chadd adr...@freebsd.org
 
   Hi,
  
   Hm, so this lets us create a virtualbox image from what, a set of
   install tarballs? Or /usr/src build?
  
   I'm using cross-build and installation from sources dir (which is after
  that got svn-up'ed and all goes again).
  It shouldn't be complex to install to image from installation media
 and/or
  tarballs, but mine main idea is to have rolling image for making some
  automated tests.
  Currently I'm establishing building and providing images scheme, will do
  images with KMS+small graphical programs, with qt+unstable KDE, and
  probably with BHyVe. I think that's most useful setups currently. And
 maybe
  some image for benchmarking :)
 
 

 FYI I have been working on a ova file generator for the release, I manage
 to
 create ova images that do work on VirtualBox without problems, there are
 still
 some problems with vmware for now, the goal is to have a standard vm ready
 image
 (ova is standard) that would work on every system that do support it.



How about in XEN 4.1 a .vhd image would be awesome, especially boot from zfs


 This is good :)
 Do you have some scripts left?


 the image can be easily created from the release.


 Well, I'm trying to build custom images, like rolling from svn [+ patches]
 [+ packages] [+ some initial config].
 A way for building images from release I think can be taken from PC-BSD,
 they distribute upcoming 9 in VM formats too.




 regards,
 Bapt




 --
 Regards,
 Alexander Yerenkow
 ___
 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
___
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: High Network Perfomance

[Outback Dingo]

On Fri, Aug 5, 2011 at 7:31 PM, Luigi Rizzo ri...@iet.unipi.it wrote:

 On Fri, Aug 05, 2011 at 04:07:22PM -0300, Victor Detoni wrote:
  Hi Luigi,
 
  Thanks for reply. That's great solution :) Will be integrated with pf or
 is
  it?

 unfortunately i don't have the time to do it, but as said
 in the thread it should not be terribly difficult.


The demo image has a modified click is there a diff for click
itself.


 cheers
 luigi

  Thanks,
  Victor
 
  On Thu, Aug 4, 2011 at 9:27 PM, Luigi Rizzo ri...@iet.unipi.it wrote:
 
   On Thu, Aug 04, 2011 at 08:39:17PM -0300, Victor Detoni wrote:
Hi Guys,
   
I'm trying tunning a FreeBSD 8.2 to high perfomance network with pf.
 My
server configuration is:
   
Dell 1950
CPU: Intel(R) Xeon(R) CPU5130  @ 2.00GHz (1995.03-MHz
   K8-class
CPU)
4 x CPU
2 NIC (Broadcom NetXtreme II BCM5708 1000Base-T)
1 NIC (em0: Intel(R) PRO/1000 Network Connection 7.1.9)
   
I want to reach the high processing of packets per second and use pf
 as
synproxy and we still processor to handle others packets or flows.
   
I know that em drivers has MULTI_QUEUE implementation that helps high
performance for Intel drivers, but I couldn't see more information
 about.
   We
can reached 500k pps, but no more traffic was processed by this
   interface.
   
I've already enabled net.isr.direct but with Intel Drivers does not
 work
   and
the most processors are in System instead of Interrupts, why? When I
   enable
net.isr.direct the processing is balanced for on CPU in system and
   another
in interrupt and I reached 1M pps, but the total perfomance is down,
 the
load grow up too fast.
   
I've changed some parameter in sysctl for intel drivers, but it
 doesn't
   have
effect.
   
Someone know what I can do to reach more packets performance? I want
 to
   use
this FreeBSD as a router/firewall only.
  
   if you feel like doing a bit of coding yourself, you could try netmap
  
   http://info.iet.unipi.it/~luigi/netmap/
  
   cheers
   luigi
  
Thanks,
Victor
___
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
  
  ___
  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
 ___
 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

___
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: AR9132 CPU and AR9100 wireless support

[Outback Dingo]

Ive got some Ubiquiti mips devices id love to get FreeBSD on permanently
and a Netgear WNDR370, if only we could boot FreeBSD out of redboot
and flash it to them it would seriously ROCK,

On Tue, Sep 14, 2010 at 4:24 PM, Stefan Bethke s...@lassitu.de wrote:

 Am 14.09.2010 um 11:35 schrieb Adrian Chadd:

  Hi everyone,
 
  I've just pushed the initial support for the AR9100 wireless MAC into
  my git repository. This is for the WMAC on the AR9132 SoC.
 
  I've tested it in 11bg hostap mode on an AP83 derived box - the
  TP-Link TL-WR1043ND. The source tree has support for the CPU, ethernet
  (but not the switch PHY; it's enough to get data across it!); flash
  and the AR9100 WMAC.
 
  I've only tested open hostap mode on 11bg on a fixed channel.
 
  The GIT repo is at:
  http://www.gitorious.org/~adrianchadd/freebsd/adrianchadd-freebsd ;
  it's the work/atheros branch. You'll need to open the unit up,
  solder on some pins to get to the serial port and acquire a TTL -
  RS232 level converter. There's pictures and howto on the OpenWRT wiki:
  http://wiki.openwrt.org/toh/tp-link/tl-wr1043nd

 That sounds really nice!  Is there some guide on how to prepare an image?
  I'm quite familiar with OpenWrt (patching and building) and have a number
 of routers (WRT-160N, WR941NL, 500gP) with serial adapters attached, but
 from the messages on the mips list, it felt the bootstrapping process might
 be a bit dauting...


 Stefan

 --
 Stefan Bethke s...@lassitu.de   Fon +49 151 14070811



 ___
 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

___
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: [CFT]: ClangBSD is selfhosting, we need testers now

[Outback Dingo]

On Fri, Apr 16, 2010 at 12:08 PM, Roman Divacky rdiva...@freebsd.orgwrote:

 Hi,

 ClangBSD is a branch of FreeBSD that aims at integrating clang (
 clang.llvm.org)
 into FreeBSD, replacing GCC as a system compiler.

 Recently, we've achieved the state when clang can compile all of FreeBSD
 world
 on i386/amd64 platforms (including all the C++ apps we have and itself)
 and a bootable kernel. Thus we feel that the time has come to ask the
 FreeBSD
 community for wider testing on i386/amd64 (you sure can help with other
 platforms too :)).

 How to setup ClangBSD:

 The default configuration of ClangBSD requires clang installed so you can
 either install fresh llvm-devel port (portinstall devel/llvm-devel) or
 change
 CC to gcc and CXX to g++ in share/mk/sys.mk. I recommend the former.


svn co http://svn.freebsd.org/base/projects/clangbsd/ clangbsd

cd clangbsd  make buildworld

echo NO_WERROR=  /etc/make.conf
echo WERROR= /etc/make.conf

make DESTDIR=/clangbsd-chroot/ installworld


 now you have ClangBSD world installed and you can chroot into it. I don't
 recommend installing ClangBSD into real root as it is not tested enough.

 You can also start using clang compiled kernel - either build the kernel in
 the ClangBSD chroot (set NO_WERROR=yo and WERROR=yo in /etc/src.conf) or
 set
 CC to clang and build kernel the normal way.

 This information (and more) is also provided on:

http://wiki.freebsd.org/BuildingFreeBSDWithClang

 We kindly ask you to setup ClangBSD chroot and/or use clang compiled kernel
 and
 use it as you would normally use FreeBSD. Please report back

 Thank you,

   Roman Divacky on behalf of the ClangBSD team


can someone explain the benefit other then not relying on gcc now ?
performance ?
___
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