From owner-freebsd-hackers Mon May 24 11:32:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from risingNet.net (RisingNet.NET [216.160.91.11]) by hub.freebsd.org (Postfix) with ESMTP id A1FB115083 for ; Mon, 24 May 1999 11:32:34 -0700 (PDT) (envelope-from boen@risingnet.net) Received: from master (Boen.KickazZ.org [207.108.221.178]) by risingNet.net (8.9.3/8.9.2) with SMTP id LAA08687 for ; Mon, 24 May 1999 11:36:36 -0700 (PDT) (envelope-from boen@risingnet.net) Message-ID: <018701bea613$d3442300$b2dd6ccf@master> From: "Anton Bun" To: Subject: Fatal trap 12 Date: Mon, 24 May 1999 11:32:46 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear FreeBSD, I'm using FreeBSD-3.1-RELEASE. My box are running 120 eggdrop bots, 5 BitchX and 12 BNC the box keep getting fatal error 12 every 1 - 2 days go longer than = that.=20 I have 256 MB RAM 450MHZ Pentium II=20 swap file system 512 MB=20 my fatal error 12 messages : panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address =3D 0xc47864 fault code =3D supervisor read, page not present instruction pointer =3D 0x8:0xf01a1aff stack pointer =3D 0x10:0xf9135f74 frame pointer =3D 0x10:0xf9135f7c code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, def32 1, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 44565 (cc1) interrupt mask =3D=20 trap number =3D 12 panic: page fault syncing disks... 95 94 55 31 done dumping to dev 20401, offset 535344 dump 256 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 = 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 = 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 = 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 = 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 = 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 = 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 = 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 = 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 = 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 = 70 69 68 67 66 65 64 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=20 --- #0 0xf0151063 in boot () (kgdb) where #0 0xf0151063 in boot () #1 0xf01512e8 in at_shutdown () #2 0xf02043c1 in trap_fatal () #3 0xf020409f in trap_pfault () #4 0xf0203d42 in trap () #5 0xf01a1aff in tcp_fasttimo () #6 0xf016673b in pffasttimo () #7 0xf0155737 in softclock () #8 0xf01fce53 in doreti_swi () #9 0x81093f9 in ?? () #10 0x810ad99 in ?? () #11 0x810abb2 in ?? () #12 0x8070f90 in ?? () #13 0x8052629 in ?? () #14 0x8048e83 in ?? () #15 0x80700b0 in ?? () #16 0x80725d6 in ?? () #17 0x80480e9 in ?? () (kgdb)=20 Are they any other way to keep my box up and not getting fatal error 12. = I already send email to: Doug White =20 Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org and he said :=20 Hm, I wonder why there are no function names below frame #9. Based on what's crashing, cc1, I'm guessing bad memory or processor cache, in a pretty serious way. Please check your memory type and settings. Please send this information, including your system version, to hackers@freebsd.org. Make sure you've followed the instructions in the kernel debugging section of the Handbook to the best of your ability. =20 =20 Thank You=20 =20 Anton Bun (System Administrator) www.RisingNet.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message