search for: swap_pager

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 r...

...r (on tar.gz format). I transferred them on the new server and started to decompress the files. Www data have been decompressed correctly on the ISCSI disk. But while the messages were being decompressed (~80GB of tar.gz) and all the DB were being restored, the server crashed. The error shown was: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 31, size: 4096 This message repeated every 30 seconds. While restarting with the single user mode I checked there wasn't any message after the crash in /var/log/messages. I think 1GB of swap should be enough, since with this configuration on FreeBSD...

...9;'s all solvable[0]. My VPS has some very limited memory (256M), but I''ve compensated with swap space (1G) Now anytime I''m putting the system under stress, by building ports or by running a git clone on the kernel repository here, I''m seeing a lot of messages about swap_pager: > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 132545, size: 4096 The system also becomes very sluggish and sometimes unresponsive. The weird thing was that one of these messages happened right after a reboot when I rebuilt an outdated port and on the main console was checking the sw...

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" shows that number of "make" processes grows until system runs out of swap. FreeBSD alc.makon 4.8-STABLE...

...ses 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 -> vm/vm.ph vm/vm_extern.h -> vm/vm_extern.ph vm/vm_kern.h -> vm/vm_kern.ph vm/vm_map.h -> vm/vm_map.ph vm/vm_object.h -> vm/vm_object.ph vm/vm_page.h -> vm/vm_page.ph vm/vm_pageout.h -> vm/vm_pageout.ph vm/vm_pager.h -> vm/vm_pager.ph vm/vm_...

...NM0011 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: indefinite wait buffer error. I had to reset computer twice in two days. mptutil does not show any errors, and smartctl shows SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATE...

Change the assembly code to use only relative references of symbols for the kernel to be PIE compatible. Position Independent Executable (PIE) support will allow to extended the KASLR randomization range below the -2G memory limit. Signed-off-by: Thomas Garnier <thgarnie at google.com> --- arch/x86/entry/entry_64.S | 16 ++++++++++------ arch/x86/kernel/relocate_kernel_64.S |

...card. Processes that don't need to page in work fine. (You can hit return in a shell, get another login: prompt on other consoles, and the like.) The system continues to respond to pings, but anything that attempts to do a disk IO simply stops. Sometimes the kernel emits messages like this: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 2, size: 4096 The test we are using to produce this "hang" is a fairly trivial expansion of a tar ball being fed via nc from another system. We run on the source system: tar cf - radar | nc -w 3 10.10.10.229 12345 And on the system being te...

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