Re: help install new kernel on root-on-ZFS on 11-STABLE

2016-10-16 Thread Shane Ambler 

On 17/10/2016 09:01, Ben Woods wrote:

On Monday, 17 October 2016, Brandon J. Wandersee <
brandon.wander...@gmail.com> wrote:


Last I checked, the automated installer created a separate pool called
"bootpool," with a symlink from /boot to /bootpool.



I believe this is the case if the option for full disk encryption is
selected in the installer. This is required until the boot loader is
capable of recognising and accessing a geli encrypted disk.


For a "plain" install, /boot is nothing more than a directory created in
the root filesystem that will get created during installation. This is
the same for UFS and ZFS. I haven't checked during a build but I don't
think anything gets installed into /boot before installkernel so you
shouldn't expect it to exist before installkernel.

As mentioned you can create a separate pool for /boot so you can load
the kernel from a non-encrypted filesystem that can then mount the
remaining encrypted filesystems.

Another alternative setup is using boot environments that would create
filesystems as /sys/ROOT/ that are then mounted as the
root filesystem. Like a plain system the /boot folder would still be
created at the installkernel stage.


--
FreeBSD - the place to B...Storing Data

Shane Ambler

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

Re: sshd whines & dies after releng/10 "freebsd-update" run

2016-10-16 Thread David Wolfskill 
On Sun, Oct 16, 2016 at 05:32:57PM -0700, Kevin Oberman wrote:
> ...
> I believe sshd no longer supports ssh1 compatibility and it looks like you
> might still have an entry in /etc/sshd/sshd.config trying to touch v1.
> Check the file for any non-default entries. Compare your sshd_config with
> the default version in /usr/src/crypto/openssh.
> 

I used to explicitly disable v1 compatibility.

The machine that's a target of the "freebsd-update" attention has
no sources, so I copied sshd_config from it to /tmp on my laptop
(which does):

g1-252(11.0-S)[4] diff -u /S2/usr/src/crypto/openssh/sshd_config 
/tmp/sshd_config
--- /S2/usr/src/crypto/openssh/sshd_config  2016-03-13 04:13:31.32369 
-0700
+++ /tmp/sshd_config2016-06-05 06:37:55.0 -0700
@@ -1,5 +1,5 @@
-#  $OpenBSD: sshd_config,v 1.98 2016/02/17 05:29:04 djm Exp $
-#  $FreeBSD: stable/10/crypto/openssh/sshd_config 296781 2016-03-12 
23:53:20Z des $
+#  $OpenBSD: sshd_config,v 1.93 2014/01/10 05:59:19 djm Exp $
+#  $FreeBSD: stable/10/crypto/openssh/sshd_config 264692 2014-04-20 
12:46:18Z des $
 
 # This is the sshd server system-wide configuration file.  See
 # sshd_config(5) for more information.
@@ -120,7 +120,7 @@
 #MaxStartups 10:30:100
 #PermitTunnel no
 #ChrootDirectory none
-#VersionAddendum FreeBSD-20160310
+#VersionAddendum FreeBSD-20140420
 
 # no default banner path
 #Banner none
@@ -128,6 +128,18 @@
 # override default of no subsystems
 Subsystem  sftp/usr/libexec/sftp-server
 
+# Disable HPN tuning improvements.
+#HPNDisabled no
+
+# Buffer size for HPN to non-HPN connections.
+#HPNBufferSize 2048
+
+# TCP receive socket buffer polling for HPN.  Disable on non autotuning 
kernels.
+#TcpRcvBufPoll yes
+
+# Allow the use of the NONE cipher.
+#NoneEnabled no
+
 # Example of overriding settings on a per-user basis
 #Match User anoncvs
 #  X11Forwarding no
g1-252(11.0-S)[5] 


On the off-chance that the VersionAddendum might be confusing at
least one of us, I copied the stable/11 version of the file to the
appropiate place on the freebsd-update target machine, then rebooted.
Still no joy: other things work, but not ssh.

Thanks for the suggestion.  I'm a bit... perplexed.

[The machine in question would be the last machine I have still
running FreeBSD-10 -- I've migrated each of the others to stable/11.]

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
Those who would murder in the name of God or prophet are blasphemous cowards.

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


signature.asc
Description: PGP signature

I'm upset about FreeBSD

2016-10-16 Thread Rostislav Krasny 
Hi,

I've been using FreeBSD for many years. Not as my main operating
system, though. But anyway several bugs and patches were contributed
and somebody even added my name into the additional contributors list.
That's pleasing but today I tried to install the FreeBSD 11.0 and I'm
upset about this operating system.

First of all I faced an old problem that I reported here a year ago:
http://comments.gmane.org/gmane.os.freebsd.stable/96598
Completely new USB flash drive flashed by the
FreeBSD-11.0-RELEASE-i386-mini-memstick.img file kills every Windows
again. If I use the Rufus util to write the img file (using DD mode)
the Windows dies immediately after the flashing. If I use the
Win32DiskImager (suggested by the Handbook) it doesn't reinitialize
the USB storage and Windows dies only if I remove and put that USB
flash drive again or boot Windows when it is connected. Nothing was
done to fix this nasty bug for a year.

Ok, I've used the trick and rebooted Windows manually into the BIOS
setup right after I flashed the USB disk by the Win32DiskImager. The
FreeBSD 11.0 installation has started. I did it on my old computer
with MBR disk schema and installed the FreeBSD on the second MBR slice
(ada0s2). The installation finished. I changed the BIOS boot
configuration back, started to reboot and quickly removed the USB
flash drive (I didn't want to kill Windows again). But suddenly my
computer appeared unbootable. The new MBR code, that was rewritten
without any notation, can't find any OS. I tried to reboot several
times. Why bsdinstall doesn't ask about changing the MBR code? Maybe I
don't want to change it. Or maybe I want to install the BSD boot
manager version of the MBR code (boot0cfg -B).

Ok, I booted from the installation USB drive again and ran 'boot0cfg
-B ada0'. My computer is bootable again, but only for Windows. If I
press F1 the Windows boots properly. If I press F2 or F2 and Enter I
see only hash tags. If I reboot after that I see F2 already selected.
But if I wait (for F2 - FreeBSD) to the selected OS automatic boot I
see the hash tags again. WTF? I've never seen such bugs with boot0 in
any previous FreeBSD version.

I'm upset. Someone else at my place was throwing the FreeBSD 11.0
installation media far away right after the first problem. What is
going on? At least, how to finish the quest?

FreeBSD is losing popularity for Linux these days. I think such a bad
user experience of very basic use cases is one of the main reason for
this loss. Forgive me for saying that, I'm just upset.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: sshd whines & dies after releng/10 "freebsd-update" run

2016-10-16 Thread Kevin Oberman 
On Sun, Oct 16, 2016 at 10:45 AM, David Wolfskill 
wrote:

> On Sun, Oct 16, 2016 at 10:29:00AM -0700, Xin Li wrote:
> > ...
> > On 10/16/16 09:26, David Wolfskill wrote:
> > > And over the last year or so, it's worked pretty well:  I have the
> > > machine set up (as is usually my approach) to be able to boot from
> > > either of a couple of slices.  I use a "dump | restore" pipeline
> > > to copy the / and /usr file systems from the "active" slice to the
> > > "inactive" slice, adjust /etc/fstab on the inactive slice to reflect
> > > reality for when it's the boot slice, then (while the file systemms
> > > from the other slice are still mounted -- e.g., on /S2) run
> > > "freebsd-update -b /S2 fetch install", then reboot from the
> > > newly-updated slice.
> > >
> > > In the past, that's Just Worked.
> >
> > Your usage probably worked because you were lucky for a few times in the
> > past.  (details below)
> >
> > > This weekend, though, I was planning to update my other systems tfrom
> > > stable/10 to stable/11, so I figured I'd try freebsd-update on this
> > > machine first.
> > >
> > [...]
> > > root@sisboombah:/tmp # `which sshd` -d
> > > Undefined symbol "ssh_compat13" referenced from COPY relocation in
> /usr/sbin/sshd
> > >
> > > Any clues?
> >
> > I think this is not going to work (stable/10 -> releng/10.3) due to ABI
> > incompatibility in a downgrade.
>
> I seem to have failed to commnunicate clearly:  The machine in question
> does not, and has not, run "stable".  It runs releng.
>
> At the moment (on the "old" slice), it reports:
>
> sisboombah(10.3-RELEASE-p7)[1] uname -a
> FreeBSD sisboombah.catwhisker.org 10.3-RELEASE-p7 FreeBSD 10.3-RELEASE-p7
> #0: Thu Aug 11 18:38:15 UTC 2016 r...@amd64-builder.daemonology.net:
> /usr/obj/usr/src/sys/GENERIC  amd64
> sisboombah(10.3-RELEASE-p7)[2]
>
> > Basically, freebsd-update is treating your stable/10 as a 10.3-RELEASE
> > installation and will fetch only changes from 10.3-RELEASE to the latest
> > patchlevel.
>
> I can see that... if the machine were running stable.
>
> > Because of a SSH vulnerability that affects 10.3, freebsd-update would
> > patch libssh (shared library used by sshd and friends), however the
> > change does not affect the main binary.  This worked by replacing your
> > existing libssh with the one shipped by freebsd-update (effectively
> > downgraded the library) and that would break sshd.
>
> As a reality check:
> sisboombah(10.3-RELEASE-p7)[4] sudo mount /S2
> Password:
> sisboombah(10.3-RELEASE-p7)[5] sudo mount /S2/usr
> sisboombah(10.3-RELEASE-p7)[6] ls -lT {,/S2}/usr/lib/private/libssh.so.*
> -r--r--r--  1 root  wheel  634232 Oct 16 11:57:32 2016
> /S2/usr/lib/private/libssh.so.5
> -r--r--r--  1 root  wheel  569864 Jun  5 13:37:52 2016
> /usr/lib/private/libssh.so.5
> sisboombah(10.3-RELEASE-p7)[7] ls -lT {,/S2}/usr/sbin/ssh*
> -r-xr-xr-x  1 root  wheel  297736 Jun  5 13:38:35 2016 /S2/usr/sbin/sshd
> -r-xr-xr-x  1 root  wheel  297736 Jun  5 13:38:35 2016 /usr/sbin/sshd
> sisboombah(10.3-RELEASE-p7)[8]
>
> > I think upgrade -r 10.2-RELEASE (ideally, 11.0-RELEASE though as it
> > would eliminate the possibility of any potential incompatibility) would
> > work because that would result in a full rewrite of all files.
>
> Well, I had seen reports of folks having "issues" with attempts to
> use freebsd-update to get to releng/11 from systems that weren't
> as up-to-date as they might be; I was actually trying to avoid a
> problem :-}
>
> Peace,
> david
> --
> David H. Wolfskill  da...@catwhisker.org
> Those who would murder in the name of God or prophet are blasphemous
> cowards.
>
> See http://www.catwhisker.org/~david/publickey.gpg for my public key.
>

I believe sshd no longer supports ssh1 compatibility and it looks like you
might still have an entry in /etc/sshd/sshd.config trying to touch v1.
Check the file for any non-default entries. Compare your sshd_config with
the default version in /usr/src/crypto/openssh.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Your recovery email address changed

2016-10-16 Thread Google via freebsd-stable 

Your recovery email address changed



Hi VNS娱乐城876502.com注册送88元,网上最火爆的游戏平台,超好赢钱游戏,
The recovery email for your Google Account maxhill...@gmail.com was
recently changed.

*Don't recognize this activity?*
Review your recently used devices

now.

Best,
The Google Accounts team



This email can't receive replies. For more information, visit the Google
Accounts Help Center .



You received this mandatory email service announcement to update you about
important changes to your Google product or account.
© 2016 Google Inc., 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: help install new kernel on root-on-ZFS on 11-STABLE

2016-10-16 Thread Aryeh Friedman 
The bug report pointed to says the same thing but the new issue is it is
not documented in the Handbook and/or not mounted by default (for someone
who is brand new to ZFS it is very counter intutive to see a symlink
pointing off into space)

On Sun, Oct 16, 2016 at 6:21 PM, Brandon J. Wandersee <
brandon.wander...@gmail.com> wrote:

>
> Aryeh Friedman writes:
>
> > I just installed 11-STABLE on a brand new system and can't find a valid
> > /boot in which to do "make installkernel" to.  I am used to how to do
> make
> > world on UFS.   How do I do it on root-on-ZFS?
>
> Last I checked, the automated installer created a separate pool called
> "bootpool," with a symlink from /boot to /bootpool. Check to see
> "bootpool" exists; if so, it's not mounted, which is another problem
> that needs addressing. If it doesn't exist, then something has changed
> and I have no idea what to do.
>
> --
> ::  Brandon J. Wandersee
> ::  brandon.wander...@gmail.com
> ::  --
> ::  'The best design is as little design as possible.'
> ::  --- Dieter Rams --
>



-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: help install new kernel on root-on-ZFS on 11-STABLE

2016-10-16 Thread Ben Woods 
On Monday, 17 October 2016, Brandon J. Wandersee <
brandon.wander...@gmail.com> wrote:
>
> Last I checked, the automated installer created a separate pool called
> "bootpool," with a symlink from /boot to /bootpool.
>

I believe this is the case if the option for full disk encryption is
selected in the installer. This is required until the boot loader is
capable of recognising and accessing a geli encrypted disk.

Regards,
Ben


-- 

--
From: Benjamin Woods
woods...@gmail.com
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: help install new kernel on root-on-ZFS on 11-STABLE

2016-10-16 Thread Brandon J . Wandersee 

Aryeh Friedman writes:

> I just installed 11-STABLE on a brand new system and can't find a valid
> /boot in which to do "make installkernel" to.  I am used to how to do make
> world on UFS.   How do I do it on root-on-ZFS?

Last I checked, the automated installer created a separate pool called
"bootpool," with a symlink from /boot to /bootpool. Check to see
"bootpool" exists; if so, it's not mounted, which is another problem
that needs addressing. If it doesn't exist, then something has changed
and I have no idea what to do.

-- 
::  Brandon J. Wandersee
::  brandon.wander...@gmail.com
::  --
::  'The best design is as little design as possible.'
::  --- Dieter Rams --
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Clandestine USB SD card slot

2016-10-16 Thread George Mitchell 
On 10/16/16 14:16, Warner Losh wrote:
> On Sun, Oct 16, 2016 at 12:08 PM, Warren Block  wrote:
>> On Sun, 16 Oct 2016, George Mitchell wrote:
>>
 So not only is it (apparently) recognized, but the sdhci_pci driver
 attached to it!  But inserting or removing a card shows no activity.
 What's my next step?  -- George
>>
>>
>> Is a device created for the empty reader?  It's worth trying to force a
>> retaste of that device with 'true > /dev/daX' after the card is inserted.
> 
> Don't look for da anything. Look for mmcsd something. The sdhci_pci
> driver provides disks that are mmcsdX. Looks like card change
> interrupts aren't happening, or there's something else making the
> driver unhappy with the SDHCI controller though...
> 
> Warner
> [...]

No /dev/mm*; no log output on card insertion/removal even with
sysctl hw.sdhci.debug=1.  Other sysctl info:

sysctl -a | grep sdhci
device  sdhci
hw.sdhci.enable_msi: 1
hw.sdhci.debug: 1
dev.sdhci_pci.0.%parent: pci0
dev.sdhci_pci.0.%pnpinfo: vendor=0x1022 device=0x7813 subvendor=0x1025
subdevice=0x0865 class=0x080501
dev.sdhci_pci.0.%location: pci0:0:20:7
dev.sdhci_pci.0.%driver: sdhci_pci
dev.sdhci_pci.0.%desc: Generic SD HCI
dev.sdhci_pci.%parent:

-- George

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

help install new kernel on root-on-ZFS on 11-STABLE

2016-10-16 Thread Aryeh Friedman 
I just installed 11-STABLE on a brand new system and can't find a valid
/boot in which to do "make installkernel" to.  I am used to how to do make
world on UFS.   How do I do it on root-on-ZFS?

-- 
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: zfs/raidz: seems like I'm failing with math

2016-10-16 Thread Eugene M. Zheganin 

Hi.

On 16.10.2016 23:42, Gary Palmer wrote:


You're confusing disk manufacturer gigabytes with real (power of two)
gigabytes.  The below turns 960 197 124 096 into real gigabytes

Yup, I thought that smartctl is better than that and already displayed 
the size with base 1024. :)


Thanks.
Eugene.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: zfs/raidz: seems like I'm failing with math

2016-10-16 Thread Eugene M. Zheganin 

Hi.

On 16.10.2016 22:06, Alan Somers wrote:

It's raw size, but the discrepancy is between 1000 and 1024.  Smartctl
is reporting base 10 size, but zpool is reporting base 1024..
960197124096.0*6/1024**4 = 5.24 TB, which is pretty close to what
zpool says.
Thanks ! It does explain it. But then again, on a pool that has been 
just created, I check the properties of the root dataset (I'm posting 
all the properties, just to display there's no child datasets or data on 
the pool):


===Cut===
# zfs get all gamestop
NAME  PROPERTY  VALUE  SOURCE
gamestop  type  filesystem -
gamestop  creation  sun oct 16 19:02 2016  -
gamestop  used  403K   -
gamestop  available 4,04T  -
gamestop  referenced153K   -
gamestop  compressratio 1.00x  -
gamestop  mounted   yes-
gamestop  quota none   default
gamestop  reservation   none   default
gamestop  recordsize128K   default
gamestop  mountpoint/gamestop  default
gamestop  sharenfs  offdefault
gamestop  checksum  on default
gamestop  compression   offdefault
gamestop  atime on default
gamestop  devices   on default
gamestop  exec  on default
gamestop  setuidon default
gamestop  readonly  offdefault
gamestop  jailedoffdefault
gamestop  snapdir   hidden default
gamestop  aclmode   discarddefault
gamestop  aclinheritrestricted default
gamestop  canmount  on default
gamestop  xattr offtemporary
gamestop  copies1  default
gamestop  version   5  -
gamestop  utf8only  off-
gamestop  normalization none   -
gamestop  casesensitivity   sensitive  -
gamestop  vscan offdefault
gamestop  nbmandoffdefault
gamestop  sharesmb  offdefault
gamestop  refquota  none   default
gamestop  refreservationnone   default
gamestop  primarycache  alldefault
gamestop  secondarycachealldefault
gamestop  usedbysnapshots   0  -
gamestop  usedbydataset 153K   -
gamestop  usedbychildren249K   -
gamestop  usedbyrefreservation  0  -
gamestop  logbias   latencydefault
gamestop  dedup offdefault
gamestop  mlslabel -
gamestop  sync  standard   default
gamestop  refcompressratio  1.00x  -
gamestop  written   153K   -
gamestop  logicalused   26,5K  -
gamestop  logicalreferenced 9,50K  -
gamestop  volmode   defaultdefault
gamestop  filesystem_limit  none   default
gamestop  snapshot_limitnone   default
gamestop  filesystem_count  none   default
gamestop  snapshot_countnone   default
gamestop  redundant_metadataalldefault
===Cut===

Only 4.03T is available. Looks like it's the actual size, since it's zfs 
and not zpool. But 960197124096 bytes * 5 / 1024^4 gives me 4.366 Tb, 
and not the 4.03 T. Where did about 300 gigs go ? I'm really trying to 
understand, not to catch some questionable logic or find errors.


Thanks.
Eugene.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: zfs/raidz: seems like I'm failing with math

2016-10-16 Thread Gary Palmer 
On Sun, Oct 16, 2016 at 09:56:10PM +0500, Eugene M. Zheganin wrote:
> Hi.
> 
> FreeBSD 11.0-RC1 r303979, zfs raidz1:
> 
> ===Cut===
> 
> # zpool status gamestop
>pool: gamestop
>   state: ONLINE
>scan: none requested
> config:
> 
>  NAMESTATE READ WRITE CKSUM
>  gamestopONLINE   0 0 0
>raidz1-0  ONLINE   0 0 0
>  da0 ONLINE   0 0 0
>  da1 ONLINE   0 0 0
>  da2 ONLINE   0 0 0
>  da3 ONLINE   0 0 0
>  da4 ONLINE   0 0 0
>  da5 ONLINE   0 0 0
> 
> ===Cut===
> 
> 6 disks 960 Gbs each:
> 
> ===Cut===
> 
> # smartctl -a /dev/da0
> smartctl 6.5 2016-05-07 r4318 [FreeBSD 11.0-RC1 amd64] (local build)
> Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
> 
> === START OF INFORMATION SECTION ===
> Model Family: Samsung based SSDs
> Device Model: SAMSUNG MZ7KM960HAHP-5
> Serial Number:S2HTNX0H507466
> LU WWN Device Id: 5 002538 c402bdac1
> Firmware Version: GXM1003Q
> User Capacity:960 197 124 096 bytes [960 GB]

You're confusing disk manufacturer gigabytes with real (power of two)
gigabytes.  The below turns 960 197 124 096 into real gigabytes

% bc
scale = 4
960197124096 / 1024 / 1024 / 1024
894.2532


> Sector Size:  512 bytes logical/physical
> 
> [...]
> 
> ===Cut===
> 
> But:
> 
> ===Cut===
> 
> # zpool list gamestop
> NAME   SIZE  ALLOC   FREE  EXPANDSZ   FRAGCAP  DEDUP HEALTH  ALTROOT
> gamestop  5,22T  4,38T   861G -24%83%  1.00x ONLINE  -
> 
> ===Cut===
> 
> Why 5.22T ? If zpool is displaying raw size, it should be 960 x 6 = 5760 
> Gb = 5.65 T. If it's displaying the actual data, then it should be 960 x 
> 5 = 4800 Gb = 4.68 T. 5.22 T is neither of these. I'm stuck, please 
> explain. :)

Take 6 disks, size calculated above, and turn that into power of two TB:

894.2532 * 6 / 1024
5.2397

Close enough to 5.22, especially after ZFS has some overhead for it's
own data structures

Regards,

Gary
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Building FreeBSD 11.0-stable on FreeBSD 10.1-stable fails

2016-10-16 Thread Warner Losh 
On Sun, Oct 16, 2016 at 12:18 PM, Dimitry Andric  wrote:
> On 16 Oct 2016, at 17:22, Warner Losh  wrote:
>>
>> On Sun, Oct 16, 2016 at 5:34 AM, Dimitry Andric  wrote:
>>> On 16 Oct 2016, at 12:20, Torfinn Ingolfsen  
>>> wrote:
 I am trying to build FreeBSD 11.0-stable on a machine which runs:
 tingo@kg-v7$ uname -a
 FreeBSD kg-v7.kg4.no 10.1-STABLE FreeBSD 10.1-STABLE #0 r278322: Fri Feb  
 6 21:36:01 CET 2015
 r...@kg-v7.kg4.no:/usr/obj/usr/src/sys/GENERIC  amd64

 I have emptied /usr/src and /usr/obj and fetched the latest stable/11 via 
 subversion:
 tingo@kg-v7$ egrep "^BRANCH|^REVISION" /usr/src/sys/conf/newvers.sh
 REVISION="11.0"
 BRANCH="STABLE"

 But building it (per the procedure in the handbook) fails at the 
 buildworld stage. Both 'make -j5 buildworld' and 'make buildworld' fails, 
 like this:

 c++: error: unable to execute command: Segmentation fault (core dumped)
> ...
>>> Please make sure your stable/10 is at least r286033.
>>
>> What's the issue this fixes?
>
> It fixes a possible crash in clang 3.4, which can occur if newer
> versions of llvm are compiled.  Unfortunately this fix only went in
> after 10.3-RELEASE.
>
>
>> Right now we have safeties in place in
>> buildworld that indicate we 'support' back to 9 sometime. If that's
>> not really the case, we need to fix something (either fix so we don't
>> need this specific revision, or fix the Makefile to indicate we don't
>> support back that far).
>
> The fix was also merged to stable/9 in r286035.  As far as I know, we
> have always required people to upgrade to the latest revision in stable
> branches before attempting to hop to the next stable branch (or head).

No. that's not always been the case. It hasn't been the case since
Ruslan Ermilov's efforts to support from the 4.x branch point upgrades
to 5, 6 and 7. We've well supported upgrading from older versions for
15 years or so. It's been documented in Makefile.inc1 for all that
time, and the documented version has generally worked for much of that
time. There was a policy that pre-dated this stating only tip of
stable to next stable, but that policy has been found to be needlessly
restrictive so people like Juniper have made sure that older -> newer
builds have been working for maybe the last 5-8 years. It causes them
big logistical issues to upgrade their build servers too often due to
dependencies that most people don't have on non-public third-party
code that doesn't gracefully upgrade. So not since the 3.x -> 4.x days
has there been a requirement to upgrade to tip of stable of X-1 before
building X. It's usually X-2 or X-3 and generally all the release
points on the branch, or at least most of the branch.

If we can't do it now because of old bugs in releases that we can't
work around (which this sounds like), we'll need to fix that in the
versions we allow to be correct. Generally, we've been able to work
around issues, but this one sounds to be almost impossible w/o host
modification.

In addition to fixing the version in Makefile,inc1, we'll need to
document this change from past expectations in the release notes
(retroactively), in UPDATING and in the handbook.

Suffice to say, this is a big problem that sadly we can only fix with
documentation.

Warner
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

stable/11: lock contention on zone_fetch_slab

2016-10-16 Thread Slawa Olhovchenkov 
@ CPU_CLK_UNHALTED_CORE [271718 samples]

22.48%  [61081]lock_delay @ /boot/kernel/kernel
 99.72%  [60908] __mtx_lock_sleep
  67.69%  [41230]  zone_fetch_slab
   100.0%  [41230]   zone_import
100.0%  [41230]zone_alloc_item
 99.99%  [41226] uma_zalloc_arg
  74.55%  [30732]  m_getm2
   100.0%  [30732]   m_uiotombuf
100.0%  [30732]sosend_generic
 99.93%  [30711] soo_write
  100.0%  [30711]  dofilewrite
   100.0%  [30711]   kern_writev
99.37%  [30518]sys_writev
 100.0%  [30518] amd64_syscall
00.63%  [193]  sys_write
 100.0%  [193]   amd64_syscall
 00.07%  [21]kern_sendit
  100.0%  [21] sendit
   100.0%  [21]  sys_sendto
100.0%  [21]   amd64_syscall
  20.84%  [8590]   m_copym
   100.0%  [8590]tcp_output
96.18%  [8262] tcp_usr_send
 100.0%  [8262]  sosend_generic
  99.67%  [8235]   soo_write
   100.0%  [8235]dofilewrite
100.0%  [8235] kern_writev
 99.38%  [8184]  sys_writev
  100.0%  [8184]   amd64_syscall
 00.62%  [51]sys_write
  100.0%  [51] amd64_syscall
  00.33%  [27] kern_sendit
   100.0%  [27]  sendit
100.0%  [27]   sys_sendto
 100.0%  [27]amd64_syscall
03.82%  [328]  tcp_timer_rexmt
 100.0%  [328]   softclock_call_cc
  100.0%  [328]softclock
   100.0%  [328] intr_event_execute_handlers
100.0%  [328]  ithread_loop
 100.0%  [328]   fork_exit
  04.55%  [1874]   tcp_output
   75.72%  [1419]tcp_usr_send
100.0%  [1419] sosend_generic
 98.38%  [1396]  soo_write
  100.0%  [1396]   dofilewrite
   100.0%  [1396]kern_writev
87.11%  [1216] sys_writev
 100.0%  [1216]  amd64_syscall
12.89%  [180]  sys_write
 100.0%  [180]   amd64_syscall
 01.62%  [23]kern_sendit
  100.0%  [23] sendit
   100.0%  [23]  sys_sendto
100.0%  [23]   amd64_syscall
   13.07%  [245] tcp_timer_rexmt
100.0%  [245]  softclock_call_cc
 100.0%  [245]   softclock
  100.0%  [245]intr_event_execute_handlers
   100.0%  [245] ithread_loop
100.0%  [245]  fork_exit
   06.46%  [121] tcp_timer_delack
100.0%  [121]  softclock_call_cc
 100.0%  [121]   softclock
  100.0%  [121]intr_event_execute_handlers
   100.0%  [121] ithread_loop
100.0%  [121]  fork_exit
   02.99%  [56]  tcp_do_segment
100.0%  [56]   tcp_input
 100.0%  [56]ip_input
  100.0%  [56] swi_net
   100.0%  [56]  intr_event_execute_handlers
100.0%  [56]   ithread_loop
 100.0%  [56]fork_exit
   01.55%  [29]  tcp_usr_disconnect
100.0%  [29]   soclose
 100.0%  [29]_fdrop
  100.0%  [29] closef
   100.0%  [29]  closefp
100.0%  [29]   amd64_syscall
   00.11%  [2]   tcp_timer_persist
100.0%  [2]softclock_call_cc
 100.0%  [2] softclock
  100.0%  [2]  intr_event_execute_handlers
   100.0%  [2]   ithread_loop
100.0%  [2]fork_exit
   00.11%  [2]   tcp_drop
100.0%  [2]tcp_timer_rexmt
 100.0%  [2] softclock_call_cc
  100.0%  [2]  softclock
   100.0%  [2]   intr_event_execute_handlers
100.0%  [2]ithread_loop
 100.0%  [2] fork_exit
  00.07%  [28] syncache_respond
   100.0%  [28]  syncache_timer
100.0%  [28]

Re: Building FreeBSD 11.0-stable on FreeBSD 10.1-stable fails

2016-10-16 Thread Dimitry Andric 
On 16 Oct 2016, at 17:22, Warner Losh  wrote:
> 
> On Sun, Oct 16, 2016 at 5:34 AM, Dimitry Andric  wrote:
>> On 16 Oct 2016, at 12:20, Torfinn Ingolfsen  
>> wrote:
>>> I am trying to build FreeBSD 11.0-stable on a machine which runs:
>>> tingo@kg-v7$ uname -a
>>> FreeBSD kg-v7.kg4.no 10.1-STABLE FreeBSD 10.1-STABLE #0 r278322: Fri Feb  6 
>>> 21:36:01 CET 2015
>>> r...@kg-v7.kg4.no:/usr/obj/usr/src/sys/GENERIC  amd64
>>> 
>>> I have emptied /usr/src and /usr/obj and fetched the latest stable/11 via 
>>> subversion:
>>> tingo@kg-v7$ egrep "^BRANCH|^REVISION" /usr/src/sys/conf/newvers.sh
>>> REVISION="11.0"
>>> BRANCH="STABLE"
>>> 
>>> But building it (per the procedure in the handbook) fails at the buildworld 
>>> stage. Both 'make -j5 buildworld' and 'make buildworld' fails, like this:
>>> 
>>> c++: error: unable to execute command: Segmentation fault (core dumped)
...
>> Please make sure your stable/10 is at least r286033.
> 
> What's the issue this fixes?

It fixes a possible crash in clang 3.4, which can occur if newer
versions of llvm are compiled.  Unfortunately this fix only went in
after 10.3-RELEASE.


> Right now we have safeties in place in
> buildworld that indicate we 'support' back to 9 sometime. If that's
> not really the case, we need to fix something (either fix so we don't
> need this specific revision, or fix the Makefile to indicate we don't
> support back that far).

The fix was also merged to stable/9 in r286035.  As far as I know, we
have always required people to upgrade to the latest revision in stable
branches before attempting to hop to the next stable branch (or head).

-Dimitry



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Clandestine USB SD card slot

2016-10-16 Thread Warner Losh 
On Sun, Oct 16, 2016 at 12:08 PM, Warren Block  wrote:
> On Sun, 16 Oct 2016, George Mitchell wrote:
>
>>> So not only is it (apparently) recognized, but the sdhci_pci driver
>>> attached to it!  But inserting or removing a card shows no activity.
>>> What's my next step?  -- George
>
>
> Is a device created for the empty reader?  It's worth trying to force a
> retaste of that device with 'true > /dev/daX' after the card is inserted.

Don't look for da anything. Look for mmcsd something. The sdhci_pci
driver provides disks that are mmcsdX. Looks like card change
interrupts aren't happening, or there's something else making the
driver unhappy with the SDHCI controller though...

Warner
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Clandestine USB SD card slot

2016-10-16 Thread Warren Block 

On Sun, 16 Oct 2016, George Mitchell wrote:


So not only is it (apparently) recognized, but the sdhci_pci driver
attached to it!  But inserting or removing a card shows no activity.
What's my next step?  -- George


Is a device created for the empty reader?  It's worth trying to force a 
retaste of that device with 'true > /dev/daX' after the card is 
inserted.

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

Re: sshd whines & dies after releng/10 "freebsd-update" run

2016-10-16 Thread David Wolfskill 
On Sun, Oct 16, 2016 at 10:29:00AM -0700, Xin Li wrote:
> ... 
> On 10/16/16 09:26, David Wolfskill wrote:
> > And over the last year or so, it's worked pretty well:  I have the
> > machine set up (as is usually my approach) to be able to boot from
> > either of a couple of slices.  I use a "dump | restore" pipeline
> > to copy the / and /usr file systems from the "active" slice to the
> > "inactive" slice, adjust /etc/fstab on the inactive slice to reflect
> > reality for when it's the boot slice, then (while the file systemms
> > from the other slice are still mounted -- e.g., on /S2) run
> > "freebsd-update -b /S2 fetch install", then reboot from the
> > newly-updated slice.
> > 
> > In the past, that's Just Worked.
> 
> Your usage probably worked because you were lucky for a few times in the
> past.  (details below)
> 
> > This weekend, though, I was planning to update my other systems tfrom
> > stable/10 to stable/11, so I figured I'd try freebsd-update on this
> > machine first.
> > 
> [...]
> > root@sisboombah:/tmp # `which sshd` -d
> > Undefined symbol "ssh_compat13" referenced from COPY relocation in 
> > /usr/sbin/sshd
> > 
> > Any clues?
> 
> I think this is not going to work (stable/10 -> releng/10.3) due to ABI
> incompatibility in a downgrade.

I seem to have failed to commnunicate clearly:  The machine in question
does not, and has not, run "stable".  It runs releng.

At the moment (on the "old" slice), it reports:

sisboombah(10.3-RELEASE-p7)[1] uname -a
FreeBSD sisboombah.catwhisker.org 10.3-RELEASE-p7 FreeBSD 10.3-RELEASE-p7 #0: 
Thu Aug 11 18:38:15 UTC 2016 
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64
sisboombah(10.3-RELEASE-p7)[2] 

> Basically, freebsd-update is treating your stable/10 as a 10.3-RELEASE
> installation and will fetch only changes from 10.3-RELEASE to the latest
> patchlevel.

I can see that... if the machine were running stable.

> Because of a SSH vulnerability that affects 10.3, freebsd-update would
> patch libssh (shared library used by sshd and friends), however the
> change does not affect the main binary.  This worked by replacing your
> existing libssh with the one shipped by freebsd-update (effectively
> downgraded the library) and that would break sshd.

As a reality check:
sisboombah(10.3-RELEASE-p7)[4] sudo mount /S2
Password:
sisboombah(10.3-RELEASE-p7)[5] sudo mount /S2/usr
sisboombah(10.3-RELEASE-p7)[6] ls -lT {,/S2}/usr/lib/private/libssh.so.*
-r--r--r--  1 root  wheel  634232 Oct 16 11:57:32 2016 
/S2/usr/lib/private/libssh.so.5
-r--r--r--  1 root  wheel  569864 Jun  5 13:37:52 2016 
/usr/lib/private/libssh.so.5
sisboombah(10.3-RELEASE-p7)[7] ls -lT {,/S2}/usr/sbin/ssh*
-r-xr-xr-x  1 root  wheel  297736 Jun  5 13:38:35 2016 /S2/usr/sbin/sshd
-r-xr-xr-x  1 root  wheel  297736 Jun  5 13:38:35 2016 /usr/sbin/sshd
sisboombah(10.3-RELEASE-p7)[8] 

> I think upgrade -r 10.2-RELEASE (ideally, 11.0-RELEASE though as it
> would eliminate the possibility of any potential incompatibility) would
> work because that would result in a full rewrite of all files.

Well, I had seen reports of folks having "issues" with attempts to
use freebsd-update to get to releng/11 from systems that weren't
as up-to-date as they might be; I was actually trying to avoid a
problem :-}

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
Those who would murder in the name of God or prophet are blasphemous cowards.

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


signature.asc
Description: PGP signature

Re: sshd whines & dies after releng/10 "freebsd-update" run

2016-10-16 Thread Xin Li 

On 10/16/16 09:26, David Wolfskill wrote:
> And over the last year or so, it's worked pretty well:  I have the
> machine set up (as is usually my approach) to be able to boot from
> either of a couple of slices.  I use a "dump | restore" pipeline
> to copy the / and /usr file systems from the "active" slice to the
> "inactive" slice, adjust /etc/fstab on the inactive slice to reflect
> reality for when it's the boot slice, then (while the file systemms
> from the other slice are still mounted -- e.g., on /S2) run
> "freebsd-update -b /S2 fetch install", then reboot from the
> newly-updated slice.
> 
> In the past, that's Just Worked.

Your usage probably worked because you were lucky for a few times in the
past.  (details below)

> This weekend, though, I was planning to update my other systems tfrom
> stable/10 to stable/11, so I figured I'd try freebsd-update on this
> machine first.
> 
[...]
> root@sisboombah:/tmp # `which sshd` -d
> Undefined symbol "ssh_compat13" referenced from COPY relocation in 
> /usr/sbin/sshd
> 
> Any clues?

I think this is not going to work (stable/10 -> releng/10.3) due to ABI
incompatibility in a downgrade.

Basically, freebsd-update is treating your stable/10 as a 10.3-RELEASE
installation and will fetch only changes from 10.3-RELEASE to the latest
patchlevel.

Because of a SSH vulnerability that affects 10.3, freebsd-update would
patch libssh (shared library used by sshd and friends), however the
change does not affect the main binary.  This worked by replacing your
existing libssh with the one shipped by freebsd-update (effectively
downgraded the library) and that would break sshd.

I think upgrade -r 10.2-RELEASE (ideally, 11.0-RELEASE though as it
would eliminate the possibility of any potential incompatibility) would
work because that would result in a full rewrite of all files.

Cheers,



signature.asc
Description: OpenPGP digital signature

Re: zfs/raidz: seems like I'm failing with math

2016-10-16 Thread Alan Somers 
On Sun, Oct 16, 2016 at 10:56 AM, Eugene M. Zheganin  wrote:
> Hi.
>
> FreeBSD 11.0-RC1 r303979, zfs raidz1:
>
> ===Cut===
>
> # zpool status gamestop
>   pool: gamestop
>  state: ONLINE
>   scan: none requested
> config:
>
> NAMESTATE READ WRITE CKSUM
> gamestopONLINE   0 0 0
>   raidz1-0  ONLINE   0 0 0
> da0 ONLINE   0 0 0
> da1 ONLINE   0 0 0
> da2 ONLINE   0 0 0
> da3 ONLINE   0 0 0
> da4 ONLINE   0 0 0
> da5 ONLINE   0 0 0
>
> ===Cut===
>
> 6 disks 960 Gbs each:
>
> ===Cut===
>
> # smartctl -a /dev/da0
> smartctl 6.5 2016-05-07 r4318 [FreeBSD 11.0-RC1 amd64] (local build)
> Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
>
> === START OF INFORMATION SECTION ===
> Model Family: Samsung based SSDs
> Device Model: SAMSUNG MZ7KM960HAHP-5
> Serial Number:S2HTNX0H507466
> LU WWN Device Id: 5 002538 c402bdac1
> Firmware Version: GXM1003Q
> User Capacity:960 197 124 096 bytes [960 GB]
> Sector Size:  512 bytes logical/physical
>
> [...]
>
> ===Cut===
>
> But:
>
> ===Cut===
>
> # zpool list gamestop
> NAME   SIZE  ALLOC   FREE  EXPANDSZ   FRAGCAP  DEDUP HEALTH  ALTROOT
> gamestop  5,22T  4,38T   861G -24%83%  1.00x ONLINE  -
>
> ===Cut===
>
> Why 5.22T ? If zpool is displaying raw size, it should be 960 x 6 = 5760 Gb
> = 5.65 T. If it's displaying the actual data, then it should be 960 x 5 =
> 4800 Gb = 4.68 T. 5.22 T is neither of these. I'm stuck, please explain. :)
>
>
> Thanks.
>
> Eugene.

It's raw size, but the discrepancy is between 1000 and 1024.  Smartctl
is reporting base 10 size, but zpool is reporting base 1024..
960197124096.0*6/1024**4 = 5.24 TB, which is pretty close to what
zpool says.

-Alan
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: update from 9.3 to 11.0

2016-10-16 Thread Doug Hardie 

> On 16 October 2016, at 08:24, Warner Losh  wrote:
> 
> On Sun, Oct 16, 2016 at 8:13 AM, Zoran Kolic  wrote:
>> I would like to know what experience and tips people on this list have
>> regarding this update. Doug Hardie made it successfully. To my eyes,
>> it is the mere change of one charracter in the file.
>> I'm a bit late due to lack of time to do the task.
>> Best regards all
> 
> I missed the original post. what's the one character change?


I was sent the patch  below.  However, it doesn't apply directly to 9.3.  Edit 
freebsd-update and go down about 1231 lines.  Generally the comment is found a 
few lines before that.  Add the comma, and all works.

-- Doug


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211398

--- Comment #5 from Xin LI  ---
(In reply to bc979 from comment #4)

Can you try applying this? (r279901)

Index: head/usr.sbin/freebsd-update/freebsd-update.sh
===
--- head/usr.sbin/freebsd-update/freebsd-update.sh  (revision 279900)
+++ head/usr.sbin/freebsd-update/freebsd-update.sh  (revision 279901)
@@ -1231,7 +1231,7 @@ fetch_metadata_sanity () {
   # Some aliases to save space later: ${P} is a character which can
   # appear in a path; ${M} is the four numeric metadata fields; and
   # ${H} is a sha256 hash.
-   P="[-+./:=%@_[~[:alnum:]]"
+   P="[-+./:=,%@_[~[:alnum:]]"
   M="[0-9]+\|[0-9]+\|[0-9]+\|[0-9]+"
   H="[0-9a-f]{64}"


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

zfs/raidz: seems like I'm failing with math

2016-10-16 Thread Eugene M. Zheganin 

Hi.

FreeBSD 11.0-RC1 r303979, zfs raidz1:

===Cut===

# zpool status gamestop
  pool: gamestop
 state: ONLINE
  scan: none requested
config:

NAMESTATE READ WRITE CKSUM
gamestopONLINE   0 0 0
  raidz1-0  ONLINE   0 0 0
da0 ONLINE   0 0 0
da1 ONLINE   0 0 0
da2 ONLINE   0 0 0
da3 ONLINE   0 0 0
da4 ONLINE   0 0 0
da5 ONLINE   0 0 0

===Cut===

6 disks 960 Gbs each:

===Cut===

# smartctl -a /dev/da0
smartctl 6.5 2016-05-07 r4318 [FreeBSD 11.0-RC1 amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Samsung based SSDs
Device Model: SAMSUNG MZ7KM960HAHP-5
Serial Number:S2HTNX0H507466
LU WWN Device Id: 5 002538 c402bdac1
Firmware Version: GXM1003Q
User Capacity:960 197 124 096 bytes [960 GB]
Sector Size:  512 bytes logical/physical

[...]

===Cut===

But:

===Cut===

# zpool list gamestop
NAME   SIZE  ALLOC   FREE  EXPANDSZ   FRAGCAP  DEDUP HEALTH  ALTROOT
gamestop  5,22T  4,38T   861G -24%83%  1.00x ONLINE  -

===Cut===

Why 5.22T ? If zpool is displaying raw size, it should be 960 x 6 = 5760 
Gb = 5.65 T. If it's displaying the actual data, then it should be 960 x 
5 = 4800 Gb = 4.68 T. 5.22 T is neither of these. I'm stuck, please 
explain. :)



Thanks.

Eugene.

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

Re: sshd whines & dies after releng/10 "freebsd-update" run

2016-10-16 Thread David Wolfskill 
On Sun, Oct 16, 2016 at 12:35:01PM -0400, Brandon Allbery wrote:
> On Sun, Oct 16, 2016 at 12:26 PM, David Wolfskill 
> wrote:
> 
> > This weekend, though, I was planning to update my other systems tfrom
> > stable/10 to stable/11, so I figured I'd try freebsd-update on this
> > machine first.
> >
> 
> Wait, you used freebsd-update on a machine running stable?

No.

My *other* machines run stable (though a couple also sometimes run
head).  This machine runs releng/10.

> It only supports
> releases. IOW you may well have *downgraded* the machine in some sense.
> (Although really it should have just failed in that case.)

Right.

> Also make sure you are not using an sshd from ports; even if such a
> down/sidegrade works for base, I'd expect it to screw up installed ports.
> 

I'm certain that I wouldn't have placed a "ports" sshd in /sur/sbin
(even had I installed one), and pkg reports negatively:

sisboombah(10.3-RELEASE-p7)[5] pkg info ssh\*
pkg: No package(s) matching ssh*
sisboombah(10.3-RELEASE-p7)[6] 

Thanks!

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
Those who would murder in the name of God or prophet are blasphemous cowards.

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


signature.asc
Description: PGP signature

Re: sshd whines & dies after releng/10 "freebsd-update" run

2016-10-16 Thread Brandon Allbery 
On Sun, Oct 16, 2016 at 12:26 PM, David Wolfskill 
wrote:

> This weekend, though, I was planning to update my other systems tfrom
> stable/10 to stable/11, so I figured I'd try freebsd-update on this
> machine first.
>

Wait, you used freebsd-update on a machine running stable? It only supports
releases. IOW you may well have *downgraded* the machine in some sense.
(Although really it should have just failed in that case.)

Also make sure you are not using an sshd from ports; even if such a
down/sidegrade works for base, I'd expect it to screw up installed ports.

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

sshd whines & dies after releng/10 "freebsd-update" run

2016-10-16 Thread David Wolfskill 
For most of my experience with FreeBSD (since 1998) and for most of my
machines, I build from source (either on the machine itself or a
dedicated "build machine"); this has been ... occasionally turbulent,
but overall, a fairly stable approach for me (and it's a great deal less
turbulent -- usually! -- now than it was a decade ago).

However, I have one machine that is pretty much dedicated to one
specific function, and for it, I thought I'd try freebsd-update.

And over the last year or so, it's worked pretty well:  I have the
machine set up (as is usually my approach) to be able to boot from
either of a couple of slices.  I use a "dump | restore" pipeline
to copy the / and /usr file systems from the "active" slice to the
"inactive" slice, adjust /etc/fstab on the inactive slice to reflect
reality for when it's the boot slice, then (while the file systemms
from the other slice are still mounted -- e.g., on /S2) run
"freebsd-update -b /S2 fetch install", then reboot from the
newly-updated slice.

In the past, that's Just Worked.

This weekend, though, I was planning to update my other systems tfrom
stable/10 to stable/11, so I figured I'd try freebsd-update on this
machine first.

But before I tried going to stable/11, I thought it might be good to
first get to the latest releng/10.

Running freebsd-update seemed to go well.  I rebooted from the updated
slice... and found that I could not ssh to the machine.  (I only
physically login to a machine other than my laptop if there's a problem
that's so bad that I can't login from the laptop)

And I found that sshd wasn't running.  Indeed, on attempting to start it
by hand:

root@sisboombah: # service sshd start
Performing sanity check on sshd configuration.
Undefined symbol "ssh_compat13" referenced from COPY relocation in 
/usr/sbin/sshd
/etc/rc.d/sshd: WARNING: failed precmd routine for sshd

Attempting to start it in "debug" mode was of no help:

root@sisboombah:/tmp # `which sshd` -d
Undefined symbol "ssh_compat13" referenced from COPY relocation in 
/usr/sbin/sshd

Any clues?

I have placed both a typescript of the freebsd-update run (actually, a
pair of them: one yesterday; another, today), as well as a typescript
from some poking around a bit, under
.

Thanks!

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
Those who would murder in the name of God or prophet are blasphemous cowards.

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


signature.asc
Description: PGP signature

Re: update from 9.3 to 11.0

2016-10-16 Thread Warner Losh 
On Sun, Oct 16, 2016 at 8:13 AM, Zoran Kolic  wrote:
> I would like to know what experience and tips people on this list have
> regarding this update. Doug Hardie made it successfully. To my eyes,
> it is the mere change of one charracter in the file.
> I'm a bit late due to lack of time to do the task.
> Best regards all

I missed the original post. what's the one character change?

Warner
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Building FreeBSD 11.0-stable on FreeBSD 10.1-stable fails

2016-10-16 Thread Warner Losh 
On Sun, Oct 16, 2016 at 5:34 AM, Dimitry Andric  wrote:
> On 16 Oct 2016, at 12:20, Torfinn Ingolfsen  
> wrote:
>> I am trying to build FreeBSD 11.0-stable on a machine which runs:
>> tingo@kg-v7$ uname -a
>> FreeBSD kg-v7.kg4.no 10.1-STABLE FreeBSD 10.1-STABLE #0 r278322: Fri Feb  6 
>> 21:36:01 CET 2015
>> r...@kg-v7.kg4.no:/usr/obj/usr/src/sys/GENERIC  amd64
>>
>> I have emptied /usr/src and /usr/obj and fetched the latest stable/11 via 
>> subversion:
>> tingo@kg-v7$ egrep "^BRANCH|^REVISION" /usr/src/sys/conf/newvers.sh
>> REVISION="11.0"
>> BRANCH="STABLE"
>>
>> But building it (per the procedure in the handbook) fails at the buildworld 
>> stage. Both 'make -j5 buildworld' and 'make buildworld' fails, like this:
>>
>> c++: error: unable to execute command: Segmentation fault (core dumped)
>> c++: error: clang frontend command failed due to signal (use -v to see 
>> invocation)
>> FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
>> Target: x86_64-unknown-freebsd10.1
>> Thread model: posix
>> c++: note: diagnostic msg: PLEASE submit a bug report to 
>> https://bugs.freebsd.org/submit/ and include the crash backtrace, 
>> preprocessed source, and associated run script.
>> c++: note: diagnostic msg:
>> 
>>
>> PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
>> Preprocessed source(s) and associated run script(s) are located at:
>> c++: note: diagnostic msg: /tmp/CGBlocks-abcdc1.cpp
>> c++: note: diagnostic msg: /tmp/CGBlocks-abcdc1.sh
>
> Please make sure your stable/10 is at least r286033.

What's the issue this fixes? Right now we have safeties in place in
buildworld that indicate we 'support' back to 9 sometime. If that's
not really the case, we need to fix something (either fix so we don't
need this specific revision, or fix the Makefile to indicate we don't
support back that far).

Warner
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

update from 9.3 to 11.0

2016-10-16 Thread Zoran Kolic 
I would like to know what experience and tips people on this list have
regarding this update. Doug Hardie made it successfully. To my eyes,
it is the mere change of one charracter in the file.
I'm a bit late due to lack of time to do the task.
Best regards all

Zoran

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

Re: Clandestine USB SD card slot

2016-10-16 Thread George Mitchell 
Whoops, I should send this to freebsd-stable instead of freebsd-usb.
Sorry! -- George

On 10/16/16 09:22, George Mitchell wrote:
> On 10/15/16 23:10, Anthony Jenkins wrote:
>> On 10/15/16 18:28, George Mitchell wrote:
>>> FreeBSD 10.3-RELEASE-p7 #0: Thu Aug 11 18:38:15 UTC 2016
>>> Acer Aspire E15
>>> There is a slot on the front of this laptop which sure looks like an
>>> SD card slot, which I hope corresponds to one of these:
>>>
>>> ugen1.1:  at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps)
>>> pwr=SAVE (0mA)
>>> ugen0.1:  at usbus0, cfg=0 md=HOST spd=SUPER
>>> (5.0Gbps) pwr=SAVE (0mA)
>>> ugen2.1:  at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps)
>>> pwr=SAVE (0mA)
>>> ugen1.2:  at usbus1, cfg=0 md=HOST
>>> spd=HIGH (480Mbps) pwr=SAVE (100mA)
>>> ugen2.2:  at usbus2, cfg=0 md=HOST
>>> spd=HIGH (480Mbps) pwr=SAVE (100mA)
>>> ugen0.2:  at usbus0, cfg=0 md=HOST
>>> spd=SUPER (5.0Gbps) pwr=ON (224mA)
>>> ugen1.3:  at usbus1, cfg=0 md=HOST spd=FULL
>>> (12Mbps) pwr=SAVE (100mA)
>>> ugen2.3:  at usbus2, cfg=0 md=HOST
>>> spd=FULL (12Mbps) pwr=ON (100mA)
>>> ugen1.4:  at usbus1, cfg=0 md=HOST
>>> spd=LOW (1.5Mbps) pwr=ON (100mA)
>>> ugen1.5:  at usbus1, cfg=0 md=HOST spd=FULL
>>> (12Mbps) pwr=SAVE (100mA)
>>> ugen1.6:  at usbus1, cfg=0 md=HOST
>>> spd=FULL (12Mbps) pwr=ON (100mA)
>>> ugen1.7:  at usbus1, cfg=0 md=HOST
>>> spd=FULL (12Mbps) pwr=ON (100mA)
>>> ugen1.8:  at usbus1, cfg=0 md=HOST
>>> spd=HIGH (480Mbps) pwr=ON (500mA)
>>>
>>> But inserting a card into the slot produces no results, even with
>>> sysctl hw.usb.umass.debug=1 hw.usb.ugen.debug=1 hw.usb.dev.debug=1.
>>> (sysctl hw.usb.debug=1 produces way too much output all the time.)
>>> Any suggestions on how I can get this slot to overcome its shyness?
>>> (I am not subscribed to the list; please CC me.)  -- George
>> Your card reader is probably on the PCI bus (and likely not supported by
>> FreeBSD); I couldn't find any of your USB Pid:Vids as card readers.
>>
>> [ajenkins@ajenkins-hplaptop ~]$ pciconf -lv
>> ...
>> none2@pci0:3:0:0:   class=0xff card=0x1995103c chip=0x522910ec
>> rev=0x01 hdr=0x00
>> vendor = 'Realtek Semiconductor Co., Ltd.'
>> device = 'RTS5229 PCI Express Card Reader'
>>
>> Anthony Jenkins
>>
> Ah!  It didn't occur to me to run pciconf.  "pciconf -lv" shows this:
> 
> sdhci_pci0@pci0:0:20:7:   class=0x080501 card=0x08651025 chip=0x78131022
> rev=0x01 hdr=0x00
> vendor = 'Advanced Micro Devices, Inc. [AMD]'
> device = 'FCH SD Flash Controller'
> class  = base peripheral
> subclass   = SD host controller
> 
> So not only is it (apparently) recognized, but the sdhci_pci driver
> attached to it!  But inserting or removing a card shows no activity.
> What's my next step?  -- George
> 

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

Re: Building FreeBSD 11.0-stable on FreeBSD 10.1-stable fails

2016-10-16 Thread Dimitry Andric 
On 16 Oct 2016, at 12:20, Torfinn Ingolfsen  
wrote:
> I am trying to build FreeBSD 11.0-stable on a machine which runs:
> tingo@kg-v7$ uname -a
> FreeBSD kg-v7.kg4.no 10.1-STABLE FreeBSD 10.1-STABLE #0 r278322: Fri Feb  6 
> 21:36:01 CET 2015
> r...@kg-v7.kg4.no:/usr/obj/usr/src/sys/GENERIC  amd64
> 
> I have emptied /usr/src and /usr/obj and fetched the latest stable/11 via 
> subversion:
> tingo@kg-v7$ egrep "^BRANCH|^REVISION" /usr/src/sys/conf/newvers.sh
> REVISION="11.0"
> BRANCH="STABLE"
> 
> But building it (per the procedure in the handbook) fails at the buildworld 
> stage. Both 'make -j5 buildworld' and 'make buildworld' fails, like this:
> 
> c++: error: unable to execute command: Segmentation fault (core dumped)
> c++: error: clang frontend command failed due to signal (use -v to see 
> invocation)
> FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
> Target: x86_64-unknown-freebsd10.1
> Thread model: posix
> c++: note: diagnostic msg: PLEASE submit a bug report to 
> https://bugs.freebsd.org/submit/ and include the crash backtrace, 
> preprocessed source, and associated run script.
> c++: note: diagnostic msg:
> 
> 
> PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
> Preprocessed source(s) and associated run script(s) are located at:
> c++: note: diagnostic msg: /tmp/CGBlocks-abcdc1.cpp
> c++: note: diagnostic msg: /tmp/CGBlocks-abcdc1.sh

Please make sure your stable/10 is at least r286033.

-Dimitry



signature.asc
Description: Message signed with OpenPGP using GPGMail

Building FreeBSD 11.0-stable on FreeBSD 10.1-stable fails

2016-10-16 Thread Torfinn Ingolfsen 
I am trying to build FreeBSD 11.0-stable on a machine which runs:
tingo@kg-v7$ uname -a
FreeBSD kg-v7.kg4.no 10.1-STABLE FreeBSD 10.1-STABLE #0 r278322: Fri Feb  6 
21:36:01 CET 2015 
r...@kg-v7.kg4.no:/usr/obj/usr/src/sys/GENERIC  amd64

I have emptied /usr/src and /usr/obj and fetched the latest stable/11 via 
subversion:
tingo@kg-v7$ egrep "^BRANCH|^REVISION" /usr/src/sys/conf/newvers.sh
REVISION="11.0"
BRANCH="STABLE"

But building it (per the procedure in the handbook) fails at the buildworld 
stage. Both 'make -j5 buildworld' and 'make buildworld' fails, like this:

c++: error: unable to execute command: Segmentation fault (core dumped)
c++: error: clang frontend command failed due to signal (use -v to see 
invocation)
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
Target: x86_64-unknown-freebsd10.1
Thread model: posix
c++: note: diagnostic msg: PLEASE submit a bug report to 
https://bugs.freebsd.org/submit/ and include the crash backtrace, preprocessed 
source, and associated run script.
c++: note: diagnostic msg: 


PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
c++: note: diagnostic msg: /tmp/CGBlocks-abcdc1.cpp
c++: note: diagnostic msg: /tmp/CGBlocks-abcdc1.sh
c++: note: diagnostic msg: 


*** Error code 254

Stop.
bmake[4]: stopped in /usr/src/lib/clang/libclangcodegen
*** Error code 1

Stop.
bmake[3]: stopped in /usr/src/lib/clang
*** Error code 1

Stop.
bmake[2]: stopped in /usr/src
*** Error code 1

Stop.
bmake[1]: stopped in /usr/src
*** Error code 1

Stop.
make: stopped in /usr/src

So I cleaned out /usr/obj again and tried this (fro /usr/src/UPDATING):
root@kg-v7# make WITHOUT_CLANG=y WITH_GCC=y -j5 buildworld
[..]

*** [CGClass.o] Error code 254

bmake[4]: stopped in /usr/src/lib/clang/libclangcodegen
2 errors

bmake[4]: stopped in /usr/src/lib/clang/libclangcodegen
*** [all_subdir_lib/clang/libclangcodegen] Error code 2

bmake[3]: stopped in /usr/src/lib/clang
--- all_subdir_lib/clang/libclangedit ---
A failure has been detected in another branch of the parallel make

bmake[4]: stopped in /usr/src/lib/clang/libclangedit
*** [all_subdir_lib/clang/libclangedit] Error code 2

bmake[3]: stopped in /usr/src/lib/clang
--- all_subdir_lib/clang/libclangast ---
A failure has been detected in another branch of the parallel make

bmake[4]: stopped in /usr/src/lib/clang/libclangast
*** [all_subdir_lib/clang/libclangast] Error code 2

bmake[3]: stopped in /usr/src/lib/clang
--- all_subdir_lib/clang/libclangfrontend ---
A failure has been detected in another branch of the parallel make

bmake[4]: stopped in /usr/src/lib/clang/libclangfrontend
*** [all_subdir_lib/clang/libclangfrontend] Error code 2

bmake[3]: stopped in /usr/src/lib/clang
4 errors

bmake[3]: stopped in /usr/src/lib/clang
*** [cross-tools] Error code 2

bmake[2]: stopped in /usr/src
1 error

bmake[2]: stopped in /usr/src
*** [_cross-tools] Error code 2

bmake[1]: stopped in /usr/src
1 error

bmake[1]: stopped in /usr/src
*** [buildworld] Error code 2

make: stopped in /usr/src
1 error

make: stopped in /usr/src

So, is there a way to fix this without building an updated stable/10 as an 
intermediary step?
References:
FreeBSD forum thread: https://forums.freebsd.org/threads/58082/
-- 
Torfinn Ingolfsen 
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: vale-ctl(-8), ifconfig(8), SIOCAIFADDR: Invalid argument [utilizing netmap(4) providing virtual switches+interfaces to BHyVe]

2016-10-16 Thread Vincenzo Maffione 
2016-10-15 11:42 GMT+02:00 Harry Schmalzbauer :

> Bezüglich Vincenzo Maffione's Nachricht vom 15.10.2016 09:32 (localtime):
> > 2016-10-14 15:38 GMT+02:00 Harry Schmalzbauer :
>
> …
> >> I'm familar with epair(4), but not with tap(4).
> >> I don't understand the man page for tap, perhaps I should read pty(4)…
> >> But I guess I don't have to know the details of tap(4), since you
> >> confirmed that it can be connected to VALE.
> >>
> >
> > It's not necessary to understand the details. However, a TAP device is
> > conceptually similar to the two ends of an epair, with the difference
> that
> > in the TAP a network interface (e.g. tap0) is conecptually "connected"
> > back-to-back to a file descriptor. The file descriptor is written/read by
> > the hypervisor (to inject/intercept packets to/from the network stack),
> > while the tap0 interface can be attached to if_bridge.
>
> Hi Vincenzo, thanks for your explanation!
>
>
> >>
> >> So one could summarize:
> >> VALE (as part of netmap(4)) can act as a if_bridge(4) replacement in
> >> FreeBSD-10/11, keeping everything else involved untouched.
> >> Please correct me if I'm wrong.
> >>
> >
> > For simple cases yes. if_bridge may have features that are not supported
> by
> > netmap (i.e. configure ports as VLAN access ports). Moreover, if_bridge
> has
> > a interface (br0), whereas VALE bridges doesn't.
>
> Again, thank you for your time! (R)STP comes to my mind (which I don't
> need any more). And I'm not sure if VALE really lacks that, but I guess
> it wouldn't match VALEs philosophy/design at all…
>

Well, VALE is a programmable switch, meaning that you can plug in a custom
forwarding function (which is just a C function). The default forwarding
function implements an L2 learning bridge without STP, because it is
thought to be used as the preferred hypervisor virtual switch, so no L2
connectivity loops, and the STP comes with an overhead. If you really wish
to have VALE with STP, you could define your own custom forwarding function
that implements it.

>
> …
> >>> https://github.com/luigirizzo/netmap). Among the new features, there
> is
> >> a
> >>> new solution for bhyve networking, which will let you attach your bhyve
> >> VMs
> >>> directly to a VALE switch, without paying additional overheads related
> to
> >>> TAPs, epairs, and vtnet emulation. You can find additional information,
> >>> code and performance numbers here:
> >>> https://wiki.freebsd.org/SummerOfCode2016/PtnetDriverAndDeviceModel.
> >>
> >> Thanks for that hint!
> >> I guess it's about ptnetmap(4)? I read papers but haven't considered it
> >> could be production-ready for FreeBSD in the near future.
> >> It's extremely interesting and I'd love to be eraly adopter, but my
> >> (ESXi) setups are currently doing well and I don't have spare time or
> >> any business project to try out… :-(
> >>
> >
> > Yes, it's ptnetmap. However, bhyve is going to have support for VALE
> ports
> > anyway (even without ptnetmap), as QEMU already does, so at least you
> will
> > be able to replace TAPs with VALE ports (while still using vtnet devices
> > for the VM).
>
> Oic, I wasn't aware that there will be a VALE-vtnet direct path! That is
> really great news :-) And a big achievment for guests preferring
> "standard" drivers, ptnetmap could limit the guest OS choice I guess.
>

Yes ptnetmap is supported on QEMU and bhyve, and as a gues you can use only
FreeBSD and Linux, at the moment.

>
> For now, I'm happy having been in touch with netmap(4) – at least with a
> very little fraction of natmap – but I'll stay the legacy way utilizing
> if_bridge(4) and see if there are still oddities and try to find some
> time to track them down (involving LACP, VLANs, Jumbo-Frames and IPv6 –
> that was the problematic constellation)
>
> Since I have extra PHYs, I can do PCIe-passthrough like before (with
> ESXi) for some special guests. I'm looking forward to find out how this
> works with bhyve!
>
> No idea, but also ptnetmap is able to do that: not only you can
pass-through a VALE port, but also you can pass-through a physical
interface.

Cheers,
  Vincenzo



> Best,
>
> -Harry
>



-- 
Vincenzo Maffione
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"