similar to: Fwd: [Re: cvs commit: src/sys/vm vm_map.c]

Displaying 20 results from an estimated 1000 matches similar to: "Fwd: [Re: cvs commit: src/sys/vm vm_map.c]"

2010 Oct 30
2
Conquer Online 2.0
Hi guys! I'm trying to install Conquer Online (http://co.91.com/). And it's not running, I already have played this game using Wine but it was about year ago I think. Here are details what I've tried: Code: OS: Arch Linux 32-bit Kernel: 2.6.35 Wine: 1.3.6 Mesa: 7.8.2-3 xf86-video-intel: 2.12.0-3 Compiz: switched off Code: [tjr at redqueen ~]$ lspci -v -s 00:02 00:02.0 VGA
2003 Oct 01
1
latest cvsup to stable kernel build fall down, go boom
GENERIC kernel build, cvsup as of 21:37 October 1 2003: ../../vm/vm_map.c: In function `vm_init2': ../../vm/vm_map.c:190: `maxfiles' undeclared (first use in this function) ../../vm/vm_map.c:190: (Each undeclared identifier is reported only once ../../vm/vm_map.c:190: for each function it appears in.) *** Error code 1 Using the freebsd protector patch (anti stack smashing), FYI.
2003 Sep 06
1
Squid memory leaks in -stable using libc malloc
Hi, Using Squid with libc's malloc, I'm seeing a big difference between what top reports as memory used for the squid process (SIZE) and what Squid's cache manager reports that Squid has allocated (total KB allocated in the memory utilization page). Squid is using around twice as much memory as expected, and seems to grow without bounds (I run out of memory every now and then).
2003 Oct 01
0
[releng_4 tinderbox] failure on alpha/alpha
TB --- 2003-10-02 04:00:01 - starting RELENG_4 tinderbox run for alpha/alpha TB --- 2003-10-02 04:00:01 - checking out the source tree TB --- cd /home/des/tinderbox/RELENG_4/alpha/alpha TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src TB --- 2003-10-02 04:07:38 - building world TB --- cd /home/des/tinderbox/RELENG_4/alpha/alpha/src TB --- /usr/bin/make -B buildworld >>>
2003 Oct 01
0
[releng_4 tinderbox] failure on i386/i386
TB --- 2003-10-02 04:44:07 - starting RELENG_4 tinderbox run for i386/i386 TB --- 2003-10-02 04:44:07 - checking out the source tree TB --- cd /home/des/tinderbox/RELENG_4/i386/i386 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src TB --- 2003-10-02 04:49:12 - building world TB --- cd /home/des/tinderbox/RELENG_4/i386/i386/src TB --- /usr/bin/make -B buildworld >>>
2004 May 26
0
FreeBSD Security Advisory FreeBSD-SA-04:11.msync
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-04:11.msync Security Advisory The FreeBSD Project Topic: buffer cache invalidation implementation issues Category: core Module: sys Announced:
2004 May 26
0
FreeBSD Security Advisory FreeBSD-SA-04:11.msync
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-04:11.msync Security Advisory The FreeBSD Project Topic: buffer cache invalidation implementation issues Category: core Module: sys Announced:
2003 Jun 10
2
CerbNG v1.0-RC2 is now avaliable!
Hello! We are proudly announce that CerbNG-1.0 Release Candidate 2 is now avaliable. There are many changes from RC1 (many new functionalities, some bug fixes, new interesting policies, new regression tests and more). It seems that CerbNG is stable for now, so we hope that the next version is going to be final 1.0 series release. We count on feedback from FreeBSD community in founding bugs (if
2003 Jun 10
2
CerbNG v1.0-RC2 is now avaliable!
Hello! We are proudly announce that CerbNG-1.0 Release Candidate 2 is now avaliable. There are many changes from RC1 (many new functionalities, some bug fixes, new interesting policies, new regression tests and more). It seems that CerbNG is stable for now, so we hope that the next version is going to be final 1.0 series release. We count on feedback from FreeBSD community in founding bugs (if
2007 Mar 16
0
freebsd-security Digest, Vol 201, Issue 2
? 2007-3-15???8:00?freebsd-security-request@freebsd.org ??? > Send freebsd-security mailing list submissions to > freebsd-security@freebsd.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.freebsd.org/mailman/listinfo/freebsd-security > or, via email, send a message with subject or body 'help' to > freebsd-security-request@freebsd.org
2003 Oct 01
1
4.9 RC1 (i386) mplayer induced panic
All: I cvsup'ed earlier this evening and am still able to reproduce this panic at will. Command line, panic backtrace, dmesg, ldd output, and mplayer version follow. If more information is needed, just let me know. % mplayer foo.mov [a quicktime file] [plays for awhile, and then panics] # gdb -k -s /usr/obj/usr/src/sys/LICHEN/kernel.debug -e /var/crash/kernel.2 -c /var/crash/vmcore.2
2003 Sep 09
1
Make installworld failure
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
2003 Aug 12
2
panic with today's stable
Did cvsup on a machine that does just mail processing (well, a lot of spam scanning) and it crashed not too much later. This kernel does not include MFC src/sys/kern/sys_process.c revisions 1.111 and 1.112: Use kmem_alloc_nofault() rather than kmem_alloc_pageable() in procfs_rwmem(). Use vm_page_hold() in place of vm_page_wire() since the page can be freed. Don't hold extra
2005 Jul 24
1
cvs commit: src/games/fortune/fortune fortune.c
On Sun, Jul 24, 2005 at 04:06:02PM +0200, Poul-Henning Kamp wrote: +> In message <20050724135738.GM46538@darkness.comp.waw.pl>, Pawel Jakub Dawidek writes: +> +> >We should probably test entropy quality on boot. +> >I've somewhere userland version of /sys/dev/rndtest/ which implements +> >FIPS140-2 tests for (P)RNGs. We can use put it into rc.d/ and warn users.
2015 Nov 11
0
[PATCH] instmem/gk20a: use DMA API CPU mapping
On 11/11/2015 06:07 PM, Alexandre Courbot wrote: > Commit 69c4938249fb ("drm/nouveau/instmem/gk20a: use direct CPU access") > tried to be smart while using the DMA-API by managing the CPU mappings of > buffers allocated with the DMA-API by itself. In doing so, it relied > on dma_to_phys() which is an architecture-private function not > available everywhere. This broke the
2008 Dec 07
2
zvol_read() and zvol_write().
I can''t find anything using those functions. Can they be removed? -- Pawel Jakub Dawidek http://www.wheel.pl pjd at FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type:
2007 Mar 14
1
Check PRIV_VFS_MOUNT when jailed.
Hi. I'd like to commit this patch: http://people.freebsd.org/~pjd/patches/vfs_mount.c.9.patch It currently should change nothing, but will be needed once we allow to grant privileges for jails. I'd like to commit it now, so I can experiment easier with my ZFS improvements. -- Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org
2007 Feb 18
3
Improper use of atomic_add_64().
Hi. I noticed that when non-64bit variable is given as a second argument to atomic_add_64() function, the result is invalid. I found few places where such situation occurs. I wonder how this got unnoticed with ztest, which fails on me within a few seconds (after I started to use Solaris atomic operations) on assertions. Maybe this only doesn''t work when compiled with gcc? Not sure, but
2013 Jun 08
1
Request for review: Sandboxing dhclient using Capsicum.
Hi. I have a series of patches to sandbox dhclient using Capsicum (capability mode and capability rights for descriptors). As usual, because chroot and setgid/setuid are not sandboxing mechanisms, there are many problems with the current sandboxing: - Access to various global namespaces (like process list, network, etc.). - Access to RAW UDP socket. - Read/write access to bpf. - Access to RAW
2015 Nov 11
2
[PATCH] instmem/gk20a: use DMA API CPU mapping
Commit 69c4938249fb ("drm/nouveau/instmem/gk20a: use direct CPU access") tried to be smart while using the DMA-API by managing the CPU mappings of buffers allocated with the DMA-API by itself. In doing so, it relied on dma_to_phys() which is an architecture-private function not available everywhere. This broke the build on several architectures. Since there is no reliable and portable