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

[Nenhum_de_Nos]

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,

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

[Bug 221050] emulators/virtualbox-ose: Bridged network doesn't work (11.1-RELEASE)

[bugzilla-noreply]

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

rkober...@gmail.com changed:

   What|Removed |Added

 CC||rkober...@gmail.com

--- Comment #14 from rkober...@gmail.com ---
(In reply to John Hood from comment #13)
Just to clarify for people, while developers try to not adjust the KBI within a
major release, it has never been a commitment.

The bottom line is that all kernel modules from ports should be re-built every
time the kernel is updated. For those running releases, this is for every
release as well as security patches which involve a kernel replacement whether
by a re-build or freebsd-update. For those of us running stable, it is every
time the kernel is updated.

While lsof does not involve a kernel module, it does poke around in the kernel
and will break far more easily with kernel changes than modules as it does its
poking outside the documented KBI.

If you build kernels from source, you can list ports needing updating in
/etc/src.conf like this:
PORTS_MODULES=emulators/virtualbox-ose-kmod sysutils/lsof

If you install packages you need to wait until a package build has been
completed after a release. This is usually two or three days, but I have seen
it take as long as a week.

-- 
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 221050] emulators/virtualbox-ose: Bridged network doesn't work (11.1-RELEASE)

[bugzilla-noreply]

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

John Hood  changed:

   What|Removed |Added

 CC||cgull+l-freebsd-bugzilla@gl
   ||up.org

--- Comment #13 from John Hood  ---
(In reply to lavr from comment #11)

This works for me too-- only virtualbox-ose-kmod must be rebuilt on 11.1, all
of its build dependencies can come from packages.

This does suggest that there is still some KBI incompatibility between 11.0 and
11.1 though.

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

[Karl Denninger]

On 7/31/2017 14:03, 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.
>
> 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
> The first is really bogus to indicate "turbo" mode.
>
> 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.
>
> Finally, the last case with power levels of -1 for all frequencies is
> probably because the CPU manufacturer (Intel?) has not published this
> information. For a while they were treating this as "proprietary"
> information. Very annoying! It's always something that is not readily
> available. Thi is one reason I suspect your CPUs are not identical.
> --
> 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"

I have a very new PCEngines unit here running 11.0-STABLE and this is
what I have in the related sysctls:

$ sysctl -a|grep cpu.0
dev.cpu.0.cx_method: C1/hlt C2/io
dev.cpu.0.cx_usage_counters: 2261969965 3038
dev.cpu.0.cx_usage: 99.99% 0.00% last 798us
dev.cpu.0.cx_lowest: C2
dev.cpu.0.cx_supported: C1/1/0 C2/2/400
dev.cpu.0.freq_levels: 1000/924 800/760 600/571
dev.cpu.0.freq: 1000
dev.cpu.0.temperature: 59.2C
dev.cpu.0.%parent: acpi0
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%location: handle=\_PR_.P000
dev.cpu.0.%driver: 

Re: issues with powerd/freq_levels

[Kevin Oberman]

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.

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
The first is really bogus to indicate "turbo" mode.

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.

Finally, the last case with power levels of -1 for all frequencies is
probably because the CPU manufacturer (Intel?) has not published this
information. For a while they were treating this as "proprietary"
information. Very annoying! It's always something that is not readily
available. Thi is one reason I suspect your CPUs are not identical.
--
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"

Re: issues with powerd/freq_levels

[Ian Smith]

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.

cheers, Ian
___
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 221050] emulators/virtualbox-ose: Bridged network doesn't work (11.1-RELEASE)

[bugzilla-noreply]

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

Marko Cupać  changed:

   What|Removed |Added

 CC||marko.cu...@mimar.rs

--- Comment #12 from Marko Cupać  ---
(In reply to Eugene Grosbein from comment #9)

Thank you for this information, as this updates my understanding that all the
packages for all the consequent minor releases are always built on an unpatched
initial major release.

Contrary to above concept, I have been building packages for minor releases on
latest binary patchlevels for these releases in poudriere, which resulted in
quite a number of complete rebuilds. I've been considering the idea to start
building everything on an unpatched 11.0-RELEASE poudriere jail. According to
this PR, it appears it's better not to.

-- 
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: Upgrade to 11.1-RELEASE fails to boot on aws EC2.

[Peter Ankerstål]

> On 28 Jul 2017, at 23:28, Peter Ankerstål  wrote:
> 
>> 
>>> On 28 Jul 2017, at 12:41, Peter Ankerstål  wrote:
>>> 
>>> Hi!
>>> 
>>> It seems that FreeBSD 11.1-RELEASE also breaks on EC2 in some cases. I had 
>>> this problem before when upgrading to 11.0. This problem was noticed in the 
>>> ERRATA: https://www.freebsd.org/releases/11.0R/errata.html#open-issues
>>> and later said to have been resolved with a EN: 
>>> https://www.freebsd.org/security/advisories/FreeBSD-EN-16:18.loader.asc
>>> 
>>> Today I tried to upgrade a 11.0-RELEASE-p7 system to 11.1-RELEASE using the 
>>> good old build world method as described in the handbook. But after reboot 
>>> the machine hangs
>>> in the loader. Reverting to a snapshot of / works fine but of course I have 
>>> a lot of problems due to kernel/world mismatch. So I tried to copy the old 
>>> /boot/ onto the newly updated
>>> system and then it actually gets past the loader. But then fails to boot 
>>> for some other reason unknown to me. (Because it does not give any video 
>>> output)
>>> 
>>> I have also posted to the forums about this with a few screenshots and more 
>>> details of what I have tried:
>>> https://forums.freebsd.org/threads/61780/
>>> 

I just installed a new VM and moved the data instead.



smime.p7s
Description: S/MIME cryptographic signature

issues with powerd/freq_levels

[Daniel Braniss]

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

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


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

so, any ideas as to what is going on?

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"

ZFS bootable pool detection code strictness

[Volodymyr Kostyrko]

Hi all.

First of all thank you for working on ZFS support. ZFS stability is 
unmatchable and I'm heavily relying on ZFS right now.


Last bootcode updates had given me some fun time. My pool contains some 
vdevs with skein enabled so new bootcode forced my pool out of boot. I 
know that my hands are dirty but I'm sure the pool is bootable as 
everything required for booting was never touched by unsupported options 
(I know the boot will fail instantly). Yes, I do like experimenting a lot.


From my point of view the code committed is just too strict locking out 
anyone who tries to play with extra pool properties. The analyzer itself 
is nice and I don't want it to go away as every extra bit of information 
about why boot may fail is precious but I'd be very happy to have some 
loader knob to disable the pool blacklisting so that the code will test 
the pool, will report everything it finds unsuitable but would allow a 
booting attempt.


Thanks in advance.

--
Sphinx of black quartz judge my vow.
___
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"