search for: swap_pages

My server just literally was brought to it's knees with this message spewing on the console: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 1203133, size: 4096 (blkno and size were varying) Some searching says that this is or was a bug. Has this been fixed yet? If so, what should I upgrade to? I'm currently running 6.3 Michael Grant

Aug 11 03:56:34 danux /kernel: swap_pager: out of swap space Aug 11 04:02:34 danux /kernel: swap_pager_getswapspace: failed Aug 11 04:02:34 danux /kernel: pid 278 (XFree86), uid 0, was killed: out of swap space i was actually looking at the screen and then everything stopped (mouse etc). i could not switch to console, but a ctrl+alt+del rebooted fine. one thing that could be taking a lot of

Hello, I manage a www (apache), database (postgresql) and e-mail (qmail) with about 100 Internet domains. We recently purchased a DELL MD3000i server with data access through ISCSI protocol. I installed a new server with FreeBSD 7.0 compiled kernel with ISCSI (v. 2.1) and SCHED_ULE scheduler. The server's local disk configuration is: 512 MB / 1024 MB SWAP 254 MB / var 2048MB / var/ qmail 512

Hi, After some more testing I thought it would be good to put this into production for my personal server. I''ve used pvhvm_v19 and built it without debugging options and installed it on a FreeBSD 9.1 system. I''ve run into some hiccups with 9.1 user land and a 10-CURRENT kernel, but that''s all solvable[0]. My VPS has some very limited memory (256M), but I''ve

Hello freebsd-stable, I have 5.5-PRERELEASE server in production, booting from ad0s1: # BLOCKSIZE=512 swapinfo Device 512-blocks Used Avail Capacity /dev/ad0s1b 2097152 52872 2044280 3% /dev/ad1s1b 2097152 51952 2045200 2% Total 4194304 104824 4089480 2% # bsdlabel ad0s1 | fgrep b: b: 2097152 0 swap

hello all! i've installed gcc-3.2 about a month ago and put "USE_GCC=3.2" into /etc/make.conf. now "make clean" for any of ports leads to smth like Apr 18 12:38:54 alc /kernel: swap_pager: out of swap space Apr 18 12:38:54 alc /kernel: swap_pager_getswapspace: failed Apr 18 12:38:54 alc /kernel: pid 219 (XFree86), uid 0, was killed: out of swap space "ps ax"

Good Day, Please cc me ( eperrin@cseven.ca ) on responses to this, I am not on either mailing list anymore. I cvsup'ed on the STABLE branch today (September 9th) at around 2:30PM EDT. No problems with buildworld or kernel build, but I am getting failures during installworld Error and output from uname -a are below. vm/pmap.h -> vm/pmap.ph vm/swap_pager.h -> vm/swap_pager.ph vm/vm.h

Hello, I'm running FreeBSD 9.0/amd64, pure ZFS setup, one Seagate disk ST2000NM0011 SN02 on LSI Logic (mpt) controller. Yes, I know that running one disk on RAID controller is a bit weird, I have to find yet if it is possible to connect disk to internal SATA controller. About two days ago, system became SLOW. Disk usage is constantly 100%, and sometimes I'm getting swap_pager:

...--git a/arch/x86/kernel/relocate_kernel_64.S b/arch/x86/kernel/relocate_kernel_64.S index a7227dfe1a2b..0c0fc259a4e2 100644 --- a/arch/x86/kernel/relocate_kernel_64.S +++ b/arch/x86/kernel/relocate_kernel_64.S @@ -208,11 +208,9 @@ identity_mapped: movq %rax, %cr3 lea PAGE_SIZE(%r8), %rsp call swap_pages - jmp *virtual_mapped_addr(%rip) - - /* Absolute value for PIE support */ -virtual_mapped_addr: - .quad virtual_mapped + movabsq $virtual_mapped, %rax + pushq %rax + ret virtual_mapped: movq RSP(%r8), %rsp -- 2.16.2.660.g709887971b-goog

We're having problems with FreeBSD 5.4, 6.0, and 6.1 and an ICP Vortex GDT8546RZ 4 port SATA RAID card in a Tyan S2460 system with dual AMD Athlon MP 1600+ CPUs. We do not have any problems with this configuration under FreeBSD 4.11, and we have the same ICP cards in Tyan based Opterion system (S2882 and S4882) run with out problems under FreeBSD 5.4 and 6.1. We can reproduce the problem on

Hi, This set of patches contains initial kexec/kdump implementation for Xen v3. Currently only dom0 is supported, however, almost all infrustructure required for domU support is ready. Jan Beulich suggested to merge Xen x86 assembler code with baremetal x86 code. This could simplify and reduce a bit size of kernel code. However, this solution requires some changes in baremetal x86 code. First of

Hi, This set of patches contains initial kexec/kdump implementation for Xen v3. Currently only dom0 is supported, however, almost all infrustructure required for domU support is ready. Jan Beulich suggested to merge Xen x86 assembler code with baremetal x86 code. This could simplify and reduce a bit size of kernel code. However, this solution requires some changes in baremetal x86 code. First of

Hi, This set of patches contains initial kexec/kdump implementation for Xen v3. Currently only dom0 is supported, however, almost all infrustructure required for domU support is ready. Jan Beulich suggested to merge Xen x86 assembler code with baremetal x86 code. This could simplify and reduce a bit size of kernel code. However, this solution requires some changes in baremetal x86 code. First of

Changes: - patch v2: - Adapt patch to work post KPTI and compiler changes - Redo all performance testing with latest configs and compilers - Simplify mov macro on PIE (MOVABS now) - Reduce GOT footprint - patch v1: - Simplify ftrace implementation. - Use gcc mstack-protector-guard-reg=%gs with PIE when possible. - rfc v3: - Use --emit-relocs instead of -pie to reduce

Changes: - patch v2: - Adapt patch to work post KPTI and compiler changes - Redo all performance testing with latest configs and compilers - Simplify mov macro on PIE (MOVABS now) - Reduce GOT footprint - patch v1: - Simplify ftrace implementation. - Use gcc mstack-protector-guard-reg=%gs with PIE when possible. - rfc v3: - Use --emit-relocs instead of -pie to reduce

Changes: - patch v3: - Update on message to describe longer term PIE goal. - Minor change on ftrace if condition. - Changed code using xchgq. - patch v2: - Adapt patch to work post KPTI and compiler changes - Redo all performance testing with latest configs and compilers - Simplify mov macro on PIE (MOVABS now) - Reduce GOT footprint - patch v1: - Simplify ftrace

These patches make the changes necessary to build the kernel as Position Independent Executable (PIE) on x86_64. A PIE kernel can be relocated below the top 2G of the virtual address space. It allows to optionally extend the KASLR randomization range from 1G to 3G. Thanks a lot to Ard Biesheuvel & Kees Cook on their feedback on compiler changes, PIE support and KASLR in general. Thanks to

These patches make the changes necessary to build the kernel as Position Independent Executable (PIE) on x86_64. A PIE kernel can be relocated below the top 2G of the virtual address space. It allows to optionally extend the KASLR randomization range from 1G to 3G. Thanks a lot to Ard Biesheuvel & Kees Cook on their feedback on compiler changes, PIE support and KASLR in general. Thanks to

Changes: - patch v1: - Simplify ftrace implementation. - Use gcc mstack-protector-guard-reg=%gs with PIE when possible. - rfc v3: - Use --emit-relocs instead of -pie to reduce dynamic relocation space on mapped memory. It also simplifies the relocation process. - Move the start the module section next to the kernel. Remove the need for -mcmodel=large on modules. Extends

Changes: - patch v1: - Simplify ftrace implementation. - Use gcc mstack-protector-guard-reg=%gs with PIE when possible. - rfc v3: - Use --emit-relocs instead of -pie to reduce dynamic relocation space on mapped memory. It also simplifies the relocation process. - Move the start the module section next to the kernel. Remove the need for -mcmodel=large on modules. Extends