firefox killed - out of swap
This is current/amd64 on a Thinkpad T410 (dmesg below). My firefox session just got killed with UVM: pid 76017 (firefox), uid 1000 killed: out of swap The machine has 8GB of ram and no swap. There was a few GB of free ram at the moment. Is there something that makes the system want to use swap even if there is real memory available? On amd64 systems with enough memeory, I have no swap as a rule: if there is a swap partition, something will start using it it seems, slowing everything down. But never before have I had a process killed for not having swap ... Jan OpenBSD 7.1-beta (GENERIC.MP) #0: Tue Mar 22 10:57:47 CET 2022 h...@t410.stare.cz:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8357658624 (7970MB) avail mem = 8087089152 (7712MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xe0010 (78 entries) bios0: vendor LENOVO version "6IET75WW (1.35 )" date 02/01/2011 bios0: LENOVO 2537BN8 acpi0 at bios0: ACPI 4.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET ASF! SLIC BOOT SSDT TCPA DMAR SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP1(S4) EXP2(S4) EXP3(S4) EXP4(S4) EXP5(S4) EHC1(S3) EHC2(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz, 2926.44 MHz, 06-25-05 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,AES,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 133MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz, 2926.01 MHz, 06-25-05 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,AES,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz, 2926.02 MHz, 06-25-05 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,AES,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 5 (application processor) cpu3: Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz, 2926.01 MHz, 06-25-05 cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,AES,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,MELTDOWN cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 2, package 0 ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins, remapped acpimcfg0 at acpi0 acpimcfg0: addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG_) acpiprt2 at acpi0: bus 2 (EXP1) acpiprt3 at acpi0: bus 3 (EXP2) acpiprt4 at acpi0: bus -1 (EXP3) acpiprt5 at acpi0: bus 5 (EXP4) acpiprt6 at acpi0: bus 13 (EXP5) acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpipci0 at acpi0 UNCR acpipci1 at acpi0 PCI0: 0x 0x0011 0x0001 acpicmos0 at acpi0 tpm0 at acpi0 TPM_ 1.2 (TIS) addr 0xfed4/0x5000, device 0x104a rev 0x4e acpibat0 at acpi0: BAT0 model "42T4751" serial 1780 type LION oem "SANYO" acpiac0 at acpi0: AC unit offline acpithinkpad0 at acpi0: version 1.0 "*pnp0c14" at acpi0 not configured "PNP0C14" at acpi0 not configured acpicpu0 at acpi0: C3(350@245 mwait.3@0x20), C2(500@205 mwait.3@0x10), C1(1000@3 mwait.1), PSS acpicpu1 at acpi0: C3(350@245 mwait.3@0x20), C2(500@205 mwait.3@0x10), C1(1000@3 mwait.1), PSS acpicpu2 at acpi0: C3(350@245 mwait.3@0x20), C2(500@205 mwait.3@0x10), C1(1000@3 mwait.1), PSS acpicpu3 at acpi0: C3(350@245 mwait.3@0x20), C2(500@205 mwait.3@0x10), C1(1000@3 mwait.1), PSS acpipwrres0 at acpi0: PUBS, resource for EHC1, EHC2 acpitz0 at acpi0: critical temperature is 100 degC acpivideo0 at acpi0: VID_ acpivout0 at acpivideo0: LCD0 acpivideo1 at acpi0: VID_ cpu0: using IvyBridge MDS workaround cpu0: Enh
out of swap
This is current/amd64. Unlike in previous versions, some memory-heavy processes (such as in building some big port) get killed with UVM: pid 11422 (cc1plus), uid 0 killed: out of swap On this machine, I have _no_ swap. However, the machine has 1G RAM, and most of it is free in the moment this happens. In fact, occasionaly, spawning a new xterm fails like this, even if there is nothing else happening and there is nearly 1G of free RAM. Has something changed in this respect? Do I _have_ to have swap? Jan OpenBSD 5.2-current (GENERIC.MP) #378: Mon Aug 20 12:55:12 MDT 2012 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error 80clock_battery real mem = 1054593024 (1005MB) avail mem = 1004150784 (957MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xe4410 (25 entries) bios0: vendor Intel Corp. version MOPNV10J.86A.0175.2010.0308.0620 date 03/08/2010 bios0: Intel Corporation D510MO acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT FACP APIC MCFG HPET SSDT acpi0: wakeup devices SLPB(S4) PS2M(S4) PS2K(S4) UAR1(S4) UAR2(S4) P32_(S4) ILAN(S4) PEX0(S4) PEX1(S4) PEX2(S4) PEX3(S4) UHC1(S3) UHC2(S3) UHC3(S3) UHC4(S3) EHCI(S3) AZAL(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Atom(TM) CPU D510 @ 1.66GHz, 1666.97 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF cpu0: 512KB 64b/line 8-way L2 cache cpu0: apic clock running at 166MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Atom(TM) CPU D510 @ 1.66GHz, 1666.69 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF cpu1: 512KB 64b/line 8-way L2 cache cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Atom(TM) CPU D510 @ 1.66GHz, 1666.69 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF cpu2: 512KB 64b/line 8-way L2 cache cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Atom(TM) CPU D510 @ 1.66GHz, 1666.69 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF cpu3: 512KB 64b/line 8-way L2 cache ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 8 acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 5 (P32_) acpiprt1 at acpi0: bus 0 (PCI0) acpiprt2 at acpi0: bus 1 (PEX0) acpiprt3 at acpi0: bus 2 (PEX1) acpiprt4 at acpi0: bus 3 (PEX2) acpiprt5 at acpi0: bus 4 (PEX3) acpicpu0 at acpi0: C1, PSS acpicpu1 at acpi0: C1, PSS acpicpu2 at acpi0: C1, PSS acpicpu3 at acpi0: C1, PSS acpibtn0 at acpi0: SLPB pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 Intel Pineview DMI rev 0x02 vga1 at pci0 dev 2 function 0 Intel Pineview Video rev 0x02 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) intagp0 at vga1 agp0 at intagp0: aperture at 0xe000, size 0x1000 inteldrm0 at vga1: apic 8 int 16 drm0 at inteldrm0 ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x01: msi pci1 at ppb0 bus 1 re0 at pci1 dev 0 function 0 Realtek 8168 rev 0x03: RTL8168D/8111D (0x2800), apic 8 int 16, address 00:27:0e:07:09:9f rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 2 ppb1 at pci0 dev 28 function 1 Intel 82801GB PCIE rev 0x01: msi pci2 at ppb1 bus 2 ppb2 at pci0 dev 28 function 2 Intel 82801GB PCIE rev 0x01: msi pci3 at ppb2 bus 3 ppb3 at pci0 dev 28 function 3 Intel 82801GB PCIE rev 0x01: msi pci4 at ppb3 bus 4 uhci0 at pci0 dev 29 function 0 Intel 82801GB USB rev 0x01: apic 8 int 23 uhci1 at pci0 dev 29 function 1 Intel 82801GB USB rev 0x01: apic 8 int 19 uhci2 at pci0 dev 29 function 2 Intel 82801GB USB rev 0x01: apic 8 int 18 uhci3 at pci0 dev 29 function 3 Intel 82801GB USB rev 0x01: apic 8 int 16 ehci0 at pci0 dev 29 function 7 Intel 82801GB USB rev 0x01: apic 8 int 23 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb4 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0xe1 pci5 at ppb4 bus 5 pcib0 at pci0 dev 31 function 0 Intel NM10 LPC rev 0x01 ahci0 at pci0 dev 31 function 2 Intel 82801GR AHCI rev 0x01: msi, AHCI 1.1 scsibus0 at ahci0: 32 targets sd0 at scsibus0 targ 0 lun 0: ATA, WDC WD6400BPVT-0, 01.0 SCSI3 0/direct fixed naa.50014ee25979e46a sd0: 610480MB, 512 bytes/sector, 1250263728 sectors sd1 at scsibus0 targ 1 lun 0: ATA, WDC WD10TPVT-00H, 01.0 SCSI3 0
Re: out of swap
On Mon, Jan 07, 2013 at 01:27:35PM +0100, Jan Stary wrote: This is current/amd64. Unlike in previous versions, some memory-heavy processes (such as in building some big port) get killed with UVM: pid 11422 (cc1plus), uid 0 killed: out of swap On this machine, I have _no_ swap. However, the machine has 1G RAM, and most of it is free in the moment this happens. In fact, occasionaly, spawning a new xterm fails like this, even if there is nothing else happening and there is nearly 1G of free RAM. Has something changed in this respect? Do I _have_ to have swap? [snip] UVM: pid 17950 (cc1plus), uid 0 killed: out of swap UVM: pid 11442 (cc1plus), uid 0 killed: out of swap cc1plus is known to require vast ammounts of memory in some cases. It is likely you *are* running out of swap. -Otto
Re: out of swap
On Mon, Jan 07, 2013 at 01:27:35PM +0100, Jan Stary wrote: This is current/amd64. Unlike in previous versions, some memory-heavy processes (such as in building some big port) get killed with UVM: pid 11422 (cc1plus), uid 0 killed: out of swap On this machine, I have _no_ swap. However, the machine has 1G RAM, and most of it is free in the moment this happens. In fact, occasionaly, spawning a new xterm fails like this, even if there is nothing else happening and there is nearly 1G of free RAM. Has something changed in this respect? Do I _have_ to have swap? 1G of ram is definitely not enough to build large ports on amd64. Everything mozilla-related, for instance, goes up to 2G and more while linking.
Re: out of swap
This is current/amd64. Unlike in previous versions, some memory-heavy processes (such as in building some big port) get killed with UVM: pid 11422 (cc1plus), uid 0 killed: out of swap On this machine, I have _no_ swap. However, the machine has 1G RAM, and most of it is free in the moment this happens. In fact, occasionaly, spawning a new xterm fails like this, even if there is nothing else happening and there is nearly 1G of free RAM. Has something changed in this respect? Do I _have_ to have swap? 1G of ram is definitely not enough to build large ports on amd64. Everything mozilla-related, for instance, goes up to 2G and more while linking. I ran into /etc/login.conf limits of datasize = 512M way before hitting any other limit, so is that bumped?
Re: out of swap
I ran into /etc/login.conf limits of datasize = 512M way before hitting any other limit, so is that bumped? that is for one process.
Re: out of swap
On Jan 07 13:27:35, h...@stare.cz wrote: This is current/amd64. Unlike in previous versions, some memory-heavy processes (such as in building some big port) get killed with UVM: pid 11422 (cc1plus), uid 0 killed: out of swap On this machine, I have _no_ swap. However, the machine has 1G RAM, and most of it is free in the moment this happens. In fact, occasionaly, spawning a new xterm fails like this, even if there is nothing else happening and there is nearly 1G of free RAM. Has something changed in this respect? Do I _have_ to have swap? On Jan 07 13:34:10, o...@drijf.net wrote: UVM: pid 17950 (cc1plus), uid 0 killed: out of swap UVM: pid 11442 (cc1plus), uid 0 killed: out of swap cc1plus is known to require vast ammounts of memory in some cases. It is likely you *are* running out of swap. On Jan 07 14:03:08, es...@nerim.net wrote: 1G of ram is definitely not enough to build large ports on amd64. Everything mozilla-related, for instance, goes up to 2G and more while linking. This was indeed a build of gtk+3. On Jan 07 07:59:46, amitk...@gmail.com wrote: I ran into /etc/login.conf limits of datasize = 512M way before hitting any other limit, so is that bumped? This was running as root, who is staff: staff:\ :datasize-cur=800M:\ :datasize-max=infinity:\ :maxproc-max=512:\ :maxproc-cur=128:\ :ignorenologin:\ :requirehome@:\ :tc=default:
Re: out of swap
On Jan 07 15:14:21, h...@stare.cz wrote: On Jan 07 13:27:35, h...@stare.cz wrote: This is current/amd64. Unlike in previous versions, some memory-heavy processes (such as in building some big port) get killed with UVM: pid 11422 (cc1plus), uid 0 killed: out of swap On this machine, I have _no_ swap. However, the machine has 1G RAM, and most of it is free in the moment this happens. In fact, occasionaly, spawning a new xterm fails like this, even if there is nothing else happening and there is nearly 1G of free RAM. Has something changed in this respect? Do I _have_ to have swap? On Jan 07 13:34:10, o...@drijf.net wrote: UVM: pid 17950 (cc1plus), uid 0 killed: out of swap UVM: pid 11442 (cc1plus), uid 0 killed: out of swap cc1plus is known to require vast ammounts of memory in some cases. It is likely you *are* running out of swap. On Jan 07 14:03:08, es...@nerim.net wrote: 1G of ram is definitely not enough to build large ports on amd64. Everything mozilla-related, for instance, goes up to 2G and more while linking. This was indeed a build of gtk+3. On Jan 07 07:59:46, amitk...@gmail.com wrote: I ran into /etc/login.conf limits of datasize = 512M way before hitting any other limit, so is that bumped? This was running as root, who is staff: No, sorry; root is in the daemon class: daemon:\ :ignorenologin:\ :datasize=infinity:\ :maxproc=infinity:\ :openfiles-cur=128:\ :stacksize-cur=8M:\ :localcipher=blowfish,8:\ :tc=default:
Re: out of swap
On Mon, Jan 07, 2013 at 03:38:37PM +0100, Jan Stary wrote: On Jan 07 15:14:21, h...@stare.cz wrote: On Jan 07 13:27:35, h...@stare.cz wrote: This is current/amd64. Unlike in previous versions, some memory-heavy processes (such as in building some big port) get killed with UVM: pid 11422 (cc1plus), uid 0 killed: out of swap On this machine, I have _no_ swap. However, the machine has 1G RAM, and most of it is free in the moment this happens. ^^ In fact, occasionaly, spawning a new xterm fails like this, even if there is nothing else happening and there is nearly 1G of free RAM. Has something changed in this respect? Do I _have_ to have swap? No, sorry; root is in the daemon class: daemon:\ :ignorenologin:\ :datasize=infinity:\ :maxproc=infinity:\ :openfiles-cur=128:\ :stacksize-cur=8M:\ :localcipher=blowfish,8:\ :tc=default: who cares ? the limiting factor here is 1G of memory. keep in mind that 64 bits ~= twice the size for some things, which include compiling and linking code. There are lots of *large* stragglers in the ports tree that won't compile within 1G of memory, heck, they can go over 2G in some cases (landry@ is starting to hit hard limits on some 32 bit machines, for instance). Theo is right: a *huge* default limit *for every normal process* is wrong. But compiling big ports is not normal. :) For starters, you could use the provided snapshots. If you don't, you're supposed to know what you're doing (obviously, there's something missing there). Heck, I even added a few paragraphs about bulk build hints to ports(7) recently. You could also question whether it's reasonable to need THAT much memory to compile and link that code. Unfortunately, we're stuck with the tools that exist. Developping a more efficient compiler+linker is a *huge* adventure... oh, and most people out there *won't even care*. If you whine that you can't compile stuff with your 1G of memory, a lot of developers will laugh at the puny amount of memory you have on your development machine. Sad but true...
Re: out of swap
On Jan 07 17:09:16, es...@nerim.net wrote: who cares ? the limiting factor here is 1G of memory. keep in mind that 64 bits ~= twice the size for some things, which include compiling and linking code. There are lots of *large* stragglers in the ports tree that won't compile within 1G of memory, heck, they can go over 2G in some cases (landry@ is starting to hit hard limits on some 32 bit machines, for instance). Theo is right: a *huge* default limit *for every normal process* is wrong. But compiling big ports is not normal. :) Right. For starters, you could use the provided snapshots. If you don't, I use snapshots and prebuilt packages whenever I can. Compiling this was a workaround - you're supposed to know what you're doing (obviously, there's something missing there). Yesterday's current/amd64, as mirrored at ftp://ftp5.eu.openbsd.org/pub/OpenBSD/snapshots/amd64/ has sets from Jan 5 and x*-sets from Jan 4. I'm not sure if that is the reason, but the obligate pkg_add -ui says Can't install gtk+3-3.6.3 because of libraries |library freetype.19.0 not found | /usr/X11R6/lib/libfreetype.so.17.2 (system): bad major | /usr/X11R6/lib/libfreetype.so.18.0 (system): bad major | /usr/X11R6/lib/libfreetype.so.18.1 (system): bad major | /usr/X11R6/lib/libfreetype.so.18.2 (system): bad major | /usr/X11R6/lib/libfreetype.so.18.3 (system): bad major That's why I am bulding it from ports (and getting the out-of-swap errors). I don't mind waiting for a newer freetype or rebulding xenocara. I was just confused by the swap messages, which seems to be explained now. Thanks. Heck, I even added a few paragraphs about bulk build hints to ports(7) recently. Time for me to re-read then. You could also question whether it's reasonable to need THAT much memory to compile and link that code. Unfortunately, we're stuck with the tools that exist. Developping a more efficient compiler+linker is a *huge* adventure... No doubt. oh, and most people out there *won't even care*. If you whine that you can't compile stuff with your 1G of memory, a lot of developers will laugh at the puny amount of memory you have on your development machine. I just didn't know that 1G of RAM that my machine has (laugh away) is not enough for compiling _those_ ports, and that in fact I *will* be hitting (my nonexistent) swap, as Otto explained. Now I do. Thank you.
Re: out of swap
Can't install gtk+3-3.6.3 because of libraries |library freetype.19.0 not found | /usr/X11R6/lib/libfreetype.so.17.2 (system): bad major | /usr/X11R6/lib/libfreetype.so.18.0 (system): bad major | /usr/X11R6/lib/libfreetype.so.18.1 (system): bad major | /usr/X11R6/lib/libfreetype.so.18.2 (system): bad major | /usr/X11R6/lib/libfreetype.so.18.3 (system): bad major That's why I am bulding it from ports (and getting the out-of-swap errors). I don't mind waiting for a newer freetype or rebulding xenocara. Right, the rebuilt xenocara (unlike the current x* sets) provides freetype.so.19 and gtk+3 and everything above is happy via pkg_add -ui.
Re: out of swap
Would http://www.openbsd.org/faq/faq14.html#Swap fix your issue? Specifically, section 14.5.3 where you create a swap space and add it to your swap pool? On Mon, Jan 7, 2013 at 10:44 AM, Jan Stary h...@stare.cz wrote: On Jan 07 17:09:16, es...@nerim.net wrote: who cares ? the limiting factor here is 1G of memory. keep in mind that 64 bits ~= twice the size for some things, which include compiling and linking code. There are lots of *large* stragglers in the ports tree that won't compile within 1G of memory, heck, they can go over 2G in some cases (landry@ is starting to hit hard limits on some 32 bit machines, for instance). Theo is right: a *huge* default limit *for every normal process* is wrong. But compiling big ports is not normal. :) Right. For starters, you could use the provided snapshots. If you don't, I use snapshots and prebuilt packages whenever I can. Compiling this was a workaround - you're supposed to know what you're doing (obviously, there's something missing there). Yesterday's current/amd64, as mirrored at ftp://ftp5.eu.openbsd.org/pub/OpenBSD/snapshots/amd64/ has sets from Jan 5 and x*-sets from Jan 4. I'm not sure if that is the reason, but the obligate pkg_add -ui says Can't install gtk+3-3.6.3 because of libraries |library freetype.19.0 not found | /usr/X11R6/lib/libfreetype.so.17.2 (system): bad major | /usr/X11R6/lib/libfreetype.so.18.0 (system): bad major | /usr/X11R6/lib/libfreetype.so.18.1 (system): bad major | /usr/X11R6/lib/libfreetype.so.18.2 (system): bad major | /usr/X11R6/lib/libfreetype.so.18.3 (system): bad major That's why I am bulding it from ports (and getting the out-of-swap errors). I don't mind waiting for a newer freetype or rebulding xenocara. I was just confused by the swap messages, which seems to be explained now. Thanks. Heck, I even added a few paragraphs about bulk build hints to ports(7) recently. Time for me to re-read then. You could also question whether it's reasonable to need THAT much memory to compile and link that code. Unfortunately, we're stuck with the tools that exist. Developping a more efficient compiler+linker is a *huge* adventure... No doubt. oh, and most people out there *won't even care*. If you whine that you can't compile stuff with your 1G of memory, a lot of developers will laugh at the puny amount of memory you have on your development machine. I just didn't know that 1G of RAM that my machine has (laugh away) is not enough for compiling _those_ ports, and that in fact I *will* be hitting (my nonexistent) swap, as Otto explained. Now I do. Thank you.
Re: out of swap
On Jan 07 14:13:15, bra...@gmail.com wrote: Would http://www.openbsd.org/faq/faq14.html#Swap fix your issue? Specifically, section 14.5.3 where you create a swap space and add it to your swap pool? The issue here was my ignorance of the _need_ for more RAM or swap. It's resolved.
out of swap error?
Hello, I've got a freshly installed amd64 (dual core opteron) system running the latest snapshot (bsd.mp kernel). I have 1GB of ram and a 1GB swap partition. The machine has next to nothing on it at this point, not even X. The only packages I have installed are postfix, fetchmail and procmail (all from the latest openbsd snapshot). After letting the system sit for about 24 hours I sat down on the console to find a dozen or so out of swap errors like this: UVM: pid 23358 (sshd), uid 0 killed: out of swap UVM: pid 11042 (newsyslog), uid 0 killed: out of swap etc... I had an ssh session already open into the box so I was able to execute top. Top showed very little memory usage (about 10MB) and no swap usage. I've searched the net and usenet for similar issues but the only posters I see having such problems are people trying to run extremely minimal systems like 16MB of ram and no swap partition. Any ideas on how I could be out of swap when I seemingly wasn't using hardly any RAM and no swap? Thanks, Jeff
