How much memory do I need for buildworld?
Hi, I've a fresh FreeBSD 10.1 installed on an old 32-bit machine. I've checked out revision 274850 of the base sources and ran 'make buildworld'. After some time it has failed: === lib/clang/libllvmx86disassembler (depend) tblgen -gen-disassembler -I /usr/src/lib/clang/libllvmx86disassembler/../../../contrib/llvm/include -I /usr/src/lib/clang/libllvmx86disassembler/../../../contrib/llvm/lib/Target/X86 -d X86GenDisassemblerTables.inc.d -o X86GenDisassemblerTables.inc.h /usr/src/lib/clang/libllvmx86disassembler/../../../contrib/llvm/lib/Target/X86/X86.td *** Signal 9 Stop. make[4]: stopped in /usr/src/lib/clang/libllvmx86disassembler *** Error code 1 According to /var/log/messages it was killed because of out of memory: Nov 22 16:55:13 mercury kernel: swap_pager: out of swap space Nov 22 16:55:13 mercury kernel: swap_pager_getswapspace(16): failed Nov 22 16:55:13 mercury kernel: pid 22841 (tblgen), uid 0, was killed: out of swap space This machine has 256MB of RAM and one 64MB swap partition. Previously I used FreeBSD 7.4-CURRENT on this machine with two swap partitions of 64MB each and never had such a problem. I use it as a router, i.e. there is no X and no other memory greedy processes. Could it be related to an llvm bug fixed by following commit? http://svnweb.freebsd.org/base?view=revisionrevision=274696 ___ 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: Using a swap file
On Thu, Oct 31, 2013 at 5:05 AM, Hiroki Sato h...@freebsd.org wrote: Rostislav Krasny rosti@gmail.com wrote in CANt7McGTBwintkopk=hevo5d4bvsyifwl_-q9uzna3pwbmm...@mail.gmail.com: ro But I have no 'late' option in my /etc/fstab: ro ro root@saturn:~ # cat /etc/fstab ro # DeviceMountpointFStypeOptionsDumpPass# ro /dev/ada0s2a/ufsrw11 ro mdnoneswapsw,file=/swapfile00 ro ro Then why 'swapon -a' (without -L) doesn't work? It's either buggy or confusing. After r255265 the option file= implies late. It is because a file-backed swap space likely to be on a mounted filesystem after the swap line. I realized that that assumption was odd and confusing as you pointed out. The user should specify a swap line with file= after the mount entry, and there is no problem with it. I will fix it. Hope to see the fix in the upcoming 10.0 release and in the Handbook. Thank you. ___ 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
Using a swap file
Hi there, I've 10.0-BETA1 i386 installed and I want to use a swap file instead of a swap partition. I created /swapfile and I'm able to enable it manually by following commands: mdconfig -a -t vnode -f /swapfile -u 0 swapon /dev/md0 This is according to the following section of the Handbook: http://www.freebsd.org/doc/handbook/adding-swap-space.html It still states that adding swapfile=path to swapfile into /etc/rc.conf enables that swap file during a boot automatically. However this is already not true for CURRENT and for the upcoming 10.0 release. According to following commit number 252310 this rc.conf parameter is obsolete http://svnweb.freebsd.org/base?view=revisionrevision=252310 It introduces different configuration and offers to add a line like following into /etc/fstab mdnoneswapsw,file=/swapfile 0 0 This is what I did but 'swapon -a' still doesn't work. I didn't try to reboot because I build world in other console. But I believe the result will be the same, because /etc/rc.d/swap runs the same command: '/sbin/swapon -aq'. So what is the right way to enable a swap file during a boot and for commands like 'swapon -a' ? Thanks P.S. The Handbook needs to be updated ___ 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: Using a swap file
On Fri, Oct 25, 2013 at 3:50 PM, Rostislav Krasny rosti@gmail.com wrote: Hi there, I've 10.0-BETA1 i386 installed and I want to use a swap file instead of a swap partition. I created /swapfile and I'm able to enable it manually by following commands: mdconfig -a -t vnode -f /swapfile -u 0 swapon /dev/md0 This is according to the following section of the Handbook: http://www.freebsd.org/doc/handbook/adding-swap-space.html It still states that adding swapfile=path to swapfile into /etc/rc.conf enables that swap file during a boot automatically. However this is already not true for CURRENT and for the upcoming 10.0 release. According to following commit number 252310 this rc.conf parameter is obsolete http://svnweb.freebsd.org/base?view=revisionrevision=252310 It introduces different configuration and offers to add a line like following into /etc/fstab mdnoneswapsw,file=/swapfile 0 0 This is what I did but 'swapon -a' still doesn't work. I didn't try to reboot because I build world in other console. But I believe the result will be the same, because /etc/rc.d/swap runs the same command: '/sbin/swapon -aq'. So what is the right way to enable a swap file during a boot and for commands like 'swapon -a' ? Thanks P.S. The Handbook needs to be updated After rebooting (into an updated system) the swap file somehow turned on and was running through /dev/md0. Unfortunately after running 'swapoff -a' it is impossibly to turn it back on and /dev/md0 is disappeared. So the swapon(8) program is still broken. ___ 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: Using a swap file
On Fri, Oct 25, 2013 at 6:31 PM, Rostislav Krasny rosti@gmail.com wrote: On Fri, Oct 25, 2013 at 3:50 PM, Rostislav Krasny rosti@gmail.com wrote: Hi there, I've 10.0-BETA1 i386 installed and I want to use a swap file instead of a swap partition. I created /swapfile and I'm able to enable it manually by following commands: mdconfig -a -t vnode -f /swapfile -u 0 swapon /dev/md0 This is according to the following section of the Handbook: http://www.freebsd.org/doc/handbook/adding-swap-space.html It still states that adding swapfile=path to swapfile into /etc/rc.conf enables that swap file during a boot automatically. However this is already not true for CURRENT and for the upcoming 10.0 release. According to following commit number 252310 this rc.conf parameter is obsolete http://svnweb.freebsd.org/base?view=revisionrevision=252310 It introduces different configuration and offers to add a line like following into /etc/fstab mdnoneswapsw,file=/swapfile 0 0 This is what I did but 'swapon -a' still doesn't work. I didn't try to reboot because I build world in other console. But I believe the result will be the same, because /etc/rc.d/swap runs the same command: '/sbin/swapon -aq'. So what is the right way to enable a swap file during a boot and for commands like 'swapon -a' ? Thanks P.S. The Handbook needs to be updated After rebooting (into an updated system) the swap file somehow turned on and was running through /dev/md0. Unfortunately after running 'swapoff -a' it is impossibly to turn it back on and /dev/md0 is disappeared. So the swapon(8) program is still broken. Finally I've figured out how to turn swap on in case it's on a swap file: root@saturn:~ # swapon -aL swapon: adding /dev/md0 as swap device This is (with an additional -q parameter) what /etc/rc.d/swaplate does during the boot. But from the swapon(8) manual page this is not obvious: The swapon utility adds the specified swap devices to the system. If the -a option is used, all swap devices in /etc/fstab will be added, unless their ``noauto'' or ``late'' option is also set. If the -L option is specified, swap devices with the ``late'' option will be added as well as ones with no option. If the -q option is used, informational messages will not be written to standard output when a swap device is added. But I have no 'late' option in my /etc/fstab: root@saturn:~ # cat /etc/fstab # DeviceMountpointFStypeOptionsDumpPass# /dev/ada0s2a/ufsrw11 mdnoneswapsw,file=/swapfile00 Then why 'swapon -a' (without -L) doesn't work? It's either buggy or confusing. P.S. Please update the Handbook as well. ___ 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
When this panic will be fixed?
When FreeBSD 5.0-RELEASE had been released I tried to install it from floppies. I got system panic and then reported this problem into [EMAIL PROTECTED] mailing list. You can find this report in http://www.atm.tut.fi/list-archive/freebsd-stable/msg08385.html or in http://docs.freebsd.org/cgi/getmsg.cgi?fetch=297316+0+archive/2003/freebsd-stable/20030126.freebsd-stable This is definitely not a hardware problem. Any Windows and FreeBSD 4.x works fine here. Actually FreeBSD 4.x works not so fine but it works; look at following chunk of FreeBSD 4.7 boot log: isa_probe_children: probing PnP devices ed0: ISA PLUG PLAY Ethernet Card at port 0x200-0x21f irq 5 on isa0 bpf: ed0 attached ed0: address 00:00:21:82:25:03, type NE2000 (16 bit) sbc0: Creative ViBRA16X at port 0x220-0x22f,0x300-0x301,0x388-0x38b irq 10 drq 0,1 on isa0 sbc0: setting card to irq 10, drq 0, 1 pcm0: SB16 DSP 4.16 (ViBRA16X) on sbc0 pcm0: sndbuf_setmap a000, 1000; 0xcc20d000 - a000 pcm0: sndbuf_setmap b000, 1000; 0xcc20e000 - b000 unknown: Game can't assign resources unknown: Game at port 0x20f on isa0 I configured the BIOS with PnP OS = No option, so the BIOS configures all my PnP devices before even MBR is loading. This is how the BIOS configures my PnP devices: NIC: irq = 10; ports range = 0x0240 - 0x025F SB: irq = 5; DMA = 0, 1; ports ranges = 0x0220 - 0x022F; 0x0300 - 0x0301; 0x0388 - 0x38B Gameport(SB): ports range = 0x0201 - 0x0201 Compare it with my FreeBSD 4.7 boot log above and with my FreeBSD 5.0 boot log (can be found in http://www.atm.tut.fi/list-archive/freebsd-stable/zip0.zip). Windows (Win98) doesn't reconfigure PnP devices those were already configured by BIOS. I think that FreeBSD should have the same behaviour. At least FreeBSD 5.x will not panic when BIOS is configured with PnP OS = No option. The NIC is ISA PnP NE-12 card (NE2000 compatable) based on UMC UM9008/F chip. The SB is ISA PnP Creative SoundBlaster 16 based on ViBRA-16 chip. The Gameport is part of the SB. There is no PCI cards. I tried to install FreeBSD 5.1-RELEASE from floppies but got the same panic. Set BIOS option PnP OS = Yes doesn't resolve FreeBSD 5.x panic. Are you going to fix this panic somewhen? Thanks. __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
5.0-RELEASE panics during the floppies boot
Hello FreeBSD 5.0-RELEASE panics during the floppies boot with following messages: panic: inthand_add: Can't initialize ICU syncing disks, buffers remaining... panic: bdwrite: buffer is not busy The box have two ISA PnP cards - a NIC based on UMC UM9008/F chip and Creative SB16 based on ViBRA16 chip. There are no PCI cards although there are 4 PCI slots. The video card is ATI XPERT 98 AGP based on ATI RAGE XL chip. There is also one non-PnP ISA card - a hardware 33600bps modem based on Rockwell chip. The BIOS have PnP OS option that can be set to No or Yes. If it set to No the BIOS initialize all PnP devices, including ISA PnP devices. Before the MBR loading (boot0) BIOS prints on the screen a diagnostic information about all initialized PnP devices, including choosen to them resurces (IRQs, DMA channels). In my case it choose IRQ 10 for my ISA PnP NIC and IRQ 5 with DMA channel 0 and 1 for my ISA PnP Creative SB16. Currently installed OS-es are FreeBSD 4.7-RELEASE and Win98SE. Win98SE get to know that BIOS already initialized all ISA PnP devices. Win98SE use the same resurces that BIOS choose. The resurces are IRQ 10 and I/O port range 0x0240-0x025F for the NIC and IRQ 5 with DMA channels 0 and 1 for the SB16. Port ranges of SB16 are not so interesting for us, so I don't tell they. FreeBSD 4.7-RELEASE don't know that or don't use PnP BIOS features. Instead 4.7 re-initialize all of my ISA PnP devices with different resurces' parameters. For example, it use IRQ 5 and I/O port range 0x0200-0x021F for the NIC. FreeBSD 5.0-RELEASE (when I do floppies boot) try to use IRQ 2 and same I/O port range for the NIC. It prints following line just before the panic: ed1: ISA PLUG PLAY Ethernet Card at port 0x200-0x21f irq 2 on isa0 If I set in my BIOS the PnP OS option to Yes I don't get this line but FreeBSD 5.0-RELEASE still panics during the boot. The panic messages are exactly the same. So, we have two problems: 1. FreeBSD (all versions) do not know about BIOS's PnP devices configuration support (at least for ISA PnP devices). 2. When FreeBSD 5.0 try to configure PnP devices (at least ISA PnP devices) it do it wrong way. FreeBSD 4.7 do it better but not perfect. I think that future FreeBSD releases must be able to work better with PnP BIOS features. Plug and Play configuration capability must be improved too, especially in 5.X. P.S. The same panic was already discussed about a year and half before. This is the link to archived copy of one that discussion member: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=471741+0+archive/2001/freebsd-current/20010930.freebsd-current __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
