🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

6 total messages Started by Sokim Mon, 23 Mar 2009 19:32
kernel panic - FreeBSD 6.4 Stable
#20806
Author: Sokim
Date: Mon, 23 Mar 2009 19:32
120 lines
6644 bytes
Cześć,
jest tu może jakiś developer, który zrozumie ten zrzut pamięci? Mam duży 
problem ze stabilnością routera, działa 5 dni bez problemu po czym przez 
godzinę potrafi się trzy razy zrebootować. Poniżej przesyłam zrzut 
pamięci. Router jest średnio obciążony, ok 50Mbit ruchu, 3 sesje BGP z 
pełnymi tablicami, Nat (ipnat), shaping (dummynet). Może problem tkwi w 
połączeniu BGP z NATem? Ma ktoś odpalonego NATa na routerze BGP?

z góry dziękuje za wszelkie sugestie, pozdrawiam
Mikołaj



# kgdb kernel.debug /var/crash/vmcore.0
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain 
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd"...

Unread portion of the kernel message buffer:


Fatal trap 12: page fault while in kernel mode
fault virtual address   = 0xc
fault code              = supervisor read, page not present
instruction pointer     = 0x20:0xc05cc4f0
stack pointer           = 0x28:0xe328aa20
frame pointer           = 0x28:0xe328aa2c
code segment            = base 0x0, limit 0xfffff, type 0x1b
                         = DPL 0, pres 1, def32 1, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 11 (swi1: net)
trap number             = 12
panic: page fault
Uptime: 5d22h10m3s
Dumping 999 MB (2 chunks)
   chunk 0: 1MB (159 pages) ... ok
   chunk 1: 999MB (255665 pages) 983 967 951 935 919 903 887 871 855 839 
823 807 791 775 759 743 727 711 695 679 663 647 631 615 599 583 567 551 
535 519 503 487 471 455 439 423 407 391 375 359 343 327 311 295 279 263 
247 231 215 199 183 167 151 135 119 103 87 71 55 39 23 7

Reading symbols from /boot/kernel/acpi.ko...done.
Loaded symbols for /boot/kernel/acpi.ko
#0  doadump () at pcpu.h:165
165             __asm __volatile("movl %%fs:0,%0" : "=r" (td));
(kgdb)
(kgdb) list *0xc05cc4f0
0xc05cc4f0 is in m_copydata (libkern.h:56).
51      static __inline int imax(int a, int b) { return (a > b ? a : b); }
52      static __inline int imin(int a, int b) { return (a < b ? a : b); }
53      static __inline long lmax(long a, long b) { return (a > b ? a : 
b); }
54      static __inline long lmin(long a, long b) { return (a < b ? a : 
b); }
55      static __inline u_int max(u_int a, u_int b) { return (a > b ? a 
: b); }
56      static __inline u_int min(u_int a, u_int b) { return (a < b ? a 
: b); }
57      static __inline quad_t qmax(quad_t a, quad_t b) { return (a > b 
? a : b); }
58      static __inline quad_t qmin(quad_t a, quad_t b) { return (a < b 
? a : b); }
59      static __inline u_long ulmax(u_long a, u_long b) { return (a > b 
? a : b); }
60      static __inline u_long ulmin(u_long a, u_long b) { return (a < b 
? a : b); }
(kgdb) backtrace
#0  doadump () at pcpu.h:165
#1  0xc059578e in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:410
#2  0xc0595a24 in panic (fmt=0xc079ab85 "%s") at 
/usr/src/sys/kern/kern_shutdown.c:566
#3  0xc076d408 in trap_fatal (frame=0xe328a9e0, eva=12) at 
/usr/src/sys/i386/i386/trap.c:838
#4  0xc076d16f in trap_pfault (frame=0xe328a9e0, usermode=0, eva=12) at 
/usr/src/sys/i386/i386/trap.c:745
#5  0xc076cdcd in trap (frame=
       {tf_fs = -996278264, tf_es = -483917784, tf_ds = -1067974616, 
tf_edi = 1, tf_esi = 0, tf_ebp = -483874260, tf_isp = -483874292, tf_ebx 
= 31, tf_edx = 0, tf_ecx = 0, tf_eax = 4684827, tf_trapno = 12, tf_err = 
0, tf_eip = -1067662096, tf_cs = 32, tf_eflags = 590338, tf_esp = 
-925909824, tf_ss = -925909813}) at /usr/src/sys/i386/i386/trap.c:435
#6  0xc075a96a in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#7  0xc05cc4f0 in m_copydata (m=0x0, off=0, len=1, cp=0xc8cfbcea "ction 
refused\r\n227 Entering Passive Mode (194,177,4,239,237,103).\r\n200 
PORT co\034\006") at /usr/src/sys/kern/uipc_mbuf.c:543
#8  0xc0450be2 in ippr_ftp_process (fin=0xe328ab6c, nat=0xc8b9d200, 
ftp=0xc8cfbc00, rv=1) at ip_ftp_pxy.c:1166
#9  0xc0450f26 in ippr_ftp_in (fin=0xe328ab6c, aps=0x477c1b, 
nat=0xc8b9d200) at ip_ftp_pxy.c:1332
#10 0xc04556f9 in appr_check (fin=0xe328ab6c, nat=0xc8b9d200) at 
/usr/src/sys/contrib/ipfilter/netinet/ip_proxy.c:543
#11 0xc044db61 in fr_natin (fin=0xe328ab6c, nat=0xc8b9d200, natadd=1, 
nflags=1) at /usr/src/sys/contrib/ipfilter/netinet/ip_nat.c:4228
#12 0xc044da3a in fr_checknatin (fin=0xe328ab6c, passp=0xe328ab68) at 
/usr/src/sys/contrib/ipfilter/netinet/ip_nat.c:4163
#13 0xc043f585 in fr_check (ip=0xc8884010, hlen=20, ifp=0x477c1b, out=0, 
mp=0xe328ac54) at /usr/src/sys/contrib/ipfilter/netinet/fil.c:2572
#14 0xc0445062 in fr_check_wrapper (arg=0x0, mp=0x0, ifp=0xc4b26000, 
dir=1) at /usr/src/sys/contrib/ipfilter/netinet/ip_fil_freebsd.c:178
#15 0xc060ff03 in pfil_run_hooks (ph=0xc08626a0, mp=0xe328aca8, 
ifp=0xc4b26000, dir=1, inp=0x0) at /usr/src/sys/net/pfil.c:139
#16 0xc062fbb7 in ip_input (m=0xc884f600) at 
/usr/src/sys/netinet/ip_input.c:468
#17 0xc060ea73 in netisr_processqueue (ni=0xc0861358) at 
/usr/src/sys/net/netisr.c:236
#18 0xc060ec6e in swi_net (dummy=0x0) at /usr/src/sys/net/netisr.c:349
#19 0xc057d55d in ithread_execute_handlers (p=0xc4a21a78, ie=0xc4a71280) 
at /usr/src/sys/kern/kern_intr.c:682
#20 0xc057d678 in ithread_loop (arg=0xc4a02720) at 
/usr/src/sys/kern/kern_intr.c:766
#21 0xc057c4e4 in fork_exit (callout=0xc057d624 <ithread_loop>, 
arg=0xc4a02720, frame=0xe328ad38) at /usr/src/sys/kern/kern_fork.c:788
#22 0xc075a9cc in fork_trampoline () at 
/usr/src/sys/i386/i386/exception.s:208
(kgdb) quit
Re: kernel panic - FreeBSD 6.4 Stable
#20807
Author: Bodek
Date: Tue, 24 Mar 2009 10:35
13 lines
921 bytes
at Mon 23 of Mar 2009 20:32, Sokim wrote:

> Cześć,
> jest tu może jakiś developer, który zrozumie ten zrzut pamięci? 

...

To developerzy już nie handlują nieruchomościami?



-- 
Bodek
Re: kernel panic - FreeBSD 6.4 Stable
#20808
Author: Sokim
Date: Tue, 24 Mar 2009 14:01
9 lines
1213 bytes
Bodek pisze:
> at Mon 23 of Mar 2009 20:32, Sokim wrote:
> > 
> To developerzy już nie handlują nieruchomościami?
> 

Nie. Ale podobno ostatnio wszyscy zaczęli pracować dla microsoftu...

http://video.google.com/videoplay?docid=6304687408656696643
Re: kernel panic - FreeBSD 6.4 Stable
#20809
Author: Tomasz Piłat
Date: Wed, 25 Mar 2009 13:37
16 lines
1605 bytes
Sokim <sokim@wp.pl> wrote:
> Cześć,
> jest tu może jakiś developer, który zrozumie ten zrzut pamięci? Mam duży 
> problem ze stabilnością routera, działa 5 dni bez problemu po czym przez 
> godzinę potrafi się trzy razy zrebootować. Poniżej przesyłam zrzut 
> pamięci. Router jest średnio obciążony, ok 50Mbit ruchu, 3 sesje BGP z 
> pełnymi tablicami, Nat (ipnat), shaping (dummynet). Może problem tkwi w 
> połączeniu BGP z NATem? Ma ktoś odpalonego NATa na routerze BGP?

Raczej wygląda na okolice FTP proxy ipfiltera...

Pokaż jeszcze kern.ipc.nmbclusters...

Ponc
-- 
Kto misiowi urwał ucho?
Re: kernel panic - FreeBSD 6.4 Stable
#20810
Author: Sokim
Date: Wed, 25 Mar 2009 14:34
10 lines
1153 bytes
Tomasz Piłat pisze:
> 
> Raczej wygląda na okolice FTP proxy ipfiltera...
> 
> Pokaż jeszcze kern.ipc.nmbclusters...
> 
> Ponc


kern.ipc.nmbclusters: 25600
Re: kernel panic - FreeBSD 6.4 Stable
#20811
Author: Sokim
Date: Wed, 25 Mar 2009 15:48
63 lines
3574 bytes
Tomasz Piłat pisze:
> Sokim <sokim@wp.pl> wrote:
> 
> Raczej wygląda na okolice FTP proxy ipfiltera...
> 
> Pokaż jeszcze kern.ipc.nmbclusters...
> 
> Ponc

Przesyłam jeszcze moje regułki ipnata...


map em0 192.168.1.0/24 -> xxx.yyy.zzz.3/32 proxy port ftp ftp/tcp
map em0 192.168.1.0/24 -> xxx.yyy.zzz.3/32 portmap tcp/udp auto
map em0 192.168.1.0/24 -> xxx.yyy.zzz.3/32

map em0 192.168.12.0/24 -> xxx.yyy.zzz.3/32 proxy port ftp ftp/tcp
map em0 192.168.12.0/24 -> xxx.yyy.zzz.3/32 portmap tcp/udp auto
map em0 192.168.12.0/24 -> xxx.yyy.zzz.3/32

map em0 192.168.13.0/24 -> xxx.yyy.zzz.4/32 proxy port ftp ftp/tcp
map em0 192.168.13.0/24 -> xxx.yyy.zzz.4/32 portmap tcp/udp auto
map em0 192.168.13.0/24 -> xxx.yyy.zzz.4/32

map em0 192.168.26.0/24 -> xxx.yyy.zzz.4/32 proxy port ftp ftp/tcp
map em0 192.168.26.0/24 -> xxx.yyy.zzz.4/32 portmap tcp/udp auto
map em0 192.168.26.0/24 -> xxx.yyy.zzz.4/32

map em0 192.168.16.0/24 -> xxx.yyy.zzz.5/32 proxy port ftp ftp/tcp
map em0 192.168.16.0/24 -> xxx.yyy.zzz.5/32 portmap tcp/udp auto
map em0 192.168.16.0/24 -> xxx.yyy.zzz.5/32

map em0 192.168.17.0/24 -> xxx.yyy.zzz.5/32 proxy port ftp ftp/tcp
map em0 192.168.17.0/24 -> xxx.yyy.zzz.5/32 portmap tcp/udp auto
map em0 192.168.17.0/24 -> xxx.yyy.zzz.5/32

map em0 192.168.25.0/24 -> xxx.yyy.zzz.6/32 proxy port ftp ftp/tcp
map em0 192.168.25.0/24 -> xxx.yyy.zzz.6/32 portmap tcp/udp auto
map em0 192.168.25.0/24 -> xxx.yyy.zzz.6/32

map em0 192.168.52.0/24 -> xxx.yyy.zzz.7/32 proxy port ftp ftp/tcp
map em0 192.168.52.0/24 -> xxx.yyy.zzz.7/32 portmap tcp/udp auto
map em0 192.168.52.0/24 -> xxx.yyy.zzz.7/32

map em0 192.168.27.0/24 -> xxx.yyy.zzz.7/32 proxy port ftp ftp/tcp
map em0 192.168.27.0/24 -> xxx.yyy.zzz.7/32 portmap tcp/udp auto
map em0 192.168.27.0/24 -> xxx.yyy.zzz.7/32

map em0 10.0.10.0/24 -> xxx.yyy.zzz.8/32 proxy port ftp ftp/tcp
map em0 10.0.10.0/24 -> xxx.yyy.zzz.8/32 portmap tcp/udp auto
map em0 10.0.10.0/24 -> xxx.yyy.zzz.8/32

map em0 10.0.11.0/24 -> xxx.yyy.zzz.9/32 proxy port ftp ftp/tcp
map em0 10.0.11.0/24 -> xxx.yyy.zzz.9/32 portmap tcp/udp auto
map em0 10.0.11.0/24 -> xxx.yyy.zzz.9/32

map em0 10.0.12.0/24 -> xxx.yyy.zzz.10/32 proxy port ftp ftp/tcp
map em0 10.0.12.0/24 -> xxx.yyy.zzz.10/32 portmap tcp/udp auto
map em0 10.0.12.0/24 -> xxx.yyy.zzz.10/32

map em0 192.168.100.0/24 -> xxx.yyy.zzz.10/32 proxy port ftp ftp/tcp
map em0 192.168.100.0/24 -> xxx.yyy.zzz.10/32 portmap tcp/udp auto
map em0 192.168.100.0/24 -> xxx.yyy.zzz.10/32
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads