Specifically, I am taking this panic when doing ip spoof attack while
syn-proxy activated. The output of system arguments below:
kern.malloc_count: 315
vm.md_malloc_wait: 0
vfs.bufmallocspace: 0
vfs.maxmallocbufspace: 86269952
vm.kmem_size: 16686845952
vm.kmem_size_min: 0
vm.kmem_size_max:
I've been under the impression that synproxy was broken for quite some
time, but I know there has been a lot of work on pf in HEAD so I can't
be sure where it might stand there. Can anyone confirm/deny this?
And not to discourage you, but the pf documentation does say Routine
use of this option
I had 2 panics: (Both occured at 3 AM, so had to be daily task)
First (Jul 2 03:06:50 2013):
--
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x19
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc06caf34
I report the current status of fsyscall/nexec.
fsyscall[1] is a system to transfer system call requests over network. The
goal of it is using FreeBSD applications at another machine (including
non-FreeBSD machines) without any modifications of applications. nexec[2]
is a system to make
On Friday, July 26, 2013 9:04:42 am rank1see...@gmail.com wrote:
I had 2 panics: (Both occured at 3 AM, so had to be daily task)
First (Jul 2 03:06:50 2013):
--
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x19
fault code = supervisor
I had 2 panics: (Both occured at 3 AM, so had to be daily task)
First (Jul 2 03:06:50 2013):
--
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x19
fault code = supervisor read, page not present
instruction pointer =
I've made a number of improvements to the write performance of the CFI
flash driver. The patch below merges the remaining changes. I've only
implemented buffered write on Intel flash as that's all I currently have
access to. I'm looking for review and/or testing of these changes.
On Friday, July 26, 2013 3:00:33 pm rank1see...@gmail.com wrote:
I had 2 panics: (Both occured at 3 AM, so had to be daily task)
First (Jul 2 03:06:50 2013):
--
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x19
fault code
Hi
Have you filed a PR? This should get fixed.
Also, being -ve is a problem. Is the value really negative? Is it
wrapping badly?
-adrian
On 25 July 2013 07:57, Tugrul Erdogan h.tugrul.erdo...@gmail.com wrote:
howdy all,
At my work, I am using 10.0-CURRENT on Intel(R) Xeon(R) E5620 with
9 matches
Mail list logo