https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192426
Mark Linimon changed:
What|Removed |Added
Keywords||patch
Assignee|freebsd-ne
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192426
Robert Clipsham changed:
What|Removed |Added
Summary|[bpf] [panic]: Kernel panic |[bpf] [panic] [patch
Summary|[panic]: Kernel panic when |[bpf] [panic]: Kernel panic
|using BPF |when using BPF
--- Comment #7 from Mark Linimon ---
Over to maintainers.
--
You are receiving this mail because:
You are the assignee for the bug
Old Synopsis: [panic][bpf] periodically kernel panic and reboot
New Synopsis: [bpf] [panic] periodically kernel panic and reboot
State-Changed-From-To: open->feedback
State-Changed-By: linimon
State-Changed-When: Thu Jul 14 01:53:36 UTC 2011
State-Changed-Why:
Most likely not amd64-specific.
The following reply was made to PR kern/133490; it has been noted by GNATS.
From: plethor...@aim.com
To: bug-follo...@freebsd.org
Cc:
Subject: Re: kern/133490: [bpf] [panic] 'kmem_map too small' panic on Dell r900
when
bpf_bufsize and bpf_maxbufsize are increased
Date: Wed, 15 Apr
Old Synopsis: 'kmem_map too small' panic on Dell r900 when bpf_bufsize and
bpf_maxbufsize are increased
New Synopsis: [bpf] [panic] 'kmem_map too small' panic on Dell r900 when
bpf_bufsize and bpf_maxbufsize are increased
Responsible-Changed-From-To: freebsd-i386->
On Thu, Feb 23, 2006 at 03:19:46AM -0500, Kris Kennaway wrote:
> I ran tcpdump and killall tcpdump in a loop on 7.0, and after a few
> minutes it panicked with:
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 0; apic id = 00
> fault virtual address = 0x8
> fault code = supervis
I ran tcpdump and killall tcpdump in a loop on 7.0, and after a few
minutes it panicked with:
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x8
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc058d0fb
stack poi
