Re: Slow boot with 256GB of RAM?

2013-11-21 Thread Ed Maste
On 16 November 2013 17:49, Eitan Adler li...@eitanadler.com wrote:
 On Sat, Nov 16, 2013 at 4:12 PM, Zach Crum crum.z...@gmail.com wrote:
 This setting is not listed in /boot/defaults/loader.conf. Is it supposed to
 be singular or plural?

 Plural.

 I will commit the patch.

The FAQ update patch looks fine.

 Does any know of cases where this memory test actually catches errors?
  How important is it?

The boot time test is primarily of historical significance, and
doesn't really provide value on contemporary systems.  It's mainly a
workaround for ancient broken BIOSes that might return bogus memory
map data.  I intend to commit the patch below that disables it by
default.

The variable name is hw.memtest.tests as it's intended to be
extended to a bitmap of tests to run at boot, with other bits
representing more comprehensive tests.

-Ed

commit 58f501f70427ce2aeb9c8b18d2b7bec543818dae
Author: Ed Maste ema...@freebsd.org
Date:   Thu Nov 21 12:31:06 2013 -0500

Disable amd64 boot time memory test by default

The page presence memory test takes a long time on large memory systems
and has little value on contemporary amd64 hardware.

diff --git a/sys/amd64/amd64/machdep.c b/sys/amd64/amd64/machdep.c
index 7f05d58..df03e55 100644
--- a/sys/amd64/amd64/machdep.c
+++ b/sys/amd64/amd64/machdep.c
@@ -1476,13 +1476,15 @@ getmemsize(caddr_t kmdp, u_int64_t first)
Maxmem = atop(physmem_tunable);

/*
-* By default enable the memory test on real hardware, and disable
-* it if we appear to be running in a VM.  This avoids touching all
-* pages unnecessarily, which doesn't matter on real hardware but is
-* bad for shared VM hosts.  Use a general name so that
-* one could eventually do more with the code than just disable it.
+* The boot memory test is disabled by default, as it takes a
+* significant amount of time on large-memory systems, and is
+* unfriendly to virtual machines as it unnecessarily touches all
+* pages.
+*
+* A general name is used as the code may be extended to support
+* additional tests beyond the current page present test.
 */
-   memtest = (vm_guest  VM_GUEST_NO) ? 0 : 1;
+   memtest = 0;
TUNABLE_ULONG_FETCH(hw.memtest.tests, memtest);

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


Re: Slow boot with 256GB of RAM?

2013-11-21 Thread Eitan Adler
On Thu, Nov 21, 2013 at 12:42 PM, Ed Maste ema...@freebsd.org wrote:
 The variable name is hw.memtest.tests as it's intended to be
 extended to a bitmap of tests to run at boot, with other bits
 representing more comprehensive tests.

 -Ed

 commit 58f501f70427ce2aeb9c8b18d2b7bec543818dae
 Author: Ed Maste ema...@freebsd.org
 Date:   Thu Nov 21 12:31:06 2013 -0500

 Disable amd64 boot time memory test by default

 The page presence memory test takes a long time on large memory systems
 and has little value on contemporary amd64 hardware.

This patch looks good to me.  Please commit it. :)
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Slow boot with 256GB of RAM?

2013-11-16 Thread Darren Pilgrim
At the risk of facetiousness, the nice thing about FreeBSD is that you 
have to deal with this problem only a few times per year. ;)


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


Re: Slow boot with 256GB of RAM?

2013-11-16 Thread Allan Jude
On 2013-11-16 00:48, Matthias Petermann wrote:
 Hello James,

 Am 16.11.2013 05:37, schrieb James R. Van Artsdalen:
  Asus Z9PA-U8 motherboard, 256GB of RAM, 2.4 GHz Xeon E5-2695 v2,
  FreeBSD 11.0-CURRENT r258092

  There is a two minute pause when booting, after the loader's SMAP
  display and the initial kernel output,

  Does anyone know what's going on here?  Even that much RAM
  shouldn't take that much time to clear.

 in an earlier discussion at FreeBSD Forums[1] it looks like this is
 related to some early stage memory test which is performed.

 It can be disabled by adding

 hw.memtest.tests=0

 to /boot/loader.conf. For my 32GB machine this helped.


 Best regards,
 Matthias


 [1] http://forums.freebsd.org/showthread.php?t=12705


I see this was in the release notes for 9.0 and 8.3, but other than
that, I don't see how anyone was supposed to find out about this

Maybe it would make sense to print 'Starting memory test, set
hw.memtest.test=0 to disable' before that starts, so anyone stuck
waiting will have a hint about what to do.


-- 
Allan Jude




signature.asc
Description: OpenPGP digital signature


Re: Slow boot with 256GB of RAM?

2013-11-16 Thread James R. Van Artsdalen
On 11/16/2013 8:52 AM, Allan Jude wrote:
 I see this was in the release notes for 9.0 and 8.3, but other than
 that, I don't see how anyone was supposed to find out about this. 
 Maybe it would make sense to print 'Starting memory test, set
 hw.memtest.test=0 to disable' before that starts, so anyone stuck
 waiting will have a hint about what to do. 

It takes less effort to speed it up than to document that it is slow.. 
For now, in my sources, I've lengthened the testing stride to 64KB.

A better fix would leave the cache on (don't fight the cache in a memory
test - it is your friend! :-) and to group all writes and reads
together  in a larger chunk - say 16MB - so as to take advantage of
write combining and cache line fetching.  And add writes of
address-specific values so address space aliasing can be detected.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Slow boot with 256GB of RAM?

2013-11-16 Thread Allan Jude
On 2013-11-16 13:36, James R. Van Artsdalen wrote:
 On 11/16/2013 8:52 AM, Allan Jude wrote:
 I see this was in the release notes for 9.0 and 8.3, but other than
 that, I don't see how anyone was supposed to find out about this. 
 Maybe it would make sense to print 'Starting memory test, set
 hw.memtest.test=0 to disable' before that starts, so anyone stuck
 waiting will have a hint about what to do. 

A patch for the FAQ to add an entry about the hw.memtest.test=0 to speed
up boot on machines with a lot of ram


-- 
Allan Jude

Index: en_US.ISO8859-1/books/faq/book.xml
===
--- en_US.ISO8859-1/books/faq/book.xml  (revision 43198)
+++ en_US.ISO8859-1/books/faq/book.xml  (working copy)
@@ -3669,6 +3669,26 @@
in man.tunefs.8;./para
/answer
   /qandaentry
+
+  qandaentry
+   question xml:id=slow-boot-memtest
+ paraWhy does os; pause for a long time at boot when the
+   system has large amounts of ram?/para
+   /question
+
+   answer
+ paraos; does a short memory test early in the boot
+   process.  This test usually only takes several seconds,
+   however if the system has many 10s or 100s of gigabytes
+   of memory it can take up to a few minutes.  This test
+   can be disabled by setting the
+   literalhw.memtest.tests/literal to
+   literal0/literal in
+   filename/boot/loader.conf/filename/para
+
+ paraFor more details, see man.loader.conf.5;./para
+   /answer
+  /qandaentry
 /qandaset
 
 sect1 xml:id=all-about-zfs


signature.asc
Description: OpenPGP digital signature


Re: Slow boot with 256GB of RAM?

2013-11-16 Thread Eitan Adler
On Sat, Nov 16, 2013 at 4:12 PM, Zach Crum crum.z...@gmail.com wrote:
 This setting is not listed in /boot/defaults/loader.conf. Is it supposed to
 be singular or plural?

Plural.

I will commit the patch.

Does any know of cases where this memory test actually catches errors?
 How important is it?

-- 
Eitan Adler
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Slow boot with 256GB of RAM?

2013-11-15 Thread James R. Van Artsdalen
Asus Z9PA-U8 motherboard, 256GB of RAM, 2.4 GHz Xeon E5-2695 v2, FreeBSD
11.0-CURRENT r258092

There is a two minute pause when booting, after the loader's SMAP
display and the initial kernel output,

Does anyone know what's going on here?  Even that much RAM shouldn't
take that much time to clear.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Slow boot with 256GB of RAM?

2013-11-15 Thread Allan Jude
On 2013-11-15 23:37, James R. Van Artsdalen wrote:
 Asus Z9PA-U8 motherboard, 256GB of RAM, 2.4 GHz Xeon E5-2695 v2, FreeBSD
 11.0-CURRENT r258092

 There is a two minute pause when booting, after the loader's SMAP
 display and the initial kernel output,

 Does anyone know what's going on here?  Even that much RAM shouldn't
 take that much time to clear.
 ___
 freebsd-current@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
It is a known issue (I have a few E5-2620s with 96 and 144gb of ram)

There was talk at MeetBSD last year about making at least output a dot
for each 1 or 8gb of something so you knew it was at least doing
something, not sure whatever happened to that.

It would be nice if it didn't that that long

-- 
Allan Jude




signature.asc
Description: OpenPGP digital signature


Re: Slow boot with 256GB of RAM?

2013-11-15 Thread Matthias Petermann
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello James,

Am 16.11.2013 05:37, schrieb James R. Van Artsdalen:
 Asus Z9PA-U8 motherboard, 256GB of RAM, 2.4 GHz Xeon E5-2695 v2,
 FreeBSD 11.0-CURRENT r258092
 
 There is a two minute pause when booting, after the loader's SMAP 
 display and the initial kernel output,
 
 Does anyone know what's going on here?  Even that much RAM
 shouldn't take that much time to clear.

in an earlier discussion at FreeBSD Forums[1] it looks like this is
related to some early stage memory test which is performed.

It can be disabled by adding

hw.memtest.tests=0

to /boot/loader.conf. For my 32GB machine this helped.


Best regards,
Matthias


[1] http://forums.freebsd.org/showthread.php?t=12705

- -- 
Matthias Petermann matth...@petermann-it.de | www.petermann-it.de
GnuPG: 0x5C3E6D75 | 5930 86EF 7965 2BBA 6572  C3D7 7B1D A3C3 5C3E 6D75
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (FreeBSD)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJShwcbAAoJEHsdo8NcPm11kTMQAI3sxsltJ7Se/CaZ7QsMmkFy
THULbdDLEAIJYBhfgfMh+wsK4DNu5uj+u8uL52hP2MjbV7MPOWX27xUYrGjbC1HZ
/QIcz+sAXvxV3eclLhlLuNtdZIh8U2ORQ20VleT/wsoAw0UuP4Bu/+akiVRWiEyF
/FfGfFolczMrcNQpt4Y3XbTaADTRVsx9ZmU7ZRDg+KKt+oRPGsngo75GwkCiiwVg
Ew+nSjlUB4pXiPW5teaG6asg2tLIgArVilJE7PP8mPGsz0rBf/gArGCyw3OweYzv
gmJ13nfVrOWAlz9ZYL8KFg1eON4qb2G3Trjl3g4rr/7vYoi2XXz19zevkxv/kDKi
xJCtHzVGFW0Dh6QN0M8tHc5aqb3+kLsulxEbDPDcmWGw7DPeFfRXYx8VNXLGphJC
+f1Br/WUa0K6BiRgn+yKHS9IX6P5s4aY2xyCMmcRoH7Q5YjCdKHOrdtqKwjMIPRm
BL0n+Viwwcu2qWmpTYNfQpcIRhAhc3F1v6RPxa8t3WYopBopkllFb/z8AbtWr8fF
kuCcEmw0PdKxSQgHHdTmy5UW2f+pDvCX3h5qX9inks8PMq1JWYwNz+7WTfDb4Bvn
pHWLE3RM78DpTDGXRuyoiwZEqh/KzHbwIw7pqWApjgINc7nifaNCRoYbxKSYVJ2s
TfnjxAn2tXfe5nLqA00E
=ePIV
-END PGP SIGNATURE-
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Slow boot with 256GB of RAM?

2013-11-15 Thread Sergey V. Dyatko
On Sat, 16 Nov 2013 06:48:11 +0100
Matthias Petermann matth...@petermann-it.de wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Hello James,
 
 Am 16.11.2013 05:37, schrieb James R. Van Artsdalen:
  Asus Z9PA-U8 motherboard, 256GB of RAM, 2.4 GHz Xeon E5-2695 v2,
  FreeBSD 11.0-CURRENT r258092
  
  There is a two minute pause when booting, after the loader's SMAP 
  display and the initial kernel output,
  
  Does anyone know what's going on here?  Even that much RAM
  shouldn't take that much time to clear.
 
 in an earlier discussion at FreeBSD Forums[1] it looks like this is
 related to some early stage memory test which is performed.
 
 It can be disabled by adding
 
   hw.memtest.tests=0
 
 to /boot/loader.conf. For my 32GB machine this helped.

+1. (box with 128GB ram)

 
 
 Best regards,
 Matthias
 
 
 [1] http://forums.freebsd.org/showthread.php?t=12705
 
 - -- 
 Matthias Petermann matth...@petermann-it.de | www.petermann-it.de
 GnuPG: 0x5C3E6D75 | 5930 86EF 7965 2BBA 6572  C3D7 7B1D A3C3 5C3E 6D75
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v2.0.22 (FreeBSD)
 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
 
 iQIcBAEBAgAGBQJShwcbAAoJEHsdo8NcPm11kTMQAI3sxsltJ7Se/CaZ7QsMmkFy
 THULbdDLEAIJYBhfgfMh+wsK4DNu5uj+u8uL52hP2MjbV7MPOWX27xUYrGjbC1HZ
 /QIcz+sAXvxV3eclLhlLuNtdZIh8U2ORQ20VleT/wsoAw0UuP4Bu/+akiVRWiEyF
 /FfGfFolczMrcNQpt4Y3XbTaADTRVsx9ZmU7ZRDg+KKt+oRPGsngo75GwkCiiwVg
 Ew+nSjlUB4pXiPW5teaG6asg2tLIgArVilJE7PP8mPGsz0rBf/gArGCyw3OweYzv
 gmJ13nfVrOWAlz9ZYL8KFg1eON4qb2G3Trjl3g4rr/7vYoi2XXz19zevkxv/kDKi
 xJCtHzVGFW0Dh6QN0M8tHc5aqb3+kLsulxEbDPDcmWGw7DPeFfRXYx8VNXLGphJC
 +f1Br/WUa0K6BiRgn+yKHS9IX6P5s4aY2xyCMmcRoH7Q5YjCdKHOrdtqKwjMIPRm
 BL0n+Viwwcu2qWmpTYNfQpcIRhAhc3F1v6RPxa8t3WYopBopkllFb/z8AbtWr8fF
 kuCcEmw0PdKxSQgHHdTmy5UW2f+pDvCX3h5qX9inks8PMq1JWYwNz+7WTfDb4Bvn
 pHWLE3RM78DpTDGXRuyoiwZEqh/KzHbwIw7pqWApjgINc7nifaNCRoYbxKSYVJ2s
 TfnjxAn2tXfe5nLqA00E
 =ePIV
 -END PGP SIGNATURE-
 ___
 freebsd-current@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to
 freebsd-current-unsubscr...@freebsd.org



-- 
wbr, tiger
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org