Re: FreeBSD 11.1-R network slowness on Samba and Windows VM on VirtualBox

2017-08-01 Thread Nenhum_de_Nos 

On Tue, August 1, 2017 11:41, Werner Griessl wrote:
> On 08/01/17 04:52, Nenhum_de_Nos wrote:
>>
>> On Sun, July 30, 2017 02:08, Nenhum_de_Nos wrote:
>>> Hi,
>>>
>>> I was running 10.3-p7 on Atom hardware and using old samba36-3.6.25_1.
>>> All
>>> was fine.
>>>
>>> Then I updated to 11.1-R by recompiling from svn, using the same
>>> kernelconfig from 10.3, and now my windows client shows timeouts and
>>> really slow connection. File copy never past kilobytes per second :(
>>>
>>> I am compiling a new samba packet from ports, but that slow is weird
>>> for
>>> me, and I could not find any other cases on web search.
>>>
>>> thanks,
>>>
>>> matheus
>>
>> Hi guys,
>>
>> I got this still going, where I installed a new Windows VM and same
>> problem. I reinstalled all ports and same problem. I use Windows shares
>> from another sources (not a VirtualBox VM) and all works fine.
>>
>> Some help were said here https://forums.freebsd.org/threads/61813/, but
>> unfortunately I have no leads so far.
>>
>> I will try to install some 10.3 box to try it out when I get some time
>> and
>> a free machine.
>>
>> If anyone has any clues.
>>
>> thanks,
>>
>
>
> Try comment out in smb4.conf the line:
> "#   case sensitive = true"
> Worked for me with samba44
>
> Werner

Hi Werner,

as I got my samba conf from old 3.6 I don't have this line there.

I tried something today.

I got and i386 netbook to work using 4.4 samba and FreeBSD hetchet
11.0-RELEASE-p1 FreeBSD 11.0-RELEASE-p1 #0 r306420: Thu Sep 29 03:40:55
UTC 2016 r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC i386.
The vm could copy files from it.

Then I compiled the samba port on the Atom amd64 machine, same problem.
I got to know the amd64 machine has custom kernel conf, but mostly just pf
stuff:

Code:
diff GENERIC FreeBSD-11-amd64-PF
19c19
< # $FreeBSD: releng/11.1/sys/amd64/conf/GENERIC 318763 2017-05-24
00:00:55Z jhb $
---
> # $FreeBSD: releng/11.0/sys/amd64/conf/GENERIC 302410 2016-07-08
00:22:14Z gjb $
22c22
< ident GENERIC
---
> ident FreeBSD-11-amd64-PF
88d87
< options   EARLY_AP_STARTUP
360a360,378
>
> # pf
>
> device pf
> device pflog
> device pfsync
>
> options ALTQ
> options ALTQ_CBQ # Class Bases Queuing (CBQ)
> options ALTQ_RED # Random Early Detection (RED)
> options ALTQ_RIO # RED In/Out
> options ALTQ_HFSC # Hierarchical Packet Scheduler (HFSC)
> options ALTQ_PRIQ # Priority Queuing (PRIQ)
>
> device carp
>
> # device polling
> options DEVICE_POLLING



I just got all ports rebuilt after the upgrade to 11.1-R, so should I do
it all again? No forget, just machines under Virtualbox suffer, all other
work fine.

thanks,

> --
> Werner Grießl  D-95440 Bayreuth, Germany
> Universitaet Bayreuth  Tel.: +49 921 55 2685
> IT-Servicezentrum/NetzeNW2 3.2.U1.143
> ___
> 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"


-- 
"We will call you Cygnus,
the God of balance you shall be."

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

11.1-RELEASE: panic! acl_from_aces: a_type is 0x4000

2017-08-01 Thread Peter 
This is mostly for the search engines, so others running into it may 
find it easier to solve.



While updating some ports via "portupgrade", I got this panic:

  Panic String: acl_from_aces: a_type is 0x4000

The phenomen was reproducible; it appeared while creating a backup 
package from the "glib" port.
I checked readability of all concerned files, did a scrub on the pool, 
but found no errors! As I was busy with other issues, I then neglected 
the matter and simply deleted and reinstalled that port.


A couple days later, working on a different installation, I got the 
exact same panic at the exact same point, while updating the "glib" port.

This time I looked closer into the matter.
According to "truss", the panic appears while "pkg" calls 
__acl_get_link() on a specific file.


That file is readable.
The directory tree can be searched.
But it is not possible to do "ls -l" on the directory -> panic!
It is possible to send+recv the Filesystem: the error gets transported
to the new filesystem! (From ZFS view it seems to be legal payload;
only from FreeBSD file-handling view it is reason for panic.)
Finally, the file can be copied, unlinked, and recreated.

I did a thorough search and found a dozen other files on the system with 
the same issue.



REMEDY:
---
It seems that such flaws can lure undetected on a system for an 
indefinite time. The only way to find them seems read all inode data,

via something like
#find -x `mount -t zfs | awk '{print $3}'` -type d -exec ls -la {} \;


ROOT CAUSE:
---
Not fully clear. It may be related to hardware (memory) flaws.
___
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"

[Bug 221146] [LAGG] Problem with second laggport

2017-08-01 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146

--- Comment #5 from Cassiano Peixoto  ---
Hi guys,

It's a bug after commit r320897.

I have the same issue running an ix interface in netmap mode after this commit.
I had to downgrade ixgbe drivers to make it works again.

Looks like a bug after driver update to 3.2.12-k.

I'm copying the author of commit.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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"

[Bug 221146] [LAGG] Problem with second laggport

2017-08-01 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146

--- Comment #4 from veg...@tuxpowered.net ---
Sorry, I meant ixl-1.7.12 from Intel.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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"

[Bug 221146] [LAGG] Problem with second laggport

2017-08-01 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146

veg...@tuxpowered.net changed:

   What|Removed |Added

 CC||veg...@tuxpowered.net

--- Comment #3 from veg...@tuxpowered.net ---
I have some Intel xl710 running failover lagg and I had an issue not totally
unlike this one. One of ports in lagg (and always the same one, unless they
were added in different order, then both would always work) would only send
frames but never receive them, so the router would become master on carp on
vlans on this lagg, never seeing carp advertisements of the primary router.
That was on FreeBSD 11.0, though. I used ixgbe-2.5.15 from Intel instead of the
one coming with Kernel and the issue was gone.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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"

[Bug 221146] [LAGG] Problem with second laggport

2017-08-01 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146

Cassiano Peixoto  changed:

   What|Removed |Added

 CC||freebsd-stable@FreeBSD.org,
   ||peixoto.cassi...@gmail.com

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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: issues with powerd/freq_levels

2017-08-01 Thread Karl Denninger 
On 8/1/2017 12:45, Ian Smith wrote:
> On Mon, 31 Jul 2017 12:03:27 -0700, Kevin Oberman wrote:
>  > On Mon, Jul 31, 2017 at 3:48 AM, Ian Smith  wrote:
>  > 
>  > > On Mon, 31 Jul 2017 10:09:11 +0300, Daniel Braniss wrote:
>  > >
>  > >  > I am trying out PCengines latest apu2 boards, and I just noticed that
>  > > with different Freebsd versions I get
>  > >  > different freq_levels, and so when idling, each box (have 5) has a
>  > > different freq/temperature value, ranging
>  > >  > from 125/69.1C, 600/59.0C to 75/56.0C
>  > >  >
>  > >  > FreeBSD apu-4 11.1-STABLE FreeBSD 11.1-STABLE #5 f565b5a06ab3 (11) 
> tip:
>  > > Mon Jul 31 09:36:33 IDT 2017
>  > >  > apu-4# sysctl dev.cpu.0.freq_levels
>  > >  > dev.cpu.0.freq_levels: 1000/980 800/807 600/609
>  > >
>  > > That looks about right.  On a Core2Duo (still on 9.3) I get:
>  > > dev.est.1.freq_settings: 2401/35000 2400/35000 1600/15000 800/12000
>  > > dev.est.0.freq_settings: 2401/35000 2400/35000 1600/15000 800/12000
>  > > dev.cpu.0.freq_levels: 2401/35000 2400/35000 1600/15000 800/12000
>  > > dev.cpu.0.freq: 800
>  > >
>  > > But only because I'd added to /boot/loader.conf:
>  > >
>  > > hint.p4tcc.0.disabled=1
>  > > hint.acpi_throttle.0.disabled=1
>  > >
>  > > which became the defaults sometime, maybe not before 11.0?  Otherwise
>  > > mine would look more similar to the one below, with all 12.5% increments
>  > > in frequency enabled, which doesn't actually save any power at all.
>  > >
>  > >  > FreeBSD apu-5 11.1-PRERELEASE FreeBSD 11.1-PRERELEASE #0 21e9d1ca9b80
>  > > (11) tip: Tue May 30 11:51:48 IDT 2017
>  > >  > apu-5# sysctl dev.cpu.0.freq_levels
>  > >  > dev.cpu.0.freq_levels: 1000/966 875/845 800/795 700/695 600/600 
> 525/525
>  > > 450/450 375/375 300/300 225/225 150/150 75/75
>  > >
>  > > Looks like either p4tcc or acpi_throttle is enabled?  See cpufreq(4).
>  > > As above, these don't buy you anything but extra busyness for powerd.
>  > >
>  > > Also noticed that the (nice, low!) milliwatt figures for 1000/800/600
>  > > freqs are a bit different to the -stable one.  Slightly Different model?
>  > >
>  > >  > FreeBSD apu-1 10.3-STABLE FreeBSD 10.3-STABLE #4 267788fd852c (10) 
> tip:
>  > > Tue Jan 10 09:09:00 IST 2017
>  > >  > apu-1# sysctl dev.cpu.0.freq_levels
>  > >  > dev.cpu.0.freq_levels: 1000/-1 875/-1 750/-1 625/-1 500/-1 375/-1
>  > > 250/-1 125/-1
>  > >
>  > > And that looks like est(4) isn't enabled/attaching at all .. see dmesg
>  > > on all of these for clues.
>  > >
>  > >  > so, any ideas as to what is going on?
>  > >
>  > > Pure guesswork on experience with older versions, I'm not up to date.
>  > >
>  > 
>  > Very odd. Are all systems running identical CPUs and BIOSes? Identical
>  > loader and sysctl configurations? Look at /var/rn/dmesg.boot for CPU
>  > information. Is EST being detected? It used to be early in the boot
>  > process, but is now fairly late. (In my case, about 2/3 through the
>  > dmesg.boot file.
>
> Hi Kevin, it's been a while ..
>
> Danny, can you put up a verbose boot dmesg.boot of one(?) for a browse? 
> Or maybe apu-4 and -1, if not all.  I'd expect error msgs on -1 anyway.
>
>  > I have p4tcc and throttling explicitly turned off (which should now be the
>  > default), but my Sandy Bridge Core i5 still shows:
>  > dev.cpu.0.freq_levels: 2501/35000 2500/35000 2000/26426 1800/23233
>  > 1600/20164 1400/17226 1200/14408 1000/11713 800/9140
>
> All truly available I see on more recent processors.  Certainly not 1/8 
> duty-cycle multipliers as p4tcc and maybe? acpi_throttle (not seen here)
>
>  > The first is really bogus to indicate "turbo" mode.
>
> Usefully bogus, in that you can flag powerd to (in your case) -M 2500 to 
> prevent it engaging "turbo" mode, as I do on my old Core2Duo, as advised 
> by Warner years ago to avoid overheating on buildworlds and such - but 
> more recent incarnations of "turbo" are supposedly far more functional.
>
> Admittedly a digression .. mostly coming from wondering about data Karl
> posted in response, indicating different Cx levels available and so used 
> by the latter 3 AP cores, which was news to me.  I'd like to know more, 
> if only for gratuitous curiosity.  Others can tick their TL;DR box :)
>
>  > Temperature is a totally separate issue. It is VERY sensitive to external
>  > issue like airflow and position of the CPU in relation to other components
>  > in the chassis Also, unless you have a lot of cores, you probably should
>  > set both economy_cx_lowest and performance_cx_lowest to Cmax. Economy
>  > should default to that, but  performance will not as that can cause issues
>  > on systems with large numbers of cores, so is set to C2. Many such system
>  > used to disable deeper sleep modes in BIOS, but I am way behind the times
>  > and don't know about the current state of affairs. Certainly for systems
>  > with 32 or fewer cores, this should not be an issue. In any case, Cx state
>  > can sharply impact

Re: issues with powerd/freq_levels

2017-08-01 Thread Ian Smith 
On Mon, 31 Jul 2017 12:03:27 -0700, Kevin Oberman wrote:
 > On Mon, Jul 31, 2017 at 3:48 AM, Ian Smith  wrote:
 > 
 > > On Mon, 31 Jul 2017 10:09:11 +0300, Daniel Braniss wrote:
 > >
 > >  > I am trying out PCengines latest apu2 boards, and I just noticed that
 > > with different Freebsd versions I get
 > >  > different freq_levels, and so when idling, each box (have 5) has a
 > > different freq/temperature value, ranging
 > >  > from 125/69.1C, 600/59.0C to 75/56.0C
 > >  >
 > >  > FreeBSD apu-4 11.1-STABLE FreeBSD 11.1-STABLE #5 f565b5a06ab3 (11) tip:
 > > Mon Jul 31 09:36:33 IDT 2017
 > >  > apu-4# sysctl dev.cpu.0.freq_levels
 > >  > dev.cpu.0.freq_levels: 1000/980 800/807 600/609
 > >
 > > That looks about right.  On a Core2Duo (still on 9.3) I get:
 > > dev.est.1.freq_settings: 2401/35000 2400/35000 1600/15000 800/12000
 > > dev.est.0.freq_settings: 2401/35000 2400/35000 1600/15000 800/12000
 > > dev.cpu.0.freq_levels: 2401/35000 2400/35000 1600/15000 800/12000
 > > dev.cpu.0.freq: 800
 > >
 > > But only because I'd added to /boot/loader.conf:
 > >
 > > hint.p4tcc.0.disabled=1
 > > hint.acpi_throttle.0.disabled=1
 > >
 > > which became the defaults sometime, maybe not before 11.0?  Otherwise
 > > mine would look more similar to the one below, with all 12.5% increments
 > > in frequency enabled, which doesn't actually save any power at all.
 > >
 > >  > FreeBSD apu-5 11.1-PRERELEASE FreeBSD 11.1-PRERELEASE #0 21e9d1ca9b80
 > > (11) tip: Tue May 30 11:51:48 IDT 2017
 > >  > apu-5# sysctl dev.cpu.0.freq_levels
 > >  > dev.cpu.0.freq_levels: 1000/966 875/845 800/795 700/695 600/600 525/525
 > > 450/450 375/375 300/300 225/225 150/150 75/75
 > >
 > > Looks like either p4tcc or acpi_throttle is enabled?  See cpufreq(4).
 > > As above, these don't buy you anything but extra busyness for powerd.
 > >
 > > Also noticed that the (nice, low!) milliwatt figures for 1000/800/600
 > > freqs are a bit different to the -stable one.  Slightly Different model?
 > >
 > >  > FreeBSD apu-1 10.3-STABLE FreeBSD 10.3-STABLE #4 267788fd852c (10) tip:
 > > Tue Jan 10 09:09:00 IST 2017
 > >  > apu-1# sysctl dev.cpu.0.freq_levels
 > >  > dev.cpu.0.freq_levels: 1000/-1 875/-1 750/-1 625/-1 500/-1 375/-1
 > > 250/-1 125/-1
 > >
 > > And that looks like est(4) isn't enabled/attaching at all .. see dmesg
 > > on all of these for clues.
 > >
 > >  > so, any ideas as to what is going on?
 > >
 > > Pure guesswork on experience with older versions, I'm not up to date.
 > >
 > 
 > Very odd. Are all systems running identical CPUs and BIOSes? Identical
 > loader and sysctl configurations? Look at /var/rn/dmesg.boot for CPU
 > information. Is EST being detected? It used to be early in the boot
 > process, but is now fairly late. (In my case, about 2/3 through the
 > dmesg.boot file.

Hi Kevin, it's been a while ..

Danny, can you put up a verbose boot dmesg.boot of one(?) for a browse? 
Or maybe apu-4 and -1, if not all.  I'd expect error msgs on -1 anyway.

 > I have p4tcc and throttling explicitly turned off (which should now be the
 > default), but my Sandy Bridge Core i5 still shows:
 > dev.cpu.0.freq_levels: 2501/35000 2500/35000 2000/26426 1800/23233
 > 1600/20164 1400/17226 1200/14408 1000/11713 800/9140

All truly available I see on more recent processors.  Certainly not 1/8 
duty-cycle multipliers as p4tcc and maybe? acpi_throttle (not seen here)

 > The first is really bogus to indicate "turbo" mode.

Usefully bogus, in that you can flag powerd to (in your case) -M 2500 to 
prevent it engaging "turbo" mode, as I do on my old Core2Duo, as advised 
by Warner years ago to avoid overheating on buildworlds and such - but 
more recent incarnations of "turbo" are supposedly far more functional.

Admittedly a digression .. mostly coming from wondering about data Karl
posted in response, indicating different Cx levels available and so used 
by the latter 3 AP cores, which was news to me.  I'd like to know more, 
if only for gratuitous curiosity.  Others can tick their TL;DR box :)

 > Temperature is a totally separate issue. It is VERY sensitive to external
 > issue like airflow and position of the CPU in relation to other components
 > in the chassis Also, unless you have a lot of cores, you probably should
 > set both economy_cx_lowest and performance_cx_lowest to Cmax. Economy
 > should default to that, but  performance will not as that can cause issues
 > on systems with large numbers of cores, so is set to C2. Many such system
 > used to disable deeper sleep modes in BIOS, but I am way behind the times
 > and don't know about the current state of affairs. Certainly for systems
 > with 32 or fewer cores, this should not be an issue. In any case, Cx state
 > can sharply impact temperature.

Indeed.  But as these are low-power devices already, it's likely less of 
a concern, but maximising efficiency and minimising stress never hurts.

 > Finally, the last case with power levels of -1 for all frequencies is
 >

Re: FreeBSD 11.1 - unknown group wheel

2017-08-01 Thread Alan Somers 
Check your /etc/nsswitch.conf file.  It's possible to screw that up so
that /etc/groups doesn't even get checked.
-Alan

On Tue, Aug 1, 2017 at 11:27 AM, Vanco, Juraj  wrote:
> Hello,
>
> I am trying to build a kernel in FreeBSD 11.0, however I am getting a message
>
> mtree -deU -f /usr/src/etc/mtree/BSD.usr.dist  -p /usr/obj/usr/src/tmp/usr 
> >/dev/null
> mtree: unknown group `wheel'
> mtree: failed at line 6 of the specification
> *** Error code 1
>
>
> However the group is known:
> # cat /etc/group | head -n 3
> # $FreeBSD: releng/11.0/etc/group 294896 2016-01-27 06:28:56Z araujo $
> #
> wheel:*:0:root
>
>
> and currently used:
> # groups
> 0
>
>
> Running any query on group result with zero answer:
> # getent group wheel
> #
> # getent group video
> #
>
>
> Similar result gives mergemaster:
> # mergemaster -p
>
> *** The directory specified for the temporary root environment,
> /var/tmp/temproot, exists.  This can be a security risk if untrusted
> users have access to the system.
>
>   Use 'd' to delete the old /var/tmp/temproot and continue
>   Use 't' to select a new temporary root directory
>   Use 'e' to exit mergemaster
>
>   Default is to use /var/tmp/temproot as is
>
> How should I deal with this? [Use the existing /var/tmp/temproot] d
>
>*** Deleting the old /var/tmp/temproot
>
> *** Creating the temporary root environment in /var/tmp/temproot
>  *** /var/tmp/temproot ready for use
>  *** Creating and populating directory structure in /var/tmp/temproot
>
> install: unknown group wheel
>
>
> I cannot find if this is any known issue... Any clue?
>
> jv
> --
> Intel Research and Development Ireland Limited
> Registered in Ireland
> Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
> Registered Number: 308263
>
>
> This e-mail and any attachments may contain confidential material for the sole
> use of the intended recipient(s). Any review or distribution by others is
> strictly prohibited. If you are not the intended recipient, please contact the
> sender and delete all copies.
> ___
> 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"
___
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"

FreeBSD 11.1 - unknown group wheel

2017-08-01 Thread Vanco, Juraj 
Hello,

I am trying to build a kernel in FreeBSD 11.0, however I am getting a message

mtree -deU -f /usr/src/etc/mtree/BSD.usr.dist  -p /usr/obj/usr/src/tmp/usr 
>/dev/null
mtree: unknown group `wheel'
mtree: failed at line 6 of the specification
*** Error code 1


However the group is known:
# cat /etc/group | head -n 3
# $FreeBSD: releng/11.0/etc/group 294896 2016-01-27 06:28:56Z araujo $
#
wheel:*:0:root


and currently used:
# groups
0


Running any query on group result with zero answer:
# getent group wheel
#
# getent group video
#


Similar result gives mergemaster:
# mergemaster -p

*** The directory specified for the temporary root environment,
/var/tmp/temproot, exists.  This can be a security risk if untrusted
users have access to the system.

  Use 'd' to delete the old /var/tmp/temproot and continue
  Use 't' to select a new temporary root directory
  Use 'e' to exit mergemaster

  Default is to use /var/tmp/temproot as is

How should I deal with this? [Use the existing /var/tmp/temproot] d

   *** Deleting the old /var/tmp/temproot

*** Creating the temporary root environment in /var/tmp/temproot
 *** /var/tmp/temproot ready for use
 *** Creating and populating directory structure in /var/tmp/temproot

install: unknown group wheel


I cannot find if this is any known issue... Any clue?

jv
--
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263


This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.
___
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: FreeBSD 11.1-R network slowness on Samba and Windows VM on VirtualBox

2017-08-01 Thread Werner Griessl 

On 08/01/17 04:52, Nenhum_de_Nos wrote:


On Sun, July 30, 2017 02:08, Nenhum_de_Nos wrote:

Hi,

I was running 10.3-p7 on Atom hardware and using old samba36-3.6.25_1. All
was fine.

Then I updated to 11.1-R by recompiling from svn, using the same
kernelconfig from 10.3, and now my windows client shows timeouts and
really slow connection. File copy never past kilobytes per second :(

I am compiling a new samba packet from ports, but that slow is weird for
me, and I could not find any other cases on web search.

thanks,

matheus


Hi guys,

I got this still going, where I installed a new Windows VM and same
problem. I reinstalled all ports and same problem. I use Windows shares
from another sources (not a VirtualBox VM) and all works fine.

Some help were said here https://forums.freebsd.org/threads/61813/, but
unfortunately I have no leads so far.

I will try to install some 10.3 box to try it out when I get some time and
a free machine.

If anyone has any clues.

thanks,




Try comment out in smb4.conf the line:
"#   case sensitive = true"
Worked for me with samba44

Werner


--
Werner Grießl  D-95440 Bayreuth, Germany
Universitaet Bayreuth  Tel.: +49 921 55 2685
IT-Servicezentrum/NetzeNW2 3.2.U1.143
___
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: FreeBSD 11.1-R network slowness on Samba

2017-08-01 Thread Terry Kennedy 
> Then I updated to 11.1-R by recompiling from svn, using the same
> kernelconfig from 10.3, and now my windows client shows timeouts and
> really slow connection. File copy never past kilobytes per second :(

  I think the issue is with the SAMBA port. I was running the samba36
port under FreeBSD 10.x and things were fine (500Mbyte/sec transfers
using 10GbE). At some point the samba36 port broke due to changes in
one or more of talloc/tdb/tevent and I tried various samba4x ports (I
am using samba44 now, samba46 doesn't seem to work with XP-type client
systems).

  Various directory traversal operations spike the CPU load up to 100%
and clients see very bursty behavior. A lot seems to depend on the 
application in use - my benchmark is clrmamepro:
https://mamedev.emulab.it/clrmamepro/

  But even things like Windows (7) Photo Viewer will just sit at the
"Loading..." message for a random length of time before displaying
the next picture.

  I am seeing easily a 10:1 performance degradation with any of the 
samba4x ports. I have tried large numbers of SAMBA config tuning
changes, different port build options, etc. without any success. I
"solved" the problem by using an old FreeBSD 8.4 box with a 10GbE
card as an NFS client to the storage server, and then exporting the
NFS-mounted storage to clients with samba36. This whole chain is
nearly as fast as the old samba36-on-storage-server setup.

  I may try resurrecting the samba36 port under FreeBSD 11.1 to see
if that has the performance I used to get. I'm not sure how hard
it will be to build samba36, though. Things have changed since the
port was retired.

Terry Kennedy http://www.glaver.org  New York, NY 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: issues with powerd/freq_levels

2017-08-01 Thread Daniel Braniss 
all boards are identical, purchased at the same time.

> On 31 Jul 2017, at 13:48, Ian Smith  wrote:
> 
> On Mon, 31 Jul 2017 10:09:11 +0300, Daniel Braniss wrote:
> 
>> I am trying out PCengines latest apu2 boards, and I just noticed that with 
>> different Freebsd versions I get
>> different freq_levels, and so when idling, each box (have 5) has a different 
>> freq/temperature value, ranging
>> from 125/69.1C, 600/59.0C to 75/56.0C
>> 
>> FreeBSD apu-4 11.1-STABLE FreeBSD 11.1-STABLE #5 f565b5a06ab3 (11) tip: Mon 
>> Jul 31 09:36:33 IDT 2017
>> apu-4# sysctl dev.cpu.0.freq_levels
>> dev.cpu.0.freq_levels: 1000/980 800/807 600/609
> 
> That looks about right.  On a Core2Duo (still on 9.3) I get:
> dev.est.1.freq_settings: 2401/35000 2400/35000 1600/15000 800/12000
> dev.est.0.freq_settings: 2401/35000 2400/35000 1600/15000 800/12000
> dev.cpu.0.freq_levels: 2401/35000 2400/35000 1600/15000 800/12000
> dev.cpu.0.freq: 800
> 
> But only because I'd added to /boot/loader.conf:
> 
> hint.p4tcc.0.disabled=1
> hint.acpi_throttle.0.disabled=1
> 

the above are in my device.hints, so I assume they now standard.

> which became the defaults sometime, maybe not before 11.0?  Otherwise 
> mine would look more similar to the one below, with all 12.5% increments 
> in frequency enabled, which doesn't actually save any power at all.
> 
>> FreeBSD apu-5 11.1-PRERELEASE FreeBSD 11.1-PRERELEASE #0 21e9d1ca9b80 (11) 
>> tip: Tue May 30 11:51:48 IDT 2017
>> apu-5# sysctl dev.cpu.0.freq_levels
>> dev.cpu.0.freq_levels: 1000/966 875/845 800/795 700/695 600/600 525/525 
>> 450/450 375/375 300/300 225/225 150/150 75/75
> 
> Looks like either p4tcc or acpi_throttle is enabled?  See cpufreq(4).
> As above, these don't buy you anything but extra busyness for powerd.
> 
> Also noticed that the (nice, low!) milliwatt figures for 1000/800/600 
> freqs are a bit different to the -stable one.  Slightly Different model?
> 
>> FreeBSD apu-1 10.3-STABLE FreeBSD 10.3-STABLE #4 267788fd852c (10) tip: Tue 
>> Jan 10 09:09:00 IST 2017
>> apu-1# sysctl dev.cpu.0.freq_levels
>> dev.cpu.0.freq_levels: 1000/-1 875/-1 750/-1 625/-1 500/-1 375/-1 250/-1 
>> 125/-1
> 
> And that looks like est(4) isn't enabled/attaching at all .. see dmesg 
> on all of these for clues.
> 
>> so, any ideas as to what is going on?
> 
> Pure guesswork on experience with older versions, I'm not up to date.
> 
> cheers, Ian

well, since I’m mostly interested in 11.1 at the moment, what you are saying is 
that’s ok,
fine by me, 

thanks,
danny

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