Re: Ryzen issues on FreeBSD ?

[Mike Tancsa]

On 1/19/2018 9:18 PM, Don Lewis wrote:
> On 19 Jan, Mike Tancsa wrote:
>> On 1/19/2018 5:45 PM, Don Lewis wrote:

 And it just hangs there. No segfaults, but it just hangs.

 A ctrl+t shows just shows

 load: 0.16  cmd: python2.7 65754 [usem] 589.51r 10.52u 1.63s 0% 122360k
 make: Working in: /usr/ports/net/samba47
>>>
>>> I sometimes seen build runaways when using poudriere to build my
>>> standard set of packages on my Ryzen machine.  I don't think this is a
>>> Ryzen-specific issue since I also see the same on older AMD FX-8320E
>>> machine, but much less frequently there.  It looks like a lost wakeup
>>> issue, but I haven't had a chance to dig into it yet.
>>
>> Odd, does this happen on Intel machines too ?
> 
> Unknown.  The last one of those I had was a Pentium III ...

it builds without issue on a couple of Intel boxes I tried.  The AMD one
is still stuck after 30 min at the same spot :(







-- 
---
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, m...@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada   http://www.tancsa.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: Ryzen issues on FreeBSD ?

[Don Lewis]

On 19 Jan, Mike Tancsa wrote:
> On 1/19/2018 5:29 PM, Don Lewis wrote:
>> On 19 Jan, Pete French wrote:
>>> Out of interest, is there anyone out there running Ryzen who *hasnt* 
>>> seen lockups ? I'd be curious if there a lot of lurkers thinking "mine 
>>> works fine"
>> 
>> No hangs or silent reboots here with either my original CPU or warranty
>> replacement once the shared page fix was in place.
> 
> 
> Hmmm, I wonder if I have a pair of the old CPUs (came from 2 different
> suppliers however).

The only real problem with the old CPUs is the random segfault problem
and some other random strangeness, like the lang/ghc build almost always
failing.

___
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: Ryzen issues on FreeBSD ?

[Don Lewis]

On 19 Jan, Mike Tancsa wrote:
> On 1/19/2018 6:16 PM, Don Lewis wrote:
>>>
>>> 0(ms-v1)# kldload amdtemp
>>> 0(ms-v1)# dmesg | tail -2
>>> ums0: at uhub0, port 3, addr 1 (disconnected)
>>> ums0: detached
>>> 0(ms-v1)#
>> 
>> What FreeBSD version are you running?  It looks like the amdtemp changes
>> for Ryzen are only in 12.0-CURRENT.   It looks like r323185 and r323195
>> need to be merged to stable/11.
> 
> releng11. It seems amdsmn is needed as well

That sounds right.

___
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: Ryzen issues on FreeBSD ?

[Don Lewis]

On 19 Jan, Mike Tancsa wrote:
> On 1/19/2018 5:45 PM, Don Lewis wrote:
>>>
>>> And it just hangs there. No segfaults, but it just hangs.
>>>
>>> A ctrl+t shows just shows
>>>
>>> load: 0.16  cmd: python2.7 65754 [usem] 589.51r 10.52u 1.63s 0% 122360k
>>> make: Working in: /usr/ports/net/samba47
>> 
>> I sometimes seen build runaways when using poudriere to build my
>> standard set of packages on my Ryzen machine.  I don't think this is a
>> Ryzen-specific issue since I also see the same on older AMD FX-8320E
>> machine, but much less frequently there.  It looks like a lost wakeup
>> issue, but I haven't had a chance to dig into it yet.
> 
> Odd, does this happen on Intel machines too ?

Unknown.  The last one of those I had was a Pentium III ...

___
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: Ryzen issues on FreeBSD ?

[Mike Tancsa]

On 1/19/2018 5:29 PM, Don Lewis wrote:
> On 19 Jan, Pete French wrote:
>> Out of interest, is there anyone out there running Ryzen who *hasnt* 
>> seen lockups ? I'd be curious if there a lot of lurkers thinking "mine 
>> works fine"
> 
> No hangs or silent reboots here with either my original CPU or warranty
> replacement once the shared page fix was in place.


Hmmm, I wonder if I have a pair of the old CPUs (came from 2 different
suppliers however).

---Mike


-- 
---
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, m...@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada   http://www.tancsa.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: Ryzen issues on FreeBSD ?

[Mike Tancsa]

On 1/19/2018 6:09 PM, Don Lewis wrote:
> 
> I just tried building samba47 here.  Top shows python spending a lot of
> time in that state and steadily growing in size, but forward progress
> does happen.  I got a successful build:
>   [00:07:54] [01] [00:06:31] Finished net/samba47 | samba47-4.7.4_1: Success
> 
> I'm currently running:
>   FreeBSD 12.0-CURRENT #0 r327261M: Wed Dec 27 22:44:16 PST 2017

RELENG11
FreeBSD ms-v1.sentex.ca 11.1-STABLE FreeBSD 11.1-STABLE #0 r328163: Fri
Jan 19 09:57:36 EST 2018

Still no luck building.

Its been stuck here for 20 min

[ 214/3804] Compiling source4/heimdal/lib/roken/estrdup.c
runner cc -pipe -g -ggdb -gdwarf-2 -gstrict-dwarf -DLIBICONV_PLUG
-fno-color-diagnostics -D_FUNCTION_DEF -g -fstack-protector
-DLDAP_DEPRECATED -fno-strict-aliasing -fno-omit-frame-pointer
-DSOCKET_WRAPPER_DISABLE=1 -D_SAMBA_HOSTCC_ -fPIC -D_REENTRANT
-D_POSIX_PTHREAD_SEMANTICS -DSTATIC_ROKEN_HOSTCC_MODULES=NULL
-DSTATIC_ROKEN_HOSTCC_MODULES_PROTO=extern void
__ROKEN_HOSTCC_dummy_module_proto(void) -MD
-Idefault/source4/heimdal_build -I../source4/heimdal_build
-Idefault/source4/heimdal/lib/roken -I../source4/heimdal/lib/roken
-Idefault/include/public -I../include/public -Idefault/source4
-I../source4 -Idefault/lib -I../lib -Idefault/source4/lib
-I../source4/lib -Idefault/source4/include -I../source4/include
-Idefault/include -I../include -Idefault/lib/replace -I../lib/replace
-Idefault -I.. -I/usr/local/include -I/usr/local/include -DLIBICONV_PLUG
-D_SAMBA_BUILD_=4 -DHAVE_CONFIG_H=1 -D_GNU_SOURCE=1
-D_XOPEN_SOURCE_EXTENDED=1 ../source4/heimdal/lib/roken/estrdup.c -c -o
default/source4/heimdal/lib/roken/estrdup_3.o


load: 0.11  cmd: python2.7 72089 [usem] 996.84r 10.84u 0.47s 0% 99788k
make: Working in: /usr/ports/net/samba47
make[1]: Working in: /usr/ports/net/samba47


-- 
---
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, m...@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada   http://www.tancsa.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: Ryzen issues on FreeBSD ?

[Mike Tancsa]

On 1/19/2018 6:16 PM, Don Lewis wrote:
>>
>> 0(ms-v1)# kldload amdtemp
>> 0(ms-v1)# dmesg | tail -2
>> ums0: at uhub0, port 3, addr 1 (disconnected)
>> ums0: detached
>> 0(ms-v1)#
> 
> What FreeBSD version are you running?  It looks like the amdtemp changes
> for Ryzen are only in 12.0-CURRENT.   It looks like r323185 and r323195
> need to be merged to stable/11.

releng11. It seems amdsmn is needed as well

---Mike

> 
> 


-- 
---
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, m...@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada   http://www.tancsa.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: Ryzen issues on FreeBSD ?

[Mike Tancsa]

On 1/19/2018 5:45 PM, Don Lewis wrote:
>>
>> And it just hangs there. No segfaults, but it just hangs.
>>
>> A ctrl+t shows just shows
>>
>> load: 0.16  cmd: python2.7 65754 [usem] 589.51r 10.52u 1.63s 0% 122360k
>> make: Working in: /usr/ports/net/samba47
> 
> I sometimes seen build runaways when using poudriere to build my
> standard set of packages on my Ryzen machine.  I don't think this is a
> Ryzen-specific issue since I also see the same on older AMD FX-8320E
> machine, but much less frequently there.  It looks like a lost wakeup
> issue, but I haven't had a chance to dig into it yet.

Odd, does this happen on Intel machines too ?

---Mike


-- 
---
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, m...@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada   http://www.tancsa.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: Ancient FreeBSD update path

[Bakul Shah]

On Fri, 19 Jan 2018 13:28:41 +0100 Andrea Brancatelli 
 wrote:
Andrea Brancatelli writes:
> Hello guys. 
> 
> I have a couple of ancient FreeBSD install that I have to bring into
> this century (read either 10.4 or 11.1) :-) 
> 
> I'm talking about a FreeBSD 8.0-RELEASE-p4 and a couple of FreeBSD
> 9.3-RELEASE-p53. 
> 
> What upgrade strategy would you suggest? 
> 
> Direct jump into the future (8 -> 11)? Progressive steps (8 -> 9 -> 10
> -> 11)? Boiling water on the HDs? :-) 
> 
> Thanks, any suggestion in more than welcome.

Incremental update will take a long time and if something gets
messed up in the middle, you will be much worse off. You may
also not find relevant packages any more for an EOLed release.
And you may have to solve problems that no longer exist on
newer packages.

What I would do is to make a backup of everything, make a list
of installed packages and config files, and do a fresh install
of the latest release. Then get the critical packages working.
Then add others as needed.

If possible do this on a separate machine so that you can
check config/program behavior on the original machine.  When
you are satisfied, either switch to the other machine or copy
things back to the original. When one of my computers was
starting to fall apart, I did this with an inexpensive used
thinkpad.

One more thing to consider: your ancient machine hardware may
need to be maintenance/repais/replacement.  A fully
operational second (temporary) machine gives you a chance to
try to do maintenace such as remove dust and cat hair
carefully, check fans and replace them if needed, replace
disks if older than 4 years, etc.
___
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: Ancient FreeBSD update path

[Don Lewis]

On 19 Jan, Mathieu Arnold wrote:
> On Fri, Jan 19, 2018 at 01:28:41PM +0100, Andrea Brancatelli wrote:
>> Hello guys. 
>> 
>> I have a couple of ancient FreeBSD install that I have to bring into
>> this century (read either 10.4 or 11.1) :-) 
>> 
>> I'm talking about a FreeBSD 8.0-RELEASE-p4 and a couple of FreeBSD
>> 9.3-RELEASE-p53. 
>> 
>> What upgrade strategy would you suggest? 
>> 
>> Direct jump into the future (8 -> 11)? Progressive steps (8 -> 9 -> 10
>> -> 11)? Boiling water on the HDs? :-) 
>> 
>> Thanks, any suggestion in more than welcome.
> 
> The *supported* upgrade strategy is to upgrade to the latest version of
> your current branch, and jump from latest version to latest version.  So
> 8.4 -> 9.3 -> 10.4 -> 11.1. (Note that you can stay at 10.4, it still is
> supported.)

Only until October 31, 2018.  At this point I'd go all the way to 11.1
to avoid going through the pain of another major OS version upgrade in
the nearish future.

___
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: Ryzen issues on FreeBSD ?

[Don Lewis]

On 19 Jan, Mike Tancsa wrote:
> On 1/19/2018 3:22 PM, Lucas Holt wrote:
>> I have an Asus Prime X370-pro and a Ryzen 7 1700 that I bought in late
> 
> Thanks! Thats the board I have, but no luck with amdtemp.  Did you have
> to change the source code for it to work ?
> 
> dmidecode shows
> 
> Manufacturer: ASUSTeK COMPUTER INC.
> Product Name: PRIME X370-PRO
> 
> Vendor: American Megatrends Inc.
> Version: 3402
> Release Date: 12/11/2017
> Address: 0xF
> Runtime Size: 64 kB
> ROM Size: 16 MB
> Characteristics:
> 
> memory is
> 
> Type: DDR4
> Type Detail: Synchronous Unbuffered (Unregistered)
> Speed: 2133 MT/s
> Manufacturer: Unknown
> Serial Number: 192BE196
> Asset Tag: Not Specified
> Part Number: CT16G4DFD824A.C16FHD
> Rank: 2
> Configured Clock Speed: 1067 MT/s
> Minimum Voltage: 1.2 V
> Maximum Voltage: 1.2 V
> Configured Voltage: 1.2 V
> 
> 
> 
> When I try and load the kld, I get nothing :(
> 
> 0(ms-v1)# kldload amdtemp
> 0(ms-v1)# dmesg | tail -2
> ums0: at uhub0, port 3, addr 1 (disconnected)
> ums0: detached
> 0(ms-v1)#

What FreeBSD version are you running?  It looks like the amdtemp changes
for Ryzen are only in 12.0-CURRENT.   It looks like r323185 and r323195
need to be merged to stable/11.

___
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: Ryzen issues on FreeBSD ?

[Don Lewis]

On 19 Jan, Mike Tancsa wrote:
> On 1/19/2018 3:48 PM, Peter Moody wrote:
>> 
>> weirdly enough though, with SMT enabled, building net/samba47 would
>> always hang (like compilation segfaults). with SMT disabled, no such
>> problems.
> 
> wow, thats so strange!  I just tried,and the same thing and see it as well.
> 
> [ 442/3804] Generating lib/ldb-samba/ldif_handlers_proto.h
> [ 443/3804] Generating source4/lib/registry/tools/common.h
> runner  /usr/local/bin/perl
> "/usr/ports/net/samba47/work/samba-4.7.4/source4/script/mkproto.pl"
> --srcdir=.. --builddir=. --public=/dev/null
> --private="default/lib/ldb-samba/ldif_handlers_proto.h"
> ../lib/ldb-samba/ldif_handlers.c ../lib/ldb-samba/ldb_matching_rules.c
> [ 444/3804] Generating source4/lib/registry/tests/proto.h
> runner  /usr/local/bin/perl
> "/usr/ports/net/samba47/work/samba-4.7.4/source4/script/mkproto.pl"
> --srcdir=.. --builddir=. --public=/dev/null
> --private="default/source4/lib/registry/tools/common.h"
> ../source4/lib/registry/tools/common.c
> 
> 
> And it just hangs there. No segfaults, but it just hangs.
> 
> A ctrl+t shows just shows
> 
> load: 0.16  cmd: python2.7 65754 [usem] 589.51r 10.52u 1.63s 0% 122360k
> make: Working in: /usr/ports/net/samba47

I just tried building samba47 here.  Top shows python spending a lot of
time in that state and steadily growing in size, but forward progress
does happen.  I got a successful build:
  [00:07:54] [01] [00:06:31] Finished net/samba47 | samba47-4.7.4_1: Success

I'm currently running:
  FreeBSD 12.0-CURRENT #0 r327261M: Wed Dec 27 22:44:16 PST 2017

___
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: Ryzen issues on FreeBSD ?

[Don Lewis]

On 19 Jan, Mike Tancsa wrote:
> On 1/19/2018 3:48 PM, Peter Moody wrote:
>> 
>> weirdly enough though, with SMT enabled, building net/samba47 would
>> always hang (like compilation segfaults). with SMT disabled, no such
>> problems.
> 
> wow, thats so strange!  I just tried,and the same thing and see it as well.
> 
> [ 442/3804] Generating lib/ldb-samba/ldif_handlers_proto.h
> [ 443/3804] Generating source4/lib/registry/tools/common.h
> runner  /usr/local/bin/perl
> "/usr/ports/net/samba47/work/samba-4.7.4/source4/script/mkproto.pl"
> --srcdir=.. --builddir=. --public=/dev/null
> --private="default/lib/ldb-samba/ldif_handlers_proto.h"
> ../lib/ldb-samba/ldif_handlers.c ../lib/ldb-samba/ldb_matching_rules.c
> [ 444/3804] Generating source4/lib/registry/tests/proto.h
> runner  /usr/local/bin/perl
> "/usr/ports/net/samba47/work/samba-4.7.4/source4/script/mkproto.pl"
> --srcdir=.. --builddir=. --public=/dev/null
> --private="default/source4/lib/registry/tools/common.h"
> ../source4/lib/registry/tools/common.c
> 
> 
> And it just hangs there. No segfaults, but it just hangs.
> 
> A ctrl+t shows just shows
> 
> load: 0.16  cmd: python2.7 65754 [usem] 589.51r 10.52u 1.63s 0% 122360k
> make: Working in: /usr/ports/net/samba47

I sometimes seen build runaways when using poudriere to build my
standard set of packages on my Ryzen machine.  I don't think this is a
Ryzen-specific issue since I also see the same on older AMD FX-8320E
machine, but much less frequently there.  It looks like a lost wakeup
issue, but I haven't had a chance to dig into it yet.

=>> Killing runaway build after 7200 seconds with no output
=>> Cleaning up wrkdir
===>  Cleaning for doxygen-1.8.13_1,2
=>> Warning: Leftover processes:
USER PID %CPU %MEM   VSZ   RSS TT  STAT STARTEDTIME COMMAND
nobody 55576  0.0  0.0 10556  1528  0  I+J  00:32   0:00.04 /usr/bin/make -C 
/usr/ports/devel/doxygen build
nobody 55625  0.0  0.0 11660  1952  0  I+J  00:32   0:00.00 - /bin/sh -e -c (cd 
/wrkdirs/usr/ports/devel/dox
ygen/work/.build; if ! /usr/bin/env 
XDG_DATA_HOME=/wrkdirs/usr/ports/devel/doxygen/work  XDG_CONFIG_HOME=/wr
kdirs/usr/ports/devel/doxygen/work  HOME=/wrkdirs/usr/ports/devel/doxygen/work 
TMPDIR="/tmp" PATH=/wrkdirs/u
sr/ports/devel/doxygen/work/.bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/nonexistent/b
in NO_PIE=yes MK_DEBUG_FILES=no MK_KERNEL_SYMBOLS=no SHELL=/bin/sh NO_LINT=YES 
PREFIX=/usr/local  LOCALBASE=
/usr/local  LIBDIR="/usr/lib"  CC="cc" CFLAGS="-O2 -pipe  -DLIBICONV_PLUG 
-fstack-protector -fno-strict-alia
sing"  CPP="cpp" CPPFLAGS="-DLIBICONV_PLUG"  LDFLAGS=" -fstack-protector" 
LIBS=""  CXX="c++" CXXFLAGS="-O2 -
pipe -DLIBICONV_PLUG -fstack-protector -fno-strict-aliasing  -DLIBICONV_PLUG"  
MANPREFIX="/usr/local" BSD_IN
STALL_PROGRAM="install  -s -m 555"  BSD_INSTALL_LIB="install  -s -m 0644"  
BSD_INSTALL_SCRIPT="install  -m 5
55"  BSD_INSTALL_DATA="install  -m 0644"  BSD_INSTALL_MAN="install  -m 444" 
/usr/bin/make -f Makefile   all
docs; then  if [ -n "" ] ; then  echo "===> Compilation failed unexpectedly.";  
(echo "") | /usr/bin/fmt 75
79 ;  fi;  false;  fi)
nobody 55636  0.0  0.0  9988  1108  0  I+J  00:32   0:00.01 `-- /usr/bin/make 
-f Makefile all docs
nobody  6734  0.0  0.0 10140  1216  0  I+J  00:42   0:00.00   `-- /usr/bin/make 
-f CMakeFiles/Makefile2 docs
nobody  6764  0.0  0.0 10140  1216  0  I+J  00:42   0:00.01 `-- 
/usr/bin/make -f CMakeFiles/Makefile2 do
c/CMakeFiles/docs.dir/all
nobody  7107  0.0  0.0 10512  1536  0  I+J  00:42   0:00.03   `-- 
/usr/bin/make -f examples/CMakeFiles/e
xamples.dir/build.make examples/CMakeFiles/examples.dir/build
nobody 12111  0.0  0.0 61468 27060  0  I+J  00:43   0:00.16 `-- 
../bin/doxygen diagrams.cfg
Killed
build of devel/doxygen | doxygen-1.8.13_1,2 ended at Sat Dec 30 18:44:47 PST 
2017
build time: 02:14:51
!!! build failure encountered !!!


___
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: Ryzen issues on FreeBSD ?

[Don Lewis]

On 19 Jan, Mike Tancsa wrote:
> On 1/19/2018 3:32 PM, Peter Moody wrote:
>> 
>> I have a ryzen5 1600X and an ASRock AB350M and I've tried just about
>> everything in all of these threads; disabling C state (no effect),
>> setting the sysctl (doesn't exist on my 11.1 RELEASE), tweaking
>> voltage and cooling settings, rma'ing the board the cpu and the
>> memory. nothing helped.
>> 
>> last night I tried disabling SMT and, so far so good.
> 
> 
> Is there anything that can be done to trigger the lockup more reliably ?
> I havent found any patterns. I have had lockups with the system is 100%
> idle and lockups when lightly loaded.  I have yet to see any segfaults
> or sig 11s while doing buildworld (make -j12 or make -j16 even)

I never seen the idle lockup problem here.  Prior to the shared page
fix, I could almost always trigger a system hang or silent reboot by
doing a parallel build of openjdk8.

___
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: Ryzen issues on FreeBSD ?

[Don Lewis]

On 19 Jan, Pete French wrote:
> Out of interest, is there anyone out there running Ryzen who *hasnt* 
> seen lockups ? I'd be curious if there a lot of lurkers thinking "mine 
> works fine"

No hangs or silent reboots here with either my original CPU or warranty
replacement once the shared page fix was in place.

___
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: Ancient FreeBSD update path

[Michael Sinatra]

On 1/19/18 4:59 AM, Mike Pumford wrote:

I've just done a 9.3 to 10.3 upgrade with freebsd-update and pkg. 
Networking wasn't avalable when the system was running 10.3 kernel with 
9.3 userland so I did that part of the update on the console.


I have run into this problem with 9.3 -> 10.x upgrades.  Basically, the 
old 9.3 ifconfig(8) breaks with the new 10.x kernel.


Even though it's not the supported method, I have had good luck running 
freebsd-update on a 9.3 system, installing the kernel and then 
immediately (no reboot) running `freebsd-update install` again to 
install userland.  *Then* reboot.  You should be able to complete the 
update (removing old files and updating ports/packages) without having 
to go to the console.


This method does not appear to be necessary for any upgrades other than 
9.3 -> 10.x.


michael

___
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: Ryzen issues on FreeBSD ?

[Mike Tancsa]

On 1/19/2018 4:27 PM, Peter Moody wrote:
>> And it just hangs there. No segfaults, but it just hangs.
> 
> yeah whoops, sorry. I had compilation segfaults on my mind b/c of the
> linked amd forums posts about gcc segfaults.
> 
> anyway, try disabling SMT and see if that helps .. ?
> 

Strange, still hangs, different location :(

[ 386/3804] HEIMDAL_GSSAPI_ASN1_PRIV_H:
bin/default/source4/heimdal/lib/gssapi/gssapi_asn1-priv.hx ->
bin/default/source4/heimdal/lib/gssapi/gssapi_asn1-priv.h
runner  cp default/source4/heimdal/lib/gssapi/gssapi_asn1-priv.hx
default/source4/heimdal/lib/gssapi/gssapi_asn1-priv.h




load: 19.29  cmd: make 79210 [wait] 301.89r 0.04u 0.00s 0% 1560k
make: Working in: /usr/ports/net/samba47
make[1]: Working in: /usr/ports/net/samba47


-- 
---
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, m...@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada   http://www.tancsa.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: Ryzen issues on FreeBSD ?

[Peter Moody]

On Fri, Jan 19, 2018 at 1:17 PM, Mike Tancsa  wrote:
> On 1/19/2018 3:48 PM, Peter Moody wrote:
>>
>> weirdly enough though, with SMT enabled, building net/samba47 would
>> always hang (like compilation segfaults). with SMT disabled, no such
>> problems.
>
> wow, thats so strange!  I just tried,and the same thing and see it as well.
>
> [ 442/3804] Generating lib/ldb-samba/ldif_handlers_proto.h
> [ 443/3804] Generating source4/lib/registry/tools/common.h
> runner  /usr/local/bin/perl
> "/usr/ports/net/samba47/work/samba-4.7.4/source4/script/mkproto.pl"
> --srcdir=.. --builddir=. --public=/dev/null
> --private="default/lib/ldb-samba/ldif_handlers_proto.h"
> ../lib/ldb-samba/ldif_handlers.c ../lib/ldb-samba/ldb_matching_rules.c
> [ 444/3804] Generating source4/lib/registry/tests/proto.h
> runner  /usr/local/bin/perl
> "/usr/ports/net/samba47/work/samba-4.7.4/source4/script/mkproto.pl"
> --srcdir=.. --builddir=. --public=/dev/null
> --private="default/source4/lib/registry/tools/common.h"
> ../source4/lib/registry/tools/common.c
>
>
> And it just hangs there. No segfaults, but it just hangs.

yeah whoops, sorry. I had compilation segfaults on my mind b/c of the
linked amd forums posts about gcc segfaults.

anyway, try disabling SMT and see if that helps .. ?

this seems to make parallel stuff perceptibly slower (like a make -j12
buildworld at the same time as make -j 12 in net/samba47), but at this
point I'm just happy with the relative stability.

> A ctrl+t shows just shows
>
> load: 0.16  cmd: python2.7 65754 [usem] 589.51r 10.52u 1.63s 0% 122360k
> make: Working in: /usr/ports/net/samba47
>
>
> ---Mike
>
>
>
> --
> ---
> Mike Tancsa, tel +1 519 651 3400
> Sentex Communications, m...@sentex.net
> Providing Internet services since 1994 www.sentex.net
> Cambridge, Ontario Canada   http://www.tancsa.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: Ryzen issues on FreeBSD ?

[Mike Tancsa]

On 1/19/2018 4:14 PM, Pete French wrote:
> To be honest this thread has put me off building my machine, the pile of
> boxes with motherboard, case, cpu and ram is still sitting next to me
> desk at work!

It is quite discouraging, isnt it :(  From my POV however, I really want
a "plan b" to Spectre / Meltdown that at least slows down attackers.  On
a few servers, I do have ways to detect after that fact intrusions
(tripwire etc), but I want to mitigate this attack from happening in the
first place as much as possible.  Supposedly Spectre exploits on AMD are
MUCH harder (or so says AMD at least) so I am hoping I can at least have
this as an option.  We even ordered a Tyan Epyc based board to see what
its like too.

---Mike



-- 
---
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, m...@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada   http://www.tancsa.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: Ryzen issues on FreeBSD ?

[Mike Tancsa]

On 1/19/2018 3:48 PM, Peter Moody wrote:
> 
> weirdly enough though, with SMT enabled, building net/samba47 would
> always hang (like compilation segfaults). with SMT disabled, no such
> problems.

wow, thats so strange!  I just tried,and the same thing and see it as well.

[ 442/3804] Generating lib/ldb-samba/ldif_handlers_proto.h
[ 443/3804] Generating source4/lib/registry/tools/common.h
runner  /usr/local/bin/perl
"/usr/ports/net/samba47/work/samba-4.7.4/source4/script/mkproto.pl"
--srcdir=.. --builddir=. --public=/dev/null
--private="default/lib/ldb-samba/ldif_handlers_proto.h"
../lib/ldb-samba/ldif_handlers.c ../lib/ldb-samba/ldb_matching_rules.c
[ 444/3804] Generating source4/lib/registry/tests/proto.h
runner  /usr/local/bin/perl
"/usr/ports/net/samba47/work/samba-4.7.4/source4/script/mkproto.pl"
--srcdir=.. --builddir=. --public=/dev/null
--private="default/source4/lib/registry/tools/common.h"
../source4/lib/registry/tools/common.c


And it just hangs there. No segfaults, but it just hangs.

A ctrl+t shows just shows

load: 0.16  cmd: python2.7 65754 [usem] 589.51r 10.52u 1.63s 0% 122360k
make: Working in: /usr/ports/net/samba47


---Mike



-- 
---
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, m...@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada   http://www.tancsa.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: Ryzen issues on FreeBSD ?

[Pete French]

Out of interest, is there anyone out there running Ryzen who *hasnt* 
seen lockups ? I'd be curious if there a lot of lurkers thinking "mine 
works fine"


To be honest this thread has put me off building my machine, the pile of 
boxes with motherboard, case, cpu and ram is still sitting next to me 
desk at work!


-pete.
___
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: Ryzen issues on FreeBSD ?

[Nimrod Levy]

I can try lowering my memory clock and see what happens.  I'm a little
skeptical because I have been able to run memtest with no errors for some
time.  I'm glad to give anything a try...


On Fri, Jan 19, 2018 at 3:49 PM Mike Tancsa  wrote:

> On 1/19/2018 3:23 PM, Ryan Root wrote:
> > This looks like the QVL list for your MB ->
> >
> http://download.gigabyte.us/FileList/Memory/mb_memory_ga-ax370-Gaming5.pdf
>
> Its an Asus MB, but the memory I have is in the above PDF list
>
> I dont see CT16G4DFD824A, but I do see other crucial products with
> slower clock speeds. Right now I do have it set to 2133 where as it was
> 2400 before.
>
> ---Mike
>
>
> >
> >
> > On 1/19/2018 12:13 PM, Mike Tancsa wrote:
> >> Drag :( I have mine disabled as well as lowering the RAM freq to 2100
> >> from 2400.  For me the hangs are infrequent.  Its only been a day and a
> >> half, so not sure if its gone or I have been "lucky"... Either ways,
> >> this platform feels way too fragile to deploy on anything :(
> >>
> >>  ---Mike
> >>
> >> On 1/19/2018 3:08 PM, Nimrod Levy wrote:
> >>> Looks like disabling the C- states in the bios didn't change anything.
> >>>
> >>> On Wed, Jan 17, 2018 at 9:22 PM Nimrod Levy  >>> > wrote:
> >>>
> >>> That looks promising. I just found that seeing in the bios and
> >>> disabled it. I'll see how it runs.
> >>>
> >>> Thanks
> >>>
> >>>
> >>> On Wed, Jan 17, 2018, 18:38 Don Lewis  >>> > wrote:
> >>>
> >>> On 17 Jan, Nimrod Levy wrote:
> >>> > I'm running 11-STABLE from 12/9.  amdtemp works for me.  It
> >>> also has the
> >>> > systl indicating that it it has the shared page fix. I'm
> >>> pretty sure I've
> >>> > seen the lockups since then.  I'll update to the latest
> STABLE
> >>> and see
> >>> > what  happens.
> >>> >
> >>> > One weird thing about my experience is that if I keep
> >>> something running
> >>> > continuously like the distributed.net <
> http://distributed.net>
> >>> client on 6 of 12 possible threads,
> >>> > it keeps the system up for MUCH longer than without.  This is
> >>> a home server
> >>> > and very lightly loaded (one could argue insanely overpowered
> >>> for the use
> >>> > case).
> >>>
> >>> This sounds like the problem with the deep Cx states that has
> been
> >>> reported by numerous Linux users.  I think some motherboard
> >>> brands are
> >>> more likely to have the problem.  See:
> >>>
> http://forum.asrock.com/forum_posts.asp?TID=5963=taichi-x370-with-ubuntu-idle-lock-ups-idle-freeze
> >>>
> >>> --
> >>>
> >>> --
> >>> Nimrod
> >>>
> >>>
> >>>
> >>> --
> >>>
> >>> --
> >>> Nimrod
> >>>
> >>
> >
> >
> > ___
> > 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
> "
> >
> >
>
>
> --
> ---
> Mike Tancsa, tel +1 519 651 3400 <(519)%20651-3400>
> Sentex Communications, m...@sentex.net
> Providing Internet services since 1994 www.sentex.net
> Cambridge, Ontario Canada   http://www.tancsa.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"
>


-- 

--
Nimrod
___
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: Ryzen issues on FreeBSD ?

[Peter Moody]

On Fri, Jan 19, 2018 at 12:39 PM, Mike Tancsa  wrote:
> On 1/19/2018 3:32 PM, Peter Moody wrote:
>>
>> I have a ryzen5 1600X and an ASRock AB350M and I've tried just about
>> everything in all of these threads; disabling C state (no effect),
>> setting the sysctl (doesn't exist on my 11.1 RELEASE), tweaking
>> voltage and cooling settings, rma'ing the board the cpu and the
>> memory. nothing helped.
>>
>> last night I tried disabling SMT and, so far so good.
>
>
> Is there anything that can be done to trigger the lockup more reliably ?
> I havent found any patterns. I have had lockups with the system is 100%
> idle and lockups when lightly loaded.  I have yet to see any segfaults
> or sig 11s while doing buildworld (make -j12 or make -j16 even)

"reliably" trigger the lockup, no.

The general pattern was high load followed by low load would lock up;
so a couple 'make -j 32 buildworld' would almost always result in a
lock up a few hours after the last one completes.

weirdly enough though, with SMT enabled, building net/samba47 would
always hang (like compilation segfaults). with SMT disabled, no such
problems.

> ---Mike
>
___
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: Ryzen issues on FreeBSD ?

[Mike Tancsa]

On 1/19/2018 3:23 PM, Ryan Root wrote:
> This looks like the QVL list for your MB ->
> http://download.gigabyte.us/FileList/Memory/mb_memory_ga-ax370-Gaming5.pdf

Its an Asus MB, but the memory I have is in the above PDF list

I dont see CT16G4DFD824A, but I do see other crucial products with
slower clock speeds. Right now I do have it set to 2133 where as it was
2400 before.

---Mike


> 
> 
> On 1/19/2018 12:13 PM, Mike Tancsa wrote:
>> Drag :( I have mine disabled as well as lowering the RAM freq to 2100
>> from 2400.  For me the hangs are infrequent.  Its only been a day and a
>> half, so not sure if its gone or I have been "lucky"... Either ways,
>> this platform feels way too fragile to deploy on anything :(
>>
>>  ---Mike
>>
>> On 1/19/2018 3:08 PM, Nimrod Levy wrote:
>>> Looks like disabling the C- states in the bios didn't change anything. 
>>>
>>> On Wed, Jan 17, 2018 at 9:22 PM Nimrod Levy >> > wrote:
>>>
>>> That looks promising. I just found that seeing in the bios and
>>> disabled it. I'll see how it runs.
>>>
>>> Thanks
>>>
>>>
>>> On Wed, Jan 17, 2018, 18:38 Don Lewis >> > wrote:
>>>
>>> On 17 Jan, Nimrod Levy wrote:
>>> > I'm running 11-STABLE from 12/9.  amdtemp works for me.  It
>>> also has the
>>> > systl indicating that it it has the shared page fix. I'm
>>> pretty sure I've
>>> > seen the lockups since then.  I'll update to the latest STABLE
>>> and see
>>> > what  happens.
>>> >
>>> > One weird thing about my experience is that if I keep
>>> something running
>>> > continuously like the distributed.net 
>>> client on 6 of 12 possible threads,
>>> > it keeps the system up for MUCH longer than without.  This is
>>> a home server
>>> > and very lightly loaded (one could argue insanely overpowered
>>> for the use
>>> > case).
>>>
>>> This sounds like the problem with the deep Cx states that has been
>>> reported by numerous Linux users.  I think some motherboard
>>> brands are
>>> more likely to have the problem.  See:
>>> 
>>> http://forum.asrock.com/forum_posts.asp?TID=5963=taichi-x370-with-ubuntu-idle-lock-ups-idle-freeze
>>>
>>> -- 
>>>
>>> --
>>> Nimrod
>>>
>>>
>>>
>>> -- 
>>>
>>> --
>>> Nimrod
>>>
>>
> 
> 
> ___
> 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"
> 
> 


-- 
---
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, m...@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada   http://www.tancsa.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: Ryzen issues on FreeBSD ?

[Mike Tancsa]

On 1/19/2018 3:32 PM, Peter Moody wrote:
> 
> I have a ryzen5 1600X and an ASRock AB350M and I've tried just about
> everything in all of these threads; disabling C state (no effect),
> setting the sysctl (doesn't exist on my 11.1 RELEASE), tweaking
> voltage and cooling settings, rma'ing the board the cpu and the
> memory. nothing helped.
> 
> last night I tried disabling SMT and, so far so good.


Is there anything that can be done to trigger the lockup more reliably ?
I havent found any patterns. I have had lockups with the system is 100%
idle and lockups when lightly loaded.  I have yet to see any segfaults
or sig 11s while doing buildworld (make -j12 or make -j16 even)

---Mike

___
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: Ryzen issues on FreeBSD ?

[Lucas Holt]

We have the same bios version.

I have corsair RAM

Handle 0x003B, DMI type 17, 40 bytes
Memory Device
Array Handle: 0x0032
Error Information Handle: 0x003A
Total Width: 64 bits
Data Width: 64 bits
Size: 16384 MB
Form Factor: DIMM
Set: None
Locator: DIMM_A2
Bank Locator: BANK 1
Type: 
Type Detail: Synchronous Unbuffered (Unregistered)
Speed: 2666 MHz
Manufacturer: Unknown
Serial Number: 
Asset Tag: Not Specified
Part Number: CMK32GX4M2A2666C16
Rank: 2
Configured Clock Speed: 1333 MHz
Minimum voltage:  1.200 V
Maximum voltage:  1.200 V
Configured voltage:  1.200 V


I just double checked and amdtemp isn't working correctly.  I was 
probably thinking of my other system which has an FX 8350.


Luke
___
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: Ryzen issues on FreeBSD ?

[Peter Moody]

On Fri, Jan 19, 2018 at 12:13 PM, Mike Tancsa  wrote:
> Drag :( I have mine disabled as well as lowering the RAM freq to 2100
> from 2400.  For me the hangs are infrequent.  Its only been a day and a
> half, so not sure if its gone or I have been "lucky"... Either ways,
> this platform feels way too fragile to deploy on anything :(
>
> ---Mike
>
> On 1/19/2018 3:08 PM, Nimrod Levy wrote:
>> Looks like disabling the C- states in the bios didn't change anything.

it's too early for me to be 100% certain, but disabling SMT in the
bios has thus far resulted in a more stable system.

I have a ryzen5 1600X and an ASRock AB350M and I've tried just about
everything in all of these threads; disabling C state (no effect),
setting the sysctl (doesn't exist on my 11.1 RELEASE), tweaking
voltage and cooling settings, rma'ing the board the cpu and the
memory. nothing helped.

last night I tried disabling SMT and, so far so good.


>> On Wed, Jan 17, 2018 at 9:22 PM Nimrod Levy > > wrote:
>>
>> That looks promising. I just found that seeing in the bios and
>> disabled it. I'll see how it runs.
>>
>> Thanks
>>
>>
>> On Wed, Jan 17, 2018, 18:38 Don Lewis > > wrote:
>>
>> On 17 Jan, Nimrod Levy wrote:
>> > I'm running 11-STABLE from 12/9.  amdtemp works for me.  It
>> also has the
>> > systl indicating that it it has the shared page fix. I'm
>> pretty sure I've
>> > seen the lockups since then.  I'll update to the latest STABLE
>> and see
>> > what  happens.
>> >
>> > One weird thing about my experience is that if I keep
>> something running
>> > continuously like the distributed.net 
>> client on 6 of 12 possible threads,
>> > it keeps the system up for MUCH longer than without.  This is
>> a home server
>> > and very lightly loaded (one could argue insanely overpowered
>> for the use
>> > case).
>>
>> This sounds like the problem with the deep Cx states that has been
>> reported by numerous Linux users.  I think some motherboard
>> brands are
>> more likely to have the problem.  See:
>> 
>> http://forum.asrock.com/forum_posts.asp?TID=5963=taichi-x370-with-ubuntu-idle-lock-ups-idle-freeze
>>
>> --
>>
>> --
>> Nimrod
>>
>>
>>
>> --
>>
>> --
>> Nimrod
>>
>
>
> --
> ---
> Mike Tancsa, tel +1 519 651 3400
> Sentex Communications, m...@sentex.net
> Providing Internet services since 1994 www.sentex.net
> Cambridge, Ontario Canada   http://www.tancsa.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"
___
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: Ryzen issues on FreeBSD ?

[Ryan Root]

Have you double checked the qualified vendors list data for your
motherboard.  Sometimes memory chips not on the list will work as it's
probably only a list of ones they've tested but it might be the problem
in this situation.  If that was already brought up by someone else sorry
for butting in.

This looks like the QVL list for your MB ->
http://download.gigabyte.us/FileList/Memory/mb_memory_ga-ax370-Gaming5.pdf


On 1/19/2018 12:13 PM, Mike Tancsa wrote:
> Drag :( I have mine disabled as well as lowering the RAM freq to 2100
> from 2400.  For me the hangs are infrequent.  Its only been a day and a
> half, so not sure if its gone or I have been "lucky"... Either ways,
> this platform feels way too fragile to deploy on anything :(
>
>   ---Mike
>
> On 1/19/2018 3:08 PM, Nimrod Levy wrote:
>> Looks like disabling the C- states in the bios didn't change anything. 
>>
>> On Wed, Jan 17, 2018 at 9:22 PM Nimrod Levy > > wrote:
>>
>> That looks promising. I just found that seeing in the bios and
>> disabled it. I'll see how it runs.
>>
>> Thanks
>>
>>
>> On Wed, Jan 17, 2018, 18:38 Don Lewis > > wrote:
>>
>> On 17 Jan, Nimrod Levy wrote:
>> > I'm running 11-STABLE from 12/9.  amdtemp works for me.  It
>> also has the
>> > systl indicating that it it has the shared page fix. I'm
>> pretty sure I've
>> > seen the lockups since then.  I'll update to the latest STABLE
>> and see
>> > what  happens.
>> >
>> > One weird thing about my experience is that if I keep
>> something running
>> > continuously like the distributed.net 
>> client on 6 of 12 possible threads,
>> > it keeps the system up for MUCH longer than without.  This is
>> a home server
>> > and very lightly loaded (one could argue insanely overpowered
>> for the use
>> > case).
>>
>> This sounds like the problem with the deep Cx states that has been
>> reported by numerous Linux users.  I think some motherboard
>> brands are
>> more likely to have the problem.  See:
>> 
>> http://forum.asrock.com/forum_posts.asp?TID=5963=taichi-x370-with-ubuntu-idle-lock-ups-idle-freeze
>>
>> -- 
>>
>> --
>> Nimrod
>>
>>
>>
>> -- 
>>
>> --
>> Nimrod
>>
>


___
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: Ryzen issues on FreeBSD ?

[Mike Tancsa]

On 1/19/2018 3:22 PM, Lucas Holt wrote:
> I have an Asus Prime X370-pro and a Ryzen 7 1700 that I bought in late

Thanks! Thats the board I have, but no luck with amdtemp.  Did you have
to change the source code for it to work ?

dmidecode shows

Manufacturer: ASUSTeK COMPUTER INC.
Product Name: PRIME X370-PRO

Vendor: American Megatrends Inc.
Version: 3402
Release Date: 12/11/2017
Address: 0xF
Runtime Size: 64 kB
ROM Size: 16 MB
Characteristics:

memory is

Type: DDR4
Type Detail: Synchronous Unbuffered (Unregistered)
Speed: 2133 MT/s
Manufacturer: Unknown
Serial Number: 192BE196
Asset Tag: Not Specified
Part Number: CT16G4DFD824A.C16FHD
Rank: 2
Configured Clock Speed: 1067 MT/s
Minimum Voltage: 1.2 V
Maximum Voltage: 1.2 V
Configured Voltage: 1.2 V



When I try and load the kld, I get nothing :(

0(ms-v1)# kldload amdtemp
0(ms-v1)# dmesg | tail -2
ums0: at uhub0, port 3, addr 1 (disconnected)
ums0: detached
0(ms-v1)#



> April.  Make sure you have the latest BIOS for these boards or else it
> will randomly freak out.
> 
> While i haven't used it much with FreeBSD, I can confirm that I had a
> lot of stability issues solved with a December BIOS update on
> MidnightBSD. I back ported the shared page fix and amdtemp.  (it's
> basically FreeBSD 9.1)
> 
> I couldn't even get it to boot until the August BIOS update.  I've had
> my box stay up at least a week, and it's my primary development box so
> I'm mostly doing src/ports builds all the time on it.
> 
> If you have the latest BIOS, check the memory timings too.  It's rather
> picky with some memory modules.
> 
> Luke
> 
> 


-- 
---
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, m...@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada   http://www.tancsa.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: Ryzen issues on FreeBSD ?

[Lucas Holt]

I have an Asus Prime X370-pro and a Ryzen 7 1700 that I bought in late 
April.  Make sure you have the latest BIOS for these boards or else it 
will randomly freak out.


While i haven't used it much with FreeBSD, I can confirm that I had a 
lot of stability issues solved with a December BIOS update on 
MidnightBSD. I back ported the shared page fix and amdtemp.  (it's 
basically FreeBSD 9.1)


I couldn't even get it to boot until the August BIOS update.  I've had 
my box stay up at least a week, and it's my primary development box so 
I'm mostly doing src/ports builds all the time on it.


If you have the latest BIOS, check the memory timings too.  It's rather 
picky with some memory modules.


Luke
___
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: Ryzen issues on FreeBSD ?

[Mike Tancsa]

Drag :( I have mine disabled as well as lowering the RAM freq to 2100
from 2400.  For me the hangs are infrequent.  Its only been a day and a
half, so not sure if its gone or I have been "lucky"... Either ways,
this platform feels way too fragile to deploy on anything :(

---Mike

On 1/19/2018 3:08 PM, Nimrod Levy wrote:
> Looks like disabling the C- states in the bios didn't change anything. 
> 
> On Wed, Jan 17, 2018 at 9:22 PM Nimrod Levy  > wrote:
> 
> That looks promising. I just found that seeing in the bios and
> disabled it. I'll see how it runs.
> 
> Thanks
> 
> 
> On Wed, Jan 17, 2018, 18:38 Don Lewis  > wrote:
> 
> On 17 Jan, Nimrod Levy wrote:
> > I'm running 11-STABLE from 12/9.  amdtemp works for me.  It
> also has the
> > systl indicating that it it has the shared page fix. I'm
> pretty sure I've
> > seen the lockups since then.  I'll update to the latest STABLE
> and see
> > what  happens.
> >
> > One weird thing about my experience is that if I keep
> something running
> > continuously like the distributed.net 
> client on 6 of 12 possible threads,
> > it keeps the system up for MUCH longer than without.  This is
> a home server
> > and very lightly loaded (one could argue insanely overpowered
> for the use
> > case).
> 
> This sounds like the problem with the deep Cx states that has been
> reported by numerous Linux users.  I think some motherboard
> brands are
> more likely to have the problem.  See:
> 
> http://forum.asrock.com/forum_posts.asp?TID=5963=taichi-x370-with-ubuntu-idle-lock-ups-idle-freeze
> 
> -- 
> 
> --
> Nimrod
> 
> 
> 
> -- 
> 
> --
> Nimrod
> 


-- 
---
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, m...@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada   http://www.tancsa.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: Ryzen issues on FreeBSD ?

[Nimrod Levy]

Looks like disabling the C- states in the bios didn't change anything.

On Wed, Jan 17, 2018 at 9:22 PM Nimrod Levy  wrote:

> That looks promising. I just found that seeing in the bios and disabled
> it. I'll see how it runs.
>
> Thanks
>
>
> On Wed, Jan 17, 2018, 18:38 Don Lewis  wrote:
>
>> On 17 Jan, Nimrod Levy wrote:
>> > I'm running 11-STABLE from 12/9.  amdtemp works for me.  It also has the
>> > systl indicating that it it has the shared page fix. I'm pretty sure
>> I've
>> > seen the lockups since then.  I'll update to the latest STABLE and see
>> > what  happens.
>> >
>> > One weird thing about my experience is that if I keep something running
>> > continuously like the distributed.net client on 6 of 12 possible
>> threads,
>> > it keeps the system up for MUCH longer than without.  This is a home
>> server
>> > and very lightly loaded (one could argue insanely overpowered for the
>> use
>> > case).
>>
>> This sounds like the problem with the deep Cx states that has been
>> reported by numerous Linux users.  I think some motherboard brands are
>> more likely to have the problem.  See:
>>
>> http://forum.asrock.com/forum_posts.asp?TID=5963=taichi-x370-with-ubuntu-idle-lock-ups-idle-freeze
>>
>> --
>
> --
> Nimrod
>


-- 

--
Nimrod
___
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: Ancient FreeBSD update path

[Miroslav Lachman]

Kurt Jaeger wrote on 2018/01/19 15:24:

Hi!


I have a couple of ancient FreeBSD install that I have to bring into
this century (read either 10.4 or 11.1) :-)

I'm talking about a FreeBSD 8.0-RELEASE-p4 and a couple of FreeBSD
9.3-RELEASE-p53.

What upgrade strategy would you suggest?


The best way is to update stepwise using freebsd-update, so:

8.0 -> 8.3 -> 9.1 -> 9.3 -> 10.1 -> 10.3


I would recommend source upgrade instead of binary freebsd-update. It is 
more predictable then freebsd-update if you are updating sooo old system



Direct jump into the future (8 -> 11)? Progressive steps (8 -> 9 -> 10
-> 11)? Boiling water on the HDs? :-)


Stepwise. Huge jumps have too many rough edges.


I did upgrade from 8.4 to 10.2 or 10.3, not sure. There was some make 
warning in make installworld phase so I did "make installworld" twice to 
be sure everything is OK.


There is (maybe) simpler way - download (or create own) tar balls of 
base and kernel of your target version (10.4 or 11.1), unpack it over 
old system (in single user) then you can use make delete-old if you will 
have /usr/src with updated source.


Miroslav Lachman
___
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: Ancient FreeBSD update path

[Mathieu Arnold]

On Fri, Jan 19, 2018 at 01:28:41PM +0100, Andrea Brancatelli wrote:
> Hello guys. 
> 
> I have a couple of ancient FreeBSD install that I have to bring into
> this century (read either 10.4 or 11.1) :-) 
> 
> I'm talking about a FreeBSD 8.0-RELEASE-p4 and a couple of FreeBSD
> 9.3-RELEASE-p53. 
> 
> What upgrade strategy would you suggest? 
> 
> Direct jump into the future (8 -> 11)? Progressive steps (8 -> 9 -> 10
> -> 11)? Boiling water on the HDs? :-) 
> 
> Thanks, any suggestion in more than welcome.

The *supported* upgrade strategy is to upgrade to the latest version of
your current branch, and jump from latest version to latest version.  So
8.4 -> 9.3 -> 10.4 -> 11.1. (Note that you can stay at 10.4, it still is
supported.)

-- 
Mathieu Arnold


signature.asc
Description: PGP signature

Re: Ancient FreeBSD update path

[Freddie Cash]

On Fri, Jan 19, 2018 at 4:28 AM, Andrea Brancatelli <
abrancate...@schema31.it> wrote:

> Hello guys.
>
> I have a couple of ancient FreeBSD install that I have to bring into
> this century (read either 10.4 or 11.1) :-)
>
> I'm talking about a FreeBSD 8.0-RELEASE-p4 and a couple of FreeBSD
> 9.3-RELEASE-p53.
>
> What upgrade strategy would you suggest?
>
> Direct jump into the future (8 -> 11)? Progressive steps (8 -> 9 -> 10
> -> 11)? Boiling water on the HDs? :-)
>

​I like to do it in steps.  It takes longer, but the results tend to be
better.

8.0 --> last 8.x release --> 9.0 --> last 9.x release --> 10.0 --> last
10.x release --> 11.0 --> last 11.x release

Backup /usr/local/etc and any other configuration files that are strewn
about.  Then format/delete /usr/ports/* and /usr/local/* and install the
ports/packages you need.

Of course, for something that ancient, it would probably be faster/better
to just backup the config files, format the drives, and install 11.1 from
scratch.  :)


-- 
Freddie Cash
fjwc...@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: Ancient FreeBSD update path

[Kurt Jaeger]

Hi!

> I have a couple of ancient FreeBSD install that I have to bring into
> this century (read either 10.4 or 11.1) :-) 
> 
> I'm talking about a FreeBSD 8.0-RELEASE-p4 and a couple of FreeBSD
> 9.3-RELEASE-p53. 
> 
> What upgrade strategy would you suggest? 

The best way is to update stepwise using freebsd-update, so:

8.0 -> 8.3 -> 9.1 -> 9.3 -> 10.1 -> 10.3

> Direct jump into the future (8 -> 11)? Progressive steps (8 -> 9 -> 10
> -> 11)? Boiling water on the HDs? :-) 

Stepwise. Huge jumps have too many rough edges.

-- 
p...@opsec.eu+49 171 3101372 2 years to go !
___
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: Ancient FreeBSD update path

[Mike Pumford]

On 19/01/2018 12:28, Andrea Brancatelli wrote:

Hello guys.

I have a couple of ancient FreeBSD install that I have to bring into
this century (read either 10.4 or 11.1) :-)

I'm talking about a FreeBSD 8.0-RELEASE-p4 and a couple of FreeBSD
9.3-RELEASE-p53.

I've just done a 9.3 to 10.3 upgrade with freebsd-update and pkg. 
Networking wasn't avalable when the system was running 10.3 kernel with 
9.3 userland so I did that part of the update on the console.


That system started life as a FreeBSD 5.x system and got left to rot at 
that version for a long time because it was an internal system with no 
external security exposure. I gradually upgraded it (using source 
builds) from major version to major version until I got to 9.3 and then 
did the 9.3 to 10.3 as a binary upgrade.


Only other trap I fell into with was packages. The system uses ldap for 
auth although fortunately it does have some local network accessible 
accounts. ldap auth was broken until I did the package update as the 9.3 
pam_ldap modules caused SSH to delay password based authentication and 
the auth processes seg-faulted.



What upgrade strategy would you suggest?

Direct jump into the future (8 -> 11)? Progressive steps (8 -> 9 -> 10
-> 11)? Boiling water on the HDs? :-)

If freebsd-update will do an upgrade from 8 to 10 or 8 to 11 and you 
have console access it ought to work. The upgrade process can be rolled 
back if the system doesn't like the new kernel for some reason and 
nothing gets installed anywhere else until the second stage of the 
upgrade. I'd probably go via 8->9.3->10/11 as those are the upgrade 
paths that were well tested.


Also don't forget the full system backups before starting. :)

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

Ancient FreeBSD update path

[Andrea Brancatelli]

Hello guys. 

I have a couple of ancient FreeBSD install that I have to bring into
this century (read either 10.4 or 11.1) :-) 

I'm talking about a FreeBSD 8.0-RELEASE-p4 and a couple of FreeBSD
9.3-RELEASE-p53. 

What upgrade strategy would you suggest? 

Direct jump into the future (8 -> 11)? Progressive steps (8 -> 9 -> 10
-> 11)? Boiling water on the HDs? :-) 

Thanks, any suggestion in more than welcome.

-- 

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