Date: Sun, 4 Jun 2000 10:44:40 -0700 (PDT) From: ahsank@one.net.pk To: freebsd-gnats-submit@FreeBSD.org Subject: kern/19000: Automatic Reebot, Fatal Message-ID: <20000604174440.8E15137B5C8@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 19000
>Category: kern
>Synopsis: Automatic Reebot, Fatal
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sun Jun 04 10:50:01 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator: Ahsan Khan
>Release: 4.0-RELEASE
>Organization:
Sun Communication Pvt. Ltd. Pakistan
>Environment:
ipv6# uname -a
FreeBSD ipv6.one.net.pk 4.0-RELEASE FreeBSD 4.0-RELEASE #0: Sun Jun 4 21:42:37
PKT 2000 root@ipv6.one.net.pk:/usr/src/sys/compile/toknow i386
ipv6#
>Description:
Dear Friends.
I have recently Setup a cache Server on FreeBSD from Linux.
The System Spec is
P-III
256MB RAM
9GB IDE
9x2 SCSI
DPT SCSI Card
FreeBSD 4.0 RELEASE
After applying patches for GRE from squid site and recompiling the following
additional feature in GENERIC kernel config
maxusers 128
ptions GRE
options PQ_LARGECACHE
options NMBCLUSTERS=8192
options SC_DISABLE_REBOOT # disable reboot key sequence
# If you have a two button mouse, you may want to add the following option
# to use the right button of the mouse to paste text.
options SC_TWOBUTTON_MOUSE
options MAXCONS=8 # number of virtual consoles
# Enable the kernel debugger.
#
options DDB
options DDB_UNATTENDED
options GDB_REMOTE_CHAT
options KTRACE #kernel tracing
options INVARIANTS
options INVARIANT_SUPPORT
options DIAGNOSTIC
options PERFMON
I am facing frequent reboot of the machine with no trace in logs. After 3
days effort I have found the following message on Consol before machine
reboot.
Fatal trap 12: page fault in kernel mode
fault virtual address =0x20
fault code =supervisor read, page not present
instruction pointer =0x8:0xc01e5d3d
stack pointer =0x10:0xc0331480
frame pointer =0x10:0xc033148c
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 =
trap number = 12
panic: page fault
syncing disks... 252 222 162 137 76 54 16
done
uptime: 1h15m21s
But remember I was using at that time maxusers256
after putting maxusr 98 and some kernel debug options now I got this message
in syslog and after some time it rebooted again when I believe it has no
number left in adjusted rtq_reallyold . It always started form 2400 and then
gradually goes down. and then reboot ,,
ipv6 /kernel: in_rtqtimo: adjusted rtq_reallyold to 2400
Can I get any help.?? I am working on it day and night and I need to stable
it.
With Regards
Ahsan Khan
Sr. System Admin
Internet Division (OneNet)
Sun Communication Pvt. Ltd.
Pakistan
http://www.one.net.pk
>How-To-Repeat:
Its happening again & again,,
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000604174440.8E15137B5C8>