Fatal trap 12 after upgrading from 8.2 to 8.4
I've got a system running on a VPS that I'm trying to upgrade from 8.2 to 8.4. It has a ZFS root. After booting the new kernel, I get: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x40 fault code = supervisor read data, page not present instruction pointer = 0x20:0x810d7691 stack pointer = 0x28:0xff81ba60 frame pointer = 0x28:0xff81ba90 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 1 (kernel) trap number = 12 panic: page fault cpuid = 0 KDB: stack backtrace: #0 0x8066cb96 at kdb_backtrace+0x66 #1 0x8063925e at panic+0x1ce #2 0x809c21d0 at trap_fatal+0x290 #3 0x809c255e at trap_pfault+0x23e #4 0x809c2a2e at trap+0x3ce #5 0x809a9624 at calltrap+0x8 #6 0x810df517 at vdev_mirror_child_select+0x67 #7 0x810dfacc at vdev_mirror_io_start+0x24c #8 0x810f7c52 at zio_vdev_io_start+0x232 #9 0x810f76f3 at zio_execute+0xc3 #10 0x810f77ad at zio_wait+0x2d #11 0x8108991e at arc_read+0x6ce #12 0x8109d9d4 at dmu_objset_open_impl+0xd4 #13 0x810b4014 at dsl_pool_init+0x34 #14 0x810c7eea at spa_load+0x6aa #15 0x810c90b2 at spa_load_best+0x52 #16 0x810cb0ca at spa_open_common+0x14a #17 0x810a892d at dsl_dir_open_spa+0x2cd Uptime: 3s Cannot dump. Device not defined or unavailable. I've booted back into the 8.2 kernel without any problems, but I'm wondering if anyone can suggest what I should try to get this working? I used freebsd-update to upgrade, and this was after the first "freebsd-update install" where it installs the kernel. My /boot/loader.conf has: zfs_load="YES" vfs.root.mountfrom="zfs:zroot" Patrick ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Fatal trap 12: page fault while in kernel mode in FreeBSD 9.1
Hi, I recently upgraded from 9.0 to 9.1 and have scince been seeing a lot of system freezes. The system will sometimes freeze when I launch an application soon after startup. If it does not freeze soon after startup it tends to run fine for the rest of the day. Full copy of core.txt @ http://pastebin.com/ezfAGGFL --core.txt.0--- FreeBSD quadcore 9.1-RELEASE-p3 FreeBSD 9.1-RELEASE-p3 #0: Mon Apr 29 18:27:25 UTC 2013 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 panic: page fault 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 "amd64-marcel-freebsd"... Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x8008 fault code = supervisor read data, page not present instruction pointer = 0x20:0x80976e19 stack pointer = 0x28:0xff8235870630 frame pointer = 0x28:0xff8235870660 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 1720 (mount_fusefs) trap number = 12 panic: page fault cpuid = 0 KDB: stack backtrace: #0 0x809208d6 at kdb_backtrace+0x66 #1 0x808ea8ee at panic+0x1ce #2 0x80bd8270 at trap_fatal+0x290 #3 0x80bd85ad at trap_pfault+0x1ed #4 0x80bd8bce at trap+0x3ce #5 0x80bc318f at calltrap+0x8 #6 0x8261a2f4 at fuse_mount+0x94 #7 0x80979371 at vfs_donmount+0x1081 #8 0x80979ad6 at sys_nmount+0x66 #9 0x80bd7b16 at amd64_syscall+0x546 #10 0x80bc3477 at Xfast_syscall+0xf7 Uptime: 4m32s Dumping 545 out of 8156 MB:..3%..12%..21%..33%..42%..53%..62%..71%..83%..91% ... (kgdb) #0 doadump (textdump=Variable "textdump" is not available. ) at pcpu.h:224 #1 0x808ea3d1 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:448 #2 0x808ea8c7 in panic (fmt=0x1 ) at /usr/src/sys/kern/kern_shutdown.c:636 #3 0x80bd8270 in trap_fatal (frame=0xc, eva=Variable "eva" is not available. ) at /usr/src/sys/amd64/amd64/trap.c:857 #4 0x80bd85ad in trap_pfault (frame=0xff8235870580, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:773 #5 0x80bd8bce in trap (frame=0xff8235870580) at /usr/src/sys/amd64/amd64/trap.c:456 #6 0x80bc318f in calltrap () at /usr/src/sys/amd64/amd64/exception.S:228 #7 0x80976e19 in vfs_getopts (opts=0x8008, name=0x82621368 "fspath", error=0xff82358707ac) at /usr/src/sys/kern/vfs_mount.c:1516 #8 0x8261a2f4 in fuse_mount () from /usr/local/modules/fuse.ko #9 0xfe000c6678e0 in ?? () #10 0xfe000c6678e0 in ?? () #11 0x00020202 in ?? () #12 0xfe022ffebaa8 in ?? () #13 0xfe000c6678e0 in ?? () #14 0x01020c6678e0 in ?? () #15 0x in ?? () #16 0xfe022ffea3a8 in ?? () #17 0x8119cb80 in see_other_uids () #18 0xff8235870700 in ?? () #19 0x808d598b in malloc_type_zone_allocated (mtp=0xfe000c6678e0, size=18446741874894338272, zindx=32776) at /usr/src/sys/kern/kern_malloc.c:368 Previous frame inner to this frame (corrupt stack?) (kgdb) Any ideas? thx ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Fatal trap 12: page fault while in kernel mode
Hi, I have got these after running Freebsd 8.1 Release p1 Amd64 for a couple hours, i have done kernel debugging it seems has anything to do with sched_ule? : admin# 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 "amd64-marcel-freebsd"... Unread portion of the kernel message buffer: kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 2; apic id = 02 fault virtual address = 0x210 fault code = supervisor read data, page not present instruction pointer = 0x20:0x80392403 stack pointer = 0x28:0xff869b30 frame pointer = 0x28:0xff869ba0 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= resume, IOPL = 0 current process = 12 (swi4: clock) trap number = 12 panic: page fault cpuid = 2 Uptime: 3h43m34s Physical memory: 4073 MB Dumping 2401 MB: 2386 Fatal trap 1: privileged instruction fault while in kernel mode cpuid = 1; apic id = 01 instruction pointer = 0x20:0xff8695a0 stack pointer = 0x28:0xff80ae41bb30 frame pointer = 0x28:0xff80ae41bb60 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 12 (irq15: ata1) trap number = 1 2370 2354 2338 2322 2306 2290 2274 2258 2242 2226 2210 2194 2178 2162 2146 2130 2114 2098 2082 2066 2050 2034 2018 2002 1986 1970 1954 1938 1922 1906 1890 1874 1858 1842 1826 1810 1794 1778 1762 1746 1730 1714 1698 1682 1666 1650 1634 1618 1602 1586 1570 1554 1538 1522 1506 1490 1474 1458 1442 1426 1410 1394 1378 1362 1346 1330 1314 1298 1282 1266 1250 1234 1218 1202 1186 1170 1154 1138 1122 1106 1090 1074 1058 1042 1026 1010 994 978 962 946 930 914 898 882 866 850 834 818 802 786 770 754 738 722 706 690 674 658 642 626 610 594 578 562 546 530 514 498 482 466 450 434 418 402 386 370 354 338 322 306 290 274 258 242 226 210 194 178 162 146 130 114 98 82 66 50 34 18 2 Reading symbols from /boot/kernel/zfs.ko...Reading symbols from /boot/kernel/zfs.ko.symbols...done. done. Loaded symbols for /boot/kernel/zfs.ko Reading symbols from /boot/kernel/opensolaris.ko...Reading symbols from /boot/kernel/opensolaris.ko.symbols...done. done. Loaded symbols for /boot/kernel/opensolaris.ko Reading symbols from /boot/kernel/krpc.ko...Reading symbols from /boot/kernel/krpc.ko.symbols...done. done. Loaded symbols for /boot/kernel/krpc.ko Reading symbols from /boot/kernel/geom_mirror.ko...Reading symbols from /boot/kernel/geom_mirror.ko.symbols...done. done. Loaded symbols for /boot/kernel/geom_mirror.ko #0 doadump () at pcpu.h:223 223 (kgdb) list *0x80392403 0x80392403 is in softclock (/usr/src/sys/kern/kern_timeout.c:356). 351 cc->cc_softticks++; 352 bucket = &cc->cc_callwheel[curticks & callwheelmask]; 353 c = TAILQ_FIRST(bucket); 354 while (c) { 355 depth++; 356 if (c->c_time != curticks) { 357 c = TAILQ_NEXT(c, c_links.tqe); 358 ++steps; 359 if (steps >= MAX_SOFTCLOCK_STEPS) { 360 cc->cc_next = c; (kgdb) list *0xff8695a0 No source file for address 0xff8695a0. (kgdb) list *0xff8695a0 No source file for address 0xff8695a0. (kgdb) backtrace #0 doadump () at pcpu.h:223 #1 0x8037cf6a in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:416 #2 0x8037d399 in panic (fmt=0x80632a5c "%s") at /usr/src/sys/kern/kern_shutdown.c:590 #3 0x805ae847 in trap_fatal (frame=0xff869a80, eva=33554448) at /usr/src/sys/amd64/amd64/trap.c:777 #4 0x805af693 in trap (frame=0xff869a80) at /usr/src/sys/amd64/amd64/trap.c:300 #5 0x80592674 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:223 #6 0x80392403 in softclock (arg=Variable "arg" is not available. ) at /usr/src/sys/kern/kern_timeout.c:355 #7 0x8035224d in intr_event_execute_handlers (p=Variable "p" is not available. ) at /usr/src/sys/kern/kern_intr.c:1220 #8 0x80353962 in ithread_loop (arg=0xff000168b460) at /usr/src/sys/kern/kern_intr.c:1233 #9 0xff
Fatal trap 12: page fault while in kernel mode
On a recently, from FreeBSD7.2 to 8.0, upgraded system, I got a spontaneous reboot during last night. A crash dump was made. files in /var/crash contain: # cat info.0 Dump header from device /dev/da0s1b Architecture: amd64 Architecture Version: 2 Dump Length: 2046042112B (1951 MB) Blocksize: 512 Dumptime: Sat Jul 10 00:22:39 2010 Hostname: radix.cmi.ua.ac.be Magic: FreeBSD Kernel Dump Version String: FreeBSD 8.0-RELEASE-p2 #0: Thu Feb 25 09:59:40 CET 2010 r...@radix.cmi.ua.ac.be:/usr/obj/usr/src/sys/GENERICQ Panic String: page fault Dump Parity: 1570614093 Bounds: 0 Dump Status: good File core.txt.0 is 3276 lines, so this for now I dont' post. If there are parts relevant, I will post them when asked. On the other hand, I followed FreeBSD Manual Ch 18.13 "How can I make the most of the data I see when my kernel panics?" and gathered the output of kgdb (see below) (my custom kernel "GENERICQ" is exactly the same os the GENERIC kernel except that disk quota is enabled, no other changes) What's the cause and how to get this solved? Is it a known bug in FreeBSD 8.0 radix# kgdb /usr/obj/usr/src/sys/GENERICQ/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 "amd64-marcel-freebsd"... Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 3; apic id = 03 fault virtual address = 0x80 fault code = supervisor read data, page not present instruction pointer = 0x20:0x805a6761 stack pointer = 0x28:0xff8a0a60 frame pointer = 0x28:0xff8a0aa0 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 12 (swi6: task queue) trap number = 12 panic: page fault cpuid = 3 Uptime: 38d14h25m5s Physical memory: 8178 MB Dumping 1951 MB:panic: bufwrite: buffer is not busy??? cpuid = 3 1936 1920 1904 1888 1872 1856 1840 1824 1808 1792 1776 1760 1744 1728 1712 1696 1680 1664 1648 1632 1616 1600 1584 1568 1552 1536 1520 1504 1488 1472 1456 1440 1424 1408 1392 1376 1360 1344 1328 1312 1296 1280 1264 1248 1232 1216 1200 1184 1168 1152 1136 1120 1104 1088 1072 1056 1040 1024 1008 992 976 960 944 928 912 896 880 864 848 832 816 800 784 768 752 736 720 704 688 672 656 640 624 608 592 576 560 544 528 512 496 480 464 448 432 416 400 384 368 352 336 320 304 288 272 256 240 224 208 192 176 160 144 128 112 96 80 64 48 32 16 Reading symbols from /boot/kernel/star_saver.ko...Reading symbols from /boot/ker nel/star_saver.ko.symbols...done. done. Loaded symbols for /boot/kernel/star_saver.ko #0 doadump () at pcpu.h:223 pcpu.h: No such file or directory. in pcpu.h (kgdb) (kgdb) backtrace #0 doadump () at pcpu.h:223 #1 0x8057f8c9 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:416 #2 0x8057fcfc in panic (fmt=0x80926acc "%s") at /usr/src/sys/kern/kern_shutdown.c:579 #3 0x80861758 in trap_fatal (frame=0xff00019eaab0, eva=Variable "ev a" is not available. ) at /usr/src/sys/amd64/amd64/trap.c:852 #4 0x80861b24 in trap_pfault (frame=0xff8a09b0, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:768 #5 0x80862414 in trap (frame=0xff8a09b0) at /usr/src/sys/amd64/amd64/trap.c:494 #6 0x80848703 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:224 #7 0x805a6761 in device_get_softc (dev=0x0) at /usr/src/sys/kern/subr_bus.c:2294 #8 0x80269a37 in ata_generic_command (request=0xff01224df618) at /usr/src/sys/dev/ata/ata-lowlevel.c:659 #9 0x80268510 in ata_begin_transaction (request=0xff01224df618) at /usr/src/sys/dev/ata/ata-lowlevel.c:103 #10 0x8026a57c in ata_start (dev=0xff0001aac500) at /usr/src/sys/dev/ata/ata-queue.c:212 #11 0x8026a807 in ata_queue_request (request=0xff01224df618) at /usr/src/sys/dev/ata/ata-queue.c:95 #12 0x805baab3 in taskqueue_run (queue=0xff00019c1d80) at /usr/src/sys/kern/subr_taskqueue.c:239 #13 0x805598cd in intr_event_execute_handlers (p=Variable "p" is not ava ilable. ) at /usr/src/sys/kern/kern_intr.c:1165 #14 0x8055ae2e in ithread_loop (arg=0xff000187c460) at /usr/src/sys/kern/kern_intr.c:1178 #15 0x80557898 in fork_exit ( callout=0x8055ada0 , arg=0xff000187c460, frame=0xff8a0c80) at /usr/src/sys/kern/ke
Re: amd64: Fatal Trap 12 in high load situations
Am Saturday 06 February 2010 10:17:05 schrob ms80: > Hi > > I have a problem installing / upgrading FreeBSD 8.0-release on a new > machine. > > The computers specs are: > > cpu: AMD Phenom II X4 > board: Gigabyte MA790GPT-UD3H > ram: 4x2GBytes DDR3/1333 > hdd: 2xMaxtor STM31000528AS > nic: 4x Intel(R) PRO/1000 > > and I'm running > FreeBSD phenom2.localnet 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 > 15:02:08 UTC 2009 > r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 > > During 'make buildworld' the machine regulary crashes with the following > panic: > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual adress = 0x8 > fault code= supervisor write data, page not > present > instruction pointer = 0x20:0x80578591 > stack pointer = 0x28:0xff80eab94700 > frame pointer = 0x28:0xff80eab94720 > code segment = base 0x0, limit 0xf, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume IOPL = 0 > current process = 22039 (uudecode) > trap number = 12 > panic: pagefault > cpuid = 0 > Uptime: 2h35m4s > Physical memory: 8176 MB > Dumping 2195 MB: 2180 2164 2148 2132 2116 > > > or this one, its from last night and the machine wrote a minidump before > locking up: > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0x8 > fault code= supervisor write data, page not > present > instruction pointer = 0x20:0x80578591 > stack pointer = 0x28:0xff80eab21500 > frame pointer = 0x28:0xff80eab21520 > code segment = base 0x0, limit 0xf, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 5238 (objcopy) > trap number = 12 > panic: page fault > cpuid = 0 > Uptime: 1h15m45s > Physical memory: 8176 MB > Dumping 2148 MB: 2133 2117 2101 2085 2069 2053 2037 2021 2005 1989 1973 > 1957 1941 1925 1909 1893 1877 1861 1845 1829 1813 1797 1781 1765 1749 1733 > 1717 1701 1685 1669 1653 1637 1621 1605 1589 1573 1557 1541 1525 1509 1493 > 1477 1461 1445 1429 1413 1397 1381 1365 1349 1333 1317 1301 1285 1269 1253 > 1237 1221 1205 1189 1173 1157 1141 1125 1109 1093 1077 1061 1045 1029 1013 > 997 981 965 949 933 917 901 885 869 853 837 821 805 789 773 757 741 725 > 709 693 677 661 645 629 613 597 581 565 549 533 517 501 485 469 453 437 > 421 405 389 373 357 341 325 309 293 277 261 245 229 213 197 181 165 149 > 133 117 101 85 69 53 37 21 5 > [snip] I know, its kind of stupid to reply to my own mails, but for reference: I edited loader.conf to contain ahci_load="YES" So far it works: The machine compiled all night and didn't crash. I had the idea because yesterday while testing the proposal to lower the ddr3 voltages, the machine crashed again. Additionally to the panic I'm already used to, I had a second panic in my core.txt.1: This was a fatal trap 1, referencing (current process) to irq 22. I checked what irq22 is and it is my atapci (ATI IXP700/800 SATA300 controller). Googling a bit around I found a tutorial how to activate ahci. I gave it a try and as said above: So far it seems to work. regards Sven -- 00 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: amd64: Fatal Trap 12 in high load situations
Am Saturday 06 February 2010 14:37:16 schrob Michael Powell: > ms80 wrote: [snip] > > There seems to be a general feeling the newer AMD processors don't much > care for higher memory voltages. Try lowering your voltages and see if it > helps. > > I am successfully using this board with the CPU clock set at 240MHz, which > with the x14 multiplier results in 3.36GHz operation. The Hypertransport > and FSB bus speeds are 2400MHz and the memory is running at 1599MHz at the > x6.66 multiplier. When I get the RAM up to 1680MHz is where I can get it > to freeze. As long as I don't do that it is totally stable. > > -Mike > > My CPU is an AMD Phenom II X 4 905e. Its (default) settings are: CPU Clock Ratio (Auto) 2500MHz CPU Northbridge Freq. (Auto) 2000MHz CPU Host Clock Contr. (Auto) HT Link Width (Auto) HT Link Freq. (Auto) 2000MHz Memory Clock(x6.66 ) 1333MHz I set the DDR3 voltage to auto, now it shows about 1.58V. Testing will take a little bit. Thank you for the hint. regards, Sven -- 00 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: amd64: Fatal Trap 12 in high load situations
Am Saturday 06 February 2010 14:03:06 schrob David N: [snip] > > What power supply do you have? > How many watts? brand? > > If you have insufficient power, it may cause the system to become unstable. > > Regards > David N I tested with an Enermax EPR425AWT Pro82+ II, 425W wich was the psu I bought and intended to use with this computer. After stumbling across the instabilities I tested with a HEC 550TE-2WX 550W, but it made no difference, so either both are faulty / insufficient or the problem is something else. regards, Sven -- 00 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: amd64: Fatal Trap 12 in high load situations
ms80 wrote: [snip] > > Thank you for your reply. > I'm using two of this: OCZ3P1333LVAM4GK > (OCZ DDR3 AMD Edition, rated for 1333MHz at 1.65V). My Board is rated for > 1066 - 1600 MHz memory, and neither the website nor the manual say > anything about limitations with memory. Anyway: I didn't overclock cpu or > memory. I have stability and long life in mind, so I try to keep the > hardware cool. During testing I underclocked the memory with 1066 and 800 > MHz which didn't help: The machine crashes anyway. The only thing to note > is that by default the board tries to set 1.5V DDR3 Voltage which is > wrong, you have to set it to 1.65V manually. > > A faulty piece of hardware was the first thing I suspected and I tested > among other things the memory with memtest86+. This runs fine for 4 > passes, without any error. As far as I can tell, my memory subsystem is > ok. > Poking around in the OCZ forum for something I thought I recalled seeing somewhere before. I had seen reports that this board might be touchy about 1.65v memory. As far as the consensus goes with the small sampling I looked at, it seemed that 1.63 or 1.64 vdc was the sweet spot. Some claims are that it didn't want to work at anything either above or below this range. My RAM is OCZ3BE1600C8LV4GK (anything with BE or AM in the part number is designed specifically for AM3). I thought it was 1.5v, but since I didn't remember for certain I checked and it shows a spec for 1.65v. However, I rebooted so I could look at the CMOS/BIOS stuff and I have the System Voltage Control section set for "AUTO" for all. Then I looked in the "PC Health Status" page and on the "DDR3 1.5V" line it was only reading 1.600v. There seems to be a general feeling the newer AMD processors don't much care for higher memory voltages. Try lowering your voltages and see if it helps. I am successfully using this board with the CPU clock set at 240MHz, which with the x14 multiplier results in 3.36GHz operation. The Hypertransport and FSB bus speeds are 2400MHz and the memory is running at 1599MHz at the x6.66 multiplier. When I get the RAM up to 1680MHz is where I can get it to freeze. As long as I don't do that it is totally stable. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: amd64: Fatal Trap 12 in high load situations
On 6 February 2010 22:18, ms80 wrote: > Am Saturday 06 February 2010 11:38:25 schrob Michael Powell: >> ms80 wrote: >> > Hi >> > >> > I have a problem installing / upgrading FreeBSD 8.0-release on a new >> > machine. >> > >> > The computers specs are: >> > >> > cpu: AMD Phenom II X4 >> > board: Gigabyte MA790GPT-UD3H >> > ram: 4x2GBytes DDR3/1333 >> > hdd: 2xMaxtor STM31000528AS >> > nic: 4x Intel(R) PRO/1000 >> >> [snip] >> >> > So here are my questions: >> > 1. Are there any known caveats or quirks regarding my hardware? >> > 2. What can I do to further investigate this issue >> > 3. Not fully on topic but might be related: The buildsystem recognizes my >> > cpu as "686 class cpu" wich is wrong. Are there any switches I can set in >> > make.conf to have 'make' use the correct values? Currently I'm using a >> > blank make.conf, meaning it is not present (as it is by default on a >> > fresh installed system). >> >> [snip] >> > > [snip too] > >> >> I believe your problem centers around memory. It may not be designed for >> AM3 socket and/or may not be able to handle a higher memory multiplier. >> When I first put this motherboard in I attempted to boot from an already >> installed OS with the memory multiplier set too high and saw numerous >> examples similar to what you are describing. Since I had bought 1600MHz >> memory I mistakenly set the multiplier too high. When I set it back to >> 1333MHz everything was fine. Either the memory multiplier is set too high >> for your RAM or it is just the wrong RAM to begin with. >> >> As far as make.conf goes I use: CPUTYPE?= k8 >> >> -Mike >> > > > Hi > > Thank you for your reply. > I'm using two of this: OCZ3P1333LVAM4GK > (OCZ DDR3 AMD Edition, rated for 1333MHz at 1.65V). My Board is rated for 1066 > - 1600 MHz memory, and neither the website nor the manual say anything about > limitations with memory. Anyway: I didn't overclock cpu or memory. I have > stability and long life in mind, so I try to keep the hardware cool. During > testing I underclocked the memory with 1066 and 800 MHz which didn't help: The > machine crashes anyway. The only thing to note is that by default the board > tries to set 1.5V DDR3 Voltage which is wrong, you have to set it to 1.65V > manually. > > A faulty piece of hardware was the first thing I suspected and I tested among > other things the memory with memtest86+. This runs fine for 4 passes, without > any error. As far as I can tell, my memory subsystem is ok. > > As for make.conf: thanks, I will set this when I try again. > > with best regards > > Sven > > -- > 00 > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > What power supply do you have? How many watts? brand? If you have insufficient power, it may cause the system to become unstable. Regards David N ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: amd64: Fatal Trap 12 in high load situations
Am Saturday 06 February 2010 11:38:25 schrob Michael Powell: > ms80 wrote: > > Hi > > > > I have a problem installing / upgrading FreeBSD 8.0-release on a new > > machine. > > > > The computers specs are: > > > > cpu: AMD Phenom II X4 > > board: Gigabyte MA790GPT-UD3H > > ram: 4x2GBytes DDR3/1333 > > hdd: 2xMaxtor STM31000528AS > > nic: 4x Intel(R) PRO/1000 > > [snip] > > > So here are my questions: > > 1. Are there any known caveats or quirks regarding my hardware? > > 2. What can I do to further investigate this issue > > 3. Not fully on topic but might be related: The buildsystem recognizes my > > cpu as "686 class cpu" wich is wrong. Are there any switches I can set in > > make.conf to have 'make' use the correct values? Currently I'm using a > > blank make.conf, meaning it is not present (as it is by default on a > > fresh installed system). > > [snip] > [snip too] > > I believe your problem centers around memory. It may not be designed for > AM3 socket and/or may not be able to handle a higher memory multiplier. > When I first put this motherboard in I attempted to boot from an already > installed OS with the memory multiplier set too high and saw numerous > examples similar to what you are describing. Since I had bought 1600MHz > memory I mistakenly set the multiplier too high. When I set it back to > 1333MHz everything was fine. Either the memory multiplier is set too high > for your RAM or it is just the wrong RAM to begin with. > > As far as make.conf goes I use: CPUTYPE?= k8 > > -Mike > Hi Thank you for your reply. I'm using two of this: OCZ3P1333LVAM4GK (OCZ DDR3 AMD Edition, rated for 1333MHz at 1.65V). My Board is rated for 1066 - 1600 MHz memory, and neither the website nor the manual say anything about limitations with memory. Anyway: I didn't overclock cpu or memory. I have stability and long life in mind, so I try to keep the hardware cool. During testing I underclocked the memory with 1066 and 800 MHz which didn't help: The machine crashes anyway. The only thing to note is that by default the board tries to set 1.5V DDR3 Voltage which is wrong, you have to set it to 1.65V manually. A faulty piece of hardware was the first thing I suspected and I tested among other things the memory with memtest86+. This runs fine for 4 passes, without any error. As far as I can tell, my memory subsystem is ok. As for make.conf: thanks, I will set this when I try again. with best regards Sven -- 00 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: amd64: Fatal Trap 12 in high load situations
ms80 wrote: > Hi > > I have a problem installing / upgrading FreeBSD 8.0-release on a new > machine. > > The computers specs are: > > cpu: AMD Phenom II X4 > board: Gigabyte MA790GPT-UD3H > ram: 4x2GBytes DDR3/1333 > hdd: 2xMaxtor STM31000528AS > nic: 4x Intel(R) PRO/1000 [snip] > > > So here are my questions: > 1. Are there any known caveats or quirks regarding my hardware? > 2. What can I do to further investigate this issue > 3. Not fully on topic but might be related: The buildsystem recognizes my > cpu as "686 class cpu" wich is wrong. Are there any switches I can set in > make.conf to have 'make' use the correct values? Currently I'm using a > blank make.conf, meaning it is not present (as it is by default on a fresh > installed system). > [snip] I am using this motherboard with an AMD x4 630 Propus cpu and 4G Ram (2x2GB). I have done a basic overclock to 3.36GHz with the ram running at 1600MHz. This is my KDE4 desktop machine running FreeBSD 8 and all ports currently up to date. When selecting the RAM to put on this motherboard you should have consulted the list from Gigabyte for approved memory and chosen very carefully. The memory I actually have was not an exact line item from the list, but it was something extremely close and which was designed and manufactured for use with an AM3 socket motherboard. You will notice that some RAM today is designed for Intel P55 chipsets and Lynnfield processors while other RAM is designed specifically for AM3/AM2 socket use. It is probably not a good idea to disregard this during selection, e.g. memory not specifically meant for AM3 socket mobos may not function correctly. I also seem to recall seeing somewhere that this motherboard acquires limitations in overclocking when all 4 sockets are filled and the best overclocking results when only 2 sockets are in use. I am only using 2 sockets in a 2x2GB arrangement for 4GB RAM total. If you are not overclocking and have all 4 sockets filled you may not be able to go above 1066MHz memory multiplier. With only 2 sockets populated 1333MHz should be attainable. I believe your problem centers around memory. It may not be designed for AM3 socket and/or may not be able to handle a higher memory multiplier. When I first put this motherboard in I attempted to boot from an already installed OS with the memory multiplier set too high and saw numerous examples similar to what you are describing. Since I had bought 1600MHz memory I mistakenly set the multiplier too high. When I set it back to 1333MHz everything was fine. Either the memory multiplier is set too high for your RAM or it is just the wrong RAM to begin with. As far as make.conf goes I use: CPUTYPE?= k8 -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
amd64: Fatal Trap 12 in high load situations
Hi I have a problem installing / upgrading FreeBSD 8.0-release on a new machine. The computers specs are: cpu: AMD Phenom II X4 board: Gigabyte MA790GPT-UD3H ram: 4x2GBytes DDR3/1333 hdd: 2xMaxtor STM31000528AS nic: 4x Intel(R) PRO/1000 and I'm running FreeBSD phenom2.localnet 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:02:08 UTC 2009 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 During 'make buildworld' the machine regulary crashes with the following panic: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual adress= 0x8 fault code = supervisor write data, page not present instruction pointer = 0x20:0x80578591 stack pointer = 0x28:0xff80eab94700 frame pointer = 0x28:0xff80eab94720 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume IOPL = 0 current process = 22039 (uudecode) trap number = 12 panic: pagefault cpuid = 0 Uptime: 2h35m4s Physical memory: 8176 MB Dumping 2195 MB: 2180 2164 2148 2132 2116 or this one, its from last night and the machine wrote a minidump before locking up: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x8 fault code = supervisor write data, page not present instruction pointer = 0x20:0x80578591 stack pointer = 0x28:0xff80eab21500 frame pointer = 0x28:0xff80eab21520 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 5238 (objcopy) trap number = 12 panic: page fault cpuid = 0 Uptime: 1h15m45s Physical memory: 8176 MB Dumping 2148 MB: 2133 2117 2101 2085 2069 2053 2037 2021 2005 1989 1973 1957 1941 1925 1909 1893 1877 1861 1845 1829 1813 1797 1781 1765 1749 1733 1717 1701 1685 1669 1653 1637 1621 1605 1589 1573 1557 1541 1525 1509 1493 1477 1461 1445 1429 1413 1397 1381 1365 1349 1333 1317 1301 1285 1269 1253 1237 1221 1205 1189 1173 1157 1141 1125 1109 1093 1077 1061 1045 1029 1013 997 981 965 949 933 917 901 885 869 853 837 821 805 789 773 757 741 725 709 693 677 661 645 629 613 597 581 565 549 533 517 501 485 469 453 437 421 405 389 373 357 341 325 309 293 277 261 245 229 213 197 181 165 149 133 117 101 85 69 53 37 21 5 While the 'current process' is a different one at any crash, 'Fatal trap 12' and 'supervisor write data, page not present' are always the same, just as the instruction pointer 0x80578591 and virtual address. The most times, the kernel hangs completly so I have to hard reset the machine to get it responding again. About once in every ten crashs it is able to write a dump before rebooting or locking up. I have no knowledge in debugging the kernel (or debugging anything else) so I tried what I found in the handbook. This resulted in the following: 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 "amd64-marcel-freebsd"... Cannot access memory at address 0x400 (kgdb) list *0x80578591 0x80578591 is in lf_advlockasync (/usr/src/sys/kern/kern_lockf.c:604). 599 LIST_INIT(&ls->ls_active); 600 LIST_INIT(&ls->ls_pending); 601 ls->ls_threads = 1; 602 603 sx_xlock(&lf_lock_states_lock); 604 LIST_INSERT_HEAD(&lf_lock_states, ls, ls_link); 605 sx_xunlock(&lf_lock_states_lock); 606 607 /* 608 * Cope if we lost a race with some other thread while (kgdb) backtrace #0 0x in ?? () Cannot access memory at address 0x0 So here are my questions: 1. Are there any known caveats or quirks regarding my hardware? 2. What can I do to further investigate this issue 3. Not fully on topic but might be related: The buildsystem recognizes my cpu as "686 class cpu" wich is wrong. Are there any switches I can set in make.conf to have 'make' use the correct values? Currently I'm using a blank make.conf, meaning it is not present (as it is by default
FATAL TRAP 12
Someone has had problems with this type of issues? what it is related to? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re[8]: fatal trap 12
Hello. After patch, whan make kernel I have this: /usr/src/sys/kern/vfs_vnops.c:750:37: error: macro "vn_lock" requires 3 arguments, but only 2 given /usr/src/sys/kern/vfs_vnops.c: In function 'vn_ioctl': /usr/src/sys/kern/vfs_vnops.c:750: error: 'vn_lock' undeclared (first use in this function) /usr/src/sys/kern/vfs_vnops.c:750: error: (Each undeclared identifier is reported only once /usr/src/sys/kern/vfs_vnops.c:750: error: for each function it appears in.) /usr/src/sys/kern/vfs_vnops.c:769: error: too few arguments to function 'VOP_UNLOCK' *** Error code 1 This problem with crashes I have after cPanel update perl to version 5.10.0... Can some body tell me - is this global problem of FreeBSD or it only with my installation? > [Please, remove the questions@ on the reply, this is the topic for > f...@]. > On Sat, Jun 06, 2009 at 08:16:00PM +0400, Chagin Dmitry wrote: >> - Forwarded message from ge...@dts.su - >> >> Date: Sat, 6 Jun 2009 10:58:11 +0400 >> From: ge...@dts.su >> To: freebsd-questions@freebsd.org >> Subject: Re[2]: fatal trap 12 >> >> Hello, Freebsd-questions. >> >> After one of new crash I have this: >> >> 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 "amd64-marcel-freebsd"... >> >> Unread portion of the kernel message buffer: >> >> >> Fatal trap 12: page fault while in kernel mode >> cpuid = 2; apic id = 02 >> fault virtual address = 0x0 >> fault code = supervisor read data, page not present >> instruction pointer = 0x8:0x804c4eb8 >> stack pointer = 0x10:0xff807a0478f0 >> frame pointer = 0x10:0xff807a047930 >> code segment= base 0x0, limit 0xf, type 0x1b >> = DPL 0, pres 1, long 1, def32 0, gran 1 >> processor eflags= interrupt enabled, resume, IOPL = 0 >> current process = 32668 (perl5.10.0) >> Physical memory: 4082 MB >> Dumping 1647 MB: 1632 1616 1600 1584 1568 1552 1536 1520 1504 1488 1472 1456 >> 1440 1424 1408 1392 1376 1360 1344 1328 1312 1296 1280 1264 1248 1232 1216 >> 1200 1184 1168 1152 1136 1120 1104 1088 1072 1056 1040 1024 1008 992 976 960 >> 944 928 912 896 880 864 848 832 816 800 784 768 752 736 720 704 688 672 656 >> 640 624 608 592 576 560 544 528 512 496 480 464 448 432 416 400 384 368 352 >> 336 320 304 288 272 256 240 224 208 192 176 160 144 128 112 96 80 64 48 32 16 >> >> Reading symbols from /boot/kernel/accf_http.ko...Reading symbols from >> /boot/kernel/accf_http.ko.symbols...done. >> done. >> Loaded symbols for /boot/kernel/accf_http.ko >> #0 doadump () at pcpu.h:195 >> 195 __asm __volatile("movq %%gs:0,%0" : "=r" (td)); >> (kgdb) list *0x804c4eb8 >> 0x804c4eb8 is in pfs_ioctl >> (/usr/src/sys/fs/pseudofs/pseudofs_vnops.c:265). >> 260 static int >> 261 pfs_ioctl(struct vop_ioctl_args *va) >> 262 { >> 263 struct vnode *vn = va->a_vp; >> 264 struct pfs_vdata *pvd = vn->v_data; >> 265 struct pfs_node *pn = pvd->pvd_pn; >> 266 struct proc *proc; >> 267 int error; >> 268 >> 269 PFS_TRACE(("%s: %lx", pn->pn_name, va->a_command)); >> (kgdb) backtrace >> #0 doadump () at pcpu.h:195 >> #1 0x801c8dac in db_fncall (dummy1=Variable "dummy1" is not >> available. >> ) at /usr/src/sys/ddb/db_command.c:516 >> #2 0x801c92df in db_command (last_cmdp=0x80b30c88, >> cmd_table=0x0, dopager=1) at /usr/src/sys/ddb/db_command.c:413 >> #3 0x801c94f0 in db_command_loop () at >> /usr/src/sys/ddb/db_command.c:466 >> #4 0x801cb0d9 in db_trap (type=Variable "type" is not available. >> ) at /usr/src/sys/ddb/db_main.c:228 >> #5 0x80554e55 in kdb_trap (type=12, code=0, tf=0xff807a047840) >> at /usr/src/sys/kern/subr_kdb.c:524 >> #6 0x807fae80 in trap_fatal (frame=0xff807a047840, eva=Variable >> "eva" is not available. >> ) at /usr/src/sys/amd64/amd64/trap.c:752 >> #7 0x807fb254 in trap_pfault (frame=0xff807a047840, us
Re: [ge...@dts.su: Re[2]: fatal trap 12]
[Please, remove the questions@ on the reply, this is the topic for f...@]. On Sat, Jun 06, 2009 at 08:16:00PM +0400, Chagin Dmitry wrote: > - Forwarded message from ge...@dts.su - > > Date: Sat, 6 Jun 2009 10:58:11 +0400 > From: ge...@dts.su > To: freebsd-questions@freebsd.org > Subject: Re[2]: fatal trap 12 > > Hello, Freebsd-questions. > > After one of new crash I have this: > > 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 "amd64-marcel-freebsd"... > > Unread portion of the kernel message buffer: > > > Fatal trap 12: page fault while in kernel mode > cpuid = 2; apic id = 02 > fault virtual address = 0x0 > fault code = supervisor read data, page not present > instruction pointer = 0x8:0x804c4eb8 > stack pointer = 0x10:0xff807a0478f0 > frame pointer = 0x10:0xff807a047930 > code segment= base 0x0, limit 0xf, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags= interrupt enabled, resume, IOPL = 0 > current process = 32668 (perl5.10.0) > Physical memory: 4082 MB > Dumping 1647 MB: 1632 1616 1600 1584 1568 1552 1536 1520 1504 1488 1472 1456 > 1440 1424 1408 1392 1376 1360 1344 1328 1312 1296 1280 1264 1248 1232 1216 > 1200 1184 1168 1152 1136 1120 1104 1088 1072 1056 1040 1024 1008 992 976 960 > 944 928 912 896 880 864 848 832 816 800 784 768 752 736 720 704 688 672 656 > 640 624 608 592 576 560 544 528 512 496 480 464 448 432 416 400 384 368 352 > 336 320 304 288 272 256 240 224 208 192 176 160 144 128 112 96 80 64 48 32 16 > > Reading symbols from /boot/kernel/accf_http.ko...Reading symbols from > /boot/kernel/accf_http.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/accf_http.ko > #0 doadump () at pcpu.h:195 > 195 __asm __volatile("movq %%gs:0,%0" : "=r" (td)); > (kgdb) list *0x804c4eb8 > 0x804c4eb8 is in pfs_ioctl > (/usr/src/sys/fs/pseudofs/pseudofs_vnops.c:265). > 260 static int > 261 pfs_ioctl(struct vop_ioctl_args *va) > 262 { > 263 struct vnode *vn = va->a_vp; > 264 struct pfs_vdata *pvd = vn->v_data; > 265 struct pfs_node *pn = pvd->pvd_pn; > 266 struct proc *proc; > 267 int error; > 268 > 269 PFS_TRACE(("%s: %lx", pn->pn_name, va->a_command)); > (kgdb) backtrace > #0 doadump () at pcpu.h:195 > #1 0x801c8dac in db_fncall (dummy1=Variable "dummy1" is not > available. > ) at /usr/src/sys/ddb/db_command.c:516 > #2 0x801c92df in db_command (last_cmdp=0x80b30c88, > cmd_table=0x0, dopager=1) at /usr/src/sys/ddb/db_command.c:413 > #3 0x801c94f0 in db_command_loop () at > /usr/src/sys/ddb/db_command.c:466 > #4 0x801cb0d9 in db_trap (type=Variable "type" is not available. > ) at /usr/src/sys/ddb/db_main.c:228 > #5 0x80554e55 in kdb_trap (type=12, code=0, tf=0xff807a047840) > at /usr/src/sys/kern/subr_kdb.c:524 > #6 0x807fae80 in trap_fatal (frame=0xff807a047840, eva=Variable > "eva" is not available. > ) at /usr/src/sys/amd64/amd64/trap.c:752 > #7 0x807fb254 in trap_pfault (frame=0xff807a047840, usermode=0) > at /usr/src/sys/amd64/amd64/trap.c:673 > #8 0x807fbc02 in trap (frame=0xff807a047840) at > /usr/src/sys/amd64/amd64/trap.c:444 > #9 0x807df35e in calltrap () at > /usr/src/sys/amd64/amd64/exception.S:209 > #10 0x804c4eb8 in pfs_ioctl (va=0xff807a047a10) at > /usr/src/sys/fs/pseudofs/pseudofs_vnops.c:264 > #11 0x805bb1d3 in vn_ioctl (fp=Variable "fp" is not available. > ) at vnode_if.h:437 > #12 0x80562d02 in kern_ioctl (td=0xff0006682000, fd=3, > com=1076655123, data=0xff00ad2b7d40 "") at file.h:269 > #13 0x80563029 in ioctl (td=0xff0006682000, > uap=0xff807a047bf0) at /usr/src/sys/kern/sys_generic.c:571 > #14 0x807fb4d6 in syscall (frame=0xff807a047c80) at > /usr/src/sys/amd64/amd64/trap.c:900 > #15 0x807df56b in Xfast_syscall () at > /usr/src/sys/amd64/amd64/exception.S:330 > #16 0x000800c9c0ec in ?? () > Previous frame inner to this frame (corrupt stack?) > (kgdb) > > > Can You help
Re[6]: fatal trap 12
Hello. I have this options in kernel: makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols options KDB options DDB options GDB What I need more in kernel conf? > 2009/6/6 >> Hello. >> >> What options I must add to kernel? Can You tell me what I must do when >> system crash next time? >> >> > On 6/6/09, ge...@dts.su wrote: >> >> Hello, Freebsd-questions. >> >> >> >> After one of new crash I have this: >> >> >> >> 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 "amd64-marcel-freebsd"... >> >> >> >> Unread portion of the kernel message buffer: >> >> >> >> >> >> Fatal trap 12: page fault while in kernel mode >> >> cpuid = 2; apic id = 02 >> >> fault virtual address = 0x0 >> >> fault code = supervisor read data, page not present >> >> instruction pointer = 0x8:0x804c4eb8 >> >> stack pointer = 0x10:0xff807a0478f0 >> >> frame pointer = 0x10:0xff807a047930 >> >> code segment= base 0x0, limit 0xf, type 0x1b >> >> = DPL 0, pres 1, long 1, def32 0, gran 1 >> >> processor eflags= interrupt enabled, resume, IOPL = 0 >> >> current process = 32668 (perl5.10.0) >> >> Physical memory: 4082 MB >> >> Dumping 1647 MB: 1632 1616 1600 1584 1568 1552 1536 1520 1504 1488 1472 >> 1456 >> >> 1440 1424 1408 1392 1376 1360 1344 1328 1312 1296 1280 1264 1248 1232 >> 1216 >> >> 1200 1184 1168 1152 1136 1120 1104 1088 1072 1056 1040 1024 1008 992 976 >> 960 >> >> 944 928 912 896 880 864 848 832 816 800 784 768 752 736 720 704 688 672 >> 656 >> >> 640 624 608 592 576 560 544 528 512 496 480 464 448 432 416 400 384 368 >> 352 >> >> 336 320 304 288 272 256 240 224 208 192 176 160 144 128 112 96 80 64 48 >> 32 >> >> 16 >> >> >> >> Reading symbols from /boot/kernel/accf_http.ko...Reading symbols from >> >> /boot/kernel/accf_http.ko.symbols...done. >> >> done. >> >> Loaded symbols for /boot/kernel/accf_http.ko >> >> #0 doadump () at pcpu.h:195 >> >> 195 __asm __volatile("movq %%gs:0,%0" : "=r" (td)); >> >> (kgdb) list *0x804c4eb8 >> >> 0x804c4eb8 is in pfs_ioctl >> >> (/usr/src/sys/fs/pseudofs/pseudofs_vnops.c:265). >> >> 260 static int >> >> 261 pfs_ioctl(struct vop_ioctl_args *va) >> >> 262 { >> >> 263 struct vnode *vn = va->a_vp; >> >> 264 struct pfs_vdata *pvd = vn->v_data; >> >> 265 struct pfs_node *pn = pvd->pvd_pn; >> >> 266 struct proc *proc; >> >> 267 int error; >> >> 268 >> >> 269 PFS_TRACE(("%s: %lx", pn->pn_name, va->a_command)); >> >> (kgdb) backtrace >> >> #0 doadump () at pcpu.h:195 >> >> #1 0x801c8dac in db_fncall (dummy1=Variable "dummy1" is not >> >> available. >> >> ) at /usr/src/sys/ddb/db_command.c:516 >> >> #2 0x801c92df in db_command (last_cmdp=0x80b30c88, >> >> cmd_table=0x0, dopager=1) at /usr/src/sys/ddb/db_command.c:413 >> >> #3 0x801c94f0 in db_command_loop () at >> >> /usr/src/sys/ddb/db_command.c:466 >> >> #4 0x801cb0d9 in db_trap (type=Variable "type" is not >> available. >> >> ) at /usr/src/sys/ddb/db_main.c:228 >> >> #5 0x80554e55 in kdb_trap (type=12, code=0, >> tf=0xff807a047840) >> >> at /usr/src/sys/kern/subr_kdb.c:524 >> >> #6 0x807fae80 in trap_fatal (frame=0xff807a047840, >> eva=Variable >> >> "eva" is not available. >> >> ) at /usr/src/sys/amd64/amd64/trap.c:752 >> >> #7 0x807fb254 in trap_pfault (frame=0xff807a0478
Re: Re[4]: fatal trap 12
2009/6/6 > Hello. > > What options I must add to kernel? Can You tell me what I must do when > system crash next time? > > > On 6/6/09, ge...@dts.su wrote: > >> Hello, Freebsd-questions. > >> > >> After one of new crash I have this: > >> > >> 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 "amd64-marcel-freebsd"... > >> > >> Unread portion of the kernel message buffer: > >> > >> > >> Fatal trap 12: page fault while in kernel mode > >> cpuid = 2; apic id = 02 > >> fault virtual address = 0x0 > >> fault code = supervisor read data, page not present > >> instruction pointer = 0x8:0x804c4eb8 > >> stack pointer = 0x10:0xff807a0478f0 > >> frame pointer = 0x10:0xff807a047930 > >> code segment= base 0x0, limit 0xf, type 0x1b > >> = DPL 0, pres 1, long 1, def32 0, gran 1 > >> processor eflags= interrupt enabled, resume, IOPL = 0 > >> current process = 32668 (perl5.10.0) > >> Physical memory: 4082 MB > >> Dumping 1647 MB: 1632 1616 1600 1584 1568 1552 1536 1520 1504 1488 1472 > 1456 > >> 1440 1424 1408 1392 1376 1360 1344 1328 1312 1296 1280 1264 1248 1232 > 1216 > >> 1200 1184 1168 1152 1136 1120 1104 1088 1072 1056 1040 1024 1008 992 976 > 960 > >> 944 928 912 896 880 864 848 832 816 800 784 768 752 736 720 704 688 672 > 656 > >> 640 624 608 592 576 560 544 528 512 496 480 464 448 432 416 400 384 368 > 352 > >> 336 320 304 288 272 256 240 224 208 192 176 160 144 128 112 96 80 64 48 > 32 > >> 16 > >> > >> Reading symbols from /boot/kernel/accf_http.ko...Reading symbols from > >> /boot/kernel/accf_http.ko.symbols...done. > >> done. > >> Loaded symbols for /boot/kernel/accf_http.ko > >> #0 doadump () at pcpu.h:195 > >> 195 __asm __volatile("movq %%gs:0,%0" : "=r" (td)); > >> (kgdb) list *0x804c4eb8 > >> 0x804c4eb8 is in pfs_ioctl > >> (/usr/src/sys/fs/pseudofs/pseudofs_vnops.c:265). > >> 260 static int > >> 261 pfs_ioctl(struct vop_ioctl_args *va) > >> 262 { > >> 263 struct vnode *vn = va->a_vp; > >> 264 struct pfs_vdata *pvd = vn->v_data; > >> 265 struct pfs_node *pn = pvd->pvd_pn; > >> 266 struct proc *proc; > >> 267 int error; > >> 268 > >> 269 PFS_TRACE(("%s: %lx", pn->pn_name, va->a_command)); > >> (kgdb) backtrace > >> #0 doadump () at pcpu.h:195 > >> #1 0x801c8dac in db_fncall (dummy1=Variable "dummy1" is not > >> available. > >> ) at /usr/src/sys/ddb/db_command.c:516 > >> #2 0x801c92df in db_command (last_cmdp=0x80b30c88, > >> cmd_table=0x0, dopager=1) at /usr/src/sys/ddb/db_command.c:413 > >> #3 0x801c94f0 in db_command_loop () at > >> /usr/src/sys/ddb/db_command.c:466 > >> #4 0x801cb0d9 in db_trap (type=Variable "type" is not > available. > >> ) at /usr/src/sys/ddb/db_main.c:228 > >> #5 0x80554e55 in kdb_trap (type=12, code=0, > tf=0xff807a047840) > >> at /usr/src/sys/kern/subr_kdb.c:524 > >> #6 0x807fae80 in trap_fatal (frame=0xff807a047840, > eva=Variable > >> "eva" is not available. > >> ) at /usr/src/sys/amd64/amd64/trap.c:752 > >> #7 0x807fb254 in trap_pfault (frame=0xff807a047840, > usermode=0) > >> at /usr/src/sys/amd64/amd64/trap.c:673 > >> #8 0x807fbc02 in trap (frame=0xff807a047840) at > >> /usr/src/sys/amd64/amd64/trap.c:444 > >> #9 0x807df35e in calltrap () at > >> /usr/src/sys/amd64/amd64/exception.S:209 > >> #10 0x804c4eb8 in pfs_ioctl (va=0xff807a047a10) at > >> /usr/src/sys/fs/pseudofs/pseudofs_vnops.c:264 > >> #11 0x805bb1d3 in vn_ioctl (fp=Variable "fp" is not available. > >> ) at vnode_if.h:437 > &g
Re[4]: fatal trap 12
Hello. What options I must add to kernel? Can You tell me what I must do when system crash next time? > On 6/6/09, ge...@dts.su wrote: >> Hello, Freebsd-questions. >> >> After one of new crash I have this: >> >> 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 "amd64-marcel-freebsd"... >> >> Unread portion of the kernel message buffer: >> >> >> Fatal trap 12: page fault while in kernel mode >> cpuid = 2; apic id = 02 >> fault virtual address = 0x0 >> fault code = supervisor read data, page not present >> instruction pointer = 0x8:0x804c4eb8 >> stack pointer = 0x10:0xff807a0478f0 >> frame pointer = 0x10:0xff807a047930 >> code segment= base 0x0, limit 0xf, type 0x1b >> = DPL 0, pres 1, long 1, def32 0, gran 1 >> processor eflags= interrupt enabled, resume, IOPL = 0 >> current process = 32668 (perl5.10.0) >> Physical memory: 4082 MB >> Dumping 1647 MB: 1632 1616 1600 1584 1568 1552 1536 1520 1504 1488 1472 1456 >> 1440 1424 1408 1392 1376 1360 1344 1328 1312 1296 1280 1264 1248 1232 1216 >> 1200 1184 1168 1152 1136 1120 1104 1088 1072 1056 1040 1024 1008 992 976 960 >> 944 928 912 896 880 864 848 832 816 800 784 768 752 736 720 704 688 672 656 >> 640 624 608 592 576 560 544 528 512 496 480 464 448 432 416 400 384 368 352 >> 336 320 304 288 272 256 240 224 208 192 176 160 144 128 112 96 80 64 48 32 >> 16 >> >> Reading symbols from /boot/kernel/accf_http.ko...Reading symbols from >> /boot/kernel/accf_http.ko.symbols...done. >> done. >> Loaded symbols for /boot/kernel/accf_http.ko >> #0 doadump () at pcpu.h:195 >> 195 __asm __volatile("movq %%gs:0,%0" : "=r" (td)); >> (kgdb) list *0x804c4eb8 >> 0x804c4eb8 is in pfs_ioctl >> (/usr/src/sys/fs/pseudofs/pseudofs_vnops.c:265). >> 260 static int >> 261 pfs_ioctl(struct vop_ioctl_args *va) >> 262 { >> 263 struct vnode *vn = va->a_vp; >> 264 struct pfs_vdata *pvd = vn->v_data; >> 265 struct pfs_node *pn = pvd->pvd_pn; >> 266 struct proc *proc; >> 267 int error; >> 268 >> 269 PFS_TRACE(("%s: %lx", pn->pn_name, va->a_command)); >> (kgdb) backtrace >> #0 doadump () at pcpu.h:195 >> #1 0x801c8dac in db_fncall (dummy1=Variable "dummy1" is not >> available. >> ) at /usr/src/sys/ddb/db_command.c:516 >> #2 0x801c92df in db_command (last_cmdp=0x80b30c88, >> cmd_table=0x0, dopager=1) at /usr/src/sys/ddb/db_command.c:413 >> #3 0x801c94f0 in db_command_loop () at >> /usr/src/sys/ddb/db_command.c:466 >> #4 0x801cb0d9 in db_trap (type=Variable "type" is not available. >> ) at /usr/src/sys/ddb/db_main.c:228 >> #5 0x80554e55 in kdb_trap (type=12, code=0, tf=0xff807a047840) >> at /usr/src/sys/kern/subr_kdb.c:524 >> #6 0x807fae80 in trap_fatal (frame=0xff807a047840, eva=Variable >> "eva" is not available. >> ) at /usr/src/sys/amd64/amd64/trap.c:752 >> #7 0x807fb254 in trap_pfault (frame=0xff807a047840, usermode=0) >> at /usr/src/sys/amd64/amd64/trap.c:673 >> #8 0x807fbc02 in trap (frame=0xff807a047840) at >> /usr/src/sys/amd64/amd64/trap.c:444 >> #9 0x807df35e in calltrap () at >> /usr/src/sys/amd64/amd64/exception.S:209 >> #10 0x804c4eb8 in pfs_ioctl (va=0xff807a047a10) at >> /usr/src/sys/fs/pseudofs/pseudofs_vnops.c:264 >> #11 0x805bb1d3 in vn_ioctl (fp=Variable "fp" is not available. >> ) at vnode_if.h:437 >> #12 0x80562d02 in kern_ioctl (td=0xff0006682000, fd=3, >> com=1076655123, data=0xff00ad2b7d40 "") at file.h:269 >> #13 0x80563029 in ioctl (td=0xff0006682000, >> uap=0xff807a047bf0) at /usr/src/sys/kern/sys_generic.c:571 >> #14 0x807fb4d6 in syscall (frame=0xff807a047c80) at >> /usr/src/sys/amd64/amd64/trap.c:900 >> #15 0xffff807df56b in Xfast_syscall () at >> /usr/src/sys/amd64/amd64/exception.S:3
Re: Re[2]: fatal trap 12
On 6/6/09, ge...@dts.su wrote: > Hello, Freebsd-questions. > > After one of new crash I have this: > > 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 "amd64-marcel-freebsd"... > > Unread portion of the kernel message buffer: > > > Fatal trap 12: page fault while in kernel mode > cpuid = 2; apic id = 02 > fault virtual address = 0x0 > fault code = supervisor read data, page not present > instruction pointer = 0x8:0x804c4eb8 > stack pointer = 0x10:0xff807a0478f0 > frame pointer = 0x10:0xff807a047930 > code segment= base 0x0, limit 0xf, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags= interrupt enabled, resume, IOPL = 0 > current process = 32668 (perl5.10.0) > Physical memory: 4082 MB > Dumping 1647 MB: 1632 1616 1600 1584 1568 1552 1536 1520 1504 1488 1472 1456 > 1440 1424 1408 1392 1376 1360 1344 1328 1312 1296 1280 1264 1248 1232 1216 > 1200 1184 1168 1152 1136 1120 1104 1088 1072 1056 1040 1024 1008 992 976 960 > 944 928 912 896 880 864 848 832 816 800 784 768 752 736 720 704 688 672 656 > 640 624 608 592 576 560 544 528 512 496 480 464 448 432 416 400 384 368 352 > 336 320 304 288 272 256 240 224 208 192 176 160 144 128 112 96 80 64 48 32 > 16 > > Reading symbols from /boot/kernel/accf_http.ko...Reading symbols from > /boot/kernel/accf_http.ko.symbols...done. > done. > Loaded symbols for /boot/kernel/accf_http.ko > #0 doadump () at pcpu.h:195 > 195 __asm __volatile("movq %%gs:0,%0" : "=r" (td)); > (kgdb) list *0x804c4eb8 > 0x804c4eb8 is in pfs_ioctl > (/usr/src/sys/fs/pseudofs/pseudofs_vnops.c:265). > 260 static int > 261 pfs_ioctl(struct vop_ioctl_args *va) > 262 { > 263 struct vnode *vn = va->a_vp; > 264 struct pfs_vdata *pvd = vn->v_data; > 265 struct pfs_node *pn = pvd->pvd_pn; > 266 struct proc *proc; > 267 int error; > 268 > 269 PFS_TRACE(("%s: %lx", pn->pn_name, va->a_command)); > (kgdb) backtrace > #0 doadump () at pcpu.h:195 > #1 0x801c8dac in db_fncall (dummy1=Variable "dummy1" is not > available. > ) at /usr/src/sys/ddb/db_command.c:516 > #2 0x801c92df in db_command (last_cmdp=0x80b30c88, > cmd_table=0x0, dopager=1) at /usr/src/sys/ddb/db_command.c:413 > #3 0x801c94f0 in db_command_loop () at > /usr/src/sys/ddb/db_command.c:466 > #4 0x801cb0d9 in db_trap (type=Variable "type" is not available. > ) at /usr/src/sys/ddb/db_main.c:228 > #5 0x80554e55 in kdb_trap (type=12, code=0, tf=0xff807a047840) > at /usr/src/sys/kern/subr_kdb.c:524 > #6 0x807fae80 in trap_fatal (frame=0xff807a047840, eva=Variable > "eva" is not available. > ) at /usr/src/sys/amd64/amd64/trap.c:752 > #7 0x807fb254 in trap_pfault (frame=0xff807a047840, usermode=0) > at /usr/src/sys/amd64/amd64/trap.c:673 > #8 0x807fbc02 in trap (frame=0xff807a047840) at > /usr/src/sys/amd64/amd64/trap.c:444 > #9 0x807df35e in calltrap () at > /usr/src/sys/amd64/amd64/exception.S:209 > #10 0x804c4eb8 in pfs_ioctl (va=0xff807a047a10) at > /usr/src/sys/fs/pseudofs/pseudofs_vnops.c:264 > #11 0x805bb1d3 in vn_ioctl (fp=Variable "fp" is not available. > ) at vnode_if.h:437 > #12 0x80562d02 in kern_ioctl (td=0xff0006682000, fd=3, > com=1076655123, data=0xff00ad2b7d40 "") at file.h:269 > #13 0x80563029 in ioctl (td=0xff0006682000, > uap=0xff807a047bf0) at /usr/src/sys/kern/sys_generic.c:571 > #14 0x807fb4d6 in syscall (frame=0xff807a047c80) at > /usr/src/sys/amd64/amd64/trap.c:900 > #15 0x807df56b in Xfast_syscall () at > /usr/src/sys/amd64/amd64/exception.S:330 > #16 0x000800c9c0ec in ?? () > Previous frame inner to this frame (corrupt stack?) > (kgdb) > > > Can You help me? What can I do? Server crash periodicaly... Add more debug options to kernel, because dump is not useful with corrupted stack. >> For this question, you must debug the kernel by Serial. >> when fatal, you use find the error by command "bt". > >> -- >> Dean >>
Re[2]: fatal trap 12
Hello, Freebsd-questions. After one of new crash I have this: 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 "amd64-marcel-freebsd"... Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 2; apic id = 02 fault virtual address = 0x0 fault code = supervisor read data, page not present instruction pointer = 0x8:0x804c4eb8 stack pointer = 0x10:0xff807a0478f0 frame pointer = 0x10:0xff807a047930 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 32668 (perl5.10.0) Physical memory: 4082 MB Dumping 1647 MB: 1632 1616 1600 1584 1568 1552 1536 1520 1504 1488 1472 1456 1440 1424 1408 1392 1376 1360 1344 1328 1312 1296 1280 1264 1248 1232 1216 1200 1184 1168 1152 1136 1120 1104 1088 1072 1056 1040 1024 1008 992 976 960 944 928 912 896 880 864 848 832 816 800 784 768 752 736 720 704 688 672 656 640 624 608 592 576 560 544 528 512 496 480 464 448 432 416 400 384 368 352 336 320 304 288 272 256 240 224 208 192 176 160 144 128 112 96 80 64 48 32 16 Reading symbols from /boot/kernel/accf_http.ko...Reading symbols from /boot/kernel/accf_http.ko.symbols...done. done. Loaded symbols for /boot/kernel/accf_http.ko #0 doadump () at pcpu.h:195 195 __asm __volatile("movq %%gs:0,%0" : "=r" (td)); (kgdb) list *0x804c4eb8 0x804c4eb8 is in pfs_ioctl (/usr/src/sys/fs/pseudofs/pseudofs_vnops.c:265). 260 static int 261 pfs_ioctl(struct vop_ioctl_args *va) 262 { 263 struct vnode *vn = va->a_vp; 264 struct pfs_vdata *pvd = vn->v_data; 265 struct pfs_node *pn = pvd->pvd_pn; 266 struct proc *proc; 267 int error; 268 269 PFS_TRACE(("%s: %lx", pn->pn_name, va->a_command)); (kgdb) backtrace #0 doadump () at pcpu.h:195 #1 0x801c8dac in db_fncall (dummy1=Variable "dummy1" is not available. ) at /usr/src/sys/ddb/db_command.c:516 #2 0x801c92df in db_command (last_cmdp=0x80b30c88, cmd_table=0x0, dopager=1) at /usr/src/sys/ddb/db_command.c:413 #3 0x801c94f0 in db_command_loop () at /usr/src/sys/ddb/db_command.c:466 #4 0x801cb0d9 in db_trap (type=Variable "type" is not available. ) at /usr/src/sys/ddb/db_main.c:228 #5 0x80554e55 in kdb_trap (type=12, code=0, tf=0xff807a047840) at /usr/src/sys/kern/subr_kdb.c:524 #6 0x807fae80 in trap_fatal (frame=0xff807a047840, eva=Variable "eva" is not available. ) at /usr/src/sys/amd64/amd64/trap.c:752 #7 0x807fb254 in trap_pfault (frame=0xff807a047840, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:673 #8 0x807fbc02 in trap (frame=0xff807a047840) at /usr/src/sys/amd64/amd64/trap.c:444 #9 0x807df35e in calltrap () at /usr/src/sys/amd64/amd64/exception.S:209 #10 0x804c4eb8 in pfs_ioctl (va=0xff807a047a10) at /usr/src/sys/fs/pseudofs/pseudofs_vnops.c:264 #11 0x805bb1d3 in vn_ioctl (fp=Variable "fp" is not available. ) at vnode_if.h:437 #12 0x80562d02 in kern_ioctl (td=0xff0006682000, fd=3, com=1076655123, data=0xff00ad2b7d40 "") at file.h:269 #13 0x80563029 in ioctl (td=0xff0006682000, uap=0xff807a047bf0) at /usr/src/sys/kern/sys_generic.c:571 #14 0x807fb4d6 in syscall (frame=0xff807a047c80) at /usr/src/sys/amd64/amd64/trap.c:900 #15 0x807df56b in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:330 #16 0x000800c9c0ec in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) Can You help me? What can I do? Server crash periodicaly... > For this question, you must debug the kernel by Serial. > when fatal, you use find the error by command "bt". > -- > Dean > 2009-06-02 > - > 发件人:georg > 发送日期:2009-06-02 14:51:45 > 收件人:freebsd-questions > 抄送: > 主题:fatal trap 12 > Hello, Freebsd-questions. >I use FreeBSD 7.2-STABLE amd64. About month ago system was crashed > with "Fatal trap 12"... >I bay new hardware and install new FreeBSD 7.2-STABLE amd64. cPanel >and ASSP (anti spam proxy). And one a day or two days have this: >Fatal trap 12: page fault while in kernel mode >cpuid: = 0;
fatal trap 12
Hello, Freebsd-questions. I use FreeBSD 7.2-STABLE amd64. About month ago system was crashed with "Fatal trap 12"... I bay new hardware and install new FreeBSD 7.2-STABLE amd64. cPanel and ASSP (anti spam proxy). And one a day or two days have this: Fatal trap 12: page fault while in kernel mode cpuid: = 0; apic id = 00 fault virtual address = 0x80 fault code= supervisor write data, page not present instruction pointer = 0x8:0x8018b839 stack pointer = 0x10:0xff807a25d190 frame pointer = 0x10:0xea5f code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 59397 (perl5.10.0) trap number = 12 And alway, after crash, I see "current process = perl5.10.0"... Can You help me? -- Regards, mailto:ge...@dts.su Yura ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: questions about Fatal Trap 12
Steve Bertrand wrote: > Glen Barber wrote: >> On Tue, Apr 14, 2009 at 5:23 PM, Ray wrote: >>> I Just had the power supply die on this machine. Could a failing power >>> supply cause this type of issues? >> >> Absolutely. > > Seconded. Power supply issues have caused me this kind of grief more > times than memory has over the years. > Yes, "me too". With the advent of the digital age there is less and less cognizance of analog electronics these days. Simply checking the output voltages with a Radio Shack VOM will make things seem to be OK, as in the measurements seem to be within the range you'd expect, but this is not an entirely accurate assessment. It can be the case where a power supply has aged to the point that it can support only some fraction of the load it was rated at when new. As long as the load stays below this derated value the box seems all right, but plug in another drive or some other hardware that pushes it over the edge and you get another story. What you will get is non-pure DC with huge amounts of unfiltered ripple. The VOM will not show this. You would have to be using an oscilloscope to see it. But even an old power supply that is not loaded down to the point of total failure can begin to show out of spec ripple measurement as load increases. This ripple can be the source of seemingly intermittent hardware problems such as hangs, mysterious automagic rebooting, lock ups, etc, that seem to have no rhyme or reason to them. Many times in the distant past I replaced one by one each subsystem with known good ones to the point where the power supply was the last thing I tried. These days if it is an older box with a lot of hours of MTBF on it I do it first, using a known good. Probably 70%+ of the time it has turned out to save lots of time. Rather than try every thing else first I have learned to eliminate the power supply first, rather than the other way around. But I also have a 100MHz dual trace 'scope too. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: questions about Fatal Trap 12
Glen Barber wrote: > On Tue, Apr 14, 2009 at 5:23 PM, Ray wrote: >> I Just had the power supply die on this machine. Could a failing power >> supply >> cause this type of issues? > > Absolutely. Seconded. Power supply issues have caused me this kind of grief more times than memory has over the years. Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: questions about Fatal Trap 12
On Tue, Apr 14, 2009 at 5:23 PM, Ray wrote: > I Just had the power supply die on this machine. Could a failing power supply > cause this type of issues? Absolutely. -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: questions about Fatal Trap 12
On Saturday 11 April 2009 19:34:29 Paul Hamilton wrote: > -Original Message- > From: owner-freebsd-questi...@freebsd.org > [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Ray > Sent: Saturday, 4 April 2009 01:45 > To: freebsd general questions > Subject: questions about Fatal Trap 12 > > Hello, > I have received a kernel Trap 12 error several times now and am trying to > figure it out. > the error occurred today, and the previous time was about two weeks ago. > last time I had to run fsck manually if that proves anything. > > > Any help or suggestions would be greatly appreciated. > Ray > ___ > > > > Hi Ray, > > I have had a few of the Trap 12 errors over the last 10 years of using > FreeBSD. From memory, mine where due to faulty motherboard/CPU. I just > moved the hard drive to another PC, and all was ok. > > The last time I received the error, was when I tried recompiling world. I > put it down to CPU heat, as it was running a LOT harder than normal day to > day use. This was on a server that had been in place for two years running > with out problem! > > Cheers, > > PaulH > I Just had the power supply die on this machine. Could a failing power supply cause this type of issues? Ray > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: questions about Fatal Trap 12
On Mon, 13 Apr 2009 18:31:31 +0300, Ray wrote: Thanks Paul and Chris, So what It comes down to is that this error is most likely a hardware problem, and I'll just have to bring the machine down for hardware replacement and/or testing? Usually yes. Back in the days when I had that sort of problems, it was memory related. So I changed the memory (memtest yelled in errors) and all was ok afterwards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: questions about Fatal Trap 12
Thanks Paul and Chris, So what It comes down to is that this error is most likely a hardware problem, and I'll just have to bring the machine down for hardware replacement and/or testing? Thanks, Ray ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
RE: questions about Fatal Trap 12
-Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Ray Sent: Saturday, 4 April 2009 01:45 To: freebsd general questions Subject: questions about Fatal Trap 12 Hello, I have received a kernel Trap 12 error several times now and am trying to figure it out. the error occurred today, and the previous time was about two weeks ago. last time I had to run fsck manually if that proves anything. uname -a gives the following: FreeBSD wserver..com 7.0-RELEASE-p3 FreeBSD 7.0-RELEASE-p3 #0: Wed Sep 17 13:30:46 MDT 2008 r...@wserver.*.com:/usr/obj/usr/src/sys/MOD amd64 Google returns results mostly for versions 4.x and 5.x, but it suggest 2 main things: test ram, and kernel panic troubleshooting. (http://www.freebsd.org/doc/en/books/faq/advanced.html#KERNEL-PANIC- TROUBLESHOOTING) Is there a way to test the ram without removing it from the machine and leave the machine functioning. I've used memtest 86 before, but obviously the machine has to be offline for this test. However, I'm a little unsure of the instructions in the handbook on troubleshooting. namely, it talks about using the nm command, put I can't figure out the data file to give it as an argument, and second I'm unsure about using a debugging Kernel on a production server. I have heard that It will significantly slow down a machine. Any help or suggestions would be greatly appreciated. Ray ___ Hi Ray, I have had a few of the Trap 12 errors over the last 10 years of using FreeBSD. From memory, mine where due to faulty motherboard/CPU. I just moved the hard drive to another PC, and all was ok. The last time I received the error, was when I tried recompiling world. I put it down to CPU heat, as it was running a LOT harder than normal day to day use. This was on a server that had been in place for two years running with out problem! Cheers, PaulH ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: questions about Fatal Trap 12
2009/4/9 Ray : > On Friday 03 April 2009 11:44:31 Ray wrote: >> Hello, >> I have received a kernel Trap 12 error several times now and am trying to >> figure it out. >> the error occurred today, and the previous time was about two weeks ago. >> last time I had to run fsck manually if that proves anything. >> >> >> uname -a gives the following: >> >> FreeBSD wserver..com 7.0-RELEASE-p3 FreeBSD 7.0-RELEASE-p3 #0: Wed >> Sep 17 13:30:46 MDT 2008 >> r...@wserver.*.com:/usr/obj/usr/src/sys/MOD amd64 >> >> >> Google returns results mostly for versions 4.x and 5.x, but it suggest 2 >> main things: >> test ram, and kernel panic troubleshooting. >> (http://www.freebsd.org/doc/en/books/faq/advanced.html#KERNEL-PANIC- >> TROUBLESHOOTING) >> >> Is there a way to test the ram without removing it from the machine and >> leave the machine functioning. I've used memtest 86 before, but obviously >> the machine has to be offline for this test. >> >> However, I'm a little unsure of the instructions in the handbook on >> troubleshooting. namely, it talks about using the nm command, but I can't >> figure out the data file to give it as an argument, and second I'm unsure >> about using a debugging Kernel on a production server. I have heard that It >> will significantly slow down a machine. >> Any help or suggestions would be greatly appreciated. >> Ray > > Can anybody make any suggestions, or is there a better list to take this > question to? > Ray > Sorry mate, I really don't think you're going to have any luck. Memory testing requires access to parts of memory that the kernel's currently munching on. Run memtest86, or yank a few sticks and run it in another computer. Chris -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: questions about Fatal Trap 12
On Friday 03 April 2009 11:44:31 Ray wrote: > Hello, > I have received a kernel Trap 12 error several times now and am trying to > figure it out. > the error occurred today, and the previous time was about two weeks ago. > last time I had to run fsck manually if that proves anything. > > > uname -a gives the following: > > FreeBSD wserver..com 7.0-RELEASE-p3 FreeBSD 7.0-RELEASE-p3 #0: Wed > Sep 17 13:30:46 MDT 2008 > r...@wserver.*.com:/usr/obj/usr/src/sys/MOD amd64 > > > Google returns results mostly for versions 4.x and 5.x, but it suggest 2 > main things: > test ram, and kernel panic troubleshooting. > (http://www.freebsd.org/doc/en/books/faq/advanced.html#KERNEL-PANIC- > TROUBLESHOOTING) > > Is there a way to test the ram without removing it from the machine and > leave the machine functioning. I've used memtest 86 before, but obviously > the machine has to be offline for this test. > > However, I'm a little unsure of the instructions in the handbook on > troubleshooting. namely, it talks about using the nm command, but I can't > figure out the data file to give it as an argument, and second I'm unsure > about using a debugging Kernel on a production server. I have heard that It > will significantly slow down a machine. > Any help or suggestions would be greatly appreciated. > Ray Can anybody make any suggestions, or is there a better list to take this question to? Ray ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
questions about Fatal Trap 12
Hello, I have received a kernel Trap 12 error several times now and am trying to figure it out. the error occurred today, and the previous time was about two weeks ago. last time I had to run fsck manually if that proves anything. uname -a gives the following: FreeBSD wserver..com 7.0-RELEASE-p3 FreeBSD 7.0-RELEASE-p3 #0: Wed Sep 17 13:30:46 MDT 2008 r...@wserver.*.com:/usr/obj/usr/src/sys/MOD amd64 Google returns results mostly for versions 4.x and 5.x, but it suggest 2 main things: test ram, and kernel panic troubleshooting. (http://www.freebsd.org/doc/en/books/faq/advanced.html#KERNEL-PANIC- TROUBLESHOOTING) Is there a way to test the ram without removing it from the machine and leave the machine functioning. I've used memtest 86 before, but obviously the machine has to be offline for this test. However, I'm a little unsure of the instructions in the handbook on troubleshooting. namely, it talks about using the nm command, put I can't figure out the data file to give it as an argument, and second I'm unsure about using a debugging Kernel on a production server. I have heard that It will significantly slow down a machine. Any help or suggestions would be greatly appreciated. Ray ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD7.1/i386 crash (fatal trap 12)
On Tue, 17 Mar 2009 06:35:04 +0300 anb...@list.ru wrote: > What can I do with it? I don`t have experience in using gdb or programming on > C. I suppose your kernel is built with "makeoptions DEBUG=-g". Then enable kernel crash dump: echo 'dumpdev="AUTO"' >> /etc/rc.conf /etc/rc.d/dumpon start After panic, get the baktrace from the dump using instructions from this page: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-gdb.html Or just run crashinfo and extract bt from generated core.txt. Post bt here or to freebsd-hackers. -- Mikolaj Golub ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
FreeBSD7.1/i386 crash (fatal trap 12)
Hello, I have problem with FreeBSD 7.1-STABLE/i386. We have FreeBSD-based cluster of VPN servers (mpd3.18 as PPTP server), and sometimes its fall down. #dmesg | less Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x1ac fault code = supervisor write, page not present instruction pointer = 0x20:0x806d673a stack pointer = 0x28:0xe6c6ca68 frame pointer = 0x28:0xe6c6cacc code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 12 (swi1: net) trap number = 12 panic: page fault cpuid = 1 Uptime: 1d13h20m2s Cannot dump. No dump device defined. Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... # uname -a FreeBSD vpn-17 7.1-STABLE FreeBSD 7.1-STABLE #6: Wed Mar 11 12:59:09 YEKT 2009 r...@vpn:/usr/src/sys/i386/compile/kconf i386 # nm -n /usr/local/drbd/vpntest/boot/kernel/kernel | grep 806d67 806d671b t ng_pptpgre_rcvdata_lower Sometimes: #dmesg | grep 'instruction pointer' instruction pointer = 0x20:0x806ca7e1 # nm -n /usr/local/drbd/vpntest/boot/kernel/kernel | grep 806ca7 806ca740 t ng_iface_ioctl What can I do with it? I don`t have experience in using gdb or programming on C. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 7.1-PRELEASE sporadically panicking with fatal trap 12
John L. Templer wrote: I'm running 7.1-PRERELEASE, with /usr/src and /usr/ports last csup-ed just a few days ago. After being up for about a day or so the system will panic because of a page fault. I'm not completely sure, but it seems that the system is more stable when gdm and gnome are disabled in rc.conf. At least it stayed up for several days when I did that. I've run memtest several times, so I'm pretty confident it's not a memory problem. Also the stack trace is always the same, so I'm thinking it's not hardware related. I've attached a stack trace from kgdb, and the output from dmesg. I'd appreciate any help you could give me with this. Please re-send to stable@ and CC [EMAIL PROTECTED] It looks like a locking problem in an error case that you are hitting (note ATA driver message prior to panic). Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
7.1-PRELEASE sporadically panicking with fatal trap 12
I'm running 7.1-PRERELEASE, with /usr/src and /usr/ports last csup-ed just a few days ago. After being up for about a day or so the system will panic because of a page fault. I'm not completely sure, but it seems that the system is more stable when gdm and gnome are disabled in rc.conf. At least it stayed up for several days when I did that. I've run memtest several times, so I'm pretty confident it's not a memory problem. Also the stack trace is always the same, so I'm thinking it's not hardware related. I've attached a stack trace from kgdb, and the output from dmesg. I'd appreciate any help you could give me with this. /var/crash# kgdb -n 5 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: acd1: WARNING - READ_TOC read data overrun 18>12 Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x188 fault code = supervisor read, page not present instruction pointer = 0x20:0xc0782714 stack pointer = 0x28:0xe52aec00 frame pointer = 0x28:0xe52aec18 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 18 (swi6: task queue) trap number = 12 panic: page fault cpuid = 0 Uptime: 8h10m38s Physical memory: 1779 MB Dumping 195 MB: 180 164 148 132 116 100 84 68 52 36 20 4 Reading symbols from /boot/kernel/sound.ko...Reading symbols from /boot/kernel/sound.ko.symbols...done. done. Loaded symbols for /boot/kernel/sound.ko Reading symbols from /boot/kernel/snd_cmi.ko...Reading symbols from /boot/kernel/snd_cmi.ko.symbols...done. done. Loaded symbols for /boot/kernel/snd_cmi.ko Reading symbols from /boot/kernel/acpi.ko...Reading symbols from /boot/kernel/acpi.ko.symbols...done. done. Loaded symbols for /boot/kernel/acpi.ko Reading symbols from /boot/kernel/linux.ko...Reading symbols from /boot/kernel/linux.ko.symbols...done. done. Loaded symbols for /boot/kernel/linux.ko Reading symbols from /usr/local/modules/fuse.ko...done. Loaded symbols for /usr/local/modules/fuse.ko Reading symbols from /boot/kernel/mach64.ko...Reading symbols from /boot/kernel/mach64.ko.symbols...done. done. Loaded symbols for /boot/kernel/mach64.ko Reading symbols from /boot/kernel/drm.ko...Reading symbols from /boot/kernel/drm.ko.symbols...done. done. Loaded symbols for /boot/kernel/drm.ko #0 doadump () at pcpu.h:196 196 pcpu.h: No such file or directory. in pcpu.h (kgdb) backtrace #0 doadump () at pcpu.h:196 #1 0xc078fae7 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc078fda9 in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:572 #3 0xc0aa174c in trap_fatal (frame=0xe52aebc0, eva=392) at /usr/src/sys/i386/i386/trap.c:939 #4 0xc0aa19d0 in trap_pfault (frame=0xe52aebc0, usermode=0, eva=392) at /usr/src/sys/i386/i386/trap.c:852 #5 0xc0aa238c in trap (frame=0xe52aebc0) at /usr/src/sys/i386/i386/trap.c:530 #6 0xc0a8827b in calltrap () at /usr/src/sys/i386/i386/exception.s:159 #7 0xc0782714 in _mtx_lock_sleep (m=0xc4ff804c, tid=3302734576, opts=0, file=0x0, line=0) at /usr/src/sys/kern/kern_mutex.c:339 #8 0xc078ed66 in _sema_post (sema=0xc4ff804c, file=0x0, line=0) at /usr/src/sys/kern/kern_sema.c:79 #9 0xc0513350 in ata_completed (context=0xc4ff8000, dummy=1) at /usr/src/sys/dev/ata/ata-queue.c:481 #10 0xc07c2e15 in taskqueue_run (queue=0xc4dbab80) at /usr/src/sys/kern/subr_taskqueue.c:282 #11 0xc07c3123 in taskqueue_swi_run (dummy=0x0) at /usr/src/sys/kern/subr_taskqueue.c:324 #12 0xc076f8db in ithread_loop (arg=0xc4dadb30) at /usr/src/sys/kern/kern_intr.c:1088 #13 0xc076c449 in fork_exit (callout=0xc076f720 , arg=0xc4dadb30, frame=0xe52aed38) at /usr/src/sys/kern/kern_fork.c:804 ---Type to continue, or q to quit--- #14 0xc0a882f0 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:264 (kgdb) up 7 #7 0xc0782714 in _mtx_lock_sleep (m=0xc4ff804c, tid=3302734576, opts=0, file=0x0, line=0) at /usr/src/sys/kern/kern_mutex.c:339 339 owner = (struct thread *)(v & ~MTX_FLAGMASK); (kgdb) list 334 * If the owner is running on another CPU, spin until the 335 * owner stops running or the state of the lock changes. 336 */ 337 v = m->mtx_lock; 338 if (v != M
Re: Fatal Trap 12 Page Fault while in Kernel Moder
Devinder Singh wrote: Hi I am using Free BSD 6.3 and am intergating Monowal and FreeRadius When i make the image i get this error Fatal Trap 12 :page fault while in kernel mode Fault virtual addres 0xbffle000 fault code -= supervisor write, page not present instruction pointer = 0*28 = trap number 12 panic = page fault Pls can some one help me on this You need to obtain more debugging information before anyone can help you. See the chapter on kernel debugging in the developers handbook. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Fatal Trap 12: Page Fault While in Kernel Mode
Hi I am getign this serios error message when i have packaged free radius in freebsd 6.3 Fatal Trap 12: page fault while in kernel mode fault virtual address fault code = supervisor write , page not present instruction pointer = 0*20 stack pointer = curent process = 0 trap njumber 12 > From: [EMAIL PROTECTED]> To: freebsd-questions@freebsd.org> Date: Tue, 1 Jul > 2008 15:58:49 +0800> Subject: Fatal Trap 12: Page Fault While in Kernel Mode> > > > > _> > Check out Barclays Premier League exclusive video clips here!> > http://fc.sg.msn.com/index.aspx___> > freebsd-questions@freebsd.org mailing list> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions> To unsubscribe, > send any mail to "[EMAIL PROTECTED]" _ Easily edit your photos like a pro with Photo Gallery. http://get.live.com/photogallery/overview___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Fatal Trap 12: Page Fault While in Kernel Mode
_ Check out Barclays Premier League exclusive video clips here! http://fc.sg.msn.com/index.aspx___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Fatal Trap 12 Page Fault while in Kernel Moder
Hi I am using Free BSD 6.3 and am intergating Monowal and FreeRadius When i make the image i get this error Fatal Trap 12 :page fault while in kernel mode Fault virtual addres 0xbffle000 fault code -= supervisor write, page not present instruction pointer = 0*28 = trap number 12 panic = page fault Pls can some one help me on this _ NEW! Get Windows Live FREE. http://www.get.live.com/wl/all___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fatal trap 12 --- can lack of APIC on SMP cause crashes?
Rudy wrote: Rudy wrote: My kernel panics! Here are a two things I did which seem to stop the Fatal trap 12's with FreeBSD-7.0-RELEASE (saw it on three different boxes): cvsup to FreeBSD-7.0-STABLE (Don't forget to change SCHED_4BSD --> SCHED_ULE as that is now the default on STABLE) disabled CARP I don't know if it was the SCHED_4BSD, the CARP, or the combination, but my boxes seem stable now. Just wanted to answer my own post in case anyone is searching for Fatal trap 12 cures for FreeBSD-7.0-RELEASE. :) FYI, "Fatal trap 12" is a very generic type of error (it can mean "null pointer dereference, among other things) and it can have many causes (e.g. anywhere in the entire kernel where there is a pointer that can become NULL through a programming or other error). You need to compare the stack traces to work out what the cause was. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fatal trap 12 --- can lack of APIC on SMP cause crashes?
Rudy wrote: My kernel panics! Here are a two things I did which seem to stop the Fatal trap 12's with FreeBSD-7.0-RELEASE (saw it on three different boxes): cvsup to FreeBSD-7.0-STABLE (Don't forget to change SCHED_4BSD --> SCHED_ULE as that is now the default on STABLE) disabled CARP I don't know if it was the SCHED_4BSD, the CARP, or the combination, but my boxes seem stable now. Just wanted to answer my own post in case anyone is searching for Fatal trap 12 cures for FreeBSD-7.0-RELEASE. :) Rudy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Fatal trap 12 --- can lack of APIC on SMP cause crashes?
My kernel panics! I reinstlled i386 and scrapped my amd64 install, however, I forgot the "APIC" line... would that cause crashes under load or high network activity? device apic# I/O apic - Rudy # uname FreeBSD example.monkeybrains.net 7.0-STABLE FreeBSD 7.0-STABLE #0: Mon May 12 15:17:23 PDT 2008 root@:/usr/obj/usr/src/sys/EXAMPLE i386 # crash message: Fatal trap 12: page fault while in kernel mode instruction pointer = 0x20:0xc05330da Following this advice: http://www.freebsd.org/doc/en/books/faq/advanced.html#KERNEL-PANIC-TROUBLESHOOTING Nothing close to 0xc05330da... here is the closest: # nm -n /boot/kernel/kernel | grep c053 c0532c5a t turnstile_first_waiter c0532c80 T turnstile_head c0532c8f T turnstile_empty c0532ca5 t turnstile_fini c0532cb8 t turnstile_init c0532d2a T init_turnstiles c0532dc6 t turnstile_adjust_thread c0532f48 t propagate_priority c0533101 T turnstile_adjust c0533144 T turnstile_free c0533168 T turnstile_alloc c053318d t init_turnstile0 - kernel config file: ###cpu HAMMER # wasn't working on amd64... cpu I686_CPU ident EXAMPLE # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols options SCHED_4BSD # 4BSD scheduler options PREEMPTION # Enable kernel thread preemption options INET# InterNETworking #optionsINET6 # IPv6 communications protocols #optionsSCTP# Stream Control Transmission Protocol options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories #optionsUFS_GJOURNAL# Enable gjournal-based UFS journaling options MD_ROOT # MD is a potential root device options NFSCLIENT # Network Filesystem Client #optionsNFSSERVER # Network Filesystem Server options NFS_ROOT# NFS usable as /, requires NFSCLIENT #optionsNTFS# NT File System #optionsMSDOSFS # MSDOS Filesystem #optionsCD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS# Pseudo-filesystem framework #optionsGEOM_PART_GPT # GUID Partition Tables. options GEOM_LABEL # Provides labelization options COMPAT_43TTY# BSD 4.3 TTY compat [KEEP THIS!] #optionsCOMPAT_IA32 # Compatible with i386 binaries #optionsCOMPAT_FREEBSD4 # Compatible with FreeBSD4 #optionsCOMPAT_FREEBSD5 # Compatible with FreeBSD5 #optionsCOMPAT_FREEBSD6 # Compatible with FreeBSD6 options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI #optionsKTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV# install a CDEV entry in /dev options ADAPTIVE_GIANT # Giant mutex is adaptive. options STOP_NMI# Stop CPUS using NMI instead of IPI #optionsAUDIT # Security event auditing # Make an SMP-capable kernel by default options SMP # Symmetric MultiProcessor Kernel # CPU frequency control device cpufreq # Bus support. device acpi device eisa device pci # ATA and ATAPI devices device ata device atadisk # ATA disk drives options ATA_STATIC_ID # Static device numbering # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device kbdmux # keyboard multiplexer device vga # VGA video card driver device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc device agp # support several AGP chipsets # Serial (COM) ports device sio # 8250, 16
Re: raid1 + degraded (take out one disk) + fatal trap 12 on next reboot
Hi Ted. Thank you for replying to my post. see my comments below. Ted Mittelstaedt wrote: Roberto, You can't simulate a disk drive failure that way. If you really want to know what's going on, the issue is that your pointing the swap to ar0. If you must get this booted again you can try booting into single user mode and editing /etc/fstab and pointing the partitions to /dev/ad0 instead of /dev/ar0 and booting. But this is an emergency action and is not recommended. It doesn't even get to that point.. it panics before giving me the shell for single user mode.. I even made a few tests trying to comment out the swap in fstab, but that didn't help. but it doesn't matter.. I solved the problem by removing and then readding the disk from the raid in the bios. One up again had to rebuild the raid in the OS.. and that was it.. If you want to simulate a drive failure, WHILE THE SYSTEM IS RUNNING pull the SATA connector on one drive. For sure that makes for a real test.. but.. Are you sure that that will not fry up the mainboard or the drive? The system should NOT trap, it should simply print a error to the console and show it's gone into degraded mode. If you then reboot, the system may or may not come back up. You have to understand the approach of RAID mirroring. Basically this is poor-man's data protection. The idea is that a disk usually fails in the middle of the day during the worst possible time. When it does you do NOT want the server to stop or crash. You want it to keep running until the evening when you can spend a couple hours getting the disk replaced. (or until the next day when you can buy a replacement drive) When you have the replacement disk ready to plug into the system, you are supposed to run a full backup of your data on the degraded array just in case the reinsertion goes badly. I have found the safest is to leave the server alone and get the replacement disk ready. Wiping it in another system with dd if=/dev/zero of=/dev/ad1 bs=50k is the best policy before reinsertion. Thank you very much for these instructions. Luckly I'm not familiar with failing drives! :) Follow the steps in the man page for reinsertion. Keep in What man page? Again Thank you very much. Best regards. Robi mind that they don't always work. If they don't then you will have to wipe both disks and regenerate the array and reinstall the OS. That is why you make a backup first when the system is off-duty. Ted -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Roberto Nunnari Sent: Tuesday, April 29, 2008 12:35 PM To: freebsd-questions@freebsd.org Subject: Re: raid1 + degraded (take out one disk) + fatal trap 12 on next reboot Nobody on this, please? :) Roberto Nunnari wrote: Hi all! I'm playing with new HW and FreeBSD 6.3 and 7.0. I set up raid 1 on two sata disks (fakeraid on ICH9R) and as long as I can see, it seams to work very well. Now I'm trying to simulate 1 disk failure (I just take out a disk and boot again). Doesn't matter which of the two disks I take out, the bios correctly shows the raid as degraded and bootable, loads the FreeBSD loader, who loads the kernel and starts the boot. But when the kernel comes to the drives (or the swap?) it fatal traps 12. The trap descriptions sais that current process is 0 (swapper). Reading that I commented out the swap partition from fstab, but that doesn't help. How can I get the system to finish the boot? Thank you and best regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: raid1 + degraded (take out one disk) + fatal trap 12 on next reboot
Roberto, You can't simulate a disk drive failure that way. If you really want to know what's going on, the issue is that your pointing the swap to ar0. If you must get this booted again you can try booting into single user mode and editing /etc/fstab and pointing the partitions to /dev/ad0 instead of /dev/ar0 and booting. But this is an emergency action and is not recommended. If you want to simulate a drive failure, WHILE THE SYSTEM IS RUNNING pull the SATA connector on one drive. The system should NOT trap, it should simply print a error to the console and show it's gone into degraded mode. If you then reboot, the system may or may not come back up. You have to understand the approach of RAID mirroring. Basically this is poor-man's data protection. The idea is that a disk usually fails in the middle of the day during the worst possible time. When it does you do NOT want the server to stop or crash. You want it to keep running until the evening when you can spend a couple hours getting the disk replaced. (or until the next day when you can buy a replacement drive) When you have the replacement disk ready to plug into the system, you are supposed to run a full backup of your data on the degraded array just in case the reinsertion goes badly. I have found the safest is to leave the server alone and get the replacement disk ready. Wiping it in another system with dd if=/dev/zero of=/dev/ad1 bs=50k is the best policy before reinsertion. Follow the steps in the man page for reinsertion. Keep in mind that they don't always work. If they don't then you will have to wipe both disks and regenerate the array and reinstall the OS. That is why you make a backup first when the system is off-duty. Ted > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Roberto Nunnari > Sent: Tuesday, April 29, 2008 12:35 PM > To: freebsd-questions@freebsd.org > Subject: Re: raid1 + degraded (take out one disk) + fatal trap 12 on > next reboot > > > Nobody on this, please? :) > > > Roberto Nunnari wrote: > > Hi all! > > > > I'm playing with new HW and FreeBSD 6.3 and 7.0. > > > > I set up raid 1 on two sata disks (fakeraid on ICH9R) > > and as long as I can see, it seams to work very well. > > > > Now I'm trying to simulate 1 disk failure (I just take > > out a disk and boot again). Doesn't matter which of the > > two disks I take out, the bios correctly shows the raid > > as degraded and bootable, loads the FreeBSD loader, who > > loads the kernel and starts the boot. > > But when the kernel comes to the drives (or the swap?) > > it fatal traps 12. The trap descriptions sais that > > current process is 0 (swapper). > > > > Reading that I commented out the swap partition from fstab, > > but that doesn't help. > > > > How can I get the system to finish the boot? > > > > Thank you and best regards. > > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: raid1 + degraded (take out one disk) + fatal trap 12 on next reboot
Nobody on this, please? :) Roberto Nunnari wrote: Hi all! I'm playing with new HW and FreeBSD 6.3 and 7.0. I set up raid 1 on two sata disks (fakeraid on ICH9R) and as long as I can see, it seams to work very well. Now I'm trying to simulate 1 disk failure (I just take out a disk and boot again). Doesn't matter which of the two disks I take out, the bios correctly shows the raid as degraded and bootable, loads the FreeBSD loader, who loads the kernel and starts the boot. But when the kernel comes to the drives (or the swap?) it fatal traps 12. The trap descriptions sais that current process is 0 (swapper). Reading that I commented out the swap partition from fstab, but that doesn't help. How can I get the system to finish the boot? Thank you and best regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
kernel: Fatal trap 12: page fault while in kernel mode
Hi all. Some problem with free. I`ve got such mess in log: Jan 4 22:47:09 fs kernel: Fatal trap 12: page fault while in kernel mode Jan 4 22:47:09 fs kernel: fault virtual address= 0x3e Jan 4 22:47:09 fs kernel: fault code = supervisor read, page not present Jan 4 22:47:09 fs kernel: instruction pointer = 0x20:0xc060cc24 Jan 4 22:47:09 fs kernel: stack pointer= 0x28:0xe529ac30 Jan 4 22:47:09 fs kernel: frame pointer= 0x28:0xe529ac34 Jan 4 22:47:09 fs kernel: code segment = base 0x0, limit 0xf, type 0x1b Jan 4 22:47:09 fs kernel: = DPL 0, pres 1, def32 1, gran 1 Jan 4 22:47:09 fs kernel: processor eflags = interrupt enabled, resume,IOPL = 0 Jan 4 22:47:09 fs kernel: current process = 9 (thread taskq) Jan 4 22:47:09 fs kernel: trap number = 12 Jan 4 22:47:09 fs kernel: panic: page fault Jan 4 22:47:09 fs kernel: Uptime: 4d0h37m10s Jan 4 22:47:09 fs kernel: Physical memory: 2013 MB Jan 4 22:47:09 fs kernel: Dumping 243 MB: 228 212 196 180 164 148 132 116 100 84 68 52 36 20 4 Jan 4 22:47:09 fs kernel: Dump complete Jan 4 22:47:09 fs kernel: Automatic reboot in 15 seconds - press a key on the console to abort Jan 4 22:47:09 fs kernel: Rebooting... Problem repeats for 6.2-RELEASE. kgdb kernel.debug /var/crash/vmcore.0 - returns this: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x3e fault code = supervisor read, page not present instruction pointer = 0x20:0xc060cc24 stack pointer = 0x28:0xe529ac30 frame pointer = 0x28:0xe529ac34 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 9 (thread taskq) trap number = 12 panic: page fault Uptime: 4d0h37m10s Physical memory: 2013 MB Dumping 243 MB: 228 212 196 180 164 148 132 116 100 84 68 52 36 20 4 #0 doadump () at pcpu.h:195 195 __asm __volatile("movl %%fs:0,%0" : "=r" (td)); I think it`s hardware problem. This machine has been working for about 9 months with no problems but I dont know how to correctly find the problem. uname -a: FreeBSD fs.ngc.net.ua 8.0-CURRENT FreeBSD 8.0-CURRENT #3: Mon Dec 31 05:07:25 EET 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/FS i386 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Kernel panic; fatal trap 12; on task 22, USB0: was Re: Moused issues?
On Sun, Oct 07, 2007 at 11:01:41AM +0200, Hans Petter Selasky wrote: > On Saturday 06 October 2007, Joe Altman wrote: > > chthonic.com/crash-crash-crash > > Hi, > > Do you have "options KDB" in your kernel config file ? Following your suggestion, I did try this; and there was no change from kernel panic and reboot. > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-options.html > > You should get a prompt when it panics. There was no prompt. > Then you type in "bt" for backtrace. > Maybe you could take a picture of that. Personally, it's a bit embarassing to be so helpless that I am forced to take a picture. I suppose if I could be certain about how to compile bootblocks, I might be able to do something on the serial console with a laptop. But the one time I attempted that was a disaster. Is my speculation about the "...no dump device found..." correct? Is it that swapon and multiuser has not occurred, and so there can occur no dump to the swap space? > Probably someone is accessing a NULL pointer. If any more damage occurs, ISTM that my entire installation will be accessing a NULL pointer; the following message is from the most recent dmesg, and is new: warning: KLD '/boot/kernel.old.bootable/drm.ko' is newer than the linker.hints file Since my hardware appears to not work with the available source, who knows how that will go? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Kernel panic; fatal trap 12; on task 22, USB0: was Re: Moused issues?
On Saturday 06 October 2007, Joe Altman wrote: > chthonic.com/crash-crash-crash Hi, Do you have "options KDB" in your kernel config file ? http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-options.html You should get a prompt when it panics. Then you type in "bt" for backtrace. Maybe you could take a picture of that. Probably someone is accessing a NULL pointer. --HPS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Kernel panic; fatal trap 12; on task 22, USB0: was Re: Moused issues?
NB: I've copied -usb because it looks to me like it's definitely USB that's implicated; but I still need a clue for getting a crash dump; -questions seems the place to ask for that. On Sun, Sep 23, 2007 at 07:57:41PM -0400, Joe Altman wrote: > > uname for the machine on which it fails: > > 6.2-STABLE FreeBSD 6.2-STABLE #0: Sun Sep 2 17:30:39 EDT 2007 i386 > > Is it possible to get more info on this for debugging short of putting > debugging in the kernel, and configuring a dump device; rebuilding > world, and hoping my machine does not become unusable? I'm still seeing the USB associated crashes, with sources updated several times and world remade between Sept. 23 and Oct. 6, 11 AM EDT. The above uname shows the only kernel I can use. I've attempted to obtain a dump using these instructions: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html#KERNELDEBUG-OBTAIN And here, I think, are the relevent details. In /etc/rc.conf, I have: ##Crash dumpdev="AUTO" dumpdir="/var/tmp/crash" /var/tmp/crash exists with appropriate permissions; and swapinfo shows 2 Gig of space: ~ $: swapinfo Device 1M-blocks UsedAvail Capacity /dev/ad0s1b 20480 2048 0% AIUI, dumpdev="AUTO" dictates the use of /dev/ad0s1b. /var/tmp has this much free space: df -m /dev/ad0s1f 3962 618 3027 17% /var/tmp However, my kernel tosses this message to the console: Fatal trap 12: page fault while in kernel mode and indicates a problem with task 22, USB[1] 0. Prior to problem with task 22, USB 0; it was the same fatal trap, task 25, USB 1. Then it indicates that there is no dump device. It seems to me that all I should have to do is define the dumpdev in rc.conf to obtain a dump; and in my case, since /var is smaller than RAM and swap, define /var/tmp/crash. So it looks to me as if I am experiencing what is described here: "...a kernel is crashing before dumpon(8) can be executed." taken from the kerneldebug.html page. Or am I missing something in the configuration of the dump device? If not, is my only option to put a dump directive into my kernel config? If so, what is the proper syntax? device dump or something else? Also, I decided it was easier for my to snap a picture than transcribe the screen; it's here if anyone is interested: chthonic.com/crash-crash-crash I'm limping along, I think; and would appreciate some clues, please. One more data point: I'm using an IBM PIII laptop; and I do not experience any crash on that; and my AMD dual core does not crash either; all three machines use, AFAICT, the same USB code. Thanks. [1] The USB controller is: http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Fatal trap 12: page fault while in kernel mode.Need help.
Hello. Trap 12 occured when I rebooted PC. Sending you backtrace. My system: amd64 3200+ Venice, MB ECS nForce4 A939,Samsung 250GB and WD 250 GB, 2 memory banks 512MB each, videocard: Geforce 6600gt 128MB, NIC on realtek chip, sound card cirrus logic cs4281. It's very unstable, crashes happen every day, so I'm hoping you would say why(any hints what hardware may cause it). How to repeat it? I don't know. It happened once during reboot process. [EMAIL PROTECTED] /var]# uname -a FreeBSD freelanc.dubki.ru 6.2-STABLE-200706 FreeBSD 6.2-STABLE-200706 #1: Mon Jul 23 13:34:27 MSD 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/DEBUGGERKERN i386 [EMAIL PROTECTED] /usr/obj/usr/src/sys/DEBUGGERKERN]# kgdb kernel.debug /var/crash/vmcore.3 kgdb: kvm_nlist(_stopped_cpus): kgdb: kvm_nlist(_stoppcbs): [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] 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: <118>Jul 25 14:06:32 freelanc syslogd: exiting on signal 15 Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...6 5 3 1 0 0 done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done All buffers synced. Fatal trap 12: page fault while in kernel mode fault virtual address = 0x4 fault code = supervisor read, page not present instruction pointer = 0x20:0xc058a4e0 stack pointer = 0x28:0xe9455c48 frame pointer = 0x28:0xe9455c58 code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 44922 (reboot) panic: from debugger Uptime: 2h45m36s Dumping 1022 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 1022MB (261600 pages) 1006 990 974 958 942 926 910 894 878 862 846 830 814 798 782 766 750 734 718 702 686 670 654 638 622 606 590 574 558 542 526 510 494 478 462 446 430 414 398 382 366 350 334 318 302 286 270 254 238 222 206 190 174 158 142 126 110 94 78 62 46 30 14 #0 doadump () at pcpu.h:165 165 __asm __volatile("movl %%fs:0,%0" : "=r" (td)); (kgdb) bt #0 doadump () at pcpu.h:165 #1 0xc053d916 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409 #2 0xc053dbdc in panic (fmt=0xc06f5278 "from debugger") at /usr/src/sys/kern/kern_shutdown.c:565 #3 0xc045361d in db_panic (addr=-1067932448, have_addr=0, count=-1, modif=0xe9455a74 "") at /usr/src/sys/ddb/db_command.c:438 #4 0xc04535b4 in db_command (last_cmdp=0xc0766784, cmd_table=0x0, aux_cmd_tablep=0xc0728e90, aux_cmd_tablep_end=0xc0728e94) at /usr/src/sys/ddb/db_command.c:350 #5 0xc045367c in db_command_loop () at /usr/src/sys/ddb/db_command.c:458 #6 0xc0455291 in db_trap (type=12, code=0) at /usr/src/sys/ddb/db_main.c:222 #7 0xc0556a2b in kdb_trap (type=12, code=0, tf=0xe9455c08) at /usr/src/sys/kern/subr_kdb.c:473 #8 0xc06cba6c in trap_fatal (frame=0xe9455c08, eva=4) at /usr/src/sys/i386/i386/trap.c:828 #9 0xc06cb7d7 in trap_pfault (frame=0xe9455c08, usermode=0, eva=4) at /usr/src/sys/i386/i386/trap.c:745 #10 0xc06cb3f1 in trap (frame= {tf_fs = 8, tf_es = 40, tf_ds = 40, tf_edi = -381330360, tf_esi = -993547624, tf_ebp = -381330344, tf_isp = -381330380, tf_ebx = 0, tf_edx = -992513384, tf_ecx = 4, tf_eax = -950651024, tf_trapno = 12, tf_err = 0, tf_eip = -1067932448, tf_cs = 32, tf_eflags = 590338, tf_esp = 0, tf_ss = -992305712}) at /usr/src/sys/i386/i386/trap.c:435 #11 0xc06b8b1a in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #12 0xc058a4e0 in cache_purgevfs (mp=0xc4d77298) at /usr/src/sys/kern/vfs_cache.c:622 #13 0xc0591f29 in dounmount (mp=0xc4d77298, flags=524288, td=0xc62ce300) at /usr/src/sys/kern/vfs_mount.c:1214 #14 0xc0597d0a in vfs_unmountall () at /usr/src/sys/kern/vfs_subr.c:2837 #15 0xc053d807 in boot (howto=0) at /usr/src/sys/kern/kern_shutdown.c:391 #16 0xc053d2a2 in reboot (td=0xc62ce300, uap=0xc7563770) at /usr/src/sys/kern/kern_shutdown.c:169 #17 0xc06cbdbb in syscall (frame= {tf_fs = 59, tf_es = 59, tf_ds = 59, tf_edi = 2, tf_esi = 18, tf_ebp = -1077941304, tf_isp = -381330076, tf_ebx = 0, tf_edx = -1, tf_ecx = 672491264, tf_eax = 55, tf_trapno = 12, tf_err = 2, tf_eip = 671802263, tf_cs = 51, tf_eflags = 662, tf_esp = -1077941380, tf_ss = 59}) at /usr/src/sys/i386/i386/trap.c:983 #18 0xc06b8b6f in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:200 #19 0x0033 in ?? () Previous frame inner to this frame (corru
Re: FreeBSD 6.2 Repeating Crash - Sleeping thread; Fatal trap 12: page fault; warning: 'T2' might be used uninitialized - SOLUTION
We finally determined the root of this problem. One of the system's memory modules was apparently going bad. When it failed permanently, the system crashed and would not reboot. We swapped out the memory (all Regsistered memory) and have not had problems since. Thanks to the list for the efforts! WB (Below is a reply drafted a long while back - included mostly to thank Beto...the rest of it is no longer relevant.) Thank you very much for your reply, Beto. I appreciate your point re: drive age. I only mentioned it because I had stated the age of the server at 5 years and hoped to forestall suggestions that an older drive might be likely to have issues. However, I did follow your suggestion and smartctl reports the drive to be in good health. I misspoke - we did not upgrade, really, but did a fresh install of 6.1 on the new drive and manually copied all user files, databases, PERL scripts, etc. to the new drive. We had been running 4.7 and, since there was not a direct route for upgrading, we did it the hard way. Your advice re: copying & renaming GENERIC is well taken - that is, in fact, exactly what we did. Further, as advised in the manual, we moved it from /usr/src to a different directory and created a sym link to avoid inadvertently overwriting it. We did not rename the ident line, but it seems unlikely that that oversight would prevent the kernel from making. Were any of the errors described familiar? - Original Message - From: "Norberto Meijome" <[EMAIL PROTECTED]> To: "Worth Bishop" <[EMAIL PROTECTED]> Cc: Sent: Wednesday, June 13, 2007 12:52 PM Subject: Re: FreeBSD 6.2 Repeating Crash - Sleeping thread; Fatal trap 12: page fault; warning: 'T2' might be used uninitialized On Tue, 12 Jun 2007 11:38:19 -0400 "Worth Bishop" <[EMAIL PROTECTED]> wrote: Addendum: For what it's worth, the 250Gb Samsung drive was added when the system was upgraded - it's only 3-4 months old. Worth, that doesnt mean much - drives can (and do) fail anyway. I suggest you run smartctl ( sysutils/smartmontools ) to run tests on your drive and ensure you don't have any actual problems with it btw, you don't mention from what version you had upgraded to 6.1. Did you do a full world upgrade as well as kernel? from your previous email, you ended up having some kernel build problems. 1) it is good practise to rename your kernel file (and ident line inside it) from GENERIC once you've modified it. It makes it obvious to see whether you are truly running the same GENERIC as everyone else. 2) make sure you have the latest and proper code for your line of src you need (eg, -STABLE , or RELEASE-p5 ,etc). You should use cvsup for this. If you need them, the default config files are in /usr/share/examples/cvsup/ . B _ {Beto|Norberto|Numard} Meijome "Never offend people with style when you can offend them with substance." Sam Brown I speak for myself, not my employer. Contents may be hot. Slippery when wet. Reading disclaimers makes you go blind. Writing them is worse. You have been Warned. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 6.2 Repeating Crash - Sleeping thread; Fatal trap 12: page fault; warning: 'T2' might be used uninitialized
Hardware can be eliminated by running memtest86 bootable ISOs from the web site. A bad sector test on the drives would be less ambiguous (kernel messages preceeding a panic). Smart can be helpful. Overheating CPUs and underpowered/overheated Power Supplies can cause problems, but they would normally manifest in memtest86+ failures www.memtest.org/ On Thu, 2007-06-14 at 02:52 +1000, Norberto Meijome wrote: > On Tue, 12 Jun 2007 11:38:19 -0400 > "Worth Bishop" <[EMAIL PROTECTED]> wrote: > > > Addendum: For what it's worth, the 250Gb Samsung drive was added when the > > system was upgraded - it's only 3-4 months old. > > Worth, > that doesnt mean much - drives can (and do) fail anyway. I suggest you run > smartctl ( sysutils/smartmontools ) to run tests on your drive and ensure you > don't have any actual problems with it > > btw, you don't mention from what version you had upgraded to 6.1. Did you do a > full world upgrade as well as kernel? > > > from your previous email, you ended up having some kernel build problems. > 1) it is good practise to rename your kernel file (and ident line inside it) > from GENERIC once you've modified it. It makes it obvious to see whether you > are truly running the same GENERIC as everyone else. > > 2) make sure you have the latest and proper code for your line of src you need > (eg, -STABLE , or RELEASE-p5 ,etc). You should use cvsup for this. If you need > them, the default config files are in /usr/share/examples/cvsup/ . > > B > _ > {Beto|Norberto|Numard} Meijome > > "Never offend people with style when you can offend them with substance." > Sam Brown > > I speak for myself, not my employer. Contents may be hot. Slippery when wet. > Reading disclaimers makes you go blind. Writing them is worse. You have been > Warned. > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Brian A. Seklecki <[EMAIL PROTECTED]> Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 6.2 Repeating Crash - Sleeping thread; Fatal trap 12: page fault; warning: 'T2' might be used uninitialized
Read: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html Also, is your /usr/src tagged RELENG_6_2 ? You can remove DEBUG=-g and that problem does not occur? You didn't try to update your src to tree to STABLE or CURRENT? ~~BAS On Tue, 2007-06-12 at 11:33 -0400, Worth Bishop wrote: > ed GENERIC and edited it, noting that "options ddb" was > already enabled. We added 'makeoptions DEBUG=-g# > Build > kernel with gdb(1) debug symbols' as suggested and tried to "make > buildkernel" which errored out stating that KDB must be enabled to use > DDB. > We edited KERNEL.DEBUG to add 'options KDB > # > Enable kernel debugger' and attempted to "make buildkernel" again. > This > time, the process stopped again with the message: > > THIRD ERROR EVENT > > [snip] > inline-unit-growth=100 --param > arge-function-growth=1000 -mno-align-long-strings > -mpreferred-stack-bounda -- Brian A. Seklecki <[EMAIL PROTECTED]> Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 6.2 Repeating Crash - Sleeping thread; Fatal trap 12: page fault; warning: 'T2' might be used uninitialized
On Tue, 12 Jun 2007 11:38:19 -0400 "Worth Bishop" <[EMAIL PROTECTED]> wrote: > Addendum: For what it's worth, the 250Gb Samsung drive was added when the > system was upgraded - it's only 3-4 months old. Worth, that doesnt mean much - drives can (and do) fail anyway. I suggest you run smartctl ( sysutils/smartmontools ) to run tests on your drive and ensure you don't have any actual problems with it btw, you don't mention from what version you had upgraded to 6.1. Did you do a full world upgrade as well as kernel? from your previous email, you ended up having some kernel build problems. 1) it is good practise to rename your kernel file (and ident line inside it) from GENERIC once you've modified it. It makes it obvious to see whether you are truly running the same GENERIC as everyone else. 2) make sure you have the latest and proper code for your line of src you need (eg, -STABLE , or RELEASE-p5 ,etc). You should use cvsup for this. If you need them, the default config files are in /usr/share/examples/cvsup/ . B _ {Beto|Norberto|Numard} Meijome "Never offend people with style when you can offend them with substance." Sam Brown I speak for myself, not my employer. Contents may be hot. Slippery when wet. Reading disclaimers makes you go blind. Writing them is worse. You have been Warned. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Fw: FreeBSD 6.2 Repeating Crash - Sleeping thread; Fatal trap 12: page fault; warning: 'T2' might be used uninitialized
Addendum: For what it's worth, the 250Gb Samsung drive was added when the system was upgraded - it's only 3-4 months old. - Original Message - From: "Worth Bishop" <[EMAIL PROTECTED]> To: Sent: Tuesday, June 12, 2007 11:33 AM Subject: FreeBSD 6.2 Repeating Crash - Sleeping thread; Fatal trap 12: page fault; warning: 'T2' might be used uninitialized Please help if you can... BACKGROUND This crash is occurring on a dual-AMD 1.6Ghz cpu white-box system with 1 Gb ram, 250Gb storage running GENERIC kernel. The system has been in production use as a web server for nearly five years. About 3 - 4 months ago, the system was upgraded from an earlier FreeBSD version to 6.1. At the same time, all supporting applications (Apache webserver, PERL, PostgreSQL, PHP, countless other applications & libraries) were upgraded to the current releases. The system was stable up until a couple of weeks ago. FIRST ERROR EVENT The system crashed during normal usage. The following message was displayed on the console which was not responsive to keyboard input: Sleeping thread (tid 100122, pid 11099) owns a non-sleepable lock panic: sleeping thread cpuid=1 The system was restarted, an fsck routine was completed (answering "yes" to all the "Do you want to salvage" type questions) and the server ran fine. For about a week. It then crashed again several times, at intervals varying from a few minutes of uptime to a few days. SECOND ERROR EVENT After some crashes, a message similar to that above was displayed. However, at other times a message similar to this was displayed: kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid=0; apic id=01 fault virtual address =0x100 fault code =supervisor read, page not present instruction pointer =0x20:0xc066c731 stack pointer =0x28:0xe432ebf0 framepointer =0x28:0xe432ebfc code segment =base 0x0, limit0xf, type 0x1b =DPL 0, pres 1, def32 1, gran1 processor eflags =resume, IOPL=0 current process =36 (syncer) trap number = 12 panic: page fault cpuid=0 uptime: 3d10h11m44s Dumping 1535 Mb (2 chunks) [NOTE: the system had 1.5Gb memory at that time. Memory was removed, reseated, swapped, etc., now 1Gb] chunk 0:1Mb (159 pages) CORRECTIONS ATTEMPTED Somewhere during this ordeal, a Google search revealed a number of other people experiencing the "Sleeping thread" problem. One of these was apparently experienced in a FreeBSD 6.x development version stress test. No definitive solution was identified in anything we say, except a single reference to the problem being a kernel bug fixed in FreeBSD 6.2. Accordingly, we upgraded from 6.1 to 6.2 but have still experienced the problem. We reviewed the 'messages' file and found references to several things which led us to check FreeBSD 6.2 ERRATA (http://www.freebsd.org/releases/6.2R/errata.html). This suggested adding 'kern.ipc.nmbclusters="0"' to the /boot/loader.conf file which might avoid a known issue. We tried this, but saw no relief. We also found a reference in the manual that suggested the issue might be a problem with the APIC in 6.x. This recommended adding 'hint.apic.0.disabled="1"' to loader.conf. Tried this; no help. In order to try to get more information about the system dumps we added: dumpdev="AUTO" and dumpdir="/usr/crash" [to get more storage space than available in /var/] and have generated several vmcore.# files of ~1 Gb each (all identical size). We attempted to use DDB to analyze the dumps (struggling now, unfamiliar with kernel debugging process) with no success. Research suggested we needed to create a debug version of the kernel (i.e., KERNEL.DEBUG) with debugging options enabled. We duly copied GENERIC and edited it, noting that "options ddb" was already enabled. We added 'makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols' as suggested and tried to "make buildkernel" which errored out stating that KDB must be enabled to use DDB. We edited KERNEL.DEBUG to add 'options KDB # Enable kernel debugger' and attempted to "make buildkernel" again. This time, the process stopped again with the message: THIRD ERROR EVENT [snip] inline-unit-growth=100 --param rge-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror /usr/src/sys/crypto/sha2/sha2.c /usr/src/sys/crypto/sha2/sha2.c: In function `SHA512_Transform': /usr/src/sys/crypto/sha2/sha2.c:753: warning: 'T2' might be used uninitialized in this function *** Error code 1 Stop in /usr/obj/usr/src/sys/KERNEL.DEBUG. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. www:/usr/src# With this, we are stumped. HELP
FreeBSD 6.2 Repeating Crash - Sleeping thread; Fatal trap 12: page fault; warning: 'T2' might be used uninitialized
Please help if you can... BACKGROUND This crash is occurring on a dual-AMD 1.6Ghz cpu white-box system with 1 Gb ram, 250Gb storage running GENERIC kernel. The system has been in production use as a web server for nearly five years. About 3 - 4 months ago, the system was upgraded from an earlier FreeBSD version to 6.1. At the same time, all supporting applications (Apache webserver, PERL, PostgreSQL, PHP, countless other applications & libraries) were upgraded to the current releases. The system was stable up until a couple of weeks ago. FIRST ERROR EVENT The system crashed during normal usage. The following message was displayed on the console which was not responsive to keyboard input: Sleeping thread (tid 100122, pid 11099) owns a non-sleepable lock panic: sleeping thread cpuid=1 The system was restarted, an fsck routine was completed (answering "yes" to all the "Do you want to salvage" type questions) and the server ran fine. For about a week. It then crashed again several times, at intervals varying from a few minutes of uptime to a few days. SECOND ERROR EVENT After some crashes, a message similar to that above was displayed. However, at other times a message similar to this was displayed: kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid=0; apic id=01 fault virtual address =0x100 fault code =supervisor read, page not present instruction pointer =0x20:0xc066c731 stack pointer =0x28:0xe432ebf0 framepointer =0x28:0xe432ebfc code segment =base 0x0, limit0xf, type 0x1b =DPL 0, pres 1, def32 1, gran1 processor eflags =resume, IOPL=0 current process =36 (syncer) trap number = 12 panic: page fault cpuid=0 uptime: 3d10h11m44s Dumping 1535 Mb (2 chunks) [NOTE: the system had 1.5Gb memory at that time. Memory was removed, reseated, swapped, etc., now 1Gb] chunk 0:1Mb (159 pages) CORRECTIONS ATTEMPTED Somewhere during this ordeal, a Google search revealed a number of other people experiencing the "Sleeping thread" problem. One of these was apparently experienced in a FreeBSD 6.x development version stress test. No definitive solution was identified in anything we say, except a single reference to the problem being a kernel bug fixed in FreeBSD 6.2. Accordingly, we upgraded from 6.1 to 6.2 but have still experienced the problem. We reviewed the 'messages' file and found references to several things which led us to check FreeBSD 6.2 ERRATA (http://www.freebsd.org/releases/6.2R/errata.html). This suggested adding 'kern.ipc.nmbclusters="0"' to the /boot/loader.conf file which might avoid a known issue. We tried this, but saw no relief. We also found a reference in the manual that suggested the issue might be a problem with the APIC in 6.x. This recommended adding 'hint.apic.0.disabled="1"' to loader.conf. Tried this; no help. In order to try to get more information about the system dumps we added: dumpdev="AUTO" and dumpdir="/usr/crash" [to get more storage space than available in /var/] and have generated several vmcore.# files of ~1 Gb each (all identical size). We attempted to use DDB to analyze the dumps (struggling now, unfamiliar with kernel debugging process) with no success. Research suggested we needed to create a debug version of the kernel (i.e., KERNEL.DEBUG) with debugging options enabled. We duly copied GENERIC and edited it, noting that "options ddb" was already enabled. We added 'makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols' as suggested and tried to "make buildkernel" which errored out stating that KDB must be enabled to use DDB. We edited KERNEL.DEBUG to add 'options KDB # Enable kernel debugger' and attempted to "make buildkernel" again. This time, the process stopped again with the message: THIRD ERROR EVENT [snip] inline-unit-growth=100 --param arge-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror /usr/src/sys/crypto/sha2/sha2.c /usr/src/sys/crypto/sha2/sha2.c: In function `SHA512_Transform': /usr/src/sys/crypto/sha2/sha2.c:753: warning: 'T2' might be used uninitialized in this function *** Error code 1 Stop in /usr/obj/usr/src/sys/KERNEL.DEBUG. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. www:/usr/src# With this, we are stumped. HELP PLEASE! Can anyone: - lead us to a solution based on these error messages? - help us understand why the GENERIC kernel with only the debugging options added failed to make? - help us understand what '/usr/src/crypto/sha2/sha2.c
Re: fatal trap 12, can't get core
On Thursday 04 January 2007 21:47, christopher floess wrote: > Hi, I'm running 5.4 with a modified GENERIC kernel, and I recently > rebooted my system to find out that it hangs on probing ad1 with a > fatal trap 12. > > Here's the entire error message > > ad1 Timeout - Read_dma retrying (2 retries left) LBA 117231345 > kernel trap 12 with interrupts disabled > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x6c > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc063fb59 > > stack pointer = 0x10:0xde0fac40 > frame pointer= 0x10:0xde0fac44 > code segment= base 0x0, limit 0xf, type ox1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = resume, IOPL = 0 > current process= 6(thread taskq) > trap number = 12 > panic: page fault > cannot dump. no dump device > > In my rc.conf I've got > > dumpdev="/dev/ad0s1b" > dumpdir="/usr/crash" > > For some reason it still says "no dump device". > Right now I'm able to boot my system into safe mode, but not single > user or normal. I > think I might not be able to get core dumps b/c my system doesn't > get far enough in the boot process, so I'm trying to follow the > directions here > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/advanced.html# >KERNEL-PANIC-TROUBLESHOOTING > > > but I'm not sure about this part of the instructions > > % nm -n /kernel.that.caused.the.panic | grep f0xx > > Do I need to replace "/kernel.that.caused.the.panic" with > /boot/kernel/kernel? If so, here' is the out put of > > > nm -n /boot/kernel/kernel | grep c063fb59 > > c063fb3c t init_turnstile0 > c063fb4c t turnstile_setowner > c063fb78 T turnstile_alloc > c063fbb0 T turnstile_free > c063fbc4 T turnstile_lookup > > Can someone help me out here? Am I going about it all wrong? Let me > know what other info might be needed. Thanks ~ Chris > Sounds a lot like you have a dead drive or controller to me. Have you tried running the drive manufacturer's diagnostics on it? -- Thanks, Josh Paetzel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
fatal trap 12, can't get core
Hi, I'm running 5.4 with a modified GENERIC kernel, and I recently rebooted my system to find out that it hangs on probing ad1 with a fatal trap 12. Here's the entire error message ad1 Timeout - Read_dma retrying (2 retries left) LBA 117231345 kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode fault virtual address = 0x6c fault code = supervisor read, page not present instruction pointer = 0x8:0xc063fb59 stack pointer = 0x10:0xde0fac40 frame pointer= 0x10:0xde0fac44 code segment= base 0x0, limit 0xf, type ox1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process= 6(thread taskq) trap number = 12 panic: page fault cannot dump. no dump device In my rc.conf I've got dumpdev="/dev/ad0s1b" dumpdir="/usr/crash" For some reason it still says "no dump device". Right now I'm able to boot my system into safe mode, but not single user or normal. I think I might not be able to get core dumps b/c my system doesn't get far enough in the boot process, so I'm trying to follow the directions here http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/advanced.html#KERNEL-PANIC-TROUBLESHOOTING but I'm not sure about this part of the instructions % nm -n /kernel.that.caused.the.panic | grep f0xx Do I need to replace "/kernel.that.caused.the.panic" with /boot/kernel/kernel? If so, here' is the out put of nm -n /boot/kernel/kernel | grep c063fb59 c063fb3c t init_turnstile0 c063fb4c t turnstile_setowner c063fb78 T turnstile_alloc c063fbb0 T turnstile_free c063fbc4 T turnstile_lookup Can someone help me out here? Am I going about it all wrong? Let me know what other info might be needed. Thanks ~ Chris -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Panic/Fatal trap 12 while installing 6.1-RELEASE
Never mind, turned out to be dodgy RAM. -- Juha ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Panic/Fatal trap 12 while installing 6.1-RELEASE
Trying to install 6.1 on a Gigabyte 8i955 Royale motherboard, with an Intel D840 and 2GB of RAM onboard. However, booting up from the 6.1 CD results in a locked up system and this on the screen: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x4 fault code = supervisor write, page not present instruction pointer = 0x20:0xc07b5e7d stack pointer = 0x28:0xc1020d44 frame pointer = 0x28:0xc1020d58 code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def 32 1, gran 1 processor eflags = interrupt enabled, resume IOPL = 0 current process = 0 () trap number = 12 panic: page fault uptime: 1s Not sure where to go from here, as system locks up solid. Booting with ACPI disabled and Safe Mode result in: vm_page_insert: page already inserted and system lockup. Verbose logging, and I get the exact same Fatal trap 12 as above. -- Juha ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
fatal trap 12 error
Hello I use FreeBSD6.0. The machine is be locked every week. it gives an error as below: I add to kernel multi cpu support. Also I haven't changed the kernel fatal trap 12: page default while in kernel mode cpuid=1 ; apic id = 00 fault code = supervisor write, page not present trap number = 12 panic : page default dumpin 1023MB (2 chunks) That 's a strange condition that I have also another machine which has been installed Freebsd6.0. That machine works well no problem. How can I get rid off this condition? Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
What does it cause that message "Fatal trap 12: page fault while in kernel mode" ?
Hello I use FreeBSD-release6.0. the server gives an error on display as below and be locked about every 10 days. Fatal trap 12: page fault while in kernel mode ... ... The server has 1 gbyte Ram, P3-550 Mhz, 2 CPU. SMP is active in kernel. What shall I do ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fatal trap 12 page fault in kernel mode
"rwarneford" <[EMAIL PROTECTED]> writes: > I am not having any success in installing FreeBSD 6.0 at all. When the > default install boot starts, it hangs at some point after identifying ad0 > and acd0. > > If I go to the boot loader prompt, set hint.acpi.0.disabled=1, or use safe > mode, install boot crashes very soon with the following output: > > > > > $PIR : BIOS IRQ 10 for 0.11INTA does not match link 0x63 irq 5 > > pci0 : on pcib0 > > > > > fatal trap 12 : page code fault while in kernel mode > > fault virtual address = 0xeba60 > > fault code = supervisor read, page not present > > instruction pointer = 0x20:0xc00eb961 > > frame pointer = 0x28:0xc10209e4 > > stack pointer = 0x28:0xc10209e4 > > code segment = base 0x0, limit 0xf, type 0x1b > > DPL 0, pres 1, def 321, gran 1 > > processor flags = interrupt enabled, resume, IOPL=0 > > current process = 0 (swapper) > > trap number = 12 > > > > Rob Have you tried 6.1 as well? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
fatal trap 12 page fault in kernel mode
I am not having any success in installing FreeBSD 6.0 at all. When the default install boot starts, it hangs at some point after identifying ad0 and acd0. If I go to the boot loader prompt, set hint.acpi.0.disabled=1, or use safe mode, install boot crashes very soon with the following output: $PIR : BIOS IRQ 10 for 0.11INTA does not match link 0x63 irq 5 pci0 : on pcib0 fatal trap 12 : page code fault while in kernel mode fault virtual address = 0xeba60 fault code = supervisor read, page not present instruction pointer = 0x20:0xc00eb961 frame pointer = 0x28:0xc10209e4 stack pointer = 0x28:0xc10209e4 code segment = base 0x0, limit 0xf, type 0x1b DPL 0, pres 1, def 321, gran 1 processor flags = interrupt enabled, resume, IOPL=0 current process = 0 (swapper) trap number = 12 Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fatal trap 12 in kernel mode
On Tue, Oct 25, 2005 at 02:18:10PM -0400, Dave wrote: > Hello, > I'm trying to do a 5.4-release install on an older box, it's an AT > motherboard, and i hope that's not my problem. I'm getting the below error > and would appreciate any help. Try disabling acpi, many older motherboards had broken acpi support (although if you're lucky there's an updated bios). Kris pgpn3PBtWKOOQ.pgp Description: PGP signature
fatal trap 12 in kernel mode
Hello, I'm trying to do a 5.4-release install on an older box, it's an AT motherboard, and i hope that's not my problem. I'm getting the below error and would appreciate any help. Thanks. Dave. Insert boot floppy and press Enter /acpi.ko text=0x414fc data=0x1dc4+0x112c syms=[0x4+0x7670+0x4+0x9d05] can't open '/boot/beastie.4th': inappropriate file type or format / Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/kernel]... Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.4-RELEASE #0: Sun May 8 10:21:06 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD-K6(tm) 3D processor (450.17-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x8800 real memory = 268435456 (256 MB) avail memory = 248946688 (237 MB) K6-family MTRR support enabled (2 registers) ACPI-0159: *** Error: AcpiLoadTables: Could not get RSDP, AE_NO_ACPI_TABLES ACPI-0213: *** Error: AcpiLoadTables: Could not load tables: AE_NO_ACPI_TABL ACPI-0213: *** Error: AcpiLoadTables: Could not load tables: AE_NO_ACPI_TABLES ACPI: table load failed: AE_NO_ACPI_TABLES npx0: on motherboard npx0: INT 16 interface cpu0 on motherboard pcib0: pcibus 0 on motherboard pir0: on motherboard pci0: on pcib0 agp0: mem 0xe000-0xe3ff at agp0: mem 0xe000-0xe3ff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xe000-0xe00f,0x376,0x170-0x177,0x atapci0: port 0xe000-0xe00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 rl0: port 0xe800-0xe8ff mem 0xe400-0xe4ff ir rl0: port 0xe800-0xe8ff mem 0xe400-0xe4ff irq 10 at device 17.0 on pci0 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:08:54:00:f3:3b ohci0: mem 0xe4001000-0xe4001fff irq 9 at device 1 ohci0: mem 0xe4001000-0xe4001fff irq 9 at device 18.0 on pci0 usb0: OHCI version 1.0 usb0: on ohci0 usb0: USB revision 1.0 uhub0: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xe4002000-0xe4002fff irq 9 at device 1 ohci1: mem 0xe4002000-0xe4002fff irq 9 at device 18.1 on pci0 usb1: OHCI version 1.0 usb1: on ohci1 usb1: USB revision 1.0 uhub1: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: at device 18.2 (no driver attached) orm0: at iomem 0xc-0xc7fff on isa0 pmtimer0 on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 fdc0: at port 0x3f0-0x3f5 irq 6 drq 2 on isa0 fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) Timecounter "TSC" frequency 450165168 Hz quality 800 Timecounters tick every 10.000 msec md0: Preloaded image 4423680 bytes at 0xc0a34270 ad0: 9541MB [19386/16/63] at ata0-master UDMA33 acd0: CDROM at ata1-slave PIO4 Fatal trap 12: page fault while in kernel mode fault virtual address = 0x1 fault code = supervisor write, page not present instruction pointer = 0x8:0xc04b4e34 stack pointer = 0x10:0xcbf37c5c frame pointer = 0x10:0xcbf37c64 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 4 (g_down) trap number = 12 panic: page fault Uptime: 3s Cannot dump. No dump device defined. Automatic reboot in 15 seconds - press a key on the console to abort kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor write, page not present instruction pointer = 0x8:0xc05ebbcd stack pointer = 0x10:0xcbf37a60 frame pointer = 0x10:0xcbf37a6c code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 0 current process = 4 (g_down) trap number = 12 panic: page fault Uptime: 5s Cannot dump. No dump device defined. Automatic reboot in
Re: Re[2]: 5.4 Installation Problems on Dell GX280 - Fatal trap 12
Thanks Stuart for reminding me of my alternative install options. I'll try installing over serial tomorrow. I've never had to install off anything but a CD, so it will be a good learning experience for me anyway. Now to just dig out that old 486 and track down a Null modem cable. . . . Daniel, I'm still a little stumped why you were able to install 5.4 on a GX280 without any problems. Maybe there is some slight variation in the Dell systems even though they are the same model #. Who knows? Or maybe a slight difference in our BIOS configs. At least there is a workaround - if not a very convient one. -John > > I've had a nightmare trying to get 5.4 (also tried 5.3) to work on a > > Dell GX280 - which had exactly the same problem. In the end, I ended up > > using a serial link to get the install done and then got inetd setup so > > that I could troubleshoot over the network. > > > This didn't help long term as the keyboard didn't work once I'd > > restarted after finishing the install. I stumbled on this script which > > seemed to do the trick: > > > http://lists.freebsd.org/pipermail/freebsd-questions/2003-October/022771 > > .html > > > I used telnet to get at rc.conf - but there probably are other better > > ways. > > > It seems a shame that Dell (and other manufacturers) are phasing out old > > 'legacy' hardware like the good ol' PS/2 ports. It's just a good job > > that they didn't kill the serial port on this particular machine! (yet) > > that sux, indeed :-( > > > Hope this helps, > > Stuart > > > > -Original Message- > > From: John Vaughan [mailto:[EMAIL PROTECTED] > > Sent: 21 June 2005 22:10 > > To: freebsd-questions@freebsd.org > > Subject: 5.4 Installation Problems on Dell GX280 - Fatal trap 12 > > > I am trying to install FreeBSD 5.4 on a Dell GX280 and am getting a > > Fatal trap 12 supervisor write, page not present error. From what > > I've read, this is an ACPI problem which I could disable if I had a > > PS2 port, but the GX280 doesn't have them. Has anyone gotten 5.4 to > > run properly on a GX280 using option 7 to boot with usb keyboard? > > > -John > > So long, I can say that I'm able to use gx280 on 5.4. I was able to > install it from CD with usb keyboard using option 7 - boot with usb > keyboard. No fatal trap 12. The only problem I had is that I wan't > able to use HTT. > > (but it was my fault I think :-) and since it is considered to be > harmful and it doesn't really boost up machine's performance, I'm > not solving it.) > > -- > Best Regards, > > DanGer, ICQ: 261701668 | e-mail protecting at: http://www.2pu.net/ > http://danger.rulez.sk | proxy list at:http://www.proxy-web.com/ > | FreeBSD - The Power to Serve! > > [ Fight Crime: Don't dial 911, shoot back!! ] > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re[2]: 5.4 Installation Problems on Dell GX280 - Fatal trap 12
Hello SHands, Wednesday, June 22, 2005, 12:37:57 AM, you thinks about: > I've had a nightmare trying to get 5.4 (also tried 5.3) to work on a > Dell GX280 - which had exactly the same problem. In the end, I ended up > using a serial link to get the install done and then got inetd setup so > that I could troubleshoot over the network. > This didn't help long term as the keyboard didn't work once I'd > restarted after finishing the install. I stumbled on this script which > seemed to do the trick: > http://lists.freebsd.org/pipermail/freebsd-questions/2003-October/022771 > .html > I used telnet to get at rc.conf - but there probably are other better > ways. > It seems a shame that Dell (and other manufacturers) are phasing out old > 'legacy' hardware like the good ol' PS/2 ports. It's just a good job > that they didn't kill the serial port on this particular machine! (yet) that sux, indeed :-( > Hope this helps, > Stuart > -Original Message- > From: John Vaughan [mailto:[EMAIL PROTECTED] > Sent: 21 June 2005 22:10 > To: freebsd-questions@freebsd.org > Subject: 5.4 Installation Problems on Dell GX280 - Fatal trap 12 > I am trying to install FreeBSD 5.4 on a Dell GX280 and am getting a > Fatal trap 12 supervisor write, page not present error. From what > I've read, this is an ACPI problem which I could disable if I had a > PS2 port, but the GX280 doesn't have them. Has anyone gotten 5.4 to > run properly on a GX280 using option 7 to boot with usb keyboard? > -John So long, I can say that I'm able to use gx280 on 5.4. I was able to install it from CD with usb keyboard using option 7 - boot with usb keyboard. No fatal trap 12. The only problem I had is that I wan't able to use HTT. (but it was my fault I think :-) and since it is considered to be harmful and it doesn't really boost up machine's performance, I'm not solving it.) -- Best Regards, DanGer, ICQ: 261701668 | e-mail protecting at: http://www.2pu.net/ http://danger.rulez.sk | proxy list at:http://www.proxy-web.com/ | FreeBSD - The Power to Serve! [ Fight Crime: Don't dial 911, shoot back!! ] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: 5.4 Installation Problems on Dell GX280 - Fatal trap 12
I've had a nightmare trying to get 5.4 (also tried 5.3) to work on a Dell GX280 - which had exactly the same problem. In the end, I ended up using a serial link to get the install done and then got inetd setup so that I could troubleshoot over the network. This didn't help long term as the keyboard didn't work once I'd restarted after finishing the install. I stumbled on this script which seemed to do the trick: http://lists.freebsd.org/pipermail/freebsd-questions/2003-October/022771 .html I used telnet to get at rc.conf - but there probably are other better ways. It seems a shame that Dell (and other manufacturers) are phasing out old 'legacy' hardware like the good ol' PS/2 ports. It's just a good job that they didn't kill the serial port on this particular machine! (yet) Hope this helps, Stuart -Original Message- From: John Vaughan [mailto:[EMAIL PROTECTED] Sent: 21 June 2005 22:10 To: freebsd-questions@freebsd.org Subject: 5.4 Installation Problems on Dell GX280 - Fatal trap 12 I am trying to install FreeBSD 5.4 on a Dell GX280 and am getting a Fatal trap 12 supervisor write, page not present error. From what I've read, this is an ACPI problem which I could disable if I had a PS2 port, but the GX280 doesn't have them. Has anyone gotten 5.4 to run properly on a GX280 using option 7 to boot with usb keyboard? -John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
5.4 Installation Problems on Dell GX280 - Fatal trap 12
I am trying to install FreeBSD 5.4 on a Dell GX280 and am getting a Fatal trap 12 supervisor write, page not present error. From what I've read, this is an ACPI problem which I could disable if I had a PS2 port, but the GX280 doesn't have them. Has anyone gotten 5.4 to run properly on a GX280 using option 7 to boot with usb keyboard? -John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fatal trap 12
On 4 May 2005 at 9:35, Lowell Gilbert wrote: > "Dan Langille" <[EMAIL PROTECTED]> writes: > > > Hi folks. My gateway has been getting this a few times a day for the > > past few days. > > > > Fatal trap 12: page fault while in kernel mode > > > > More detail at http://www.langille.org/tmp/fatal-trap-12.txt > > > > Conversations to date indicate a hardware problem. Any > > recommendations/suggestions? > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#TRAP-12-PANIC Well is this interesting... Another fatal trap 12. On new hardware. The HDD is the only item left over from the old box. I think I'll cvsup and build world to get up to the latest stable from FreeBSD 4.11-STABLE (BAST) #5: Sun Mar 13 06:49:51 EST 2005 -- Dan Langille : http://www.langille.org/ BSDCan - The Technical BSD Conference - http://www.bsdcan.org/ NEW brochure available at http://www.bsdcan.org/2005/advocacy/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fatal trap 12
On 4 May 2005 at 9:35, Lowell Gilbert wrote: > "Dan Langille" <[EMAIL PROTECTED]> writes: > > > Hi folks. My gateway has been getting this a few times a day for the > > past few days. > > > > Fatal trap 12: page fault while in kernel mode > > > > More detail at http://www.langille.org/tmp/fatal-trap-12.txt > > > > Conversations to date indicate a hardware problem. Any > > recommendations/suggestions? > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#TRAP-12-PANIC FYI, the HDD was transferred into a new computer today. It's been running for just under 24 hours. No problems. So at least we know it wasn't the drive... ;) The old machine is still around. If I get eager, I'll try debugging the issue. thanks -- Dan Langille : http://www.langille.org/ BSDCan - The Technical BSD Conference - http://www.bsdcan.org/ NEW brochure available at http://www.bsdcan.org/2005/advocacy/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fatal trap 12
On 4 May 2005 at 9:35, Lowell Gilbert wrote: > "Dan Langille" <[EMAIL PROTECTED]> writes: > > > Hi folks. My gateway has been getting this a few times a day for the > > past few days. > > > > Fatal trap 12: page fault while in kernel mode > > > > More detail at http://www.langille.org/tmp/fatal-trap-12.txt > > > > Conversations to date indicate a hardware problem. Any > > recommendations/suggestions? > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#TRAP-12-PANIC Thanks! Perhaps after BSDCan I can get time to do this. cheers -- Dan Langille : http://www.langille.org/ BSDCan - The Technical BSD Conference - http://www.bsdcan.org/ NEW brochure available at http://www.bsdcan.org/2005/advocacy/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fatal trap 12
"Dan Langille" <[EMAIL PROTECTED]> writes: > Hi folks. My gateway has been getting this a few times a day for the > past few days. > > Fatal trap 12: page fault while in kernel mode > > More detail at http://www.langille.org/tmp/fatal-trap-12.txt > > Conversations to date indicate a hardware problem. Any > recommendations/suggestions? http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#TRAP-12-PANIC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
fatal trap 12
Hi folks. My gateway has been getting this a few times a day for the past few days. Fatal trap 12: page fault while in kernel mode More detail at http://www.langille.org/tmp/fatal-trap-12.txt Conversations to date indicate a hardware problem. Any recommendations/suggestions? -- Dan Langille : http://www.langille.org/ BSDCan - The Technical BSD Conference - http://www.bsdcan.org/ NEW brochure available at http://www.bsdcan.org/2005/advocacy/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Installing FreeBSD -> Fatal trap 12
nicholaserho wrote: Hello, I am trying to install FreeBSD from floppies on a 486-DX-33, and with the three floppies I made I cant get to the boot menu screen (with the devil) but if I attempt to boot I get a "Fatal trap 12: page fault while in kernal mode" error. The same error happens if I try safe mode except my system restart. What can I do to fix this so I can install FreeBSD? Exact Error Message: -------- Fatal Trap 12: page fault while in kernal mode fault virtual address = 0x409b341b falut code = supervisor read, page not present instuction pointer = 0x8:0xc066c17d stack pointer = 0x10:0xc1021c10 frame pointer = 0x10:0xc1021c10 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 0 current process = 0 () trap number = 12 panic: page fault Uptime: 1s - Any advice that you could give me would be welcome. Thank you for your time. 1. Do you have more than 16 MB system RAM? You need more than 16 to install versions of FreeBSD higher than 5.2.1. 2. Try diabling "PNPBIOS" type options in the system's BIOS setup tool. 3. Make another set of floppies on new diskettes. 4. Check the hardware compatibility list at www.freebsd.org against the components in your system. Hope one of these does some good. Kevin Kinsey ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Installing FreeBSD -> Fatal trap 12
Hello, I am trying to install FreeBSD from floppies on a 486-DX-33, and with the three floppies I made I cant get to the boot menu screen (with the devil) but if I attempt to boot I get a "Fatal trap 12: page fault while in kernal mode" error. The same error happens if I try safe mode except my system restart. What can I do to fix this so I can install FreeBSD? Exact Error Message: -------- Fatal Trap 12: page fault while in kernal mode fault virtual address = 0x409b341b falut code = supervisor read, page not present instuction pointer = 0x8:0xc066c17d stack pointer = 0x10:0xc1021c10 frame pointer = 0x10:0xc1021c10 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 0 current process = 0 () trap number = 12 panic: page fault Uptime: 1s - Any advice that you could give me would be welcome. Thank you for your time. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
"Fatal trap 12" 0xeb902 SIS630 Chipset
Ref : http://lists.freebsd.org/pipermail/freebsd-questions/2004-May/046387.html I am still having this problem in FreeBSD 5.2.1 with an SIS630 Chipset The "set hw.pcic.intr_path" and "set hw.pcic.irq" commands worked in versions 4.x Does anyone know the equivalent commands for 5.x Thanks in advance. Colman. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fatal Trap 12 while booting up?
In message <[EMAIL PROTECTED]>, Andy Holyer write s: >unknown: can't assign resources (port) >Timecounters tick every 10.000 msec > > >Fatal Trap 12: page fault while in kernel mode > >And then tries to reboot. Over and over again. I seem to recall there >was a known fix for this behaviour... I have an HP DVD burner that will make a FreeBSD 5.2.1 or 5.3 beta 7 system do this fairly reliably if there's not a slave drive on the chain with it. YMMV. -s ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Fatal Trap 12 while booting up?
A colleague "helped" me by powering-down my FreeBSD 5.1-RELEASE server. This box doesn't boot with ACPI enabled (I think the hardware's too old), but now it goes through a bunch of devices and then comes up with: unknown: can't assign resources (port) Timecounters tick every 10.000 msec Fatal Trap 12: page fault while in kernel mode And then tries to reboot. Over and over again. I seem to recall there was a known fix for this behaviour... Thanks in advance for any advice. --- Andy Holyer, Systems Administrator Hedgehog Broadband, 11 Marlborough Place Brighton BN1 1UB 08451 260895 x 241 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Fatal Trap 12: page fault while in kernel mode
Attempting to do hardware upgrades. alas, since I dropped in a new motherboard / processor combo, I get (hand transposed): Fatal trap 12: page fault while in kernel mode fault virtual address = 0x5e fault code = supervisor write, page no present instruction pointer = 0x8:0xc062d6e1 stack pointer = 0x10:0xe0f03b7c frame pointer = 0x10:0xe0f03b7c code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 45 (syncer) trap number = 12 panic: page fault this is not a debug kernel. In fact, this latest one occurred while I was attempting to build said debug kernel. Single user mode, 5.x as of right around 5.3-BETA2 tag, may have been close to 5.3-BETA3. Any more info I can provide, gonna keep attempting to build the debug kernel, hope that one of these attempts it will finish before the panic (seems to be happening withing 15min of boot) I'm just totally dead in the water at this point.. ideas please? thanks ~j -- Jonathan T. Sage Theatrical Lighting / Set Designer Professional Web Design "He said he likes me, but he's not in-like with me."- Connie, King of the Hill [HTTP://www.JTSage.com] [HTTP://design.JTSage.com] [EMAIL PROTECTED] [See Headers for Contact Info] signature.asc Description: OpenPGP digital signature
Re: Installation 4-10 Stable - Fatal Trap 12
On Mon, Jul 12, 2004 at 07:34:19PM +0100, Kenneth Christie wrote: > I cannot get past the attached message when trying to install Free BSD 4.10 stable. > Can you give me an indication as to what the problem might be ? (I am totally new to > Unix, and was wanting to install Free BSD to learn about it. I have searched the > FAQs but without coming across a similar message, although one did suggest disabling > ACPI during the installation. How would I do this if this is what I need to do ?). Please enhance your karma by hitting the return key every 72 or so characters. Sorry -- you attachment was eaten by the attachment eater. Only certain MIME types are permitted on the FreeBSD mailing lists. However I can say confidently that trying to disable ACPI on a 4.10 install won't work. There isn't any ACPI support turned on by default in 4.x: all of the advice about turning off ACPI applies to 5.x, and in that case, the installation procedure is a bit different and gives you that choice fairly early on. Fatal Trap 12 means "non-existent system call invoked". Seeing it while attempting to boot a kernel either means that the kernel is broken, or that you have hardware problems. In the first instance, you could have a corrupt kernel image on your installation media. If you're trying to install from floppy disks, throw away any disks you've been using and try again with some nice new fresh from the manufacturer floppies. Otherwise, if you're using one of the .iso images, try checking the md5 checksum to make sure everything came down OK. Knowing as little about Windows as I do, I have no reliable idea about how to do that. However a little googling pulled up this page, which looks like just the ticket: http://www.fastsum.com/ If on the other hand, it's a hardware problem then you'll have to work out if your system is faulty. That's something you tend to learn how to deal with through experience and not something easily described in a simple e-mail like this. Of course, it could be that you have hardware which simply isn't supported under FreeBSD 4.10 -- most of the time FreeBSD will simply igore kit it doesn't know how to drive, but if it's something important like the disk controller all bets are off. Try comparing your system against the lists of devices in the 4.10 Hardware Notes: http://www.freebsd.org/releases/4.10R/hardware-i386.html Also search the FreeBSD mailing lists for other mentions of your particular brand of system (or of the motherboard in your system) -- some makes have specific settings that need to be in the BIOS before they will work with FreeBSD. A good interface for searching FreeBSD mailing lists is available at: http://freebsd.rambler.ru/ Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgpo6dEg9Ryj8.pgp Description: PGP signature
Installation 4-10 Stable - Fatal Trap 12
I cannot get past the attached message when trying to install Free BSD 4.10 stable. Can you give me an indication as to what the problem might be ? (I am totally new to Unix, and was wanting to install Free BSD to learn about it. I have searched the FAQs but without coming across a similar message, although one did suggest disabling ACPI during the installation. How would I do this if this is what I need to do ?).___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Fatal trap 12: page fault while in kernel mode
I recently installed freebsd 5.2.1, which seemed to go well. But lately my system has been locking up and rebooting. I have included the error that is displayed each time my system locks. Jun 29 20:37:09 candice syslogd: kernel boot file is /boot/kernel/kernel Jun 29 20:37:09 candice kernel: Jun 29 20:37:09 candice kernel: Jun 29 20:37:09 candice kernel: Fatal trap 12: page fault while in kernel mode Jun 29 20:37:09 candice kernel: cpuid = 0; apic id = 00 Jun 29 20:37:09 candice kernel: fault virtual address = 0xc5f12321 Jun 29 20:37:09 candice kernel: fault code = supervisor read, page not present Jun 29 20:37:09 candice kernel: instruction pointer = 0x8:0xc0694770 Jun 29 20:37:09 candice kernel: stack pointer = 0x10:0xddd77a1c Jun 29 20:37:09 candice kernel: frame pointer = 0x10:0xddd77a28 Jun 29 20:37:09 candice kernel: code segment = base 0x0, limit 0xf, type 0x1b Jun 29 20:37:09 candice kernel: = DPL 0, pres 1, def32 1, gran 1 Jun 29 20:37:09 candice kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Jun 29 20:37:09 candice kernel: current process = 21866 (devinfo) Jun 29 20:37:09 candice kernel: trap number = 12 Jun 29 20:37:09 candice kernel: panic: page fault Jun 29 20:37:09 candice kernel: cpuid = 0; Jun 29 20:37:09 candice kernel: Jun 29 20:37:09 candice kernel: syncing disks, buffers remaining... 3428 3428 3427 3427 3427 3427 3427 3427 3427 3427 3427 3427 3427 3427 3427 3427 3427 342 7 3427 3427 3427 3427 Does anyone have an idea why this is happening? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fatal trap 12: page fault while in kernel mode
On Wed, Jun 23, 2004 at 09:52:48PM -0400, fred wrote: > Hi, > > > > Recently my freebsd machine always dead, and the below error messages are gotten > when reboot the machin, could anyone help me? Start by updating to a modern release; there have been literally thousands of bugs fixed since 5.0-DP1. > FreeBSD 5.0-DP1 FreeBSD 5.0-DP1 #0: Wed Aug 27 07:07:21 CST 2003 root@:/usr/src/sys/i386/compile/PEARL i386 In general, you need to provide more information than this when you run into a kernel panic. See the chapter on kernel debugging in the developer's handbook for full details. Kris P.S. Please wrap your lines at 70 characters so your emails may be easily read. pgpFYqMDIzhXD.pgp Description: PGP signature
Fatal trap 12: page fault while in kernel mode
Hi, Recently my freebsd machine always dead, and the below error messages are gotten when reboot the machin, could anyone help me? Jun 24 09:09:02 pearl kernel: Fatal trap 12: page fault while in kernel mode Jun 24 09:09:02 pearl kernel: fault virtual address = 0xe852eba9 Jun 24 09:09:02 pearl kernel: fault code= supervisor read, page not present Jun 24 09:09:02 pearl kernel: instruction pointer = 0x8:0xc028dd4c Jun 24 09:09:02 pearl kernel: stack pointer = 0x10:0xda7f0b20 Jun 24 09:09:02 pearl kernel: frame pointer = 0x10:0xda7f0b3c Jun 24 09:09:02 pearl kernel: code segment = base 0x0, limit 0xf, type 0x1b Jun 24 09:09:02 pearl kernel: = DPL 0, pres 1, def32 1, gran 1 Jun 24 09:09:02 pearl kernel: processor eflags = interrupt enabled, resume, IOPL = 0 The configuration of my machine is: FreeBSD 5.0-DP1 FreeBSD 5.0-DP1 #0: Wed Aug 27 07:07:21 CST 2003 root@:/usr/src/sys/i386/compile/PEARL i386 Thanks, Fred Zhang ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fatal trap 12
On Mon, Apr 05, 2004 at 06:24:12PM -0700, [EMAIL PROTECTED] wrote: > Were installing 5.2 from discs we purchased from BSD > Mall. The system starts to load, The daeman page shows > up with the boot options. What ever we pick it ends up > showing the Error message: Fatal trap 12: page fault > while in Kernel mode. > any suggestions? See: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/troubleshoot.html#SIGNAL11 Yes -- I know that your system died with Signal 12 and that question is talking about Signal 11, but it is applicable. Suspect your hardware first. Do what you can to rule out hardware problems before you do anything else. You might want to try booting the install media in the 'No ACPI' mode. If you're trying to install on a multi-processor nForce2 board, you might need to disable apic and smp as well -- see http://lists.freebsd.org/pipermail/freebsd-current/2004-March/024070.html What ever you do, aim to upgrade to 5.2.1-RELEASE-pN as soon as possible: 5.2 had some nasty bugs, which is why 5.2.1 was released. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
fatal trap 12
Were installing 5.2 from discs we purchased from BSD Mall. The system starts to load, The daeman page shows up with the boot options. What ever we pick it ends up showing the Error message: Fatal trap 12: page fault while in Kernel mode. any suggestions? thanx ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Fatal trap 12: page fault while in kernel mode HELP ?!?
I have a fresh install if FBSD 4.9 rc2 with bge0 Netgear 302T( gigabit ethernet interface) the machine runs fine when left alone...however whenever i try to do large file transfers across my LAN to the BSD box ..i get an error like: "Fatal trap 12: page fault while in kernel mode" this seems to only happen when trasnferring files across the LAN to the machine ..anyone have any thoughts any help is greatly appreciated -- Brent Bailey -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fatal trap 12
On Tue, Mar 02, 2004 at 02:06:25PM +, Matthew Seaman wrote: > On Mon, Mar 01, 2004 at 01:11:49PM -0300, Marco wrote: > > Hello, my name is Marco Giardini. My problem is the following one: When the > > operating system initiates leaves mensage to me error that makes me > > reinitiate the maquina. mensage that leaves is fatal trap 12. > > http://www.freebsd.org/doc/es_ES.ISO8859-1/books/faq/troubleshoot.html#Q4.9. > > Fatal trap 12 happens for much the same reasons as Signal 11. > > Try running this to see if you can confirm hardware errors. Oops. I meant to add: http://www.memtest86.com/ Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
Re: fatal trap 12
On Mon, Mar 01, 2004 at 01:11:49PM -0300, Marco wrote: > Hello, my name is Marco Giardini. My problem is the following one: When the > operating system initiates leaves mensage to me error that makes me > reinitiate the maquina. mensage that leaves is fatal trap 12. http://www.freebsd.org/doc/es_ES.ISO8859-1/books/faq/troubleshoot.html#Q4.9. Fatal trap 12 happens for much the same reasons as Signal 11. Try running this to see if you can confirm hardware errors. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
fatal trap 12
Hello, my name is Marco Giardini. My problem is the following one: When the operating system initiates leaves mensage to me error that makes me reinitiate the maquina. mensage that leaves is fatal trap 12. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fatal trap 12
Daren Desjardins wrote: Over the weekend my bsd 4.9 apparantly rebooted for kicks by itself, reporting a fatal trap 12 in messages. I looked through the list history and found some posts indicating it may be a memory issue. If you suspect a memory problem, then try getting your BIOS to find it. Reboot your machine then press whatever key you need to get into your BIOS. Look for an option which turns on extended memory checking on boot (or which turns off quick memory checking), turn on extended check, save the setting, reboot and watch the BIOS cycle through endless memory checks. If it finds a problem it'll tell you. If it does, then you'll have to try removing memory chips one-by-one to try to find the one at fault. (Note that motherboards often (always?) require the memory chips to be inserted sequentially. I.e. if you take out the first chip, you have to move all the others up -- you can't just leave the first slot empty). Make sure to use some kind of anti-static protection when handling memory chips, otherwise you really will have a memory problem. --Alex ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Fatal trap 12
Over the weekend my bsd 4.9 apparantly rebooted for kicks by itself, reporting a fatal trap 12 in messages. I looked through the list history and found some posts indicating it may be a memory issue. Im hoping someone can confirm/deny this for me so I know how to start tracking this down. The machine had an uptime of over 20days prior to reboot, it happened at 3am which is shortly after the daily cronjob is suppose to run. I never recieved my daily report that night either. Jan 16 15:28:24 lithium /kernel: pid 97521 (mysqlcc), uid 1000: exited on signal 11 (core dumped) Jan 17 03:06:06 lithium /kernel: Jan 17 03:06:06 lithium /kernel: Jan 17 03:06:06 lithium /kernel: Fatal trap 12: page fault while in kernel mode Jan 17 03:06:06 lithium /kernel: fault virtual address = 0x24 Jan 17 03:06:06 lithium /kernel: fault code = supervisor read, page not present Jan 17 03:06:06 lithium /kernel: instruction pointer= 0x8:0xc029b52b Jan 17 03:06:06 lithium /kernel: stack pointer = 0x10:0xe29ccf14 Jan 17 03:06:06 lithium /kernel: frame pointer = 0x10:0xe29ccf84 Jan 17 03:06:06 lithium /kernel: code segment = base 0x0, limit 0xf, type 0x1b Jan 17 03:06:06 lithium /kernel: = DPL 0, pres 1, def32 1, gran 1 Jan 17 03:06:06 lithium /kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Jan 17 03:06:06 lithium /kernel: current process= 3 (pagedaemon) Jan 17 03:06:06 lithium /kernel: interrupt mask = none Jan 17 03:06:06 lithium /kernel: trap number= 12 Jan 17 03:06:06 lithium /kernel: panic: page fault Jan 17 03:06:06 lithium /kernel: Jan 17 03:06:06 lithium /kernel: syncing disks... 62 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Jan 17 03:06:06 lithium /kernel: Copyright (c) 1992-2003 The FreeBSD Project. Jan 17 03:06:06 lithium /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Jan 17 03:06:06 lithium /kernel: The Regents of the University of California. All rights reserved. Jan 17 03:06:06 lithium /kernel: FreeBSD 4.9-RELEASE #0: Thu Dec 18 16:38:31 EST 2003 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Installation problems-Fatal trap 12 error
On Tue, Nov 18, 2003 at 07:16:29AM -0800, Craig Caughlin wrote: > I'm brand new to FreeBSD (but I've worked with Unix and Linux a little). I'm > trying to install FreeBSD, but I constantly get this Fatal Trap 12: page > fault while in kernel mode error. I don't know where to begin to try and > solve this so I can proceed with my install. Suggestions??? Thank you. > > My computer is a Dell 600SC Poweredge Server, Promise Ultra disk controller, > Primary HD: WD 160 GB, Secondary HD Hitachi 40Gb, 512 Mb RAM. That's fairly often a sign of hardware problems. Does the system run correctly under other OSes? Can you run a few cycles of memtest86 (http://www.memtest86.com/) without any errors coming up? There is also: http://lists.freebsd.org/pipermail/freebsd-hackers/2003-July/002101.html http://lists.freebsd.org/pipermail/freebsd-current/2003-April/000621.html and the audit trail in: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern%2F54549 Looks like several people are having similar problems... You don't say which version of FreeBSD you're trying to install. If you're a beginner with FreeBSD, then I'd strongly advise you to start by installing 4.9-RELEASE -- remember that the 5.x versions are still "New Technology" releases and not yet suitable for production use. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
Installation problems-Fatal trap 12 error
Hi folks, I'm brand new to FreeBSD (but I've worked with Unix and Linux a little). I'm trying to install FreeBSD, but I constantly get this Fatal Trap 12: page fault while in kernel mode error. I don't know where to begin to try and solve this so I can proceed with my install. Suggestions??? Thank you. My computer is a Dell 600SC Poweredge Server, Promise Ultra disk controller, Primary HD: WD 160 GB, Secondary HD Hitachi 40Gb, 512 Mb RAM. Thank you, Craig ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fatal trap 12: page trap while in kernel mode
Hi! I had this issue not long ago and it turned out to be a hardware issue. The memory was bad. I was able to recreate this by running some command like: find / -name file_that_doesnt_exist -print (just so that it will go thru the whole FS). It would puke almost instantly. We replaced the memory and it never happened again. hope this helps -pranav *** Pranav A. Desai On Fri, 7 Nov 2003, Chris Hastie wrote: > I have a nasty feeling that this may be a hardware problem rather than > FreeBSD, but any pointers appreciated. > > Over the last couple of days, with no changes in configuration, one of > my boxes has started to die with increasing frequency, throwing up > errors like this: > > Fatal trap 12: Page trap while in kernel mode > Fault virtual address = 0x2c2 > fault code = supervisor writ, page not present > instruction pointer = 0x8:0xc0272faf > stack pointer = 0x10:0xd54e8cf4 > frame pointer = 0x10:0xd54e8d0c > code segment= bas 0x0, limit 0xff, type 0x1b > = DPL0, pres1, def 32 1, gran1 > processor eflags= interrupt enabled, resume, IOPL = 0 > current process = 15 (random) > trap number = 12 > panic: page fault > syncing disks, buffers remaining... panic: free locked buf > Terminate ACPI > > Although it announces that it is about to reboot, it just goes to a > blank console in which even the reset button has no effect (actually it > does cause the HDD LED to flicker for a few seconds). > > Increasingly, cycling the power goes to the same foreboding blank > monitor without even a murmur from the BIOS, let alone an attempt to > boot FreeBSD. > > All the hardware is around two months old - an MSI KM2M motherboard with > AMD Athlon 2200, 512MB RAM and 2 x 60 GB HDD in software RAID 1 using > Vinum. FreeBSD is 5.1 RELEASE. > -- > Chris Hastie > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Fatal trap 12: page trap while in kernel mode
I have a nasty feeling that this may be a hardware problem rather than FreeBSD, but any pointers appreciated. Over the last couple of days, with no changes in configuration, one of my boxes has started to die with increasing frequency, throwing up errors like this: Fatal trap 12: Page trap while in kernel mode Fault virtual address = 0x2c2 fault code = supervisor writ, page not present instruction pointer = 0x8:0xc0272faf stack pointer = 0x10:0xd54e8cf4 frame pointer = 0x10:0xd54e8d0c code segment= bas 0x0, limit 0xff, type 0x1b = DPL0, pres1, def 32 1, gran1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 15 (random) trap number = 12 panic: page fault syncing disks, buffers remaining... panic: free locked buf Terminate ACPI Although it announces that it is about to reboot, it just goes to a blank console in which even the reset button has no effect (actually it does cause the HDD LED to flicker for a few seconds). Increasingly, cycling the power goes to the same foreboding blank monitor without even a murmur from the BIOS, let alone an attempt to boot FreeBSD. All the hardware is around two months old - an MSI KM2M motherboard with AMD Athlon 2200, 512MB RAM and 2 x 60 GB HDD in software RAID 1 using Vinum. FreeBSD is 5.1 RELEASE. -- Chris Hastie ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fatal trap 12
I briefly tried RELENG_4 back when it was 4.9 RC1, and was getting hard locks when I exited X. Unfortunately, at the time I didn't really have time to troubleshoot it, so I rolled back to 4.8, which was only giving me Sig 11's when exiting KDE apps like konsole & knode. :) Perhaps this weekend, I'll try cvsuping back to -STABLE and see if that helps. On that subject, has anyone seen any issue with -STABLE where it just goes to a black screen on exiting X? As I recall, my nvidia driver also wrote an error in the X log along the lines of "Unable to destroy surface" or something similar. chris --- Mike Tancsa <[EMAIL PROTECTED]> wrote: > > There are a few VM fixes that have gone into RELENG_4, thats where your > kernel is really panicing. If its an option for you, I would try > RELENG_4 > rather than the security branch. > > ---Mike > > At 09:48 AM 16/10/2003, Chris Readle wrote: > >Got another one this morning. This time the only thing running was the > >make index && make readmes, and XFree86. > > > >Actually, they both may have finished by then, I started them up then > had > >to go to sleep, so I'm not entirely sure how far along it got in the > >process. I do know it was past the index and working on the readmes, > >though. > > > >/var/log/messages: > >Oct 16 01:26:37 creadle /kernel: Fatal trap 12: page fault while in > kernel > >mode > >Oct 16 01:26:37 creadle /kernel: fault virtual address = 0xfd9b > >Oct 16 01:26:37 creadle /kernel: fault code = supervisor > read, > >page not present > >Oct 16 01:26:37 creadle /kernel: instruction pointer= > 0x8:0xc022c1c8 > >Oct 16 01:26:37 creadle /kernel: stack pointer = > 0x10:0xd2e2ee4c > >Oct 16 01:26:37 creadle /kernel: frame pointer = > 0x10:0xd2e2ee54 > >Oct 16 01:26:37 creadle /kernel: code segment = base 0x0, > limit > >0xf, type 0x1b > >Oct 16 01:26:37 creadle /kernel: = DPL 0, pres 1, def32 1, gran 1 > >Oct 16 01:26:37 creadle /kernel: processor eflags = interrupt > >enabled, resume, IOPL = 0 > >Oct 16 01:26:37 creadle /kernel: current process= 53504 > >(sh) > >Oct 16 01:26:37 creadle /kernel: interrupt mask = none > >Oct 16 01:26:37 creadle /kernel: trap number= 12 > >Oct 16 01:26:37 creadle /kernel: panic: page fault > >Oct 16 01:26:37 creadle /kernel: > > > >nm -n: > >[EMAIL PROTECTED] chris]$ nm -n /kernel | grep c022c1c8 > >[EMAIL PROTECTED] chris]$ nm -n /kernel | grep c022c1c > >[EMAIL PROTECTED] chris]$ nm -n /kernel | grep c022c1 > >c022c19c T vm_page_lookup > >c022c1f8 T vm_page_rename > > > >chris > > > >--- Chris Readle <[EMAIL PROTECTED]> wrote: > > > Hi all, > > > > > > New to FBSD, and in the process of moving my Linux/Windows PC to > > > FBSD/Windows. > > > > > > I got two spontaneous reboots last night (the first times it > happened) > > > and > > > I got fatal trap 12s in /var/log/messages each time. I wasn't doing > > > anything too heavy, just a make index && make readmes on my ports, > > > listening to some music through XMMS and browsing the web via > Mozilla. > > > > > > I searched the archives and the FAQ. I haven't built a debugging > kernel > > > yet, but I thought I would post the info I have in the hopes that > > > someone > > > might be able to help. > > > > > > I did do an nm - n on the kernel, however. > > > > > > uname -a: > > > FreeBSD creadle.oc.cox.net 4.8-RELEASE-p13 FreeBSD 4.8-RELEASE-p13 > #4: > > > Wed > > > Oct 15 08:55:21 PDT 2003 > > > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CREADLE i386 > > > > > > /var/log/messages: > > > Oct 14 21:45:23 creadle /kernel: Fatal trap 12: page fault while in > > > kernel > > > mode > > > Oct 14 21:45:23 creadle /kernel: fault virtual address = 0xbfca02c8 > > > Oct 14 21:45:23 creadle /kernel: fault code = supervisor > > > read, > > > page not present > > > Oct 14 21:45:23 creadle /kernel: instruction pointer= > 0x8:0xc028fe83 > > > Oct 14 21:45:23 creadle /kernel: stack pointer = > > > 0x10:0xd2cfbcf8 > > > Oct 14 21:45:23 creadle /kernel: frame pointer = > > > 0x10:0xd2cfbd08 > > > Oct 14 21:45:23 creadle /kernel: code segment = base 0x0, > > > limit > > > 0xf, type 0x1b > > > Oct 14 21
Re: Fatal trap 12
There are a few VM fixes that have gone into RELENG_4, thats where your kernel is really panicing. If its an option for you, I would try RELENG_4 rather than the security branch. ---Mike At 09:48 AM 16/10/2003, Chris Readle wrote: Got another one this morning. This time the only thing running was the make index && make readmes, and XFree86. Actually, they both may have finished by then, I started them up then had to go to sleep, so I'm not entirely sure how far along it got in the process. I do know it was past the index and working on the readmes, though. /var/log/messages: Oct 16 01:26:37 creadle /kernel: Fatal trap 12: page fault while in kernel mode Oct 16 01:26:37 creadle /kernel: fault virtual address = 0xfd9b Oct 16 01:26:37 creadle /kernel: fault code = supervisor read, page not present Oct 16 01:26:37 creadle /kernel: instruction pointer= 0x8:0xc022c1c8 Oct 16 01:26:37 creadle /kernel: stack pointer = 0x10:0xd2e2ee4c Oct 16 01:26:37 creadle /kernel: frame pointer = 0x10:0xd2e2ee54 Oct 16 01:26:37 creadle /kernel: code segment = base 0x0, limit 0xf, type 0x1b Oct 16 01:26:37 creadle /kernel: = DPL 0, pres 1, def32 1, gran 1 Oct 16 01:26:37 creadle /kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Oct 16 01:26:37 creadle /kernel: current process= 53504 (sh) Oct 16 01:26:37 creadle /kernel: interrupt mask = none Oct 16 01:26:37 creadle /kernel: trap number= 12 Oct 16 01:26:37 creadle /kernel: panic: page fault Oct 16 01:26:37 creadle /kernel: nm -n: [EMAIL PROTECTED] chris]$ nm -n /kernel | grep c022c1c8 [EMAIL PROTECTED] chris]$ nm -n /kernel | grep c022c1c [EMAIL PROTECTED] chris]$ nm -n /kernel | grep c022c1 c022c19c T vm_page_lookup c022c1f8 T vm_page_rename chris --- Chris Readle <[EMAIL PROTECTED]> wrote: > Hi all, > > New to FBSD, and in the process of moving my Linux/Windows PC to > FBSD/Windows. > > I got two spontaneous reboots last night (the first times it happened) > and > I got fatal trap 12s in /var/log/messages each time. I wasn't doing > anything too heavy, just a make index && make readmes on my ports, > listening to some music through XMMS and browsing the web via Mozilla. > > I searched the archives and the FAQ. I haven't built a debugging kernel > yet, but I thought I would post the info I have in the hopes that > someone > might be able to help. > > I did do an nm - n on the kernel, however. > > uname -a: > FreeBSD creadle.oc.cox.net 4.8-RELEASE-p13 FreeBSD 4.8-RELEASE-p13 #4: > Wed > Oct 15 08:55:21 PDT 2003 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CREADLE i386 > > /var/log/messages: > Oct 14 21:45:23 creadle /kernel: Fatal trap 12: page fault while in > kernel > mode > Oct 14 21:45:23 creadle /kernel: fault virtual address = 0xbfca02c8 > Oct 14 21:45:23 creadle /kernel: fault code = supervisor > read, > page not present > Oct 14 21:45:23 creadle /kernel: instruction pointer= 0x8:0xc028fe83 > Oct 14 21:45:23 creadle /kernel: stack pointer = > 0x10:0xd2cfbcf8 > Oct 14 21:45:23 creadle /kernel: frame pointer = > 0x10:0xd2cfbd08 > Oct 14 21:45:23 creadle /kernel: code segment = base 0x0, > limit > 0xf, type 0x1b > Oct 14 21:45:23 creadle /kernel: = DPL 0, pres 1, def32 1, gran 1 > Oct 14 21:45:23 creadle /kernel: processor eflags = interrupt > enabled, resume, IOPL = 0 > Oct 14 21:45:23 creadle /kernel: current process= 73961 > (sh) > Oct 14 21:45:23 creadle /kernel: interrupt mask = net tty bio > cam > Oct 14 21:45:23 creadle /kernel: trap number= 12 > Oct 14 21:45:23 creadle /kernel: panic: page fault > > nm -n: > creadle# nm -n /kernel | grep c028fe8 > c028fe88 T pmap_ts_referenced > creadle# nm -n /kernel | grep c028fe > c028fe7c T pmap_phys_address > c028fe88 T pmap_ts_referenced > > I did two because I thought it was odd that the first one came up with a > higher address than the actual pointer. > > Any good suggestions? > > chris > > > __ > Do you Yahoo!? > The New Yahoo! Shopping - with improved product search > http://shopping.yahoo.com > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" __ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"