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 Address 0x1 out of bounds) 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 0x8034fb29 in fork_exit (callout=0x803538d0 ithread_loop, arg=0xff000168b460, frame
Page Fault While in Kernel Mode (IPNAT)
Hi, I have a firewall for NAT operations only. While doing NAT, server crashes. Below you can find the required info about my problem. Thanks. Some useful info about my NAT server: FreeBSD xxx.cc.boun.edu.tr 7.3-RELEASE FreeBSD 7.3-RELEASE #2: Fri Sep 17 15:09:54 EEST 2010 x...@xxx.cc.boun.edu.tr:/usr/obj/usr/src/sys/FW i386 bge0: HP NC7782 Gigabit Server Adapter, ASIC rev. 0x002100 mem 0xfdef-0xfdef irq 25 at device 1.0 on pci3 bge1: HP NC7782 Gigabit Server Adapter, ASIC rev. 0x002100 mem 0xfdee-0xfdee irq 26 at device 1.1 on pci3 net.inet.ipf.ipf_natrules_sz: 127 net.inet.ipf.ipf_nattable_sz: 30 513/897/1410 mbufs in use (current/cache/total) 512/540/1052/0 mbuf clusters in use (current/cache/total/max) 512/512 mbuf+clusters out of packet secondary zone in use (current/cache) 0/5/5/12800 4k (page size) jumbo clusters in use (current/cache/total/max) 0/0/0/6400 9k jumbo clusters in use (current/cache/total/max) 0/0/0/3200 16k jumbo clusters in use (current/cache/total/max) 1152K/1324K/2476K bytes allocated to network (current/cache/total) 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) 0/0/0 requests for jumbo clusters denied (4k/9k/16k) 0/5/6656 sfbufs in use (current/peak/max) 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile 0 calls to protocol drain routines mappedin183625863out126618997 added2265807expired1350387 no memory8899bad nat12314 inuse13690 orphans0 rules49 wilds0 hash efficiency97.64% bucket usage4.46% minimal length0 maximal length3 average length1.024 TCP Entries per state 0 1 2 3 4 5 6 7 8 91011 42 223651 417 3311 348 2002320 0 3763 729 Debug info: GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd... Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address= 0x4 fault code= supervisor read, page not present instruction pointer= 0x20:0x8593c94b stack pointer= 0x28:0x853488dc frame pointer= 0x28:0x85348958 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= 25 (irq26: bge1) trap number= 12 panic: page fault cpuid = 0 Uptime: 2d0h6m24s Physical memory: 2035 MB Dumping 335 MB: 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/acpi.ko...Reading symbols from /boot/kernel/acpi.ko.symbols...done. done. Loaded symbols for /boot/kernel/acpi.ko Reading symbols from /boot/kernel/ipl.ko...Reading symbols from /boot/kernel/ipl.ko.symbols...done. done. Loaded symbols for /boot/kernel/ipl.ko #0 doadump () at pcpu.h:196 196__asm __volatile(movl %%fs:0,%0 : =r (td)); ### #0 doadump () at pcpu.h:196 #1 0x80746017 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0x807462e9 in panic (fmt=Variable fmt is not available. ) at /usr/src/sys/kern/kern_shutdown.c:574 #3 0x8097483c in trap_fatal (frame=0x8534889c, eva=4) at /usr/src/sys/i386/i386/trap.c:950 #4 0x80974aa0 in trap_pfault (frame=0x8534889c, usermode=0, eva=4) at /usr/src/sys/i386/i386/trap.c:863 #5 0x80975459 in trap (frame=0x8534889c) at /usr/src/sys/i386/i386/trap.c:541 #6 0x8095915b in calltrap () at /usr/src/sys/i386/i386/exception.s:166 #7 0x8593c94b in nat_new (fin=0x853489c0, np=0x855ee800, natsave=0x0, flags=Variable flags is not available. ) at /usr/src/sys/modules/ipfilter/../../contrib/ipfilter/netinet/ip_nat.c:2577 #8 0x8593cf04 in fr_checknatout (fin=0x853489c0, passp=0x85348a6c) at /usr/src/sys/modules/ipfilter/../../contrib/ipfilter/netinet/ip_nat.c:3828 #9 0x85959c6c in fr_check (ip=0x873c0810, hlen=20, ifp=0x855b7400, out=1, mp=0x85348ab8) at /usr/src/sys/modules/ipfilter/../../contrib/ipfilter/netinet/fil.c:2624 #10 0x859517be in fr_check_wrapper (arg=0x0, mp=0x85348ab8, ifp=0x855b7400, dir=2) at /usr/src/sys/modules/ipfilter/../../contrib/ipfilter/netinet/ip_fil_freebsd.c:178 #11 0x807f5708 in pfil_run_hooks (ph=0x80b026e0, mp=0x85348b44, ifp=0x855b7400, dir=2, inp=0x0) at /usr/src/sys/net/pfil.c:78 #12 0x8080ea72 in ip_output (m=0x85b2a800, opt=0x0, ro=0x85348b7c, flags=1, imo=0x0, inp=0x0) at /usr/src/sys/netinet/ip_output.c:443 #13 0x8080bb04 in ip_forward (m
Page Fault While in Kernel Mode (IPNAT)
Hi, I have a firewall for NAT operations only. While doing NAT, server crashes. Below you can find the required info about my problem. Thanks. Some useful info about my NAT server: FreeBSD xxx.cc.boun.edu.tr 7.3-RELEASE FreeBSD 7.3-RELEASE #2: Fri Sep 17 15:09:54 EEST 2010 x...@xxx.cc.boun.edu.tr:/usr/obj/usr/src/sys/FW i386 bge0: HP NC7782 Gigabit Server Adapter, ASIC rev. 0x002100 mem 0xfdef-0xfdef irq 25 at device 1.0 on pci3 bge1: HP NC7782 Gigabit Server Adapter, ASIC rev. 0x002100 mem 0xfdee-0xfdee irq 26 at device 1.1 on pci3 net.inet.ipf.ipf_natrules_sz: 127 net.inet.ipf.ipf_nattable_sz: 30 513/897/1410 mbufs in use (current/cache/total) 512/540/1052/0 mbuf clusters in use (current/cache/total/max) 512/512 mbuf+clusters out of packet secondary zone in use (current/cache) 0/5/5/12800 4k (page size) jumbo clusters in use (current/cache/total/max) 0/0/0/6400 9k jumbo clusters in use (current/cache/total/max) 0/0/0/3200 16k jumbo clusters in use (current/cache/total/max) 1152K/1324K/2476K bytes allocated to network (current/cache/total) 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) 0/0/0 requests for jumbo clusters denied (4k/9k/16k) 0/5/6656 sfbufs in use (current/peak/max) 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile 0 calls to protocol drain routines mappedin183625863out126618997 added2265807expired1350387 no memory8899bad nat12314 inuse13690 orphans0 rules49 wilds0 hash efficiency97.64% bucket usage4.46% minimal length0 maximal length3 average length1.024 TCP Entries per state 0 1 2 3 4 5 6 7 8 91011 42 223651 417 3311 348 2002320 0 3763 729 Debug info: GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd... Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address= 0x4 fault code= supervisor read, page not present instruction pointer= 0x20:0x8593c94b stack pointer= 0x28:0x853488dc frame pointer= 0x28:0x85348958 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= 25 (irq26: bge1) trap number= 12 panic: page fault cpuid = 0 Uptime: 2d0h6m24s Physical memory: 2035 MB Dumping 335 MB: 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/acpi.ko...Reading symbols from /boot/kernel/acpi.ko.symbols...done. done. Loaded symbols for /boot/kernel/acpi.ko Reading symbols from /boot/kernel/ipl.ko...Reading symbols from /boot/kernel/ipl.ko.symbols...done. done. Loaded symbols for /boot/kernel/ipl.ko #0 doadump () at pcpu.h:196 196__asm __volatile(movl %%fs:0,%0 : =r (td)); ### #0 doadump () at pcpu.h:196 #1 0x80746017 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0x807462e9 in panic (fmt=Variable fmt is not available. ) at /usr/src/sys/kern/kern_shutdown.c:574 #3 0x8097483c in trap_fatal (frame=0x8534889c, eva=4) at /usr/src/sys/i386/i386/trap.c:950 #4 0x80974aa0 in trap_pfault (frame=0x8534889c, usermode=0, eva=4) at /usr/src/sys/i386/i386/trap.c:863 #5 0x80975459 in trap (frame=0x8534889c) at /usr/src/sys/i386/i386/trap.c:541 #6 0x8095915b in calltrap () at /usr/src/sys/i386/i386/exception.s:166 #7 0x8593c94b in nat_new (fin=0x853489c0, np=0x855ee800, natsave=0x0, flags=Variable flags is not available. ) at /usr/src/sys/modules/ipfilter/../../contrib/ipfilter/netinet/ip_nat.c:2577 #8 0x8593cf04 in fr_checknatout (fin=0x853489c0, passp=0x85348a6c) at /usr/src/sys/modules/ipfilter/../../contrib/ipfilter/netinet/ip_nat.c:3828 #9 0x85959c6c in fr_check (ip=0x873c0810, hlen=20, ifp=0x855b7400, out=1, mp=0x85348ab8) at /usr/src/sys/modules/ipfilter/../../contrib/ipfilter/netinet/fil.c:2624 #10 0x859517be in fr_check_wrapper (arg=0x0, mp=0x85348ab8, ifp=0x855b7400, dir=2) at /usr/src/sys/modules/ipfilter/../../contrib/ipfilter/netinet/ip_fil_freebsd.c:178 #11 0x807f5708 in pfil_run_hooks (ph=0x80b026e0, mp=0x85348b44, ifp=0x855b7400, dir=2, inp=0x0) at /usr/src/sys/net/pfil.c:78 #12
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 ithread_loop, arg=0xff000187c460, frame=0xff8a0c80) at /usr/src/sys/kern/kern_fork.c:843 #16 0x80848bde in fork_trampoline () at /usr/src/sys/amd64/amd64
Re: page fault while in kernel mode
On Monday 20 October 2008 08:52:07 pm Robert Fitzpatrick wrote: On Mon, 2008-10-20 at 13:45 -0400, John Baldwin wrote: i386 cannot address more than 4GB unless the kernel is built with PAE mode enabled. This isn't enabled in GENERIC for many (justified) reasons. If you have more than 4GB, you should be using amd64, so you made the right decision there. If you aren't using kernel modules, then PAE should work fine. You can make kernel modules work with PAE as well, but that takes more work. Thanks for the help, I am missing AMD Features for this CPU in dmesg, so it looks like the CPU does not support amd64. I tried to build my own kernel with PAE option and getting the following error... /usr/src/sys/dev/advansys/advansys.c: In function 'adv_action': /usr/src/sys/dev/advansys/advansys.c:259: warning: cast from pointer to integer of different size *** Error code 1 Any idea what I can do for this error? Some drivers don't work with PAE (see all the 'nodevice' lines in /sys/i386/conf/PAE). You'll need to purge those drivers from your config. If you are using the hardware those drivers support, then you can't use PAE. -- John Baldwin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: page fault while in kernel mode
On Tue, 2008-10-21 at 12:03 -0400, John Baldwin wrote: Some drivers don't work with PAE (see all the 'nodevice' lines in /sys/i386/conf/PAE). You'll need to purge those drivers from your config. If you are using the hardware those drivers support, then you can't use PAE. Thanks for the help. Excuse the ignorance, I'm more a programmer than system guy. How do I purge a driver, or know which driver to look for, from the config and know what the driver supports? Do you mean, in this case, remove 'nodevice adv' from the PAE file? If so, I don't know what that supports :/ -- Robert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: page fault while in kernel mode
On Tue, Oct 21, 2008 at 02:35:22PM -0400, Robert Fitzpatrick wrote: On Tue, 2008-10-21 at 12:03 -0400, John Baldwin wrote: Some drivers don't work with PAE (see all the 'nodevice' lines in /sys/i386/conf/PAE). You'll need to purge those drivers from your config. If you are using the hardware those drivers support, then you can't use PAE. Thanks for the help. Excuse the ignorance, I'm more a programmer than system guy. How do I purge a driver, or know which driver to look for, from the config and know what the driver supports? Do you mean, in this case, remove 'nodevice adv' from the PAE file? If so, I don't know what that supports :/ Yeah, I don't think anyone's really explaining this very well to you, so I'll try a different approach: Certain FreeBSD drivers do not work in PAE mode. The drivers which don't work are listed in the /sys/i386/conf/PAE file. They're prefixed by the word nodevice, which tells the kernel config reader DO NOT build this device, because it won't work. You will need to take the nodevice lines from /sys/i386/conf/PAE and put them into your kernel config file. (There are alternative methods such as using include directives and so on, but I'm trying to keep this explanation simple.) Make sense now? :-) -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: page fault while in kernel mode
On Tue, 2008-10-21 at 11:47 -0700, Jeremy Chadwick wrote: The drivers which don't work are listed in the /sys/i386/conf/PAE file. They're prefixed by the word nodevice, which tells the kernel config reader DO NOT build this device, because it won't work. You will need to take the nodevice lines from /sys/i386/conf/PAE and put them into your kernel config file. (There are alternative methods such as using include directives and so on, but I'm trying to keep this explanation simple.) Make sense now? :-) Perfect sense now, believe it or not I was beginning to think along these lines as I was doing some searching and found 'device adv' in my config file and there was a description of the hardware it was for, which I don't have. Thanks for the clarification, now let's see if I can get this build done...thanks to all! -- Robert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: page fault while in kernel mode
On Tuesday 21 October 2008 02:47:11 pm Jeremy Chadwick wrote: On Tue, Oct 21, 2008 at 02:35:22PM -0400, Robert Fitzpatrick wrote: On Tue, 2008-10-21 at 12:03 -0400, John Baldwin wrote: Some drivers don't work with PAE (see all the 'nodevice' lines in /sys/i386/conf/PAE). You'll need to purge those drivers from your config. If you are using the hardware those drivers support, then you can't use PAE. Thanks for the help. Excuse the ignorance, I'm more a programmer than system guy. How do I purge a driver, or know which driver to look for, from the config and know what the driver supports? Do you mean, in this case, remove 'nodevice adv' from the PAE file? If so, I don't know what that supports :/ Yeah, I don't think anyone's really explaining this very well to you, so I'll try a different approach: Certain FreeBSD drivers do not work in PAE mode. The drivers which don't work are listed in the /sys/i386/conf/PAE file. They're prefixed by the word nodevice, which tells the kernel config reader DO NOT build this device, because it won't work. You will need to take the nodevice lines from /sys/i386/conf/PAE and put them into your kernel config file. (There are alternative methods such as using include directives and so on, but I'm trying to keep this explanation simple.) Make sense now? :-) Alternatively, you could just remove the 'device adv' line from your kernel config rather than adding lots of 'nodevice' lines at the bottom. You can usually do 'man 4 driver name' to see what devices it supports. In this case, adv(4) supports mostly ancient Advansys SCSI host adapters. The manpage has a full list of the various model numbers, etc. -- John Baldwin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: page fault while in kernel mode
On Tue, 2008-10-21 at 15:09 -0400, John Baldwin wrote: Alternatively, you could just remove the 'device adv' line from your kernel config rather than adding lots of 'nodevice' lines at the bottom. You can usually do 'man 4 driver name' to see what devices it supports. In this case, adv(4) supports mostly ancient Advansys SCSI host adapters. The manpage has a full list of the various model numbers, etc. Yes, that is what I thought. Right now, I am just commenting them out, now I know what people mean when they say they are running a trimmed/clean kernel. I did see one potential issue... # USB support device uhci# UHCI PCI-USB interface device ohci# OHCI PCI-USB interface device ehci# EHCI PCI-USB interface (USB 2.0) device usb # USB Bus (required) I see all of these with nodevice lines in the PAE file. Although I have USB ports, I don't use them, but I was concerned by the 'required' on the last one, is it OK to remove? Also, would I then need to disable USB in the BIOS to avoid errors? -- Robert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: page fault while in kernel mode
On Tue, Oct 21, 2008 at 03:22:28PM -0400, Robert Fitzpatrick wrote: On Tue, 2008-10-21 at 15:09 -0400, John Baldwin wrote: Alternatively, you could just remove the 'device adv' line from your kernel config rather than adding lots of 'nodevice' lines at the bottom. You can usually do 'man 4 driver name' to see what devices it supports. In this case, adv(4) supports mostly ancient Advansys SCSI host adapters. The manpage has a full list of the various model numbers, etc. Yes, that is what I thought. Right now, I am just commenting them out, now I know what people mean when they say they are running a trimmed/clean kernel. I did see one potential issue... # USB support device uhci# UHCI PCI-USB interface device ohci# OHCI PCI-USB interface device ehci# EHCI PCI-USB interface (USB 2.0) device usb # USB Bus (required) I see all of these with nodevice lines in the PAE file. Although I have USB ports, I don't use them, but I was concerned by the 'required' on the last one, is it OK to remove? Also, would I then need to disable USB in the BIOS to avoid errors? If you remove device usb, you will also need to remove uhci, ohci, ehci, umass, ukbd, etc. etc. etc... from your config as well. You do not need to disable USB support in the BIOS; the kernel will simply state that it sees devices on the PCI bus but lacks a driver to attach to them. This will not harm anything. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: page fault while in kernel mode
On Tuesday 21 October 2008 03:22:28 pm Robert Fitzpatrick wrote: On Tue, 2008-10-21 at 15:09 -0400, John Baldwin wrote: Alternatively, you could just remove the 'device adv' line from your kernel config rather than adding lots of 'nodevice' lines at the bottom. You can usually do 'man 4 driver name' to see what devices it supports. In this case, adv(4) supports mostly ancient Advansys SCSI host adapters. The manpage has a full list of the various model numbers, etc. Yes, that is what I thought. Right now, I am just commenting them out, now I know what people mean when they say they are running a trimmed/clean kernel. I did see one potential issue... # USB support device uhci# UHCI PCI-USB interface device ohci# OHCI PCI-USB interface device ehci# EHCI PCI-USB interface (USB 2.0) device usb # USB Bus (required) I see all of these with nodevice lines in the PAE file. Although I have USB ports, I don't use them, but I was concerned by the 'required' on the last one, is it OK to remove? Also, would I then need to disable USB in the BIOS to avoid errors? Actually, USB is ok with PAE. I recently updated the PAE configs to not disable PAE and at work we've run PAE kernels with USB enabled for a few years now on 6.x w/o any problems. -- John Baldwin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: page fault while in kernel mode
On Sun, 2008-10-19 at 13:16 -0700, Jeremy Chadwick wrote: On Sun, Oct 19, 2008 at 03:50:01PM -0400, Robert Fitzpatrick wrote: I took a working 5.4-i386 server and trying to convert its RAID 5 to RAID 10 and load 7.0 amd64. I kept getting BTX halted even after flashing the latest bios and firmware for the raid card, Intel SRCZCR, in this dual Xeon 2.4GHz supermicro superserver. I have another server, bit newer, but same basic hardware makeup with Xeon 3.0 procs that runs 6.1-amd64 fine. Anyway, so I have resorted to the i386 version of 7.0 to see if the server is just incapable of running amd64, which after passing the initial boot where amd64 failed, now gives me the subject error after some reference to GEOM_LABEL. I did rebuild the RAID to RAID-10, can someone tell me what this error means? http://columbus.webtent.org/freebsd.png Can you please try 7.1-BETA2 instead (ISOs are now available)? There have been fixes/improvements to BTX since 7.0-RELEASE which could fix your problem. Thanks, but that didn't work either trying 7.1-BETA2 amd64 :( Forgot to mention I added memory to this server as well, took it from 2GB it was using under 5.4-RELEASE up to 6GB filling all slots, that is why I wanted to load amd64. I reduced down to 4GB and now am able to install 7.0-RELEASE i386. Does this mean that I may have a hardware issue or can FreeBSD produce the page fault I was getting when using over 4GB with i386? I would love to figure out this BTX halted issue instead...any ideas on that? -- Robert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: page fault while in kernel mode
On Mon, Oct 20, 2008 at 12:07:17PM -0400, Robert Fitzpatrick wrote: On Sun, 2008-10-19 at 13:16 -0700, Jeremy Chadwick wrote: On Sun, Oct 19, 2008 at 03:50:01PM -0400, Robert Fitzpatrick wrote: I took a working 5.4-i386 server and trying to convert its RAID 5 to RAID 10 and load 7.0 amd64. I kept getting BTX halted even after flashing the latest bios and firmware for the raid card, Intel SRCZCR, in this dual Xeon 2.4GHz supermicro superserver. I have another server, bit newer, but same basic hardware makeup with Xeon 3.0 procs that runs 6.1-amd64 fine. Anyway, so I have resorted to the i386 version of 7.0 to see if the server is just incapable of running amd64, which after passing the initial boot where amd64 failed, now gives me the subject error after some reference to GEOM_LABEL. I did rebuild the RAID to RAID-10, can someone tell me what this error means? http://columbus.webtent.org/freebsd.png Can you please try 7.1-BETA2 instead (ISOs are now available)? There have been fixes/improvements to BTX since 7.0-RELEASE which could fix your problem. Thanks, but that didn't work either trying 7.1-BETA2 amd64 :( Forgot to mention I added memory to this server as well, took it from 2GB it was using under 5.4-RELEASE up to 6GB filling all slots, that is why I wanted to load amd64. I reduced down to 4GB and now am able to install 7.0-RELEASE i386. Does this mean that I may have a hardware issue or can FreeBSD produce the page fault I was getting when using over 4GB with i386? i386 cannot address more than 4GB unless the kernel is built with PAE mode enabled. This isn't enabled in GENERIC for many (justified) reasons. If you have more than 4GB, you should be using amd64, so you made the right decision there. I would love to figure out this BTX halted issue instead...any ideas on that? Boot loader problems are difficult to figure out/debug for reasons which should be obvious. I'm CC'ing John Baldwin here, who has experience with BTX. He might be able to shed some light on this. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: page fault while in kernel mode
On Monday 20 October 2008 12:32:37 pm Jeremy Chadwick wrote: Forgot to mention I added memory to this server as well, took it from 2GB it was using under 5.4-RELEASE up to 6GB filling all slots, that is why I wanted to load amd64. I reduced down to 4GB and now am able to install 7.0-RELEASE i386. Does this mean that I may have a hardware issue or can FreeBSD produce the page fault I was getting when using over 4GB with i386? i386 cannot address more than 4GB unless the kernel is built with PAE mode enabled. This isn't enabled in GENERIC for many (justified) reasons. If you have more than 4GB, you should be using amd64, so you made the right decision there. If you aren't using kernel modules, then PAE should work fine. You can make kernel modules work with PAE as well, but that takes more work. I would love to figure out this BTX halted issue instead...any ideas on that? Boot loader problems are difficult to figure out/debug for reasons which should be obvious. I'm CC'ing John Baldwin here, who has experience with BTX. He might be able to shed some light on this. You will get a BTX fault in 7.0 if your CPU does not support 64-bit long mode (i.e., amd64). You can check to see if your CPU does support it by looking in the 'AMD features' line of 'dmesg' from an i386 kernel and seeing if you have a 'LM' feature. If you don't, your CPU only supports i386. -- John Baldwin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: page fault while in kernel mode
On Mon, 2008-10-20 at 13:45 -0400, John Baldwin wrote: i386 cannot address more than 4GB unless the kernel is built with PAE mode enabled. This isn't enabled in GENERIC for many (justified) reasons. If you have more than 4GB, you should be using amd64, so you made the right decision there. If you aren't using kernel modules, then PAE should work fine. You can make kernel modules work with PAE as well, but that takes more work. Thanks for the help, I am missing AMD Features for this CPU in dmesg, so it looks like the CPU does not support amd64. I tried to build my own kernel with PAE option and getting the following error... /usr/src/sys/dev/advansys/advansys.c: In function 'adv_action': /usr/src/sys/dev/advansys/advansys.c:259: warning: cast from pointer to integer of different size *** Error code 1 Any idea what I can do for this error? -- Robert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
page fault while in kernel mode
I took a working 5.4-i386 server and trying to convert its RAID 5 to RAID 10 and load 7.0 amd64. I kept getting BTX halted even after flashing the latest bios and firmware for the raid card, Intel SRCZCR, in this dual Xeon 2.4GHz supermicro superserver. I have another server, bit newer, but same basic hardware makeup with Xeon 3.0 procs that runs 6.1-amd64 fine. Anyway, so I have resorted to the i386 version of 7.0 to see if the server is just incapable of running amd64, which after passing the initial boot where amd64 failed, now gives me the subject error after some reference to GEOM_LABEL. I did rebuild the RAID to RAID-10, can someone tell me what this error means? http://columbus.webtent.org/freebsd.png Thanks for any guidance. -- Robert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
page fault while in kernel mode
I took a working 5.4-i386 server and trying to convert its RAID 5 to RAID 10 and load 7.0 amd64. I kept getting BTX halted even after flashing the latest bios and firmware for the raid card, Intel SRCZCR, in this dual Xeon 2.4GHz supermicro superserver. I have another server, bit newer, but same basic hardware makeup with Xeon 3.0 procs that runs 6.1-amd64 fine. Anyway, so I have resorted to the i386 version of 7.0 to see if the server is just incapable of running amd64, which after passing the initial boot where amd64 failed, now gives me the subject error after some reference to GEOM_LABEL. I did rebuild the RAID to RAID-10, can someone tell me what this error means? http://columbus.webtent.org/freebsd.png Thanks for any guidance. -- Robert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: page fault while in kernel mode
On Sun, Oct 19, 2008 at 03:50:01PM -0400, Robert Fitzpatrick wrote: I took a working 5.4-i386 server and trying to convert its RAID 5 to RAID 10 and load 7.0 amd64. I kept getting BTX halted even after flashing the latest bios and firmware for the raid card, Intel SRCZCR, in this dual Xeon 2.4GHz supermicro superserver. I have another server, bit newer, but same basic hardware makeup with Xeon 3.0 procs that runs 6.1-amd64 fine. Anyway, so I have resorted to the i386 version of 7.0 to see if the server is just incapable of running amd64, which after passing the initial boot where amd64 failed, now gives me the subject error after some reference to GEOM_LABEL. I did rebuild the RAID to RAID-10, can someone tell me what this error means? http://columbus.webtent.org/freebsd.png Can you please try 7.1-BETA2 instead (ISOs are now available)? There have been fixes/improvements to BTX since 7.0-RELEASE which could fix your problem. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ 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]
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]
Kernel Panic: isp - page fault while in kernel mode
Revision 4.0.70 isp1: Qlogic ISP 2432 PCI FC-AL Adapter port 0x6400-0x64ff mem 0xfdfe-0xfdfe3fff irq 16 at device 0.1 on pci19 isp1: [GIANT-LOCKED] Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x2c fault code = supervisor read, page not present instruction pointer = 0x20:0xc045f1ea stack pointer = 0x28:0xc1020660 frame pointer = 0x28:0xc1020660 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 = 0 (swapper) trap number = 12 panic: page fault cpuid = 0 Uptime: 1s Automatic reboot in 15 seconds - press a key on the console to abort ___ 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: isp - page fault while in kernel mode
Greg Himes wrote: Hello All, Last week, one half of my dual port Qlogic fibre channel interface started causing a page fault panic while probing the second port at boot time. I was able to get the system back up by disabling the BIOS on the second port. The system still sees the 2nd port, but politely displays a few errors, then continues on. This all started after I powered the system down for maintenance. System is running FreeBSD 6.3-RELEASE i386 What is the proper way to help debug this problem? See the developers handbook. Kris P.S. And don't do this, you're crippling your network: WARNING: MPSAFE network stack disabled, expect reduced performance. ___ 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]
[panic]page fault while in kernel mode
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 http://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/DEBUGGER KERN 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: 118Jul 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 ?? () Any info is appreciated. with regards, Slava Gonahchan. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman
Page fault while in kernel mode
Hi, I am running 5.3-RELEASE on a P4 2.4GHz with 512 MB RAM. It is a normal PC hardware not a real server hardware. Today in the morning (while I was away from the console) kernel panicked and the output was Page fault while in kernel mode (the guy who wrote that down didn't write other information). The box was rebooted and the error appeared again in about 3 minutes. After second reboot everything seems to be back to normal. The load on this machine is quite low, about 0.1; it runs mail server, serves some web pages and does NAT via pf. Finally the question: what is more likely: that it is hardware which is causing troubles or that an upgrade to FreeBSD 5.5 (or eventually 6.1) would help? Or is there a third possibility? Thanks, Nejc smime.p7s Description: S/MIME Cryptographic Signature
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: page fault while in kernel mode
On Mon, Oct 24, 2005 at 12:11:29PM +0100, Owen Smith wrote: Whats the best thing todo? debugging kernel etc or just upgrade to 5.4? The latter. A few hundred bugs were fixed between 5.3 and 5.4, and the former is no longer supported anyway. Kris pgpT4R8dnqxnu.pgp Description: PGP signature
page fault while in kernel mode
Hi Whilst running 5.3-RELEASE-p22 on a GENERIC+ SMP options kernel we have had this: Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 00 fault virtual address = 0x42d38cf0 fault code = supervisor write, page not present instruction pointer = 0x8:0xc062f242 stack pointer = 0x10:0xeb4649bc frame pointer = 0x10:0xeb4649c4 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 = 1015 (screen) trap number = 12 panic: page fault cpuid = 1 boot() called on cpu#1 Uptime: 12d18h29m43s Cannot dump. No dump device defined. iir0: Flushing all Host Drives. Please wait ... kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 01 fault virtual address = 0x24 fault code = supervisor read, page not present instruction pointer = 0x8:0xc062c613 stack pointer = 0x10:0xe4dffc30 frame pointer = 0x10:0xe4dffc44 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 0 current process = 37 (swi5: clock sio) trap number = 12 spin lock sched lock held by 0xc22b94b0 for 5 seconds panic: spin lock held too long cpuid = 1 spin lock sched lock held by 0xc22b94b0 for 5 seconds panic: spin lock held too long cpuid = 1 # nm -n /boot/kernel/kernel | grep c062f c062f098 T openbsd_poll c062f0a8 T clear_selinfo_list c062f0d4 T selrecord c062f178 T selwakeup c062f188 T selwakeuppri c062f198 t doselwakeup c062f320 t selectinit c062f348 t pipeinit c062f37c t pipe_zone_ctor c062f454 t pipe_zone_dtor c062f468 t pipe_zone_init c062f48c t pipe_zone_fini c062f4a0 T pipe c062f794 t pipespace_new c062f8d0 t pipespace c062f8e0 t pipe_create c062f94c t pipe_read c062ff34 t pipe_build_write_buffer It is the 2nd time in a month the server has crashed the first time it rebooted on its own so I didn't get the error, but this time I had to power cycle it. The server is a Dual 800MHz intel box with 1.5GB RAM and 4*36GB RAID SCSI disks, It generally is not under much load. Whats the best thing todo? debugging kernel etc or just upgrade to 5.4? Thanks Ogg ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: page fault while in kernel mode
On Mon, Oct 24, 2005 at 12:11:29PM +0100, Owen Smith wrote: Whats the best thing todo? debugging kernel etc or just upgrade to 5.4? Run a memory est on the machine. memtest386 works well. -- U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong Terror - New York Times 9/3/1967 ___ 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
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
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]
page fault while in kernel mode
Hi, My FreeBSD machine dead at every monrning, and below is the error messages, could anyone help me? pearl# uname -a FreeBSD host1 5.0-DP1 FreeBSD 5.0-DP1 #0: Wed Aug 27 07:07:21 CST 2003 root@:/usr/src/sys/i386/compile/PEARL i386 Jun 26 14:38:06 pearl kernel: Jun 26 14:38:06 pearl kernel: Fatal trap 12: page fault while in kernel mode Jun 26 14:38:06 pearl kernel: fault virtual address = 0xfd1f1af1 Jun 26 14:38:06 pearl kernel: fault code= supervisor read, page not present Jun 26 14:38:06 pearl kernel: inwtruction pointer = 0x8:0xc028dd4c Jun 26 14:38:06 pearl kernel: stack pointer !0= 0x10:0xda6c1b20 Jun 26 14:38:06 pearl kernel: frame pointer = 0x10:0xdi6c1b3c Jun 26 14:38:06 pearl kernel: code segment = base 0x0, limit 0xf, type 0x1b Jun 26 14:38:06 pearl kernel: = DPL 0, pres 1\xac def32 1,!gran 1 Jun 26 14:38:06 pearl kernel: processor eflags = interrupt enabled, resume, IOPL = 0 ___ [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
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: 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 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]
page fault while in kernel mode?
Hello, I am having the following problem. About a week or so ago this started. My box running 4.9-STABLE keeps panicing and rebooting, below is an output of dmesg -a. Also i have tried to replace the memory and the hard drive is only 5 months old or so. Here is the error i recieve Fatal trap 12: page fault while in kernel mode fault virtual address = 0xa83a0028 fault code = supervisor read, page not present instruction pointer = 0x8:0xc3e4ea17 stack pointer = 0x10:0xc041faec frame pointer = 0x10:0xc041fb1c 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 = Idle interrupt mask = trap number = 12 panic: page fault syncing disks... Fatal trap 12: page fault while in kernel mode fault virtual address = 0x30 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0325a14 stack pointer = 0x10:0xc041f81c frame pointer = 0x10:0xc041f824 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 = Idle interrupt mask = bio trap number = 12 panic: page fault And here is the output of dmesg -a Mon Mar 22 18:55:04 EST 2004 Fatal trap 12: page fault while in kernel mode fault virtual address = 0x8dc40020 fault code = supervisor read, page not present instruction pointer = 0x8:0xc3e4ea17 stack pointer = 0x10:0xc041fc28 frame pointer = 0x10:0xc041fc58 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 = Idle interrupt mask = trap number = 12 panic: page fault syncing disks... Fatal trap 12: page fault while in kernel mode fault virtual address = 0x30 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0325a14 stack pointer = 0x10:0xc041fa4c frame pointer = 0x10:0xc041fa54 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 = Idle interrupt mask = bio trap number = 12 panic: page fault Uptime: 4m13s Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... Copyright (c) 1992-2003 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 4.9-STABLE #0: Tue Mar 16 00:53:17 EST 2004 [EMAIL PROTECTED]:/usr/src/sys/compile/SOLAR Timecounter i8254 frequency 1193182 Hz CPU: Intel Pentium III (1101.95-MHz 686-class CPU) Origin = GenuineIntel Id = 0x68a Stepping = 10 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR, PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 267255808 (260992K bytes) config di atkbd0 config q avail memory = 254062592 (248108K bytes) Preloaded elf kernel kernel at 0xc0536000. Preloaded userconfig_script /boot/kernel.conf at 0xc053609c. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 6 entries at 0xc00f42e0 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82810E (i810E GMCH) Host To Hub bridge on motherboard pci0: PCI bus on pcib0 agp0: Intel 82810E (i810E GMCH) SVGA controller mem 0xffe8- 0xffef,0xf800-0xfbff irq 11 at device 1.0 on pci0 pcib1: Intel 82801AA (ICH) Hub to PCI bridge at device 30.0 on pci0 pci1: PCI bus on pcib1 dc0: ADMtek AN985 10/100BaseTX port 0xd400-0xd4ff mem 0xffcff800- 0xffcffbff irq 5 at device 2.0 on pci1 dc0: Ethernet address: 00:04:5a:61:b9:0b miibus0: MII bus on dc0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: D-Link DFE-530TX+ 10/100BaseTX port 0xd800-0xd8ff mem 0xffcffc00-0xffcffcff irq 9 at device 3.0 on pci1 rl0: Ethernet address: 00:50:ba:ac:e8:b1 miibus1: MII bus on rl0 rlphy0: RealTek internal media interface on miibus1 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: Intel 82801AA (ICH) PCI to LPC bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH ATA66 controller port 0xffa0-0xffaf at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: Intel 82801AA (ICH) USB controller port 0xef00-0xef1f irq 9 at device 31.2 on pci0 usb0: Intel 82801AA (ICH) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub1: vendor 0x0416 USB HUB, class 9/0, rev 1.10/0.05, addr 2 uhub1: 4 ports with 4 removable
Re: Fatal trap 12: page fault while in kernel mode
On Tuesday 22 July 2003 00:13, Jeremy Gaddis wrote: One of my machines spontaneously rebooted today, during a run of `portsdb -Uu` after a cvsup of the ports collection. It's also done it a few times before, but I wasn't around and wasn't able to catch anything that it spit it before it rebooted. I was able to reproduce it, and here's what was output before the reboot: I'm not an expert, but I'd say: rebuild the kernel with debug symbols and get a core dump. This would help a lot. Daniela ___ [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 Tue, Jul 22, 2003 at 02:07:23PM +, Daniela wrote: On Tuesday 22 July 2003 00:13, Jeremy Gaddis wrote: One of my machines spontaneously rebooted today, during a run of `portsdb -Uu` after a cvsup of the ports collection. It's also done it a few times before, but I wasn't around and wasn't able to catch anything that it spit it before it rebooted. I was able to reproduce it, and here's what was output before the reboot: I'm not an expert, but I'd say: rebuild the kernel with debug symbols and get a core dump. This would help a lot. Yes..see the chapter in the developers handbook. Kris pgp0.pgp Description: PGP signature
Fatal trap 12: page fault while in kernel mode
One of my machines spontaneously rebooted today, during a run of `portsdb -Uu` after a cvsup of the ports collection. It's also done it a few times before, but I wasn't around and wasn't able to catch anything that it spit it before it rebooted. I was able to reproduce it, and here's what was output before the reboot: Fatal trap 12: page fault while in kernel mode fault virtual address = 0xc0f95240 fault code = supervisor read, page not present instruction pointer = 0x8:0xc018306c stack pointer = 0x10:0xc40aaba4 frame pointer = 0x10:0xc40aabc4 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 = 2550 (sh) interrupt mask = none trap number = 12 panic: page fault [EMAIL PROTECTED]:ttyp0:~]$ uname -a FreeBSD pluto.main.gaddis.org 4.8-STABLE FreeBSD 4.8-STABLE #0: Sun Jun 1 01:12:47 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PLUTO i386 [EMAIL PROTECTED]:ttyp0:~]$ dmesg Copyright (c) 1992-2003 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 4.8-STABLE #0: Sun Jun 1 01:12:47 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PLUTO Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 199310034 Hz CPU: Pentium/P54C (199.31-MHz 586-class CPU) Origin = GenuineIntel Id = 0x52c Stepping = 12 Features=0x1bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8 real memory = 33554432 (32768K bytes) config di ppc0 No such device: ppc0 Invalid command or syntax. Type `?' for help. config di bt0 No such device: bt0 Invalid command or syntax. Type `?' for help. config di aic0 No such device: aic0 Invalid command or syntax. Type `?' for help. config di aha0 No such device: aha0 Invalid command or syntax. Type `?' for help. config di adv0 No such device: adv0 Invalid command or syntax. Type `?' for help. config en ed0 No such device: ed0 Invalid command or syntax. Type `?' for help. config po ed0 0x300 No such device: ed0 Invalid command or syntax. Type `?' for help. config ir ed0 10 No such device: ed0 Invalid command or syntax. Type `?' for help. config iom ed0 0xd8000 No such device: ed0 Invalid command or syntax. Type `?' for help. config f ed0 0 No such device: ed0 Invalid command or syntax. Type `?' for help. config q avail memory = 29859840 (29160K bytes) Preloaded elf kernel kernel at 0xc02ea000. Preloaded userconfig_script /boot/kernel.conf at 0xc02ea09c. Intel Pentium detected, installing workaround for F00F bug md0: Malloc disk npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 isab0: Intel 82371SB PCI to ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX3 ATA controller port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: SiS 6326 SVGA controller at 19.0 rl0: Accton MPX 5030/5038 10/100BaseTX port 0x6100-0x61ff mem 0xe081-0xe08100ff irq 11 at device 20.0 on pci0 rl0: Ethernet address: 00:e0:29:96:62:f9 miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto orm0: Option ROM at iomem 0xc-0xc7fff on isa0 fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ad0: 19541MB Maxtor 5T020H2 [39704/16/63] at ata0-master WDMA2 acd0: CDROM BCD-44XH CD-ROM at ata1-master PIO4 Mounting root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted [EMAIL PROTECTED]:ttyp0:~]$ The box in question is a P200 w/ 32 MB of RAM and 20 GB HDD, running 4.8-STABLE. I'd appreciate any comments or suggestions as to what I might do to track down the source of this problem. Thanks, j. -- Jeremy L. Gaddis [EMAIL PROTECTED] http://www.gaddis.org ___ [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'm trying to install 5.0-RELEASE on a Gateway Solo 5150 laptop (PII-366/128M), can't seem to get past this situation while booting from the CD: Fatal trap 12: page fault while in kernel mode fault virtual address = 0xc8ea5048 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0246a25 stack pointer = 0x10:0xc885a960 frame pointer = 0x10:0xc885ab8c 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 (cbb0) trap number = 12 panic: page fault syncing discs, buffers remaining... done Uptime: 1s Terminate ACPI ata1-slave: ATAPI identify retries exceeded Automatic reboot in 15 seconds - press a key on the console to abort Can anyone decipher this for me and suggest a course of action? Thanks!! -- Bobb Shires [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Kernel Panic : Fatal trap 12: page fault while in kernel mode
Not sure who to send this to. I'm fairly new to FreeBSD. I was running this in Virtual PC v5.1 evalulation and FreeBSD panicrd when I resumed from a pause in the Virtual PC menu. Let me know if there is any information I can provide. -Nick uname -a FreeBSD freebsd.home.net 5.0-RELEASE FreeBSD 5.0-RELEASE #0: Thu Jan 16 22:16:5 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 Fatal trap 12: page fault while in kernel mode fault virtual address = 0x74 fault code = supervisor read, page not present instruction pointer = 0x8:0xc02dd3bc stack pointer = 0x10:0xc86c3c78 frame pointer = 0x10:0xc86c3c94 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, IOPL = 0 current process = 20 (irq14: ata0) trap number = 12 panic: page fault To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message