July 2016 - Intel-nda - mailman3.cels.anl.gov

Re: [JLSE-Intel-NDA] Adding knl01 - knl08
by Allen, Benjamin S. 11 Jul '16

11 Jul '16

Yes, fixed this. It should now be working on these new nodes. Ben > On Jul 11, 2016, at 9:32 AM, Swann Perarnau <swann(a)anl.gov> wrote: > > Ben, > > Is IPMI available on those nodes too ? I can't get a power status: > >> [perarnau@jlselogin2 ~]$ ipmitool -U jlseuser -I lanplus -H knl03.fto power status >> Error: Unable to establish IPMI v2 / RMCP+ session >> Unable to get Chassis Power Status > > Thanks, > > -- > Swann > > On Fri, Jul 08, 2016 at 09:16:28PM +0000, Allen, Benjamin S. wrote: >> knl01 through knl08 are now installed. Note, I'm keeping knl07 and knl08 reserved as we'll be using them for integration testing as we get Cobalt setup for these KNL nodes. >> >> knl01 through knl08 match knl00 specs, i.e. Xeon Phi 7210 (bin3), 192GB DDR4-2133, 200GB SSD. >> >> Also note all of the KNL nodes now have an active OmniPath interface. IPs: 172.27.6.104 - 172.27.6.114, DNS: knl<N>.jop.alcf.anl.gov. >> >> Ben >> _______________________________________________ >> Intel-nda mailing list >> Intel-nda(a)lists.jlse.anl.gov >> https://lists.jlse.anl.gov/mailman/listinfo/intel-nda

1 0

Re: [JLSE-Intel-NDA] Adding knl01 - knl08
by Swann Perarnau 11 Jul '16

11 Jul '16

Ben, Is IPMI available on those nodes too ? I can't get a power status: > [perarnau@jlselogin2 ~]$ ipmitool -U jlseuser -I lanplus -H knl03.fto power status > Error: Unable to establish IPMI v2 / RMCP+ session > Unable to get Chassis Power Status Thanks, -- Swann On Fri, Jul 08, 2016 at 09:16:28PM +0000, Allen, Benjamin S. wrote: > knl01 through knl08 are now installed. Note, I'm keeping knl07 and knl08 reserved as we'll be using them for integration testing as we get Cobalt setup for these KNL nodes. > > knl01 through knl08 match knl00 specs, i.e. Xeon Phi 7210 (bin3), 192GB DDR4-2133, 200GB SSD. > > Also note all of the KNL nodes now have an active OmniPath interface. IPs: 172.27.6.104 - 172.27.6.114, DNS: knl<N>.jop.alcf.anl.gov. > > Ben > _______________________________________________ > Intel-nda mailing list > Intel-nda(a)lists.jlse.anl.gov > https://lists.jlse.anl.gov/mailman/listinfo/intel-nda

1 0

[JLSE-Intel-NDA] Vtune 2016 Update 4 Installed
by Allen, Benjamin S. 08 Jul '16

08 Jul '16

Vtune 2016 Update 4, which includes the KNL support (previously NDA bits), is now installed at /soft/compilers/intel/vtune_amplifier_xe_2016.4.0.470476. Ben

1 0

[JLSE-Intel-NDA] Adding knl01 - knl08
by Allen, Benjamin S. 08 Jul '16

08 Jul '16

knl01 through knl08 are now installed. Note, I'm keeping knl07 and knl08 reserved as we'll be using them for integration testing as we get Cobalt setup for these KNL nodes. knl01 through knl08 match knl00 specs, i.e. Xeon Phi 7210 (bin3), 192GB DDR4-2133, 200GB SSD. Also note all of the KNL nodes now have an active OmniPath interface. IPs: 172.27.6.104 - 172.27.6.114, DNS: knl<N>.jop.alcf.anl.gov. Ben

1 0

[JLSE-Intel-NDA] REMINDER: Intel DAP boxes set up, continue discussion
by Vitali Morozov 08 Jul '16

08 Jul '16

Hello, this is a reminder that we will continue discussion started in this thread on the call with Intel today 4pm CDT. Argonne folks have 1172 reserved. Thanks, Vitali -------- Original Message -------- Subject: [JLSE-Intel-NDA] Fwd: Intel DAP boxes set up Date: Wed, 29 Jun 2016 16:38:47 +0000 From: Kumaran, Kalyan <kumaran(a)alcf.anl.gov> To: intel-nda(a)jlse.anl.gov <intel-nda(a)jlse.anl.gov> Sent from my iPhone Begin forwarded message: > *From:* "Meadows, Lawrence F" <lawrence.f.meadows(a)intel.com > <mailto:[email protected]>> > *Date:* June 29, 2016 at 10:02:13 PM GMT+5:30 > *To:* "Kumaran, Kalyan" <kumaran(a)alcf.anl.gov > <mailto:[email protected]>>, "Sodani, Avinash" > <avinash.sodani(a)intel.com <mailto:[email protected]>> > *Cc:* "Finkel, Hal J." <hfinkel(a)anl.gov <mailto:[email protected]>>, > "Harms, Kevin" <harms(a)alcf.anl.gov <mailto:[email protected]>>, > "Morozov, Vitali A." <morozov(a)alcf.anl.gov > <mailto:[email protected]>>, "Kirkendall, Keith G" > <keith.g.kirkendall(a)intel.com <mailto:[email protected]>>, > "Allen, Benjamin S." <bsallen(a)alcf.anl.gov > <mailto:[email protected]>>, "Allison, CM" <cm.allison(a)intel.com > <mailto:[email protected]>>, "Valles, Antonio C" > <antonio.c.valles(a)intel.com <mailto:[email protected]>> > *Subject:* *Re: [JLSE-Intel-NDA] Intel DAP boxes set up* > > The issue is that over time, the Linux free page list becomes > effectively randomized, so a program will receive pages with physical > addresses in several different 16 GiB regions, resulting in collisions > in the direct-mapped MCDRAM cache. > > We have had success with a kernel patch that provides a sysctl to sort > the free list. However, that patch is seen as a hack by the linux > community and is proving difficult to upstream. We are investigating > other approaches. > > The sorting patch requires that a utility be run as root before every > job and does not completely mitigate the problem but does help a lot > (effectively zero collisions up to 12-14 GiB of application memory usage). > > I am interested in ANL's views on using such a patch in your enviroment. > > -- Larry > > On 6/29/16, 9:21 AM, "Kumaran, Kalyan" <kumaran(a)alcf.anl.gov > <mailto:[email protected]>> wrote: > > Is this the same issue reported by Trinity folks? > > Sent from my iPhone > >> On Jun 29, 2016, at 8:44 PM, Sodani, Avinash >> <avinash.sodani(a)intel.com <mailto:[email protected]>> wrote: >> >> Ccing Larry and Antonio. >> >> -Avinash >> >> -----Original Message----- >> From: Hal Finkel [mailto:[email protected]] >> Sent: Tuesday, June 28, 2016 6:44 PM >> To: Kalyan Kumaran >> Cc: Kevin Harms; Vitali A. Morozov; Kirkendall, Keith G; Benjamin S. >> Allen; Allison, CM; Sodani, Avinash >> Subject: Re: [JLSE-Intel-NDA] Intel DAP boxes set up >> >> ----- Original Message ----- >>> From: "Kalyan Kumaran" <kumaran(a)alcf.anl.gov >>> <mailto:[email protected]>> >>> To: "Hal J. Finkel" <hfinkel(a)anl.gov <mailto:[email protected]>>, >>> "avinash sodani" <avinash.sodani(a)intel.com >>> <mailto:[email protected]>> >>> Cc: "Kevin Harms" <harms(a)alcf.anl.gov <mailto:[email protected]>>, >>> "Vitali A. Morozov" <morozov(a)alcf.anl.gov >>> <mailto:[email protected]>>, "keith g kirkendall" >>> <keith.g.kirkendall(a)intel.com >>> <mailto:[email protected]>>, "Benjamin S. Allen" >>> <bsallen(a)alcf.anl.gov <mailto:[email protected]>>, "cm allison" >>> <cm.allison(a)intel.com <mailto:[email protected]>> >>> Sent: Tuesday, June 28, 2016 8:40:15 PM >>> Subject: Re: [JLSE-Intel-NDA] Intel DAP boxes set up >>> >>> Copying Avinash. >>> >>> Sent from my iPhone >>> >>>> On Jun 29, 2016, at 6:12 AM, Hal Finkel <hfinkel(a)anl.gov >>>> <mailto:[email protected]>> wrote: >>>> >>>> Hi Kevin, >>>> >>>> Thanks! >>>> >>>> Also, from the release notes: >>>> >>>> Issue number: 0000003 >>>> Description: Application Performance can degrade over time >>>> when >>>> MCDRAM is used in cache mode >>>> Impact: The direct-mapped nature of MCDRAM-as-cache is >>>> by >>>> design. Real applications that need more than >>>> 16GB >>>> of memory will not exhibit this time-based >>>> degradation; it is really only a problem for >>>> benchmarking when running smaller datasets. >>>> Mitigation: Workaround is to reboot the node >>>> >>>> That seems scary. I believe we were considering booting the nodes >>>> in cache mode by default on Theta. Maybe that's a bad idea. >>>> >>>> Intel Tracking ID: 0001418 >>>> Affected OS: CentOS 7.2, RHEL 7.2, SLES 12, SLES 12 SP1 >>>> Description: [Tools] rpm rebuild not working >>>> Notes: Will not be Fixed; Not a defect >>>> >>>> Why not? >>>> >>>> -Hal >>>> >>>> ----- Original Message ----- >>>>> From: "Kevin Harms" <harms(a)alcf.anl.gov <mailto:[email protected]>> >>>>> To: "Hal J. Finkel" <hfinkel(a)anl.gov <mailto:[email protected]>> >>>>> Cc: "Vitali A. Morozov" <morozov(a)alcf.anl.gov >>>>> <mailto:[email protected]>>, >>>>> intel-nda(a)lists.jlse.anl.gov <mailto:[email protected]> >>>>> Sent: Tuesday, June 28, 2016 7:30:30 PM >>>>> Subject: Re: [JLSE-Intel-NDA] Intel DAP boxes set up >>>>> >>>>> >>>>> I believe this kernel is just a set of selected backports from >>>>> the >>>>> main kernel. It?s possible this bug is related to a problem with >>>>> PTE handling. Intel reported some bug where dirty pages were >>>>> handled incorrectly under some conditions. That?s all the info we >>>>> got. I haven?t seen the fix yet. The mpsp 1.3.3 is out as well, >>>>> renamed xppsl_1.3.3. >> >> I installed this version. Same problem: >> >> Message from syslogd@kingly at Jun 28 20:14:29 ... >> kernel:BUG: soft lockup - CPU#223 stuck for 22s! [sh:24755] >> >> Message from syslogd@kingly at Jun 28 20:14:36 ... >> kernel:BUG: soft lockup - CPU#247 stuck for 22s! [as:25704] >> >> ... >> >> $ uname -a >> Linux kingly 3.10.0-327.13.1.el7.xppsl_1.3.3.151.x86_64 #1 SMP Fri >> Jun 10 15:04:35 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux >> >> -Hal >> >>>>> >>>>> https://software.intel.com/en-us/articles/intel-xeon-phi-processor-software >>>>> http://registrationcenter-download.intel.com/akdlm/irc_nas/9325/xppsl-1.3.3… >>>>> >>>>> >>>>> kevin >>>>> >>>>>> Hi Kevin, >>>>>> >>>>>> FWIW, no, the problem happened again with the new kernel: >>>>>> >>>>>> Message from syslogd@kingly at Jun 28 19:12:49 ... >>>>>> kernel:BUG: soft lockup - CPU#104 stuck for 23s! [cc1plus:77778] >>>>>> >>>>>> Message from syslogd@kingly at Jun 28 19:12:51 ... >>>>>> kernel:BUG: soft lockup - CPU#177 stuck for 23s! [cc1plus:77662] >>>>>> >>>>>> ... >>>>>> >>>>>> What's special about this kernel? Could I build a mainline kernel >>>>>> and expect it to work reasonably? >>>>>> >>>>>> -Hal >>>>>> >>>>>> ----- Original Message ----- >>>>>>> From: "Hal Finkel" <hfinkel(a)anl.gov <mailto:[email protected]>> >>>>>>> To: "Kevin Harms" <harms(a)alcf.anl.gov <mailto:[email protected]>> >>>>>>> Cc: "Vitali A. Morozov" <morozov(a)alcf.anl.gov >>>>>>> <mailto:[email protected]>>, >>>>>>> intel-nda(a)lists.jlse.anl.gov <mailto:[email protected]> >>>>>>> Sent: Tuesday, June 28, 2016 12:47:02 PM >>>>>>> Subject: Re: [JLSE-Intel-NDA] Intel DAP boxes set up >>>>>>> >>>>>>> Thanks! I'll upgrade. >>>>>>> >>>>>>> -Hal >>>>>>> >>>>>>> ----- Original Message ----- >>>>>>>> From: "Kevin Harms" <harms(a)alcf.anl.gov >>>>>>>> <mailto:[email protected]>> >>>>>>>> To: "Hal J. Finkel" <hfinkel(a)anl.gov <mailto:[email protected]>>, >>>>>>>> "Vitali A. Morozov" >>>>>>>> <morozov(a)alcf.anl.gov <mailto:[email protected]>> >>>>>>>> Cc: intel-nda(a)lists.jlse.anl.gov >>>>>>>> <mailto:[email protected]> >>>>>>>> Sent: Tuesday, June 28, 2016 11:59:20 AM >>>>>>>> Subject: Re: [JLSE-Intel-NDA] Intel DAP boxes set up >>>>>>>> >>>>>>>> >>>>>>>> I updated this page to indicate how to upgrade to the mpsp >>>>>>>> 1.3.2 >>>>>>>> kernel. https://wiki.jlse.anl.gov/display/knl/Intel+DAP+Setup >>>>>>>> >>>>>>>> No idea, if that will fix this problem though :) >>>>>>>> >>>>>>>> kevin >>>>>>>> >>>>>>>>> FYI: James and I have been experimenting with our box. We had >>>>>>>>> to >>>>>>>>> reset it after we hit some kernel bug: >>>>>>>>> >>>>>>>>> Message from syslogd@kingly at Jun 27 14:29:44 ... >>>>>>>>> kernel:BUG: soft lockup - CPU#77 stuck for 22s! >>>>>>>>> [cc1plus:15316] >>>>>>>>> >>>>>>>>> Message from syslogd@kingly at Jun 27 14:30:43 ... >>>>>>>>> kernel:BUG: soft lockup - CPU#149 stuck for 23s! >>>>>>>>> [cc1plus:14840] >>>>>>>>> >>>>>>>>> Message from syslogd@kingly at Jun 27 14:30:44 ... >>>>>>>>> kernel:BUG: soft lockup - CPU#8 stuck for 23s! [cc1plus:15337] >>>>>>>>> >>>>>>>>> Message from syslogd@kingly at Jun 27 14:30:46 ... >>>>>>>>> kernel:BUG: soft lockup - CPU#49 stuck for 22s! [as:16806] >>>>>>>>> >>>>>>>>> Message from syslogd@kingly at Jun 27 14:30:47 ... >>>>>>>>> kernel:BUG: soft lockup - CPU#27 stuck for 22s! >>>>>>>>> [cc1plus:16548] >>>>>>>>> >>>>>>>>> Message from syslogd@kingly at Jun 27 14:30:50 ... >>>>>>>>> kernel:BUG: soft lockup - CPU#34 stuck for 22s! [cmake:16807] >>>>>>>>> >>>>>>>>> Message from syslogd@kingly at Jun 27 14:30:52 ... >>>>>>>>> kernel:BUG: soft lockup - CPU#154 stuck for 22s! [cmake:16810] >>>>>>>>> >>>>>>>>> Message from syslogd@kingly at Jun 27 14:30:54 ... >>>>>>>>> kernel:BUG: soft lockup - CPU#35 stuck for 23s! >>>>>>>>> [cc1plus:15807] >>>>>>>>> >>>>>>>>> Message from syslogd@kingly at Jun 27 14:30:55 ... >>>>>>>>> kernel:BUG: soft lockup - CPU#77 stuck for 22s! >>>>>>>>> [cc1plus:15316] >>>>>>>>> >>>>>>>>> Message from syslogd@kingly at Jun 27 14:30:55 ... >>>>>>>>> kernel:BUG: soft lockup - CPU#91 stuck for 22s! [cmake:16813] >>>>>>>>> >>>>>>>>> Message from syslogd@kingly at Jun 27 14:30:58 ... >>>>>>>>> kernel:BUG: soft lockup - CPU#124 stuck for 23s! [make:16811] >>>>>>>>> >>>>>>>>> Message from syslogd@kingly at Jun 27 14:31:00 ... >>>>>>>>> kernel:BUG: soft lockup - CPU#149 stuck for 23s! >>>>>>>>> [cc1plus:14840] >>>>>>>>> >>>>>>>>> ... (this went on for a while) >>>>>>>>> >>>>>>>>> The kernel (3.10.0-327.el7.centos.mpsp_1.3.1.45.x86_64) seems >>>>>>>>> like >>>>>>>>> some special build? >>>>>>>>> >>>>>>>>> -Hal >>>>>>>>> >>>>>>>>> ----- Original Message ----- >>>>>>>>>> From: "Vitali A. Morozov" <morozov(a)anl.gov >>>>>>>>>> <mailto:[email protected]>> >>>>>>>>>> To: "Kalyan Kumaran" <kumaran(a)alcf.anl.gov >>>>>>>>>> <mailto:[email protected]>>, >>>>>>>>>> intel-nda(a)lists.jlse.anl.gov >>>>>>>>>> <mailto:[email protected]> >>>>>>>>>> Sent: Thursday, June 23, 2016 10:47:37 AM >>>>>>>>>> Subject: Re: [JLSE-Intel-NDA] Intel DAP boxes set up >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> I have updated the Ethernet port issue that I have >>>>>>>>>> encountered. >>>>>>>>>> >>>>>>>>>> Vitali >>>>>>>>>> >>>>>>>>>> On 06/23/2016 10:42 AM, Kumaran, Kalyan wrote: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> For folks setting these up please see instructions at: >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> https://wiki.jlse.anl.gov/display/knl/Intel+DAP+Setup >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Kevin, Scott and Vitali will be adding information as they >>>>>>>>>> set >>>>>>>>>> the >>>>>>>>>> machines up. Others are welcome to add stuff. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -Kumar >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Intel-nda mailing list Intel-nda(a)lists.jlse.anl.gov >>>>>>>>>> <mailto:[email protected]> >>>>>>>>>> https://lists.jlse.anl.gov/mailman/listinfo/intel-nda >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Intel-nda mailing list >>>>>>>>>> Intel-nda(a)lists.jlse.anl.gov >>>>>>>>>> <mailto:[email protected]> >>>>>>>>>> https://lists.jlse.anl.gov/mailman/listinfo/intel-nda >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Hal Finkel >>>>>>>>> Assistant Computational Scientist >>>>>>>>> Leadership Computing Facility >>>>>>>>> Argonne National Laboratory >>>>>>>>> _______________________________________________ >>>>>>>>> Intel-nda mailing list >>>>>>>>> Intel-nda(a)lists.jlse.anl.gov <mailto:[email protected]> >>>>>>>>> https://lists.jlse.anl.gov/mailman/listinfo/intel-nda >>>>>>> >>>>>>> -- >>>>>>> Hal Finkel >>>>>>> Assistant Computational Scientist >>>>>>> Leadership Computing Facility >>>>>>> Argonne National Laboratory >>>>>>> _______________________________________________ >>>>>>> Intel-nda mailing list >>>>>>> Intel-nda(a)lists.jlse.anl.gov <mailto:[email protected]> >>>>>>> https://lists.jlse.anl.gov/mailman/listinfo/intel-nda >>>>>> >>>>>> -- >>>>>> Hal Finkel >>>>>> Assistant Computational Scientist >>>>>> Leadership Computing Facility >>>>>> Argonne National Laboratory >>>> >>>> -- >>>> Hal Finkel >>>> Assistant Computational Scientist >>>> Leadership Computing Facility >>>> Argonne National Laboratory >>>> _______________________________________________ >>>> Intel-nda mailing list >>>> Intel-nda(a)lists.jlse.anl.gov <mailto:[email protected]> >>>> https://lists.jlse.anl.gov/mailman/listinfo/intel-nda >> >> -- >> Hal Finkel >> Assistant Computational Scientist >> Leadership Computing Facility >> Argonne National Laboratory > >

1 0

Re: [JLSE-Intel-NDA] EXIT CODE: 11
by Jiang, Wei 07 Jul '16

07 Jul '16

thanks! Wei Jiang, PhD, Leadership Computing Facility Argonne National Laboratory 9700S, Cass Ave, Lemont, IL60439 630-252-8688 (office) 630-252-7121 (fax) ________________________________________ From: intel-nda-bounces(a)lists.jlse.anl.gov [intel-nda-bounces(a)lists.jlse.anl.gov] on behalf of Steven Pieper [spieper(a)anl.gov] Sent: Thursday, July 07, 2016 9:39 PM To: intel-nda(a)lists.jlse.anl.gov Subject: Re: [JLSE-Intel-NDA] EXIT CODE: 11 Yes, stderr should presumably have a segfault message and maybe a traceback. Steve Steven C. Pieper, Senior Physicist Emeritus: spieper(a)anl.gov Argonne National Laboratory, Physics Division, Bldg. 203, Argonne, IL 60439 Phone: 630-252-4232 Fax -6008 Secretary, Debra Beres, -4100 http://www.phy.anl.gov/theory/staff/scp.html On 07/07/2016 09:20 PM, Jiang, Wei wrote: > Hi, I am testing a code and get the following error. Does the 'EXIT CODE: 11' mean bad memory operation? > > =================================================================================== > = BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES > = PID 111784 RUNNING AT knl00.ftm.alcf.anl.gov > = EXIT CODE: 11 > = CLEANING UP REMAINING PROCESSES > = YOU CAN IGNORE THE BELOW CLEANUP MESSAGES > > Thanks > > Wei Jiang, PhD, Leadership Computing Facility > Argonne National Laboratory > 9700S, Cass Ave, Lemont, IL60439 > 630-252-8688 <callto:630-252-8688> (office) > 630-252-7121 <callto:630-252-7121> (fax) > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- -- > > > _______________________________________________ > Intel-nda mailing list > Intel-nda(a)lists.jlse.anl.gov > https://lists.jlse.anl.gov/mailman/listinfo/intel-nda _______________________________________________ Intel-nda mailing list Intel-nda(a)lists.jlse.anl.gov https://lists.jlse.anl.gov/mailman/listinfo/intel-nda

1 0

Re: [JLSE-Intel-NDA] EXIT CODE: 11
by Steven Pieper 07 Jul '16

07 Jul '16

Yes, stderr should presumably have a segfault message and maybe a traceback. Steve Steven C. Pieper, Senior Physicist Emeritus: spieper(a)anl.gov Argonne National Laboratory, Physics Division, Bldg. 203, Argonne, IL 60439 Phone: 630-252-4232 Fax -6008 Secretary, Debra Beres, -4100 http://www.phy.anl.gov/theory/staff/scp.html On 07/07/2016 09:20 PM, Jiang, Wei wrote: > Hi, I am testing a code and get the following error. Does the 'EXIT CODE: 11' mean bad memory operation? > > =================================================================================== > = BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES > = PID 111784 RUNNING AT knl00.ftm.alcf.anl.gov > = EXIT CODE: 11 > = CLEANING UP REMAINING PROCESSES > = YOU CAN IGNORE THE BELOW CLEANUP MESSAGES > > Thanks > > Wei Jiang, PhD, Leadership Computing Facility > Argonne National Laboratory > 9700S, Cass Ave, Lemont, IL60439 > 630-252-8688 <callto:630-252-8688> (office) > 630-252-7121 <callto:630-252-7121> (fax) > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- -- > > > _______________________________________________ > Intel-nda mailing list > Intel-nda(a)lists.jlse.anl.gov > https://lists.jlse.anl.gov/mailman/listinfo/intel-nda

1 0

[JLSE-Intel-NDA] EXIT CODE: 11
by Jiang, Wei 07 Jul '16

07 Jul '16

Hi, I am testing a code and get the following error. Does the 'EXIT CODE: 11' mean bad memory operation? =================================================================================== = BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES = PID 111784 RUNNING AT knl00.ftm.alcf.anl.gov = EXIT CODE: 11 = CLEANING UP REMAINING PROCESSES = YOU CAN IGNORE THE BELOW CLEANUP MESSAGES Thanks Wei Jiang, PhD, Leadership Computing Facility Argonne National Laboratory 9700S, Cass Ave, Lemont, IL60439 630-252-8688<callto:630-252-8688> (office) 630-252-7121<callto:630-252-7121> (fax) ________________________________

1 0

Re: [JLSE-Intel-NDA] disable HW prefetch on KNL
by Kumbhar Pramod Shivaji 06 Jul '16

06 Jul '16

Thanks Ben for providing BIOS info. I see following : [BIOS::Advanced::Processor Configuration] L1 Prefetcher=Enabled ;Options: Disabled=00: Enabled=01 L2 Prefetcher=Enabled ;Options: Disabled=00: Enabled=01 So this might be one way to disable/enable the hardware perfecting (?). -Pramod On 06 Jul 2016, at 19:48, Kumbhar Pramod Shivaji <pramod.kumbhar(a)epfl.ch<mailto:[email protected]>> wrote: Regarding knl hardware prefetcher, I read something like “hardware prefetchers can be disabled within the BIOS menus at boot time or using BIOS tools, specific to your machine”. I am not sure if this is true (for current knl nodes / BIOS), people who can look at BIOS settings or intel folks can provide more information regarding this. “software” or “compiler” prefetching is enabled by default with -O2 which could be disabled by -opt-prefetch=0 / -no-opt-prefetch or “pragma noprefetch”. I see prefetch instructions like prefetcht0, prefetchnt1 or _mm_prefetch intrinsics but haven’t come across anything to disable it like data stream control register you mentioned for power8 (expect for some<https://software.intel.com/en-us/articles/disclosure-of-hw-prefetcher-contr…> other microarchitectures). -Pramod On 06 Jul 2016, at 08:29, Delalondre Fabien Jonathan <fabien.delalondre(a)epfl.ch<mailto:[email protected]>> wrote: Last time i asked intel it was not possible to disable hardware prefetcher. I believe you can pass hints to indicate you want to disable software prefetcher but i dont remember whether they were just hints (that can be ignored) or not. Best, Fabien On 6 juil. 2016, at 00:05, Chunduri, Sudheer <chunduri(a)anl.gov<mailto:[email protected]>> wrote: Hi, Is there a way to disable HW prefetch on KNL? For ex, on POWER8, user can use intrinsics such as __prefetch_set_dscr_register(40) to disable hw prefetch Or user can use a compiler flag to control prefetch. Is there a similar method available for KNL? regards Sudheer _______________________________________________ Intel-nda mailing list Intel-nda(a)lists.jlse.anl.gov<mailto:[email protected]> https://lists.jlse.anl.gov/mailman/listinfo/intel-nda _______________________________________________ Intel-nda mailing list Intel-nda(a)lists.jlse.anl.gov<mailto:[email protected]> https://lists.jlse.anl.gov/mailman/listinfo/intel-nda _______________________________________________ Intel-nda mailing list Intel-nda(a)lists.jlse.anl.gov<mailto:[email protected]> https://lists.jlse.anl.gov/mailman/listinfo/intel-nda

1 0

Re: [JLSE-Intel-NDA] Checking BIOS settings on knl nodes (sudo access)
by Allen, Benjamin S. 06 Jul '16

06 Jul '16

Dumped it to /tmp/master.ini on knl00. Ben > On Jul 6, 2016, at 6:11 AM, Kumbhar Pramod Shivaji <pramod.kumbhar(a)epfl.ch> wrote: > > Hello, > > I would like to see the BIOS settings on knl nodes using below command: > > sudo /usr/bin/syscfg/syscfg /s settings.txt > > This requires sudo access. Would it be possible to get above settings information? > I assume sudo access is limited and wondering if it would be possible to get sudo permissions to check above settings. > > Thank you! > > -Pramod > _______________________________________________ > Intel-nda mailing list > Intel-nda(a)lists.jlse.anl.gov > https://lists.jlse.anl.gov/mailman/listinfo/intel-nda

1 0