On 26 October 2016 at 18:55, Adrian Sevcenco <[email protected]> wrote:
> On 10/26/2016 08:32 PM, Catalin Muresan wrote: > > 2016-10-26 18:00 GMT+01:00 Adrian Sevcenco <[email protected]>: > > > >> Salut! Am intilnit o problema ciudata si nu stiu cum sa o procesez : > >> > >> [root@compute-0-0 ~]# dmidecode -t memory | grep -E 'Size.*MB' > >> Size: 1024 MB > >> Size: 1024 MB > >> Size: 1024 MB > >> Size: 1024 MB > >> > >> [root@compute-0-0 ~]# free -m > >> total used free shared buffers > cached > >> Mem: 7998 1437 6560 0 396 > 722 > >> -/+ buffers/cache: 318 7679 > >> Swap: 8191 0 8191 > >> > >> [root@compute-0-0 ~]# hwloc-ls --no-caches > >> Machine (7998MB) > >> ..... > >> > >> [root@compute-0-0 ~]# numastat -m | grep MemTotal > >> MemTotal 8190.93 8190.93 > >> > >> e clar ca memoria e busita .. iar joburi pe masina imi crapa cu > >> std::bad_alloc .. > >> dar de ce, inclusiv dupa reboot free -m imi arata 8 gb??? > >> daca ar arata marimea ce functioneaza as putea sa fac ceva, ar functiona > >> swapul, > >> si as reduce joburile pe masina ... > >> > >> Ceva idei in legatura cu conditiile in care pot aparea astfel de > >> discrepante? > >> > > > > dmesg | grep 0.000000 > > > > (cam tot legat de linux care detecteaza memoria ar fi acolo, daca nu, > > adauga mai mult, pina la, inclusiv "Memory:"). > > > > pune ce iese intr-un pastebin sa vedem si noi. > http://pastebin.com/za5eKGMk mda., am zis sa faci grep pe aia pentru ca kernel-ul meu are timings: [cata@lemon ~]$ dmesg|grep 0.0000000 [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009e7ff] usable [ 0.000000] BIOS-e820: [mem 0x000000000009e800-0x000000000009ffff] reserved ^^^^^^^^^^^^^^^ fa un paste cu tot ce e pina la linia: [ 0.000000] Memory: 16366760K/16733348K available (8133K kernel code, 1298K rwdata, 3284K rodata, 1584K init, 1516K bss, 366588K reserved, 0K cma-reserved) > > > in cel mai rau caz poti "rezolva" cu mem= > > > > mem=nn[KMG] [KNL,BOOT] Force usage of a specific amount of memory > > Amount of memory to be used when the kernel is not able > > to see the whole system memory or for test. > > [X86] Work as limiting max address. Use together > > with memmap= to avoid physical address space collisions. > > Without memmap= PCI devices could be placed at addresses > > belonging to unused RAM. > > > > sau mai bine (tocmai am aflat si eu ca este, citind documentatia) > > > > memtest= [KNL,X86,ARM] Enable memtest > > Format: <integer> > > default : 0 <disable> > > Specifies the number of memtest passes to be > > performed. Each pass selects another test > > pattern from a given set of patterns. Memtest > > fills the memory with this pattern, validates > > memory contents and reserves bad memory > > regions that are detected. > > > > memtest=2 ar trebui sa se miste repede la boot. > > > > Spune-ne si noua ce iese > mda, momentan dau cu memtester (centos 6.8) si am ajuns aici : > > [root@compute-0-0 ~]# memtester 7G 1 > memtester version 4.2.1 (64-bit) > Copyright (C) 2010 Charles Cazabon. > Licensed under the GNU General Public License version 2 (only). > > pagesize is 4096 > pagesizemask is 0xfffffffffffff000 > want 7168MB (7516192768 bytes) > got 7168MB (7516192768 bytes), trying mlock ...locked. > Loop 1/1: > Stuck Address : ok > Random Value : ok > Compare XOR : ok > Compare SUB : ok > Compare MUL : ok > Compare DIV : ok > Compare OR : ok > Compare AND : ok > Sequential Increment: ok > Solid Bits : ok > Block Sequential : testing 108 > > nu stiu ce sa mai zic ... zilele viitoare cind mai imi fac putin timp > incerc cu memtest ... nu stiam de aceasta optiune, multumesc frumos de > info! > am incercat pe Fedora 24 (desktop-ul meu) si nu vad nimic interesant in dmesg. > > Adrian > > > > > _______________________________________________ > RLUG mailing list > [email protected] > http://lists.lug.ro/mailman/listinfo/rlug > > _______________________________________________ RLUG mailing list [email protected] http://lists.lug.ro/mailman/listinfo/rlug
