Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 15 Jun 2001 08:44:21 -0300 (BRT)
From:      Paulo Fragoso <paulo@nlink.com.br>
To:        <freebsd-hardware@FreeBSD.ORG>
Subject:   Reboots
Message-ID:  <20010615081926.V10848-100000@mirage.nlink.com.br>

next in thread | raw e-mail | index | archive | help
Hi,

We've got a router using 1 - Etinc <ET/5025PQ QUAD Adapter> (Wan card) and
3 - 3Com 3c905C-TX. We are using 4.2-RELEASE and that system reboots
several times at day.

We've compiled the kernel with -g and following:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kerneldebug.html

We can find this:

hercules{root}:/sys/compile/KERNEL3:14# gdb -k
GNU gdb 4.18
Copyright 1998 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-unknown-freebsd".
(kgdb) symbol-file kernel.debug
Reading symbols from kernel.debug...done.
(kgdb) exec-file /var/crash/kernel.1
(kgdb) core-file /var/crash/vmcore.1
IdlePTD 4304896
initial pcb at 352100
panicstr: page fault
panic messages:
---
Fatal trap 12: page fault while in kernel mode
fault virtual address   = 0x9fc00e00
fault code              = supervisor read, page not present
instruction pointer     = 0x8:0xc019ed4c
stack pointer           = 0x10:0xc03234dc
frame pointer           = 0x10:0xc03234f8
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         = Idle
interrupt mask          = net tty
trap number             = 12
panic: page fault

syncing disks...
done
Uptime: 4m36s
xl0: command never completed!
xl0: command never completed!
xl1: command never completed!
xl1: command never completed!
xl2: command never completed!
xl2: command never completed!

dumping to dev #ad/0x30001, offset 131104
dump ata0: resetting devices .. done
63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39
38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14
13 12 11 10 9 8 7 6 5 4 3 2 1 0
---
#0  dumpsys () at ../../kern/kern_shutdown.c:469
469             if (dumping++) {
(kgdb) where
#0  dumpsys () at ../../kern/kern_shutdown.c:469
#1  0xc018741f in boot (howto=256) at ../../kern/kern_shutdown.c:309
#2  0xc018779c in poweroff_wait (junk=0xc0317baf, howto=0)
    at ../../kern/kern_shutdown.c:556
#3  0xc0295c35 in trap_fatal (frame=0xc032349c, eva=2680163840)
    at ../../i386/i386/trap.c:951
#4  0xc029590d in trap_pfault (frame=0xc032349c, usermode=0,
eva=2680163840)
    at ../../i386/i386/trap.c:844
#5  0xc02954c7 in trap (frame={tf_fs = -1071906800, tf_es = 6422544,
      tf_ds = 16, tf_edi = -1070451468, tf_esi = 6422528,
      tf_ebp = -1070451464, tf_isp = -1070451512, tf_ebx = 1,
      tf_edx = -1614803456, tf_ecx = 1, tf_eax = 6422528, tf_trapno = 12,
      tf_err = 0, tf_eip = -1072042676, tf_cs = 8, tf_eflags = 66182,
      tf_esp = -1036100864, tf_ss = -1070249612}) at
../../i386/i386/trap.c:443
#6  0xc019ed4c in m_copym (m=0xc0a84900, off0=0, len=40, wait=1)
    at ../../kern/uipc_mbuf.c:621
#7  0xc01dc08b in ip_forward (m=0xc0a84900, srcrt=0)
    at ../../netinet/ip_input.c:1508
#8  0xc01db1c2 in ip_input (m=0xc0a84900) at ../../netinet/ip_input.c:563
#9  0xc01db52f in ipintr () at ../../netinet/ip_input.c:759
(kgdb) up 10
#9  0xc01db52f in ipintr () at ../../netinet/ip_input.c:759
759                     ip_input(m);
(kgdb) list
754                     s = splimp();
755                     IF_DEQUEUE(&ipintrq, m);
756                     splx(s);
757                     if (m == 0)
758                             return;
759                     ip_input(m);
760             }
761     }
762
763     /*
(kgdb)

How we aren't expert with kernel dumps any answer will help us.

Is that a hardware problmes, or any DOS attack?

We are using DUMMYNET for some control flow, can be this the problem?

We've changed the motherboard (was an Intel now an ASUS), 3 network
adapter (was two ISA and an Intel fxp now three 3Com) and the memory. We
are using same Etinc Wan Adapter (eth0).

Many Thanks,
Paulo.

-- 
   __O
 _-\<,_     Why drive when you can bike?
(_)/ (_)



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hardware" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010615081926.V10848-100000>