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
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: mem
0xfdef-0xfdef irq 25 at device 1.0 on pci3
bge1: 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=0x85b2a800, srcrt=0)
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: mem
0xfdef-0xfdef irq 25 at device 1.0 on pci3
bge1: 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
Re: Page fault in kernel when using CD, BSD 7.2
Mark Terribile wrote: AMI BIOS. The NB heatsink is barely warm (fan cooled), the not necessarily a good sign, you would get this if the heat from the cpu is not getting transferred to the heatsink. Remove, clean, apply new heat transfer compound, make sure the heatsink is actually seating properly, not getting lodged on something. Chris ___ 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: Page fault in kernel when using CD, BSD 7.2
Hi, > Second problem: on a machine (Core 2 Quad, 2.24 GHz) the > CD/DVD drive has started to give me page faults in the kernel. > The "press any key on the console" to halt the reboot does > not work. > > Okay, now it's happening with nothing but the fsck > running. > It takes maybe fifteen minutes. Okay, I've got a suspect. I got it past the fsck by going ino Single User and doing the file systems one disk at a time. (Two on this machine). I suspect the power supply has gone marginal. My spare is much bigger than the what I need for this machine; I'll wait on a replacement if I can. And I'll let you all know. Thanks to those who've written. Mark Terribile materrib...@yahoo.com ___ 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: Page fault in kernel when using CD, BSD 7.2
-Original Message- From: Mark Terribile [mailto:materrib...@yahoo.com] Sent: 12 August 2010 03:32 To: freebsd-questions@freebsd.org Subject: Page fault in kernel when using CD, BSD 7.2 Hi, In the last two days I've had two nasty problems on two machines. The first started dumping core on epiphany, apparently when the Javascript garbage collector ran. I found that the fan on the video card was running and stopping. I jury-rigged a fan over it (until I get a new one) and the problem has gone away. Probably nothing to do with the second problem, but who knows? Second problem: on a machine (Core 2 Quad, 2.24 GHz) the CD/DVD drive has started to give me page faults in the kernel. The "press any key on the console" to halt the reboot does not work. I've been using this drive on and off for months. I've checked all the connections (PATA), blown out the machine (the temperatures reported by sysctl range from 50 to 59 degrees from core to core), and put a different power lead into the drive. Sometimes the console gets large transfer errors (I don't want to excite the problem right now, as the fsck is finally running) before the fault. The disk transfers don't work, the drive won't open, the process can't be interrupted, etc. The error usually comes a few minutes after the drive stops working. Yes, the processor is running a little hot, but I don't think it's dangerous and its been like this for months. I have a compact heat sink on it and the interaction between the rotor/stator fan and the CPU speed control reduces the speed too much at low load. But again, it's been like that for months. Does anyone have any suggestions? Is it worth trying a new PATA or SATA drive? Mark Terribile materrib...@yahoo.com Might be worthwhile running memtest on the machine. Regards Graeme ___ 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"
Page fault in kernel when using CD, BSD 7.2
Hi, In the last two days I've had two nasty problems on two machines. The first started dumping core on epiphany, apparently when the Javascript garbage collector ran. I found that the fan on the video card was running and stopping. I jury-rigged a fan over it (until I get a new one) and the problem has gone away. Probably nothing to do with the second problem, but who knows? Second problem: on a machine (Core 2 Quad, 2.24 GHz) the CD/DVD drive has started to give me page faults in the kernel. The "press any key on the console" to halt the reboot does not work. I've been using this drive on and off for months. I've checked all the connections (PATA), blown out the machine (the temperatures reported by sysctl range from 50 to 59 degrees from core to core), and put a different power lead into the drive. Sometimes the console gets large transfer errors (I don't want to excite the problem right now, as the fsck is finally running) before the fault. The disk transfers don't work, the drive won't open, the process can't be interrupted, etc. The error usually comes a few minutes after the drive stops working. Yes, the processor is running a little hot, but I don't think it's dangerous and its been like this for months. I have a compact heat sink on it and the interaction between the rotor/stator fan and the CPU speed control reduces the speed too much at low load. But again, it's been like that for months. Does anyone have any suggestions? Is it worth trying a new PATA or SATA drive? Mark Terribile materrib...@yahoo.com ___ 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"
Page fault in kernel when using CD, BSD 7.2
Hi, > Second problem: on a machine (Core 2 Quad, 2.24 GHz) the > CD/DVD drive has started to give me page faults in the kernel. > The "press any key on the console" to halt the reboot does > not work. Okay, now it's happening with nothing but the fsck running. It takes maybe fifteen minutes. I'm using an ASUS P5N7A-VM mobo, AMI BIOS. The NB heatsink is barely warm (fan cooled), the memory is just warm to the touch, I've blown everything out, etc. I've got two SATA disks (Seagate and WD), in a carrier well-ventilated by a fan. They are barely warm. The CD was not in use. Ambient temperature is about 83 to 86F and this machine is a mobo on a standoffs on a board (until I free up the case it's supposed to go in). Granted that I may have a HW problem, but does the way the problem has manifested suggest anything about where to start? Mark Terribile materrib...@yahoo.com ___ 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: Sudden refusal to boot with page fault in swapper
On 14/06/10 10:51, Matthew Hambley wrote: My FreeBSD system (amd64, SATA, root on ZFS) has suddenly started refusing to boot up. It crashes out with a page fault just after the ZFS warning that I "only" have 4GB of RAM. Just to conclude this issue in case anyone searches for it in the future. As suggested elsewhere the problem was indeed the VirtualBox kernel modules. These should not be loaded a boot time but as part of the rc.conf/rc.local procedure. -- (\/)atthew ___ 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: fnd cause "panic: page fault"
On 02/08/2010 05:59, n dhert wrote: > Sometimes my FreeBSD8.0-p4 machine does an automatic reboot after > panic: page fault. (Fatal trap 12: page fault while in kernel mode) > It's at random times. > What in general can be the cause of that? > Is it always due to hardware memory errors? This is very commonly an indication of hardware problems. Usually memory gone bad. Running memtest86 may help you confirm if you do have bad RAM. Or take out your RAM by halves and see if you can identify a bad stick. > What else can be a cause, how to find out ? > I have output in /var/crash but don't understand very much of it > and don't know where to look to find the cause. > please help .. The problem can be due to other causes -- but signal 12 == SIGSYS meaning "non existent system call invoked": unless you're a kernel developer, that's quite hard to achieve without bad hardware. Cheers, Matthew signature.asc Description: OpenPGP digital signature
fnd cause "panic: page fault"
Sometimes my FreeBSD8.0-p4 machine does an automatic reboot after panic: page fault. (Fatal trap 12: page fault while in kernel mode) It's at random times. What in general can be the cause of that? Is it always due to hardware memory errors? What else can be a cause, how to find out ? I have output in /var/crash but don't understand very much of it and don't know where to look to find the cause. please help .. ___ 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
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: Page fault in swapper on boot
Richard Kolkovich wrote: > On Mon, Jun 28, 2010 at 02:16:42PM -0500, Richard Kolkovich wrote: >> I rebooted today to recover a couple devices which were in use by zombie >> processes. Now, I'm met with the same page fault documented in this >> previous message: >> >> http://lists.freebsd.org/pipermail/freebsd-questions/2010- June/217625.html >> >> I also performed the gettext upgrade between my last reboot and this one, >> but I had no problems >> completing it. I have since booted the MFS live CD, mounted my zpools >> and updated world and kernel >> (RELENG_8 as of this morning) - still have the same page fault in the >> same place. I also tried >> GENERIC - no dice there, either. Single user, no-ACPI, etc. don't work. >> >> I'll build some debugging into the kernel and see what else I can find... > > I should have done this before spamming the list, but at least I can > provide a solution. > > With debugging enabled, I saw the problem child is the VirtualBox network > module (vboxnetflt.ko). I set both enable_vboxdrv and enable_vboxnetflt > to NO in loader.conf, and I was able to boot just fine. > > Sorry for the noise - hope this helps someone else out. > The recent gettext update is a dependency for both the vbox kernel modules and the virtualbox-ose ports. Try rebuilding/reinstalling both with make && make deinstall && make reinstall if you still wish to use them. -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: Page fault in swapper on boot
On Mon, Jun 28, 2010 at 02:16:42PM -0500, Richard Kolkovich wrote: > I rebooted today to recover a couple devices which were in use by zombie > processes. Now, I'm met > with the same page fault documented in this previous message: > > http://lists.freebsd.org/pipermail/freebsd-questions/2010-June/217625.html > > I also performed the gettext upgrade between my last reboot and this one, but > I had no problems > completing it. I have since booted the MFS live CD, mounted my zpools and > updated world and kernel > (RELENG_8 as of this morning) - still have the same page fault in the same > place. I also tried > GENERIC - no dice there, either. Single user, no-ACPI, etc. don't work. > > I'll build some debugging into the kernel and see what else I can find... I should have done this before spamming the list, but at least I can provide a solution. With debugging enabled, I saw the problem child is the VirtualBox network module (vboxnetflt.ko). I set both enable_vboxdrv and enable_vboxnetflt to NO in loader.conf, and I was able to boot just fine. Sorry for the noise - hope this helps someone else out. -- Richard Kolkovich http://www.sigil.org PGP Key: 0x9E54EF59 (http://pgp.mit.edu) pgpVWLmRRrn2z.pgp Description: PGP signature
Page fault in swapper on boot
I rebooted today to recover a couple devices which were in use by zombie processes. Now, I'm met with the same page fault documented in this previous message: http://lists.freebsd.org/pipermail/freebsd-questions/2010-June/217625.html I also performed the gettext upgrade between my last reboot and this one, but I had no problems completing it. I have since booted the MFS live CD, mounted my zpools and updated world and kernel (RELENG_8 as of this morning) - still have the same page fault in the same place. I also tried GENERIC - no dice there, either. Single user, no-ACPI, etc. don't work. I'll build some debugging into the kernel and see what else I can find... Has anyone else seen this or have any clues as to how to fix it? Thanks, -- Richard Kolkovich http://www.sigil.org PGP Key: 0x9E54EF59 (http://pgp.mit.edu) pgpXUckls7Kte.pgp Description: PGP signature
Sudden refusal to boot with page fault in swapper
My FreeBSD system (amd64, SATA, root on ZFS) has suddenly started refusing to boot up. It crashes out with a page fault just after the ZFS warning that I "only" have 4GB of RAM. The following is a transcription of what I see: ZFS file system version 13 ZFS storage pool version 13 Timecounters tick every 1.000msec Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x4 fault code = supervisor write data, page not present instruction pointer = 0x20:0xf...810c522a stack pointer = 0x28:0xf...81128af0 frame pointer = 0x28:0xf...81128b10 code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interupt enabled, resume, IOPL = 0 current process = 0 (swapper) trap number = 12 panic: page fault cupid = 0 uptime : 1s Cannot dump, Device not defined or unavailable Automatic reboot in 15 seconds The ellipses in addresses represents continued f's. These addresses seem to be the same each time. I have tried using the "Without ACPI" boot option to no avail. Originally I had a problem in that using a USB keyboard meant I was unable to press a key to halt the reboot timer but a USB to PS/2 adapter solved that. This problem has suspiciously started happening after I had trouble performing the big "gettext" upgrade to the ports tree but I don't see how changes to the ports tree can affect the base system which is presumably where I still am this early in the boot process. However, for completeness, the "portmaster -w -r gettext" command kept failing half way through over the "xz" archiver. In the end I gave up and went with a "portmaster -a" expecting some minor problems which could be fixed with manual recompilation of effected ports. While some web searching didn't turn up an answer to my problem it did show that a memory fault is often suspected in these situations. I used an "Ultimate Boot" disc to test the memory and it tested okay. Have I hosed my system? And help gratefully received. -- (\/)atthew ___ 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: Busy disk and page fault
On Mon, Mar 09, 2009 at 05:04:16PM +0100, Wojciech Puchar wrote: >> The server is overload, the disk is 100% busy with 250 write operations >> per second and a throuput of 6MB/s. >> My first idea is because of mass random access/write on the disk. But I also >> see >> the server can make 20k page fault per second. > what page fault? most page faults in FreeBSD doesn't mean disk access, > just no mapping present in page tables, which gets mapped after the > fault. > Only if page is actually not present in memory it is fetched from disk. > top shows in what state is a process. > if it's biord or biorw - it's doing disk/file I/O, not swapping. The box don't swap. I just ask if page fault interrupt postgresql process and fragment/de-optimize disk write. -- Nicolas Haller ___ 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: Busy disk and page fault
The server is overload, the disk is 100% busy with 250 write operations per second and a throuput of 6MB/s. My first idea is because of mass random access/write on the disk. But I also see the server can make 20k page fault per second. what page fault? most page faults in FreeBSD doesn't mean disk access, just no mapping present in page tables, which gets mapped after the fault. Only if page is actually not present in memory it is fetched from disk. top shows in what state is a process. if it's biord or biorw - it's doing disk/file I/O, not swapping. that's about FreeBSD part - about postgress part ask on postgress mailing list. i don't use it so i can't help you. ___ 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"
Busy disk and page fault
Hi all, I'm asking myself about a problem I have with a Postgresql server on FreeBSD 7.1-RELEASE. The server is overload, the disk is 100% busy with 250 write operations per second and a throuput of 6MB/s. My first idea is because of mass random access/write on the disk. But I also see the server can make 20k page fault per second. So, did you think I really have a disk contention or this high number of page fault can be a problem (and if it can, how to resolve it). Thanks, -- Nicolas Haller ___ 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: Page Fault.
On Monday 01 December 2008 21:34:14 Keith wrote:
> On Mon, 1 Dec 2008, Mel wrote:
> |->On Monday 01 December 2008 19:32:59 Keith wrote:
> |->>
> |->> ==
> |->> kernel trap 12 with interrupts disabled
> |->>
> |->> Fatal trap 12: page fault while in kernel mode
> |->> cpuid = 2; apic id = 02
> |->> fault virtual address = 0x104
> |->> fault code = supervisor read, page not present
> |->> instruction pointer = 0x20:0xc066ca51
> |->> stack pointer = 0x28:0xe6ec0c90
> |->> frame pointer = 0x28:0xe6ec0c9c
> |->> code segment= base 0x0, limit 0xf, type 0x1b
> |->> = DPL 0, pres 1, def32 1, gran 1
> |->> processor eflags = resume, IOPL = 0
> |->> current process = 9 (thread taskq)
> |->> trap number = 12
> |->> panic: page fault
> |->> Uptime: 6d6h23m45s
> |->> #0 doadump () at pcpu.h:165
> |->> 165 __asm __volatile("movl %%fs:0,%0" : "=r" (td));
> |->>
> |->>
> |->frame 0 useless. You need the frame after calltrap().
> |->And:
> |->
> |->> instruction pointer = 0x20:0xc066ca51
> |->list *0xc066ca51
> |->
> |->Generally a bt will show the needed information.
> |->Likely cause: file system corruption, caused by background_fsck, but a
> |->backtrace should show more.
>
> Ok, so how does one fix corruption if that is the case? Here is a
> backtrace, but means nothing to me unfortunately.
>
> (kgdb) backtrace
> #0 doadump () at pcpu.h:165
> #1 0xc067582a in boot (howto=260) at ../../../kern/kern_shutdown.c:409
> #2 0xc0675b51 in panic (fmt=0xc08f090b "%s") at
> ../../../kern/kern_shutdown.c:565
>
> #3 0xc0899f1c in trap_fatal (frame=0xe6ec0c50, eva=260) at
> ../../../i386/i386/trap.c:837
>
> #4 0xc089968e in trap (frame={tf_fs = 8, tf_es = -920256472, tf_ds =
> -420741080, tf_edi = -936184704, tf_esi = 4, tf_ebp = -420737892, tf_isp
> = -420737924, tf_ebx = -920236452, tf_edx = 6, tf_ecx = -936306488, tf_eax
> = 1, tf_trapno = 12, tf_err = 0, tf_eip = -1067005359, tf_cs = 32,
> tf_eflags = 65538, tf_esp = -930065784, tf_ss = 4}) at
> ../../../i386/i386/trap.c:270
>
> #5 0xc08859ca in calltrap () at ../../../i386/i386/exception.s:139
>
> #6 0xc066ca51 in _mtx_lock_sleep (m=0xc9264e5c, tid=3358782592, opts=0,
> file=0x0, line=0) at ../../../kern/kern_mutex.c:546
>
> #7 0xc06bbdb6 in unp_gc (arg=0x0, pending=1) at
> ../../../kern/uipc_usrreq.c:1714
This has been fixed:
http://www.freebsd.org/cgi/query-pr.cgi?pr=113823
--
Mel
Problem with today's modular software: they start with the modules
and never get to the software part.
___
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.
On Mon, 1 Dec 2008, Mel wrote:
|->On Monday 01 December 2008 19:32:59 Keith wrote:
|->>
|->> ==
|->> kernel trap 12 with interrupts disabled
|->>
|->> Fatal trap 12: page fault while in kernel mode
|->> cpuid = 2; apic id = 02
|->> fault virtual address = 0x104
|->> fault code = supervisor read, page not present
|->> instruction pointer = 0x20:0xc066ca51
|->> stack pointer = 0x28:0xe6ec0c90
|->> frame pointer = 0x28:0xe6ec0c9c
|->> code segment= base 0x0, limit 0xf, type 0x1b
|->> = DPL 0, pres 1, def32 1, gran 1
|->> processor eflags= resume, IOPL = 0
|->> current process = 9 (thread taskq)
|->> trap number = 12
|->> panic: page fault
|->> Uptime: 6d6h23m45s
|->> #0 doadump () at pcpu.h:165
|->> 165 __asm __volatile("movl %%fs:0,%0" : "=r" (td));
|->>
|->>
|->frame 0 useless. You need the frame after calltrap().
|->And:
|->
|->> instruction pointer = 0x20:0xc066ca51
|->list *0xc066ca51
|->
|->Generally a bt will show the needed information.
|->Likely cause: file system corruption, caused by background_fsck, but a
|->backtrace should show more.
Ok, so how does one fix corruption if that is the case? Here is a
backtrace, but means nothing to me unfortunately.
(kgdb) backtrace
#0 doadump () at pcpu.h:165
#1 0xc067582a in boot (howto=260) at ../../../kern/kern_shutdown.c:409
#2 0xc0675b51 in panic (fmt=0xc08f090b "%s") at
../../../kern/kern_shutdown.c:565
#3 0xc0899f1c in trap_fatal (frame=0xe6ec0c50, eva=260) at
../../../i386/i386/trap.c:837
#4 0xc089968e in trap (frame={tf_fs = 8, tf_es = -920256472, tf_ds =
-420741080, tf_edi = -936184704, tf_esi = 4, tf_ebp = -420737892, tf_isp
= -420737924, tf_ebx = -920236452, tf_edx = 6, tf_ecx = -936306488, tf_eax = 1,
tf_trapno = 12,
tf_err = 0, tf_eip = -1067005359, tf_cs = 32, tf_eflags = 65538, tf_esp =
-930065784, tf_ss = 4}) at ../../../i386/i386/trap.c:270
#5 0xc08859ca in calltrap () at ../../../i386/i386/exception.s:139
#6 0xc066ca51 in _mtx_lock_sleep (m=0xc9264e5c, tid=3358782592, opts=0,
file=0x0, line=0) at ../../../kern/kern_mutex.c:546
#7 0xc06bbdb6 in unp_gc (arg=0x0, pending=1) at
../../../kern/uipc_usrreq.c:1714
#8 0xc06964d3 in taskqueue_run (queue=0xc843fa80) at
../../../kern/subr_taskqueue.c:257
#9 0xc06969b6 in taskqueue_thread_loop (arg=0x1) at
../../../kern/subr_taskqueue.c:376
#10 0xc065ef6d in fork_exit (callout=0xc0696924 ,
arg=0xc09f1d28, frame=0xe6ec0d38) at ../../../kern/kern_fork.c:821
#11 0xc0885a2c in fork_trampoline () at ../../../i386/i386/exception.s:208
___
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.
On Monday 01 December 2008 19:32:59 Keith wrote:
> Have a machine, Dell dual CPU/quad core Xeon. Runs FBSD 6.2.
> Custom kernel, with IPFW compiled in and using SMP.
>
> FreeBSD 6.2-RELEASE FreeBSD 6.2-RELEASE #1: Wed Jan 23
> 12:17:29 PST 2008
>
> It runs, Dovecot, Postfix, Mysql, Apache. Standard email stuff. Put into
> production in March, ran perfect until July 29th when it rebooted by
> itself.
>
> It rebooted 2 more times in the last few months on its own. But in the
> last 6 weeks it has become a weekly occurance, with uptime no more than
> 6-7 days at most.
>
> The last 2 times I have cores and have run kgdb on them. Both vmcore's
> show the same things. Same pointers etc, the only difference is what the
> cpuid was at the time.
>
> ==
> kernel trap 12 with interrupts disabled
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 2; apic id = 02
> fault virtual address = 0x104
> fault code = supervisor read, page not present
> instruction pointer = 0x20:0xc066ca51
> stack pointer = 0x28:0xe6ec0c90
> frame pointer = 0x28:0xe6ec0c9c
> code segment= base 0x0, limit 0xf, type 0x1b
> = DPL 0, pres 1, def32 1, gran 1
> processor eflags= resume, IOPL = 0
> current process = 9 (thread taskq)
> trap number = 12
> panic: page fault
> cpuid = 2
> Uptime: 6d6h23m45s
> Dumping 3327 MB (2 chunks)
> chunk 0: 1MB (159 pages) ... ok
> chunk 1: 3327MB (851624 pages) 3311 3295 3279 3263 3247 3231 3215 3199
> 3183 3167 3151 3135 3119 3103 3087 3071 3055 3039 3023 3007 2991 2975 2959
> 2943 2927 2911 2895 2879 2863 2847 2831 2815 2799 2783 2767 2751 2735 2719
> 2703 2687 2671 2655 2639 2623 2607 2591 2575 2559 2543 2527 2511 2495 2479
> 2463 2447 2431 2415 2399 2383 2367 2351 2335 2319 2303 2287 2271 2255 2239
> 2223 2207 2191 2175 2159 2143 2127 2111 2095 2079 2063 2047 2031 2015 1999
> 1983 1967 1951 1935 1919 1903 1887 1871 1855 1839 1823 1807 1791 1775 1759
> 1743 1727 1711 1695 1679 1663 1647 1631 1615 1599 1583 1567 1551 1535 1519
> 1503 1487 1471 1455 1439 1423 1407 1391 1375 1359 1343 1327 1311 1295 1279
> 1263 1247 1231 1215 1199 1183 1167 1151 1135 1119 1103 1087 1071 1055 1039
> 1023 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751
> 735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463
> 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175
> 159 143 127 111 95 79 63 47 31 15
>
> #0 doadump () at pcpu.h:165
> 165 __asm __volatile("movl %%fs:0,%0" : "=r" (td));
>
>
> What might be the cause for this? It is the in the same place every time.
> Once the machine hung and had to be powercycled. But on the screen was the
> same page fault error on the same process.
>
frame 0 useless. You need the frame after calltrap().
And:
> instruction pointer = 0x20:0xc066ca51
list *0xc066ca51
Generally a bt will show the needed information.
Likely cause: file system corruption, caused by background_fsck, but a
backtrace should show more.
--
Mel
Problem with today's modular software: they start with the modules
and never get to the software part.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Page Fault.
Have a machine, Dell dual CPU/quad core Xeon. Runs FBSD 6.2.
Custom kernel, with IPFW compiled in and using SMP.
FreeBSD 6.2-RELEASE FreeBSD 6.2-RELEASE #1: Wed Jan 23
12:17:29 PST 2008
It runs, Dovecot, Postfix, Mysql, Apache. Standard email stuff. Put into
production in March, ran perfect until July 29th when it rebooted by
itself.
It rebooted 2 more times in the last few months on its own. But in the
last 6 weeks it has become a weekly occurance, with uptime no more than
6-7 days at most.
The last 2 times I have cores and have run kgdb on them. Both vmcore's
show the same things. Same pointers etc, the only difference is what the
cpuid was at the time.
==
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
cpuid = 2; apic id = 02
fault virtual address = 0x104
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc066ca51
stack pointer = 0x28:0xe6ec0c90
frame pointer = 0x28:0xe6ec0c9c
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= resume, IOPL = 0
current process = 9 (thread taskq)
trap number = 12
panic: page fault
cpuid = 2
Uptime: 6d6h23m45s
Dumping 3327 MB (2 chunks)
chunk 0: 1MB (159 pages) ... ok
chunk 1: 3327MB (851624 pages) 3311 3295 3279 3263 3247 3231 3215 3199
3183 3167 3151 3135 3119 3103 3087 3071 3055 3039 3023 3007 2991 2975 2959
2943 2927 2911 2895 2879 2863 2847 2831 2815 2799 2783 2767 2751 2735 2719
2703 2687 2671 2655 2639 2623 2607 2591 2575 2559 2543 2527 2511 2495 2479
2463 2447 2431 2415 2399 2383 2367 2351 2335 2319 2303 2287 2271 2255 2239
2223 2207 2191 2175 2159 2143 2127 2111 2095 2079 2063 2047 2031 2015 1999
1983 1967 1951 1935 1919 1903 1887 1871 1855 1839 1823 1807 1791 1775 1759
1743 1727 1711 1695 1679 1663 1647 1631 1615 1599 1583 1567 1551 1535 1519
1503 1487 1471 1455 1439 1423 1407 1391 1375 1359 1343 1327 1311 1295 1279
1263 1247 1231 1215 1199 1183 1167 1151 1135 1119 1103 1087 1071 1055 1039
1023 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751
735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463
447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175
159 143 127 111 95 79 63 47 31 15
#0 doadump () at pcpu.h:165
165 __asm __volatile("movl %%fs:0,%0" : "=r" (td));
What might be the cause for this? It is the in the same place every time.
Once the machine hung and had to be powercycled. But on the screen was the
same page fault error on the same process.
Is this flaky hardware?
Thanks,
Keith.
___
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 ' 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 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 ' 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 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 ' 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 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 ' 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 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 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 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 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 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]"
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, 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 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 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]"
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: Atheros Wireless Card Causes Page Fault
On Thu, Jul 17, 2008 at 9:38 AM, Edward Ruggeri <[EMAIL PROTECTED]> wrote: > Hi, > > This is a question about a hardware problem. I hope this is an > appropriate place to ask. > > I have a recently purchased Lenovo ThinkPad, with a Atheros 5212 > wireless card (well, dmesg says it's an Atheros 5212; I believe it). > It also has a wired internet connector, which works perfectly fine. I > wish I was writing you from that computer, but I am at work right now > and don't have the ThinkPad at my fingertips. I can update later > tonight, but perhaps you can spot my error with just the somewhat > incomplete information I have right now. My Lenovo representative informs me it may be a Ar5006ex, if that helps. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Atheros Wireless Card Causes Page Fault
Hi, This is a question about a hardware problem. I hope this is an appropriate place to ask. I have a recently purchased Lenovo ThinkPad, with a Atheros 5212 wireless card (well, dmesg says it's an Atheros 5212; I believe it). It also has a wired internet connector, which works perfectly fine. I wish I was writing you from that computer, but I am at work right now and don't have the ThinkPad at my fingertips. I can update later tonight, but perhaps you can spot my error with just the somewhat incomplete information I have right now. I have compiled the Atheros driver and wireless support into my kernel: "device ath device ath_hal device ath_rate_sample device wlan device wlan_wep device wlan_ccmp device wlan_tkip" The card is detected correctly upon system startup. If I write ifconfig_ath0="DHCP" into /etc/rc.conf (or, alternatively, use dhclient ath0) the system connects to the wireless router and gets an IP address successfully. (My wireless at home is unsecured). I go to test the connection in Lynx. Google loads (yay!). I submit a google search, that may load. But I rarely get a third page transmitted before I get a page fault. The error is quite like this person's (http://lists.freebsd.org/pipermail/freebsd-current/2006-September/065608.html), though his problem didn't seem to be resolved on the list. In particular, the system reports a "fatal trap 12: page fault while in kernel mode". Fault virtual address is 0x0, not 0xc, if it makes a difference. The fault code is also "supervisor read, page not present." The current process is ath0 taskq. To my (totally uneducated) eyes, this seems to be a driver problem. I am not certain of my wireless card's make/number, but I assume that it really is an Atheros 5212, not only because that's what FreeBSD says, but that's also what Lenovo ships as the basic ThinkPad card (I didn't go with Intel wireless). So if I'm using the right driver, I'm not sure what the issue might be. Thanks for any help you might have! Sincerely, -- Ned Ruggeri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Atheros Wireless Card Causes Page Fault
Hi, This is a question about a hardware problem. I hope this is an appropriate place to ask. I have a recently purchased Lenovo ThinkPad, with a Atheros 5212 wireless card (well, dmesg says it's an Atheros 5212; I believe it). It also has a wired internet connector, which works perfectly fine. I wish I was writing you from that computer, but I am at work right now and don't have the ThinkPad at my fingertips. I can update later tonight, but perhaps you can spot my error with just the somewhat incomplete information I have right now. I have compiled the Atheros driver and wireless support into my kernel: "device ath device ath_hal device ath_rate_sample device wlan device wlan_wep device wlan_ccmp device wlan_tkip" The card is detected correctly upon system startup. If I write ifconfig_ath0="DHCP" into /etc/rc.conf (or, alternatively, use dhclient ath0) the system connects to the wireless router and gets an IP address successfully. (My wireless at home is unsecured). I go to test the connection in Lynx. Google loads (yay!). I submit a google search, that may load. But I rarely get a third page transmitted before I get a page fault. The error is quite like this person's (http://lists.freebsd.org/pipermail/freebsd-current/2006-September/065608.html), though his problem didn't seem to be resolved on the list. In particular, the system reports a "fatal trap 12: page fault while in kernel mode". Fault virtual address is 0x0, not 0xc, if it makes a difference. The fault code is also "supervisor read, page not present." The current process is ath0 taskq. To my (totally uneducated) eyes, this seems to be a driver problem. I am not certain of my wireless card's make/number, but I assume that it really is an Atheros 5212, not only because that's what FreeBSD says, but that's also what Lenovo ships as the basic ThinkPad card (I didn't go with Intel wireless). So if I'm using the right driver, I'm not sure what the issue might be. Thanks for any help you might have! Sincerely, -- Ned Ruggeri ___ 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 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: reboot after panic : page fault for two consecutive days now with FreeBSD stable 7.0
Edwin L. Culp wrote:
Kris Kennaway <[EMAIL PROTECTED]> escribió:
eculp wrote:
This is on a relatively new Dell dualcore with 4G of ram running up
to date stable. I'm not on site so I have no idea what might be
provoking these crashes. In fact in many years of running FreeBSD
I've not seen something just happen like this. It is a
simi-production machine that cvsups daily and builds and installs a
new world and kernel. Ports are updated about once a week and
haven't seen any issues previously. It has been running 24/7 since
new, about 8 months.
3 files were generated info, bounds and vmcore. The info file follows:
Dump header from device /dev/mfid0s1b
Architecture: i386
Architecture Version: 2
Dump Length: 341225472B (325 MB)
Blocksize: 512
Dumptime: Wed Jun 11 12:34:24 2008
Hostname: casasponti.net
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 7.0-STABLE #258: Tue Jun 10 05:54:42 CDT 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/ENCONTACTO
Panic String: page fault
Dump Parity: 2395754794
Bounds: 2
Dump Status: good
the vmcore is about 300M so I'm not attaching it;) I could put it on
line at a moments notice. I think that what I need is probably a
crash course on debugging a crash and I really don't know where to
start since after over 10 years with freebsd I've never needed it.
Any help, suggestions, etc. would be greatly appreciated.
See the developers' handbook chapter on kernel debugging.
However, panics that "suddenly" start happening frequently on a system
that has been stable for a while with no OS or workload changes made,
are usually due to the hardware starting to fail.
Kris
I got as far as I could. I recompiled the kernel with debuging and
waited for a new panic. I got the fourth one a few minutes ago and went
as far as I could with the handbook.
# kgdb kernel.debug /var/crash/vmcore.4
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= 0x0
fault code= supervisor write, page not present
instruction pointer= 0x20:0xc0716ba9
stack pointer= 0x28:0xe6d2bc4c
frame pointer= 0x28:0xe6d2bc4c
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= 13 (swi4: clock sio)
trap number= 12
panic: page fault
cpuid = 0
Uptime: 1d4h34m22s
Physical memory: 3315 MB
Dumping 273 MB: 258 242 226 210 194 178 162 146 130 114 98 82 66 50 34 18 2
Reading symbols from /boot/kernel/mfi_linux.ko...Reading symbols from
/boot/kernel/mfi_linux.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/mfi_linux.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/fdescfs.ko...Reading symbols from
/boot/kernel/fdescfs.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/fdescfs.ko
#0 doadump () at pcpu.h:195
195__asm __volatile("movl %%fs:0,%0" : "=r" (td));
That is as far as I got, any suggestions appreciated. I'm going to check
the others and see if the get further.
I believe the instructions tell you to run 'bt' :) However, my advice
re failing hardware remains in effect.
Kris
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: reboot after panic : page fault for two consecutive days now with FreeBSD stable 7.0
Kris Kennaway <[EMAIL PROTECTED]> escribió:
eculp wrote:
This is on a relatively new Dell dualcore with 4G of ram running up
to date stable. I'm not on site so I have no idea what might be
provoking these crashes. In fact in many years of running FreeBSD
I've not seen something just happen like this. It is a
simi-production machine that cvsups daily and builds and installs a
new world and kernel. Ports are updated about once a week and
haven't seen any issues previously. It has been running 24/7 since
new, about 8 months.
3 files were generated info, bounds and vmcore. The info file follows:
Dump header from device /dev/mfid0s1b
Architecture: i386
Architecture Version: 2
Dump Length: 341225472B (325 MB)
Blocksize: 512
Dumptime: Wed Jun 11 12:34:24 2008
Hostname: casasponti.net
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 7.0-STABLE #258: Tue Jun 10 05:54:42 CDT 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/ENCONTACTO
Panic String: page fault
Dump Parity: 2395754794
Bounds: 2
Dump Status: good
the vmcore is about 300M so I'm not attaching it;) I could put it
on line at a moments notice. I think that what I need is probably
a crash course on debugging a crash and I really don't know where
to start since after over 10 years with freebsd I've never needed
it. Any help, suggestions, etc. would be greatly appreciated.
See the developers' handbook chapter on kernel debugging.
However, panics that "suddenly" start happening frequently on a
system that has been stable for a while with no OS or workload
changes made, are usually due to the hardware starting to fail.
Kris
I got as far as I could. I recompiled the kernel with debuging and
waited for a new panic. I got the fourth one a few minutes ago and
went as far as I could with the handbook.
# kgdb kernel.debug /var/crash/vmcore.4
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 = 0x0
fault code = supervisor write, page not present
instruction pointer = 0x20:0xc0716ba9
stack pointer = 0x28:0xe6d2bc4c
frame pointer = 0x28:0xe6d2bc4c
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 = 13 (swi4: clock sio)
trap number = 12
panic: page fault
cpuid = 0
Uptime: 1d4h34m22s
Physical memory: 3315 MB
Dumping 273 MB: 258 242 226 210 194 178 162 146 130 114 98 82 66 50 34 18 2
Reading symbols from /boot/kernel/mfi_linux.ko...Reading symbols from
/boot/kernel/mfi_linux.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/mfi_linux.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/fdescfs.ko...Reading symbols from
/boot/kernel/fdescfs.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/fdescfs.ko
#0 doadump () at pcpu.h:195
195 __asm __volatile("movl %%fs:0,%0" : "=r" (td));
That is as far as I got, any suggestions appreciated. I'm going to
check the others and see if the get further.
ed
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: reboot after panic : page fault for two consecutive days nowwith FreeBSD stable 7.0
I had a similar problem when I tried to use kgdb to diagnose a page fault. I found that it worked fine on another vmcore from the next crash - without any knowledge of the subject, I assume that sometimes when FreeBSD crashed it was unable to write a correct vmcore? Anyway, try it again with other vmcores; I did not specifically enable debugging in the kernel but still got a sensible trace. Yours, Mark > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of eculp > Sent: 11 June 2008 20:23 > To: Kris Kennaway > Cc: [EMAIL PROTECTED] > Subject: Re: reboot after panic : page fault for two > consecutive days nowwith FreeBSD stable 7.0 > > Quoting "Kris Kennaway" <[EMAIL PROTECTED]>: > > > eculp wrote: > >> This is on a relatively new Dell dualcore with 4G of ram > running up > >> to date stable. I'm not on site so I have no idea what might be > >> provoking these crashes. In fact in many years of running > FreeBSD > >> I've not seen something just happen like this. It is a > >> simi-production machine that cvsups daily and builds and > installs a > >> new world and kernel. Ports are updated about once a week and > >> haven't seen any issues previously. It has been running > 24/7 since > >> new, about 8 months. > >> > >> 3 files were generated info, bounds and vmcore. The info > file follows: > >> > >> Dump header from device /dev/mfid0s1b > >> Architecture: i386 > >> Architecture Version: 2 > >> Dump Length: 341225472B (325 MB) > >> Blocksize: 512 > >> Dumptime: Wed Jun 11 12:34:24 2008 > >> Hostname: casasponti.net > >> Magic: FreeBSD Kernel Dump > >> Version String: FreeBSD 7.0-STABLE #258: Tue Jun 10 > 05:54:42 CDT 2008 > >>[EMAIL PROTECTED]:/usr/obj/usr/src/sys/ENCONTACTO > >> Panic String: page fault > >> Dump Parity: 2395754794 > >> Bounds: 2 > >> Dump Status: good > >> > >> the vmcore is about 300M so I'm not attaching it;) I could put it > >> on line at a moments notice. I think that what I need is > probably > >> a crash course on debugging a crash and I really don't know where > >> to start since after over 10 years with freebsd I've never needed > >> it. Any help, suggestions, etc. would be greatly appreciated. > > > > See the developers' handbook chapter on kernel debugging. > > Thanks Kris. I did that and I'm assuming that since > debugging was not > enabled in my kernel I got: > > /usr/obj/usr/src/sys/ENCONTACTO # kgdb kernel.debug > /var/crash/vmcore.2 > 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"... > Cannot access memory at address 0x0 > (kgdb) > > I assume it will only work with the new kernel because the > kernel.debug only got to Cannot access memory at address 0x4b55. > Which means I have to wait for another crash. > > I have already compiled a new kernelwith debuging and will reboot > tonight to install the kernel and hopefully will never need > to test it. > > Thanks for your help, > > ed > > > > > However, panics that "suddenly" start happening frequently on a > > system that has been stable for a while with no OS or workload > > changes made, are usually due to the hardware starting to fail. > > > > Kris > > > > ___ > 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: reboot after panic : page fault for two consecutive days now with FreeBSD stable 7.0
Quoting "Kris Kennaway" <[EMAIL PROTECTED]>: eculp wrote: This is on a relatively new Dell dualcore with 4G of ram running up to date stable. I'm not on site so I have no idea what might be provoking these crashes. In fact in many years of running FreeBSD I've not seen something just happen like this. It is a simi-production machine that cvsups daily and builds and installs a new world and kernel. Ports are updated about once a week and haven't seen any issues previously. It has been running 24/7 since new, about 8 months. 3 files were generated info, bounds and vmcore. The info file follows: Dump header from device /dev/mfid0s1b Architecture: i386 Architecture Version: 2 Dump Length: 341225472B (325 MB) Blocksize: 512 Dumptime: Wed Jun 11 12:34:24 2008 Hostname: casasponti.net Magic: FreeBSD Kernel Dump Version String: FreeBSD 7.0-STABLE #258: Tue Jun 10 05:54:42 CDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ENCONTACTO Panic String: page fault Dump Parity: 2395754794 Bounds: 2 Dump Status: good the vmcore is about 300M so I'm not attaching it;) I could put it on line at a moments notice. I think that what I need is probably a crash course on debugging a crash and I really don't know where to start since after over 10 years with freebsd I've never needed it. Any help, suggestions, etc. would be greatly appreciated. See the developers' handbook chapter on kernel debugging. Thanks Kris. I did that and I'm assuming that since debugging was not enabled in my kernel I got: /usr/obj/usr/src/sys/ENCONTACTO # kgdb kernel.debug /var/crash/vmcore.2 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"... Cannot access memory at address 0x0 (kgdb) I assume it will only work with the new kernel because the kernel.debug only got to Cannot access memory at address 0x4b55. Which means I have to wait for another crash. I have already compiled a new kernelwith debuging and will reboot tonight to install the kernel and hopefully will never need to test it. Thanks for your help, ed However, panics that "suddenly" start happening frequently on a system that has been stable for a while with no OS or workload changes made, are usually due to the hardware starting to fail. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: reboot after panic : page fault for two consecutive days now with FreeBSD stable 7.0
eculp wrote: This is on a relatively new Dell dualcore with 4G of ram running up to date stable. I'm not on site so I have no idea what might be provoking these crashes. In fact in many years of running FreeBSD I've not seen something just happen like this. It is a simi-production machine that cvsups daily and builds and installs a new world and kernel. Ports are updated about once a week and haven't seen any issues previously. It has been running 24/7 since new, about 8 months. 3 files were generated info, bounds and vmcore. The info file follows: Dump header from device /dev/mfid0s1b Architecture: i386 Architecture Version: 2 Dump Length: 341225472B (325 MB) Blocksize: 512 Dumptime: Wed Jun 11 12:34:24 2008 Hostname: casasponti.net Magic: FreeBSD Kernel Dump Version String: FreeBSD 7.0-STABLE #258: Tue Jun 10 05:54:42 CDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ENCONTACTO Panic String: page fault Dump Parity: 2395754794 Bounds: 2 Dump Status: good the vmcore is about 300M so I'm not attaching it;) I could put it on line at a moments notice. I think that what I need is probably a crash course on debugging a crash and I really don't know where to start since after over 10 years with freebsd I've never needed it. Any help, suggestions, etc. would be greatly appreciated. See the developers' handbook chapter on kernel debugging. However, panics that "suddenly" start happening frequently on a system that has been stable for a while with no OS or workload changes made, are usually due to the hardware starting to fail. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: reboot after panic : page fault for two consecutive days now with FreeBSD stable 7.0
Quoting eculp <[EMAIL PROTECTED]>: This is on a relatively new Dell dualcore with 4G of ram running up to date stable. I'm not on site so I have no idea what might be provoking these crashes. In fact in many years of running FreeBSD I've not seen something just happen like this. It is a simi-production machine that cvsups daily and builds and installs a new world and kernel. Ports are updated about once a week and haven't seen any issues previously. It has been running 24/7 since new, about 8 months. 3 files were generated info, bounds and vmcore. The info file follows: Dump header from device /dev/mfid0s1b Architecture: i386 Architecture Version: 2 Dump Length: 341225472B (325 MB) Blocksize: 512 Dumptime: Wed Jun 11 12:34:24 2008 Hostname: casasponti.net Magic: FreeBSD Kernel Dump Version String: FreeBSD 7.0-STABLE #258: Tue Jun 10 05:54:42 CDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ENCONTACTO Panic String: page fault Dump Parity: 2395754794 Bounds: 2 Dump Status: good the vmcore is about 300M so I'm not attaching it;) I could put it on line at a moments notice. I think that what I need is probably a crash course on debugging a crash and I really don't know where to start since after over 10 years with freebsd I've never needed it. Any help, suggestions, etc. would be greatly appreciated. Forgot I did try to debug but got nowhere: /usr/obj/usr/src/sys/ENCONTACTO # kgdb kernel.debug /var/crash/vmcore.2 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"... Cannot access memory at address 0x0 (kgdb) Ignorance, I'm sure. Thanks, ed ___ 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]"
reboot after panic : page fault for two consecutive days now with FreeBSD stable 7.0
This is on a relatively new Dell dualcore with 4G of ram running up to date stable. I'm not on site so I have no idea what might be provoking these crashes. In fact in many years of running FreeBSD I've not seen something just happen like this. It is a simi-production machine that cvsups daily and builds and installs a new world and kernel. Ports are updated about once a week and haven't seen any issues previously. It has been running 24/7 since new, about 8 months. 3 files were generated info, bounds and vmcore. The info file follows: Dump header from device /dev/mfid0s1b Architecture: i386 Architecture Version: 2 Dump Length: 341225472B (325 MB) Blocksize: 512 Dumptime: Wed Jun 11 12:34:24 2008 Hostname: casasponti.net Magic: FreeBSD Kernel Dump Version String: FreeBSD 7.0-STABLE #258: Tue Jun 10 05:54:42 CDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ENCONTACTO Panic String: page fault Dump Parity: 2395754794 Bounds: 2 Dump Status: good the vmcore is about 300M so I'm not attaching it;) I could put it on line at a moments notice. I think that what I need is probably a crash course on debugging a crash and I really don't know where to start since after over 10 years with freebsd I've never needed it. Any help, suggestions, etc. would be greatly appreciated. Thanks, ed ___ 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 Panic: isp - page fault while in kernel mode
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? Listed below is the boot info: /boot/kernel/acpi.ko text=0x44e84 data=0x24e0+0x1b8c syms=[0x4+0x7dc0 +0x4+0xab62] 786428K of memory above 4GB ignored Copyright (c) 1992-2008 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 6.3-STABLE #11: Fri Apr 11 13:25:41 PDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LAACO WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant WARNING: MPSAFE network stack disabled, expect reduced performance. module_register: module pci/bce already exists! Module pci/bce failed to register: 17 module_register: module bce/miibus already exists! Module bce/miibus failed to register: 17 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU5160 @ 3.00GHz (3000.13-MHz 686- class CPU) Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 Features=0xbfebfbff,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> Features2=0x4e3bd,DCA> AMD Features=0x2000 AMD Features2=0x1 Cores per package: 2 real memory = 3487916032 (3326 MB) avail memory = 3408932864 (3251 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) hptrr: HPT RocketRAID controller driver v1.1 (Apr 11 2008 13:25:27) acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x908-0x90b on acpi0 acpi_hpet0: iomem 0xfed0-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 pcib0: on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci4: on pcib1 pcib2: at device 0.0 on pci4 pci5: on pcib2 pcib3: at device 0.0 on pci5 pci6: on pcib3 pcib4: at device 0.0 on pci6 pci7: on pcib4 bce0: mem 0xfa00-0xfbff irq 16 at device 0.0 on pci7 miibus0: on bce0 brgphy0: on miibus0 brgphy0: 1000baseSX-FDX, auto bce0: Ethernet address: 00:17:a4:77:00:0a bce0: [GIANT-LOCKED] bce0: ASIC (0x57081021); Rev (B2); Bus (PCI-X, 64-bit, 133MHz); F/W (0x01090605); Flags( MSI ) pcib5: at device 1.0 on pci5 pci8: on pcib5 pcib6: at device 0.3 on pci4 pci9: on pcib6 pcib7: at device 3.0 on pci0 pci10: on pcib7 pcib8: at device 0.0 on pci10 pci11: on pcib8 pcib9: at device 4.0 on pci11 pci12: on pcib9 ciss0: port 0x4000-0x40ff mem 0xfdb8-0xfdbf,0xfdb7-0xfdb77fff irq 18 at device 8.0 on pci11 ciss0: [GIANT-LOCKED] pcib10: at device 4.0 on pci0 pci13: on pcib10 ciss1: port 0x5000-0x50ff mem 0xfdd0-0xfddf,0xfdcf-0xfdcf0fff irq 19 at device 0.0 on pci13 ciss1: [GIANT-LOCKED] pcib11: at device 5.0 on pci0 pci16: on pcib11 pcib12: at device 0.0 on pci16 pci17: on pcib12 bge0: mem 0xfdef-0xfdef,0xfdee-0xfdee irq 18 at device 4.0 on pci17 bge0: Ethernet address: 00:17:a4:77:00:24 bge0: [GIANT-LOCKED] bge1: mem 0xfded-0xfded,0xfdec-0xfdec irq 19 at device 4.1 on pci17 bge1: Ethernet address: 00:17:a4:77:00:26 bge1: [GIANT-LOCKED] pcib13: at device 6.0 on pci0 pci19: on pcib13 isp0: port 0x6000-0x60ff mem 0xfdff-0xfdff3fff irq 19 at device 0.0 on pci19 isp0: [GIANT-LOCKED] isp0: Board Type 2422, Chip Revision 0x2, resident F/W Revision 4.0.70 isp1: 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 _
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:
<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 ?? ()
Any info is appreciated.
with
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&#
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: 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: panic: page fault - 6.0-RELEASE-p7 (now 6.1-RC2)
At 09:14 AM 5/5/2006, you wrote:
Hello,
We have a group of web and mail servers that run under a moderate
load. We recently upgraded them from 4/5.x to 6.0. While we
thought we had done enough testing, apparently we hadn't and are now
experiencing panic's on a number of the servers. Some of our more
heavily loaded servers have been fine for days, while others will
crash every 6 to 36 hours. Below are some pieces of information
that may be helpful.
Should I be posting this to another list as well?
I know I can decrease NMBCLUSTERS dramatically, and give more memory
to the kernel if that would help.
I've read a number of similar cases where this panic was related to
a hardware failure, and while I can't rule that out completely, it
does seem unusual that several servers are apparently having the
same problem. Could it be that hardware problems existed before the
upgrade, but are now brought out by the increased load caused by the
new OS version and other installed software? We have IPMI cards in
some of the crashing servers and they all report normal
temperatures, fan speeds, and voltages. Nothing unusual in the event logs.
I'm willing to dig deeper and do more testing if anyone has suggestions.
As suggested, we have upgraded to 6.1-RC2 and are experiencing the
same or a very similar panic. Some things have changed on the
system, so I'll re-post our config, backtrace and dmesg again.
Also, in the past I have seen kgdb report the process that caused the
panic, as well as some other information when first loaded, but
sometimes it doesn't show that information - am I doing something
wrong there? It has shown that information before, and it has always
been tcpserver from the ucspi-tcp-0.88_2 port.
Differences from the 6.1-RC2 GENERIC kernel config
---
#cpuI486_CPU
cpu I586_CPU
cpu I686_CPU
ident MAIL_6_1
options SUIDDIR
options QUOTA
options IPFIREWALL
options IPFIREWALL_VERBOSE
options IPFIREWALL_VERBOSE_LIMIT=10
options NMBCLUSTERS=65536
options KVA_PAGES="640"
options VM_KMEM_SIZE_MAX=(512*1048576)
options VM_KMEM_SIZE_SCALE=2
options ASR_COMPAT
options SHMMAXPGS=131072
options SEMMNI=128
options SEMMNS=512
options SEMUME=100
options SEMMNU=256
---
---
mail-da-5# kgdb /boot/kernel/kernel.debug vmcore.8
[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:
#0 doadump () at pcpu.h:165
165 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) bt
#0 doadump () at pcpu.h:165
#1 0x6064e239 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:402
#2 0x6064e4d0 in panic (fmt=0x60894857 "%s") at
/usr/src/sys/kern/kern_shutdown.c:558
#3 0x608496d4 in trap_fatal (frame=0x9c8f7ad8, eva=172) at
/usr/src/sys/i386/i386/trap.c:836
#4 0x6084943b in trap_pfault (frame=0x9c8f7ad8, usermode=0, eva=172)
at /usr/src/sys/i386/i386/trap.c:744
#5 0x60849079 in trap (frame=
{tf_fs = 1619263496, tf_es = 1627652136, tf_ds = 40, tf_edi =
55, tf_esi = 0, tf_ebp = -1668318412, tf_isp = -1668318460, tf_ebx =
-1668318064, tf_edx = 1738397568, tf_ecx = 0, tf_eax = 4, tf_trapno =
12, tf_err = 2, tf_eip = 1617891744, tf_cs = 32, tf_eflags = 66182,
tf_esp = 1835631104, tf_ss = 0})
at /usr/src/sys/i386/i386/trap.c:434
#6 0x6083890a in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#7 0x606f11a0 in ip_ctloutput (so=0x4, sopt=0x9c8f7c90) at atomic.h:146
#8 0x6070123b in tcp_ctloutput (so=0x66b34858, sopt=0x9c8f7c90) at
/usr/src/sys/netinet/tcp_usrreq.c:1038
#9 0x60687c04 in sosetopt (so=0x66b34858, sopt=0x9c8f7c90) at
/usr/src/sys/kern/uipc_socket.c:1560
#10 0x6068ce95 in kern_setsockopt (td=0x679dd780, s=0, level=4,
name=4, val=0x679dd780, valseg=UIO_USERSPACE,
valsize=0) at /usr/src/sys/kern/uipc_syscalls.c:1351
#11 0x6068cdc6 in setsockopt (td=0x679dd780, uap=0x4) at
/usr/src/sys/kern/uipc_syscalls.c:1307
#12 0x608499eb in syscall (frame=
{tf_fs = 1606352955, tf_es = 59, tf_ds = 1606352955, tf_edi =
1606413432, tf_esi = 3, tf_ebp = 1606413224, tf_isp = -1668317852,
tf_ebx = 0, tf_edx = 2, tf_ecx = 134545464, tf_eax = 105, tf_trapno =
12, tf_err = 2, tf_eip = 672065711, tf_cs = 51, tf_eflags = 514,
tf_esp = 1606413180, tf_ss = 59})
at /usr/src/sys/i386/i386/trap.c:981
#13
Re: panic: page fault - 6.0-RELEASE-p7
On Fri, May 05, 2006 at 09:14:04AM -0600, Nick Wood wrote: > Hello, > > We have a group of web and mail servers that run under a moderate > load. We recently upgraded them from 4/5.x to 6.0. While we thought > we had done enough testing, apparently we hadn't and are now > experiencing panic's on a number of the servers. Some of our more > heavily loaded servers have been fine for days, while others will > crash every 6 to 36 hours. Below are some pieces of information that > may be helpful. Try 6.1 first in case the bug is already fixed. Kris pgpPzXZAJeLJa.pgp Description: PGP signature
panic: page fault - 6.0-RELEASE-p7
Hello,
We have a group of web and mail servers that run under a moderate
load. We recently upgraded them from 4/5.x to 6.0. While we thought
we had done enough testing, apparently we hadn't and are now
experiencing panic's on a number of the servers. Some of our more
heavily loaded servers have been fine for days, while others will
crash every 6 to 36 hours. Below are some pieces of information that
may be helpful.
Should I be posting this to another list as well?
I know I can decrease NMBCLUSTERS dramatically, and give more memory
to the kernel if that would help.
I've read a number of similar cases where this panic was related to a
hardware failure, and while I can't rule that out completely, it does
seem unusual that several servers are apparently having the same
problem. Could it be that hardware problems existed before the
upgrade, but are now brought out by the increased load caused by the
new OS version and other installed software? We have IPMI cards in
some of the crashing servers and they all report normal temperatures,
fan speeds, and voltages. Nothing unusual in the event logs.
I'm willing to dig deeper and do more testing if anyone has suggestions.
Differences from GENERIC:
--
#cpuI486_CPU
#cpuI586_CPU
cpu I686_CPU
ident PAYMAIL
options SUIDDIR
options QUOTA
options IPFIREWALL
options IPFIREWALL_VERBOSE
options IPFIREWALL_VERBOSE_LIMIT=10
options NMBCLUSTERS=65536
options KVA_PAGES="640"
options VM_KMEM_SIZE_MAX=(512*1048576)
options VM_KMEM_SIZE_SCALE=2
options ASR_COMPAT
options SHMMAXPGS=131072
options SEMMNI=128
options SEMMNS=512
options SEMUME=100
options SEMMNU=256
--
--
mail-da-2# kgdb /boot/kernel/kernel.debug vmcore.2
[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:
ber = 12
panic: page fault
Uptime: 1d6h4m36s
Dumping 2047 MB (3 chunks)
chunk 0: 1MB (158 pages) ... ok
chunk 1: 2046MB (523773 pages) 2031 2015 1999 1983 1967 1951 1935
1919 1903 1887 1871 1855 1839 1823 1807 1791 1775 1759 1743 1727 1711
1695 1679 1663 1647 1631 1615 1599 1583 1567 1551 1535 1519 1503 1487
1471 1455 1439 1423 1407 1391 1375 1359 1343 1327 1311 1295 1279 1263
1247 1231 1215 1199 1183 1167 1151 1135 1119 1103 1087 1071 1055 1039
1023 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767
751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495
479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223
207 191 175 159 143 127 111 95 79 63 47 31 15 ... ok
chunk 2: 1MB (128 pages)
#0 doadump () at pcpu.h:165
165 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) bt
#0 doadump () at pcpu.h:165
#1 0x606384aa in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399
#2 0x60638740 in panic (fmt=0x6085598b "%s") at
/usr/src/sys/kern/kern_shutdown.c:555
#3 0x6080ebf8 in trap_fatal (frame=0x9c497ad8, eva=172) at
/usr/src/sys/i386/i386/trap.c:831
#4 0x6080e963 in trap_pfault (frame=0x9c497ad8, usermode=0, eva=172)
at /usr/src/sys/i386/i386/trap.c:742
#5 0x6080e5c1 in trap (frame=
{tf_fs = 1692663816, tf_es = 1680080936, tf_ds = 40, tf_edi =
55, tf_esi = 0, tf_ebp = -1672905932, tf_isp = -1672905980, tf_ebx =
-1672905584, tf_edx = 1677080448, tf_ecx = 0, tf_eax = 4, tf_trapno =
12, tf_err = 2, tf_eip = 1617791092, tf_cs = 32, tf_eflags = 66182,
tf_esp = 1773435648, tf_ss = 0}) at /usr/src/sys/i386/i386/trap.c:432
#6 0x607fe6aa in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#7 0x606d8874 in ip_ctloutput (so=0x4, sopt=0x9c497c90) at atomic.h:146
#8 0x606e88ef in tcp_ctloutput (so=0x64e419bc, sopt=0x9c497c90) at
/usr/src/sys/netinet/tcp_usrreq.c:1036
#9 0x60671c00 in sosetopt (so=0x64e419bc, sopt=0x9c497c90) at
/usr/src/sys/kern/uipc_socket.c:1553
#10 0x60676e5d in kern_setsockopt (td=0x63f63780, s=0, level=4,
name=4, val=0x63f63780, valseg=UIO_USERSPACE, valsize=0)
at /usr/src/sys/kern/uipc_syscalls.c:1331
#11 0x60676d8e in setsockopt (td=0x63f63780, uap=0x4) at
/usr/src/sys/kern/uipc_syscalls.c:1287
#12 0x6080ef0f in syscall (frame=
{tf_fs = 1606352955, tf_es = 59, tf_ds = 1606352955,
Re: Page Fault - Wireless problem?
> Unread portion of the kernel message buffer:
> ural0: could not transmit buffer: SHORT_XFER
>
>
> Fatal trap 12: page fault while in kernel mode
> fault virtual address = 0x4
> fault code = supervisor read, page not present
> instruction pointer = 0x20:0xc0667091
> stack pointer = 0x28:0xd33e4c00
> frame pointer = 0x28:0xd33e4c0c
> 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 = 32 (irq21: uhci0 uhci1+)
> trap number = 12
> panic: page fault
I am not a USB/Ralink expert, but it the node can be removed
mid-transmission elsewhere (ural_free_tx_list) on input errors.
I don't know about threading issues that would require extra locking
as well:
in sys/dev/usb/
--- if_ural.c.orig Sun Jan 29 08:16:36 2006
+++ if_ural.c Thu Feb 23 08:30:36 2006
@@ -881,8 +881,10 @@
m_freem(data->m);
data->m = NULL;
- ieee80211_free_node(data->ni);
- data->ni = NULL;
+ if (data->ni != NULL) {
+ ieee80211_free_node(data->ni);
+ data->ni = NULL;
+ }
sc->tx_queued--;
ifp->if_opackets++;
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Page Fault - Wireless problem?
I am getting the following panic that happens intermittently using 6,0
and 6.1 prerelease with GENERIC and modified kermels
[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:
ural0: could not transmit buffer: SHORT_XFER
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x4
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc0667091
stack pointer = 0x28:0xd33e4c00
frame pointer = 0x28:0xd33e4c0c
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 = 32 (irq21: uhci0 uhci1+)
trap number = 12
panic: page fault
Uptime: 1h4m21s
Dumping 479 MB (2 chunks)
chunk 0: 1MB (157 pages) ... ok
chunk 1: 479MB (122608 pages) 463 447 431 415 399 383 367 351 335 319
303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15
#0 doadump () at pcpu.h:165
165 __asm __volatile("movl %%fs:0,%0" : "=r" (td));
(kgdb) where
#0 doadump () at pcpu.h:165
#1 0xc05db1a2 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399
#2 0xc05db438 in panic (fmt=0xc07b409e "%s")
at /usr/src/sys/kern/kern_shutdown.c:555
#3 0xc0772294 in trap_fatal (frame=0xd33e4bc0, eva=4)
at /usr/src/sys/i386/i386/trap.c:836
#4 0xc0771ffb in trap_pfault (frame=0xd33e4bc0, usermode=0, eva=4)
at /usr/src/sys/i386/i386/trap.c:744
#5 0xc0771c59 in trap (frame=
{tf_fs = 8, tf_es = 40, tf_ds = 40, tf_edi = -1020522496, tf_esi =
0, tf_ebp = -750892020, tf_isp = -750892052, tf_ebx = -1020519468,
tf_edx = -1020526944, tf_ecx = -1021865984, tf_eax = 0, tf_trapno = 12,
tf_err = 0, tf_eip = -1067028335, tf_cs = 32, tf_eflags = 66118, tf_esp
= -1020519468, tf_ss = -1020479488}) at /usr/src/sys/i386/i386/trap.c:434
#6 0xc0761cfa in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#7 0xc0667091 in ieee80211_free_node (ni=0x0)
at /usr/src/sys/net80211/ieee80211_node.c:1573
#8 0xc0575307 in ural_txeof (xfer=0xc34ba100, priv=0xc32c1bd4,
status=USBD_NORMAL_COMPLETION) at /usr/src/sys/dev/usb/if_ural.c:884
#9 0xc058d24e in usb_transfer_complete (xfer=0xc34ba100)
at /usr/src/sys/dev/usb/usbdi.c:863
#10 0xc056afd8 in ehci_idone (ex=0xc34ba100) at
/usr/src/sys/dev/usb/ehci.c:875
#11 0xc056aeb3 in ehci_check_intr (sc=0xc3179000, ex=0xc34ba100)
---Type to continue, or q to quit---
at /usr/src/sys/dev/usb/ehci.c:760
#12 0xc056aded in ehci_softintr (v=0xc3179000)
at /usr/src/sys/dev/usb/ehci.c:694
#13 0xc058a56d in usb_schedsoftintr (bus=0x0) at
/usr/src/sys/dev/usb/usb.c:871
#14 0xc056abce in ehci_intr1 (sc=0xc3179000) at
/usr/src/sys/dev/usb/ehci.c:594
#15 0xc056ab0e in ehci_intr (v=0xc3179000) at
/usr/src/sys/dev/usb/ehci.c:553
#16 0xc05c6b79 in ithread_loop (arg=0xc3088280)
at /usr/src/sys/kern/kern_intr.c:547
#17 0xc05c5e00 in fork_exit (callout=0xc05c6a20 ,
arg=0xc3088280, frame=0xd33e4d38) at /usr/src/sys/kern/kern_fork.c:789
#18 0xc0761d5c in fork_trampoline () at
/usr/src/sys/i386/i386/exception.s:208
uname -a
FreeBSD rainbow.Belkin 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #4: Thu Feb
16 23:19:36 GMT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/DAVES
i386
dmesg part
ural0: Belkin Belkin 54g USB Network Adapter, rev 2.00/0.01, addr 2
ural0: MAC/BBP RT2570 (rev 0x05), RF RT2526
ural0: Ethernet address: 00:11:50:8a:93:47
ural0: if_start running deferred for Giant
This e-mail and the information contained is confidential and is intended
solely for the person to whom it is addressed.
If you are not the intended recipient or have received it in error we would appreciate a prompt notice that it has been wrongly despatched and will reimburse any reasonable cost involved in notifying us. We thank you for your help in this regard.
We would also advise that you should not use, disclose or copy this information in any medium, as if you do, you may be breaking the law and thereby incurring liability.
We do not accept any liability to any third party acting or failing to act on
any information contained in this e-mail
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.0 Release kernel panic - page fault
Hello,
Thanks for your reply. Actually i experienced page faults mostly
when browsing web mostly from linux opera. So i installed firefox from
ports. It didnt cause any panic until yeserday, when it caused the
crash. And after that system panic occured while booting. Well i don't
know if a particular application is causing system panic but most
panics occured when i was using net.
Can you tell me if there are any other options for kernel
configuration file which can make the debugging mor verbose? I only
used -g option in my kernel config.
I'm attaching another crash dump which occurred last night when i was
browsing net.
Greetings,
Abhijit
kernel dump
Unread portion of the kernel message buffer:
panic: clist reservation botch
Uptime: 1h4m51s
Dumping 510 MB (2 chunks)
chunk 0: 1MB (159 pages) ... ok
chunk 1: 510MB (130528 pages) 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) where
#0 doadump () at pcpu.h:165
#1 0xc04c524a in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399
#2 0xc04c54e0 in panic (fmt=0xc06266e5 "clist reservation botch")
at /usr/src/sys/kern/kern_shutdown.c:555
#3 0xc04f90be in b_to_q (
src=0xc18318ae "ept: */*\r\nAccept-Language: en-us,en;q=0.5\r\nAccept-Encodi
ng: gzip,deflate\r\nAccept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7\r\nKeep-Alive
: 300\r\nConnection: keep-alive\r\nReferer: http://www.hi5.com/friend/di";..., am
ount=704, clistp=0xc1669838) at /usr/src/sys/kern/tty_subr.c:104
#4 0xc0539e44 in pppasyncstart (sc=0xc1a3c400)
at /usr/src/sys/net/ppp_tty.c:582
#5 0xc053539e in pppoutput (ifp=0xc1636400, m0=0xc171cb00, dst=0xc1b64310,
rtp=0xc17dbb58) at /usr/src/sys/net/if_ppp.c:961
#6 0xc054be9c in ip_output (m=0xc171cb00, opt=0xc1636400, ro=0xd5440bb0,
flags=0, imo=0x0, inp=0xc1814a8c) at /usr/src/sys/netinet/ip_output.c:776
#7 0xc0554bfa in tcp_output (tp=0xc1bddac8)
at /usr/src/sys/netinet/tcp_output.c:1080
#8 0xc055a661 in tcp_timer_rexmt (xtp=0xc1bddac8)
at /usr/src/sys/netinet/tcp_timer.c:579
#9 0xc04d12cf in softclock (dummy=0x0)
at /usr/src/sys/kern/kern_timeout.c:290
#10 0xc04b0e41 in ithread_loop (arg=0xc1581480)
at /usr/src/sys/kern/kern_intr.c:547
#11 0xc04b00c8 in fork_exit (callout=0xc04b0ce8 ,
at /usr/src/sys/kern/kern_shutdown.c:555
#3 0xc04f90be in b_to_q (
src=0xc18318ae "ept: */*\r\nAccept-Language: en-us,en;q=0.5\r\nAccept-Encodi
ng: gzip,deflate\r\nAccept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7\r\nKeep-Alive
: 300\r\nConnection: keep-alive\r\nReferer: http://www.hi5.com/friend/di";..., am
ount=704, clistp=0xc1669838) at /usr/src/sys/kern/tty_subr.c:104
#4 0xc0539e44 in pppasyncstart (sc=0xc1a3c400)
at /usr/src/sys/net/ppp_tty.c:582
#5 0xc053539e in pppoutput (ifp=0xc1636400, m0=0xc171cb00, dst=0xc1b64310,
rtp=0xc17dbb58) at /usr/src/sys/net/if_ppp.c:961
#6 0xc054be9c in ip_output (m=0xc171cb00, opt=0xc1636400, ro=0xd5440bb0,
flags=0, imo=0x0, inp=0xc1814a8c) at /usr/src/sys/netinet/ip_output.c:776
#7 0xc0554bfa in tcp_output (tp=0xc1bddac8)
at /usr/src/sys/netinet/tcp_output.c:1080
#8 0xc055a661 in tcp_timer_rexmt (xtp=0xc1bddac8)
at /usr/src/sys/netinet/tcp_timer.c:579
#9 0xc04d12cf in softclock (dummy=0x0)
at /usr/src/sys/kern/kern_timeout.c:290
#10 0xc04b0e41 in ithread_loop (arg=0xc1581480)
at /usr/src/sys/kern/kern_intr.c:547
#11 0xc04b00c8 in fork_exit (callout=0xc04b0ce8 ,
arg=0xc1581480, frame=0xd5440d38) at /usr/src/sys/kern/kern_fork.c:789
#12 0xc05ebe2c in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:208
(kgdb) bt full
#0 doadump () at pcpu.h:165
No locals.
#1 0xc04c524a in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399
first_buf_printf = 1
#2 0xc04c54e0 in panic (fmt=0xc06266e5 "clist reservation botch")
at /usr/src/sys/kern/kern_shutdown.c:555
td = (struct thread *) 0xc15cb480
bootopt = 260
newpanic = 0
ap = 0xc15cb480 "0¨\\Á uXÁ"
buf = "clist reservation botch", '\0'
#3 0xc04f90be in b_to_q (
src=0xc18318ae "ept: */*\r\nAccept-Language: en-us,en;q=0.5\r\nAccept-Encodi
ng: gzip,deflate\r\nAccept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7\r\nKeep-Alive
: 300\r\nConnection: keep-alive\r\nReferer: http://www.hi5.com/friend/di";..., am
ount=704, clistp=0xc1669838) at /usr/src/sys/kern/tty_subr.c:104
prev = (struct cblock *) 0x0
cblockp = (struct cblock *) 0xc1af9380
firstbyte = 0xc0c293c0 " \223ÂÀ`\224ÂÀÄÉdÀÀ)bÀz\acÀ"
lastbyte = 0x3
startmask = 0 '\0'
endmask = 0 '\0'
startbit = 0
endbit = -1067774825
num_between = 0
numc = 108
#4 0xc0539e44 in pppasyncstart (sc=0xc1a3c400)
at /usr/src/sys/net/ppp_tty.c:582
tp = (struct tty *) 0xc1669800
m = (struct mbuf *) 0xc171bd00
len = 878
Re: 6.0 Release kernel panic - page fault
Hello, Thanks for your reply. Actually i experienced page faults mostly when browsing web mostly from linux opera. So i installed firefox from ports. It didnt cause any panic until yeserday, when it caused the crash. And after that system panic occured while booting. Well i don't know if a particular application is causing system panic but most panics occured when i was using net. Can you tell me if there are any other options for kernel configuration file which can make the debugging mor verbose? I only used -g option in my kernel config. I'm attaching another crash dump which occurred last night when i was browsing net. Greetings, Abhijit On 23 Dec 2005 09:49:58 -0500, Lowell Gilbert <[EMAIL PROTECTED]> wrote: > Abhi <[EMAIL PROTECTED]> writes: > > >I'm experiencing kernel panics with 6.0 Release. I did a fresh > > install of 6.0 Release after playing with some linux distros and > > Freebsd 5.4 Release. The only problem i had was due to faulty RAM. I > > replaced the RAM and had no problems. But for somedays my system has > > started to panic randomly. All the crash dumps i got show something > > wrong in the file pcpu.h at line 165. > > That just means it's dumping core. You need to look a little > deeper for why it's doing so. > > > I'm ttaching my custom kernel configuration file and one crash dump i > > got with kgdb. I hope someone can tell me why this's happening, and if > > this's freebsd problem or hardware problem. > > In this case, it's smashing its own stack while doing a bcopy() > (or some related function). If that's not consistent, this > probably *is* a hardware problem. If it's dependable, then maybe > not. Try to track down commonalities in what the system is doing > when it panics. If possible. > -- If Karl, instead of writing a lot about Capital, had made a lot of Capital, it would have been much better. -- Karl Marx's Mother coredump1 Description: Binary data ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.0 Release kernel panic - page fault
Hello, Thanks for your reply. Actually i experienced page faults mostly when browsing web mostly from linux opera. So i installed firefox from ports. It didnt cause any panic until yeserday, when it caused the crash. And after that system panic occured while booting. Well i don't know if a particular application is causing system panic but most panics occured when i was using net. Can you tell me if there are any other options for kernel configuration file which can make the debugging mor verbose? I only used -g option in my kernel config. Greetings, Abhijit On 23 Dec 2005 09:49:58 -0500, Lowell Gilbert <[EMAIL PROTECTED]> wrote: > Abhi <[EMAIL PROTECTED]> writes: > > >I'm experiencing kernel panics with 6.0 Release. I did a fresh > > install of 6.0 Release after playing with some linux distros and > > Freebsd 5.4 Release. The only problem i had was due to faulty RAM. I > > replaced the RAM and had no problems. But for somedays my system has > > started to panic randomly. All the crash dumps i got show something > > wrong in the file pcpu.h at line 165. > > That just means it's dumping core. You need to look a little > deeper for why it's doing so. > > > I'm ttaching my custom kernel configuration file and one crash dump i > > got with kgdb. I hope someone can tell me why this's happening, and if > > this's freebsd problem or hardware problem. > > In this case, it's smashing its own stack while doing a bcopy() > (or some related function). If that's not consistent, this > probably *is* a hardware problem. If it's dependable, then maybe > not. Try to track down commonalities in what the system is doing > when it panics. If possible. > -- If Karl, instead of writing a lot about Capital, had made a lot of Capital, it would have been much better. -- Karl Marx's Mother ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.0 Release kernel panic - page fault
Abhi <[EMAIL PROTECTED]> writes: >I'm experiencing kernel panics with 6.0 Release. I did a fresh > install of 6.0 Release after playing with some linux distros and > Freebsd 5.4 Release. The only problem i had was due to faulty RAM. I > replaced the RAM and had no problems. But for somedays my system has > started to panic randomly. All the crash dumps i got show something > wrong in the file pcpu.h at line 165. That just means it's dumping core. You need to look a little deeper for why it's doing so. > I'm ttaching my custom kernel configuration file and one crash dump i > got with kgdb. I hope someone can tell me why this's happening, and if > this's freebsd problem or hardware problem. In this case, it's smashing its own stack while doing a bcopy() (or some related function). If that's not consistent, this probably *is* a hardware problem. If it's dependable, then maybe not. Try to track down commonalities in what the system is doing when it panics. If possible. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
6.0 Release kernel panic - page fault
Hi, I'm experiencing kernel panics with 6.0 Release. I did a fresh install of 6.0 Release after playing with some linux distros and Freebsd 5.4 Release. The only problem i had was due to faulty RAM. I replaced the RAM and had no problems. But for somedays my system has started to panic randomly. All the crash dumps i got show something wrong in the file pcpu.h at line 165. I'm ttaching my custom kernel configuration file and one crash dump i got with kgdb. I hope someone can tell me why this's happening, and if this's freebsd problem or hardware problem. Thanks for your help. Greetings, Abhijit - dmesg output: - 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 6.0-RELEASE #0: Sat Dec 17 13:02:27 IST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LUGBURZ Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel Pentium III (702.99-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383f9ff real memory = 535691264 (510 MB) avail memory = 519077888 (495 MB) npx0: [FAST] npx0: on motherboard npx0: INT 16 interface cpu0 on motherboard pcib0: pcibus 0 on motherboard pir0: on motherboard pci0: on pcib0 agp0: mem 0xe800-0xebff,0xeff8-0xefff irq 11 at device 1.0 on pci0 pcib1: at device 30.0 on pci0 pci1: on pcib1 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 uhci0: port 0xda00-0xda1f irq 9 at device 31.2 on pci0 uhci0: [GIANT-LOCKED] usb0: 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 pcm0: port 0xde00-0xdeff,0xdc00-0xdc3f irq 10 at device 31.5 on pci0 pcm0: [GIANT-LOCKED] pcm0: pmtimer0 on isa0 orm0: at iomem 0xc-0xc7fff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: 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 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: can't assign resources (memory) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (irq) Timecounter "TSC" frequency 702986027 Hz quality 800 Timecounters tick every 1.000 msec ad0: DMA limited to UDMA33, controller found non-ATA66 cable ad0: 19092MB at ata0-master UDMA33 acd0: CDRW at ata0-slave UDMA33 acd1: CDROM at ata1-master PIO4 Trying to mount root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted Loading configuration files. kernel dumps on /dev/ad0s1b Entropy harvesting: interrupts ethernet point_to_point kickstart . swapon: adding /dev/ad0s1b as swap device Starting file system checks: /dev/ad0s1a: 1542 files, 43159 used, 210656 free (1800 frags, 26107 blocks, 0.7% fragmentation) /dev/ad0s1h: DEFER FOR BACKGROUND CHECKING /dev/ad0s1f: DEFER FOR BACKGROUND CHECKING /dev/ad0s1e: DEFER FOR BACKGROUND CHECKING /dev/ad0s1g: DEFER FOR BACKGROUND CHECKING /dev/ad0s1d: DEFER FOR BACKGROUND CHECKING cd0 at ata0 bus 0 target 1 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed cd1 at ata1 bus 0 target 0 lun 0 cd1: Removable CD-ROM SCSI-0 device cd1: 16.000MB/s transfers cd1: Attempt to query device size failed: NOT READY, Medium not present WARNING: /data was not properly dismounted WARNING: /home was not properly dismounted WARNING: /tmp was not properly dismounted /tmp: mount pending error: blocks 16 files 5 WARNING: /usr was not properly dismounted WARNING: /var was not properly dismounted Setting hostname: localhost. lo0: flags=8049 mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet 127.0.0.1 netmask 0xff00 Additional routing options: . Starting devd. Mounting NFS file systems: . Creating and/or trimming log files: . Starting syslogd. Checking for core dump on /dev/ad0s1b... savecore: reboot after panic: page fault
Re: FreeBSD 6.0-RELEASE - panic: page fault
On Mon, 2005-12-12 at 11:35 +, Miguel Saturnino wrote:
> My server reboots sporadically (once a day, maximum) and I hope someone
> can shed some light on why this is happening.
>
> I've upgraded to 6.0-RELEASE yesterday but the symptoms remain...
> Attached is the backtrace of the crash dump and the relevant portion
> of /var/log/messages.
>
> My custom kernel is the generic kernel plus support for quotas.
>
> Also, during last buildworld I got a "segmentation fault" (only thing I
> have in /etc/make.conf is "CFLAGS= -O -pipe" and "NO_PROFILE= true"). I
> then tried it again (in the exact same conditions), and it worked. Don't
> know if that might indicate bad RAM (the only memory test I'm able to
> run is memtest but it can only lock (to test) about 15% of the total
> system memory...).
>
Since I got no answers, I'll reply to myself ;)
I have now replaced the memory, but the problem persists. So I guess
it's highly unlikely that the problem is with the RAM. I started saving
the output of top, vmstat and iostat at each minute, and this is from
the last records I got before the last crash (the machine is a web
server but has only a few low traffic sites):
top:
last pid: 29978; load averages: 0.00, 0.00, 0.00 up 0+16:10:46
19:41:00
123 processes: 1 running, 122 sleeping
Mem: 186M Active, 115M Inact, 64M Wired, 14M Cache, 60M Buf, 114M Free
Swap: 2048M Total, 2048M Free
vmstat:
===
procs memory page disk faults cpu
r b w avmfre flt re pi po fr sr ad0 in sy cs us sy id
0 2 0 517256 130988 84 0 0 0 90 4 0 214 42726 495 7 4
90
iostat:
===
tty ad0 cpu
tin tout KB/t tps MB/s us ni sy in id
0 12 13.06 6 0.07 7 0 3 0 90
latest backtrace:
=
Unread portion of the kernel message buffer:
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x24
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc0657a48
stack pointer = 0x28:0xd565eafc
frame pointer = 0x28:0xd565eb10
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = resume, IOPL = 0
current process = 37 (swi1: net)
trap number = 12
panic: page fault
Uptime: 16h11m16s
Dumping 510 MB (2 chunks)
chunk 0: 1MB (159 pages) ... ok
chunk 1: 510MB (130544 pages) 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 0xc0638202 in boot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:399
#2 0xc0638498 in panic (fmt=0xc084ece2 "%s")
at /usr/src/sys/kern/kern_shutdown.c:555
#3 0xc0808370 in trap_fatal (frame=0xd565eabc, eva=36)
at /usr/src/sys/i386/i386/trap.c:831
#4 0xc0807b12 in trap (frame=
{tf_fs = -1065418744, tf_es = -1046544344, tf_ds = -714801112,
tf_edi = 1, tf_esi = -1032972416, tf_ebp = -714740976, tf_isp =
-714741016, tf_ebx = -1046540928, tf_edx = -1032972416, tf_ecx =
-1064083040, tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip =
-1067091384, tf_cs = 32, tf_eflags = 589954, tf_esp = 40, tf_ss = 0})
at /usr/src/sys/i386/i386/trap.c:267
#5 0xc07f750a in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#6 0xc0657a48 in propagate_priority (td=0xc26e1780)
at /usr/src/sys/kern/subr_turnstile.c:233
#7 0xc06581f6 in turnstile_wait (lock=0xc09361a0, owner=0xc26e1780)
at /usr/src/sys/kern/subr_turnstile.c:628
#8 0xc062fa6c in _mtx_lock_sleep (m=0xc09361a0, tid=3248426368, opts=0,
file=0x0, line=0) at /usr/src/sys/kern/kern_mutex.c:553
#9 0xc06772bd in sf_buf_mext (addr=0xd4623000, args=0x0)
at /usr/src/sys/kern/uipc_syscalls.c:1690
#10 0xc066d6bd in mb_free_ext (m=0xc2162b00)
at /usr/src/sys/kern/uipc_mbuf.c:258
#11 0xc06748a4 in sbdrop_locked (sb=0xc1deb0c8, len=0) at mbuf.h:427
#12 0xc06d7938 in tcp_input (m=0xc1be3d00, off0=20)
at /usr/src/sys/netinet/tcp_input.c:2121
#13 0xc06cf1c1 in ip_input (m=0xc1be3d00)
at /usr/src/sys/netinet/ip_input.c:778
#14 0xc06ac483 in netisr_processqueue (ni=0xc09292d8)
at /usr/src/sys/net/netisr.c:236
#15 0xc06ac67e in swi_net (dummy=0x0) at /usr/src/sys/net/netisr.c:349
#16 0xc0623df9 in ithread_loop (arg=0xc19e4180)
at /usr/src/sys/kern/kern_intr.c:547
#17 0xc0623080 in fork_exit (callout=0xc0623ca0 ,
arg=0xc19e4180, frame=0xd565ed38)
at /usr/src/sys/kern/kern_fork.c:789
#18 0xc07f756c in fork_trampoline ()
at /usr/src/sys/i386/i386/exception.s:208
(kgdb) f 5
#5 0xc07f750a in calltrap () at /usr/src/sys/i386/i386/excepti
FreeBSD 6.0-RELEASE - panic: page fault
tel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Dec 12 01:32:48 tiger kernel: uhub2: 2 ports with 2 removable, self powered Dec 12 01:32:48 tiger kernel: uhci3: port 0xac00-0xac1f irq 16 at device 29.3 on pci0 Dec 12 01:32:48 tiger kernel: uhci3: [GIANT-LOCKED] Dec 12 01:32:48 tiger kernel: usb3: on uhci3 Dec 12 01:32:48 tiger kernel: usb3: USB revision 1.0 Dec 12 01:32:48 tiger kernel: uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Dec 12 01:32:48 tiger kernel: uhub3: 2 ports with 2 removable, self powered Dec 12 01:32:48 tiger kernel: ehci0: mem 0xf818-0xf81803ff irq 23 at device 29.7 on pci0 Dec 12 01:32:48 tiger kernel: ehci0: [GIANT-LOCKED] Dec 12 01:32:48 tiger kernel: usb4: EHCI version 1.0 Dec 12 01:32:48 tiger kernel: usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 Dec 12 01:32:48 tiger kernel: usb4: on ehci0 Dec 12 01:32:48 tiger kernel: usb4: USB revision 2.0 Dec 12 01:32:48 tiger kernel: uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 Dec 12 01:32:48 tiger kernel: uhub4: 8 ports with 8 removable, self powered Dec 12 01:32:48 tiger kernel: pcib1: at device 30.0 on pci0 Dec 12 01:32:48 tiger kernel: pci1: on pcib1 Dec 12 01:32:48 tiger kernel: rl0: port 0x9000-0x90ff mem 0xf800-0xf8ff irq 23 at device 3.0 on pci1 Dec 12 01:32:48 tiger kernel: miibus0: on rl0 Dec 12 01:32:48 tiger kernel: rlphy0: on miibus0 Dec 12 01:32:48 tiger kernel: rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Dec 12 01:32:48 tiger kernel: rl0: Ethernet address: 00:01:6c:28:f9:c0 Dec 12 01:32:48 tiger kernel: isab0: at device 31.0 on pci0 Dec 12 01:32:48 tiger kernel: isa0: on isab0 Dec 12 01:32:48 tiger kernel: atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 31.1 on pci0 Dec 12 01:32:48 tiger kernel: ata0: on atapci0 Dec 12 01:32:48 tiger kernel: ata1: on atapci0 Dec 12 01:32:48 tiger kernel: pci0: at device 31.3 (no driver attached) Dec 12 01:32:48 tiger kernel: acpi_tz0: on acpi0 Dec 12 01:32:48 tiger kernel: fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 Dec 12 01:32:48 tiger kernel: fdc0: [FAST] Dec 12 01:32:48 tiger kernel: pmtimer0 on isa0 Dec 12 01:32:48 tiger kernel: orm0: at iomem 0xd4000-0xd4fff on isa0 Dec 12 01:32:48 tiger kernel: atkbdc0: at port 0x60,0x64 on isa0 Dec 12 01:32:48 tiger kernel: atkbd0: irq 1 on atkbdc0 Dec 12 01:32:48 tiger kernel: kbd0 at atkbd0 Dec 12 01:32:48 tiger kernel: atkbd0: [GIANT-LOCKED] Dec 12 01:32:48 tiger kernel: ppc0: parallel port not found. Dec 12 01:32:48 tiger kernel: sc0: at flags 0x100 on isa0 Dec 12 01:32:48 tiger kernel: sc0: VGA <16 virtual consoles, flags=0x300> Dec 12 01:32:48 tiger kernel: sio0: configured irq 4 not in bitmap of probed irqs 0 Dec 12 01:32:48 tiger kernel: sio0: port may not be enabled Dec 12 01:32:48 tiger kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Dec 12 01:32:48 tiger kernel: sio0: type 8250 or not responding Dec 12 01:32:48 tiger kernel: sio1: configured irq 3 not in bitmap of probed irqs 0 Dec 12 01:32:48 tiger kernel: sio1: port may not be enabled Dec 12 01:32:48 tiger kernel: vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Dec 12 01:32:48 tiger kernel: Timecounter "TSC" frequency 2393193168 Hz quality 800 Dec 12 01:32:48 tiger kernel: Timecounters tick every 1.000 msec Dec 12 01:32:48 tiger kernel: ad0: 76319MB at ata0-master UDMA100 Dec 12 01:32:48 tiger kernel: Trying to mount root from ufs:/dev/ad0s1a Dec 12 01:32:48 tiger kernel: WARNING: / was not properly dismounted Dec 12 01:32:48 tiger kernel: WARNING: /tmp was not properly dismounted Dec 12 01:32:48 tiger kernel: WARNING: /usr was not properly dismounted Dec 12 01:32:48 tiger kernel: WARNING: /var was not properly dismounted Dec 12 01:32:48 tiger kernel: WARNING: /home was not properly dismounted Dec 12 01:32:48 tiger savecore: reboot after panic: page fault Dec 12 01:32:48 tiger savecore: writing core to vmcore.2 Dec 12 01:32:49 tiger kernel: rl0: link state changed to UP Dec 12 01:33:53 tiger ntpd[414]: ntpd 4.2.0-a Sun Dec 11 13:24:06 WET 2005 (1) Dec 12 01:34:00 tiger named[569]: starting BIND 9.3.1 Dec 12 01:34:01 tiger proftpd[593]: tiger.example.net - ProFTPD 1.2.9 (stable) (built Mon Jan 19 16:05:43 MST 2004) standalone mode STARTUP Dec 12 01:34:02 tiger named[569]: command channel listening on 127.0.0.1#953 Dec 12 01:34:02 tiger named[569]: command channel listening on ::1#953 Dec 12 01:34:07 tiger named[569]: running Dec 12 01:35:09 tiger fsck: /dev/ad0s1d: 958 files, 1000 used, 1015303 free (47 frags, 126907 blocks, 0.0% fragmentation) Dec 12 01:37:13 tiger fsck: /dev/ad0s1e: UNREF FILE I=361249 OWNER=root MODE=100755 Dec 12 01:37:13 tiger fsck: /dev/ad0s1e: SIZE=10084 MTIME=Jul 1 19:06 2005 (CLEARED) Dec 12 01:37:13 tiger fsck: /dev/ad0s1e: UNREF FILE I=558720 OWNER=root MODE=100555 Dec 12 01:37:13 tiger fsck: /dev/ad0s1e: SIZE=37925 MTIME=Nov 29 18:06 2005 (CLEARED) Dec 12 01:37:13 tiger
Re: Page fault in kernel mode, 6.0-RELEASE
Kris Kennaway <[EMAIL PROTECTED]> writes: > On Tue, Nov 15, 2005 at 11:48:15PM +0100, Guido Van Hoecke wrote: >> I am fairly new at FreeBSD. I installed a 'beastie' server with >> >> FreeBSD 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 >> [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC >> >> but it traps immediately after the boot menu with following output >> immediately after the boot menu: >> >> /boot/kernel/acpi.ko text=0x40c2c data=0x2160+0x1090 \ >> syms=[0x4+0x7810+0x4+0xa292] >> >> Fatal trap 12: page fault while in kernel mode >> fault virtual address = 0x8 >> fault code = supervisor read, page not present >> instruction pointer = 0x20:0xc079abb9 >> stack pointer = 0x28:0xc0c20d4c >> frame pointer = 0x28:0xc0c20d58 >> 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 () >> trap number = 12 >> panic: page fault >> Uptime: 1s >> >> Note that the /boot/kernel/acpi.ko line is absent if I boot with acpi >> disabled (menu option 2). But the trap info is not affected by slecting >> that boot option. > > Are you using other modules (e.g. nvidia driver)? No Kris, this is just when booting from the generic release cd's. I had an old Hercules 3d Prophet card and just used that, without loading anything special. > > Kris ___ 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 in kernel mode, 6.0-RELEASE
On Tue, Nov 15, 2005 at 11:48:15PM +0100, Guido Van Hoecke wrote: > I am fairly new at FreeBSD. I installed a 'beastie' server with > > FreeBSD 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC > > but it traps immediately after the boot menu with following output > immediately after the boot menu: > > /boot/kernel/acpi.ko text=0x40c2c data=0x2160+0x1090 \ > syms=[0x4+0x7810+0x4+0xa292] > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x8 > fault code = supervisor read, page not present > instruction pointer = 0x20:0xc079abb9 > stack pointer = 0x28:0xc0c20d4c > frame pointer = 0x28:0xc0c20d58 > 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 () > trap number = 12 > panic: page fault > Uptime: 1s > > Note that the /boot/kernel/acpi.ko line is absent if I boot with acpi > disabled (menu option 2). But the trap info is not affected by slecting > that boot option. Are you using other modules (e.g. nvidia driver)? Kris pgpPPSG6pJq9A.pgp Description: PGP signature
Page fault in kernel mode, 6.0-RELEASE
I am fairly new at FreeBSD. I installed a 'beastie' server with FreeBSD 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC but it traps immediately after the boot menu with following output immediately after the boot menu: /boot/kernel/acpi.ko text=0x40c2c data=0x2160+0x1090 \ syms=[0x4+0x7810+0x4+0xa292] Fatal trap 12: page fault while in kernel mode fault virtual address = 0x8 fault code = supervisor read, page not present instruction pointer = 0x20:0xc079abb9 stack pointer = 0x28:0xc0c20d4c frame pointer = 0x28:0xc0c20d58 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 () trap number = 12 panic: page fault Uptime: 1s Note that the /boot/kernel/acpi.ko line is absent if I boot with acpi disabled (menu option 2). But the trap info is not affected by slecting that boot option. This is a 1.7 Ghz P4 with 1Gb mry and a fast 250Gb drive fully dedicated (using normal partition scheme, not 'dangourously dedicated') to FreeBSD. It has an MSI 845 Pro2 motherboard. I had this trap during the first install yesterday. So I restarted the installation and all went fine. After the installation, I rebooted beastie and had no problems. I was able to work on it locally as well as over an ssh connection to it. Some time late at night, beastie trapped as reported above. Since then, it never got beyond this trap. That's it. Full stop! I looked into the BIOS setup, trying to change default settings that might influence the kernel, such as disabling APIC mode. No success. I booted the machine from a memtest86 CD and had it testing the memory during several hours. No errors were detected. I ran all test programs I could find (a.o. using Hiren's boot cd), and didn't find any problems with the PC. Still, I am pretty sure there must be a problem with that PC. Booting from the FreeBSD-6.0-RC1 or FreeBSD-5.4R cd's causes the same trap at the same point. Well, right now they just reboot after the menu. And so does FreeSBIE 1.1 (FreeBSD 5.3 Live CD) I've been further experimenting with the BIOS, I have upgraded it to the latest version available from MSI. Bottom line is that now it does not trap anymore. After the boot menu, it goes a bit furthre. It shows the CopyRight and Release info and reboots automaticlally without any further info. Is there anything I can do to get more info about the reason for this frustrating behaviour? I do hope that more kernel-knowledgeable people will be able to point my nose in the proper direction, given the consistant moment where the error occurs. This is so frustrating, and I almost do feel ashame to dump this onto the FreeBSD community, but I am desperate to get this server installed and running! Guido. ___ 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
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]"
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: Boot page fault - alternative kernel needed?
On Thu, Jul 28, 2005 at 10:28:18AM -0500, Kevin Kinsey wrote:
> Jason Morgan wrote:
>
> >I have an old laptop that I am finally trying to get FreeBSD installed on.
> >It was recently running Linux just fine, but I am having a tough time
> >getting FreeBSD installed on it. Here is the error I get when booting.
> >I have typed all that is visible on the screen when it crashes.
> >
> ># Begin
> >
> >isa0: on isab0
> >atapci0: port
> >0x3000-0x300f,0x376,0x170-0x177,0x
> >3f6,0x1f0-0x1f7 at device 1.1 on pci0
> >ata0: channel #0 on atapci0
> >ata1: channel #1 on atapci0
> >uhci0: at device 1.2 on pci0
> >
> >
> >Fatal trap 12: page fault while in kernel mode
> >fault virtual address = 0xeb97b
> >fault code = supervisor read, page not present
> >instruction pointer= 0x8:0xc00eb87c
> >stack pointer = 0x10:0xc10209f0
> >frame pointer = 0x10:0xc10209f0
> >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
> >
> ># End
> >
> >So, my question is: Is this the UHCI driver failing to load
> >(happens at this same point every time I try to boot it)?
> >Is there any way around this? Possible using a trimmed down
> >kernel to boot? Any suggestions?
> >
> >Thanks in advance,
> >Jason
> >
> >
>
> Kevin Kinsey wrote:
>
> Well, the error message seems to indicate that the
> swapper if failing ... but it could be that it's failing
> because the previously loaded uhci device code finds
> a bug in your hardware --- IANAE, but IIRC FBSD 5
> (&& you don't say what version you're using) doesn't
> always play well with APM, ACPI, or what-not on
> some older laptops.
>
> We probably need someone else to tell us the
> exact incantation, but you might be able to
> 'escape to loader prompt' and set the equivalent
> of {ACPI_LOAD =0} (like I said, not sure of exact
> syntax) before attempting to boot (see loader(8)
> in the on-line manual or on another machine).
>
> If you're trying FBSD 5, I've heard of some people
> having success with older laptops and FBSD 4.
> Otherwise, they can run 5 but without APM or
> ACPI support.
>
> Like I said, I can't say for certain that this is
> what your issue is, but if you've not got a working
> system, it probably can't hurt to futz around with
> it a bit.
>
> Hopefully somebody else knows the magic words
Well, I've tried everything I know to do. I've tried installing FBSD 4.11 as
well as tweaking settings
before booting the kernel. I've tried the following settings in various
combinations:
set hint.acpi.0.disabled=1
set hint.uhci.0.disabled=1
set hint.uhci.1.disabled=1
acpi_load=NO
No luck. Are there any other workarounds out there or something obvious that
I've missed?
Thanks for the help,
Jason
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot page fault - alternative kernel needed?
Jason Morgan wrote:
I have an old laptop that I am finally trying to get FreeBSD installed on.
It was recently running Linux just fine, but I am having a tough time
getting FreeBSD installed on it. Here is the error I get when booting.
I have typed all that is visible on the screen when it crashes.
# Begin
isa0: on isab0
atapci0: port 0x3000-0x300f,0x376,0x170-0x177,0x
3f6,0x1f0-0x1f7 at device 1.1 on pci0
ata0: channel #0 on atapci0
ata1: channel #1 on atapci0
uhci0: at device 1.2 on pci0
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xeb97b
fault code = supervisor read, page not present
instruction pointer= 0x8:0xc00eb87c
stack pointer = 0x10:0xc10209f0
frame pointer = 0x10:0xc10209f0
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
# End
So, my question is: Is this the UHCI driver failing to load
(happens at this same point every time I try to boot it)?
Is there any way around this? Possible using a trimmed down
kernel to boot? Any suggestions?
Thanks in advance,
Jason
Well, the error message seems to indicate that the
swapper if failing ... but it could be that it's failing
because the previously loaded uhci device code finds
a bug in your hardware --- IANAE, but IIRC FBSD 5
(&& you don't say what version you're using) doesn't
always play well with APM, ACPI, or what-not on
some older laptops.
We probably need someone else to tell us the
exact incantation, but you might be able to
'escape to loader prompt' and set the equivalent
of {ACPI_LOAD =0} (like I said, not sure of exact
syntax) before attempting to boot (see loader(8)
in the on-line manual or on another machine).
If you're trying FBSD 5, I've heard of some people
having success with older laptops and FBSD 4.
Otherwise, they can run 5 but without APM or
ACPI support.
Like I said, I can't say for certain that this is
what your issue is, but if you've not got a working
system, it probably can't hurt to futz around with
it a bit.
Hopefully somebody else knows the magic words
HTH,
Kevin Kinsey
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Boot page fault - alternative kernel needed?
I have an old laptop that I am finally trying to get FreeBSD installed on. It was recently running Linux just fine, but I am having a tough time getting FreeBSD installed on it. Here is the error I get when booting. I have typed all that is visible on the screen when it crashes. # Begin isa0: on isab0 atapci0: port 0x3000-0x300f,0x376,0x170-0x177,0x 3f6,0x1f0-0x1f7 at device 1.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 uhci0: at device 1.2 on pci0 Fatal trap 12: page fault while in kernel mode fault virtual address = 0xeb97b fault code = supervisor read, page not present instruction pointer= 0x8:0xc00eb87c stack pointer = 0x10:0xc10209f0 frame pointer = 0x10:0xc10209f0 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 # End So, my question is: Is this the UHCI driver failing to load (happens at this same point every time I try to boot it)? Is there any way around this? Possible using a trimmed down kernel to boot? Any suggestions? Thanks in advance, Jason ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Boot page fault - alternative kernel needed?
I have an old laptop that I am finally trying to get FreeBSD installed on. It was recently running Linux just fine, but I am having a tough time getting FreeBSD installed on it. Here is the error I get when booting. I have typed all that is visible on the screen when it crashes. # Begin isa0: on isab0 atapci0: port 0x3000-0x300f,0x376,0x170-0x177,0x 3f6,0x1f0-0x1f7 at device 1.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 uhci0: at device 1.2 on pci0 Fatal trap 12: page fault while in kernel mode fault virtual address = 0xeb97b fault code = supervisor read, page not present instruction pointer= 0x8:0xc00eb87c stack pointer = 0x10:0xc10209f0 frame pointer = 0x10:0xc10209f0 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 # End So, my question is: Is this the UHCI driver failing to load (happens at this same point every time I try to boot it)? Is there any way around this? Possible using a trimmed down kernel to boot? Any suggestions? Thanks in advance, Jason ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
page fault when starting system with new hard disk
FreeBSD 4.11-stable. details: FreeBSD enterprise 4.11-STABLE FreeBSD 4.11-STABLE #0: Sun Jan 30 22:07:15 PST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NEWKERNEL_20050130 i386 Put a new hard disk is my system today, and setup partitions for storing data files iso's etc. it is setup as a slave drive on the ide channel the master drive that freebsd lives on. It is a seagate barracuda 160 gb ata100. When I boot, I get this error: (couldnt write all of this down and it kept going:) ad7: Read commmand timeout tag=0 (something) -resetting (does this a few times with some other output) Then I get this: Fatal Trap12: page fault while in kernel mode fault virtual address =0x7800bc fault code=supervisor write, page not present instruction pointer =0x8:0xc01d72ec stack pointer = 0x10:0xc03698ec frame pointer = (same evil hex code) code segment = base0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def 32,1, gran1 processor eflags = interupt enabled, resume, fopl=0 current process= idle interupt mask = hio trap number= 12 panic: page fault syncing disks... done rebooting in 15 seconds --karl __ Do you Yahoo!? Yahoo! Personals - Better first dates. More second dates. http://personals.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 5.3: panic page fault with nge driver
No one has replied to my posts. :( I hope I provided all the info that was needed. I tried 5.3-STABLE, but no success. OS still panics with same message below. 5.2.1-RELEASE works, but its not current anymore and I don't want to install an older OS. Besides, even with 5.2.1, I had to hardcode the media settings for the interface. OpenBSD 3.6 does not seem to have this problem and uses the same driver. So until I see that the problem is fixed, I have to move my IDS's over to OpenBSD. sp0ng3b0b wrote: I am getting a page fault with a new install of FreeBSD 5.3 Release. Something changed with the nge driver in FreeBSD 5.3. I did not have this problem with 5.2.1. I just performed a clean install on a box that had been running 5.2.1 RELEASE for a few months. The box is an Instrusion Detection System. I have fiber taps in place on the network and use the rx ports of the nic to monitor the traffic. In 5.2.1, i would do this to bond ports and monitor them: # ifconfig nge0 media 1000baseSX mediaopt full-duplex promisc -arp up # ifconfig nge1 media 1000baseSX mediaopt full-duplex promisc -arp up # ngctl mkpeer fec dummy fec # ngctl msg fec0: add_iface '"nge0"' # ngctl msg fec0: add_iface '"nge1"' # ngctl msg fec0: set_mode_inet # ifconfig fec0 promisc -arp up However, when i set the media options for nge0, the machine panics and dies. The panic message is hand typed below. FreeBSD 5.3 RELEASE. Intel Pentium 4 3.06GHz CPU 1GB RAM 80GB Maxtor HD (1x) Intel 82801DB (ICH4) Pro/100 Ethernet (6x) NetGear GA621 fiber 1GB NIC Fatal trap 12: page fault while in kernel mode fault virtual address= 0x8 fault code= supervisor read, page not present instruction pointer= 0x8:0xc055a002 stack pointer= 0x10:0xe32a2c9c frame pointer= 0x10:0xe32a2cac code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def 2 1, gran 1 processor eflags= interrupt enabled, resuep, IOPL = 0 current process= 27 (irq17: nge0) trap number= 12 panic: page fault ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 5.3: panic page fault with nge driver
I found some more info: ---snip--- To: <[EMAIL PROTECTED]> Date: Tue, 16 Nov 2004 14:28:58 - Subject: 5.3-RELEASE with nge crashes regularly under load I tried enabling giant and setting the sysctl neither helped. Unfortunately didn't have time to setup and get a dump of the kernel panic as I had to get the machine up and running ASAP. Replaced the netcard with an em and all was well. Test to reproduce should be rsync on a dir with some large files in. Steve ---snip--- This could be the problem. Well, it was hard enough convincing mgmt to let me use FreeBSD instead of RedHat. But I am not going to get budget for new nics...especially when the worked before. If ANYONE can help...I would appreciate it. Again, to restate, nge driver is causing a "panic: page fault". sp0ng3b0b wrote: I've been told that this might be fixed in CURRENT. That's nice, but I am trying to run a production quality server and CURRENT is not recommended for that purpose. Any recommendations? By the way, is Questions the wrong list for my problem? sp0ng3b0b wrote: I am getting a page fault with a new install of FreeBSD 5.3 Release. Something changed with the nge driver in FreeBSD 5.3. I did not have this problem with 5.2.1. I just performed a clean install on a box that had been running 5.2.1 RELEASE for a few months. The box is an Instrusion Detection System. I have fiber taps in place on the network and use the rx ports of the nic to monitor the traffic. In 5.2.1, i would do this to bond ports and monitor them: # ifconfig nge0 media 1000baseSX mediaopt full-duplex promisc -arp up # ifconfig nge1 media 1000baseSX mediaopt full-duplex promisc -arp up # ngctl mkpeer fec dummy fec # ngctl msg fec0: add_iface '"nge0"' # ngctl msg fec0: add_iface '"nge1"' # ngctl msg fec0: set_mode_inet # ifconfig fec0 promisc -arp up However, when i set the media options for nge0, the machine panics and dies. The panic message is hand typed below. FreeBSD 5.3 RELEASE. Intel Pentium 4 3.06GHz CPU 1GB RAM 80GB Maxtor HD (1x) Intel 82801DB (ICH4) Pro/100 Ethernet (6x) NetGear GA621 fiber 1GB NIC Fatal trap 12: page fault while in kernel mode fault virtual address= 0x8 fault code= supervisor read, page not present instruction pointer= 0x8:0xc055a002 stack pointer= 0x10:0xe32a2c9c frame pointer= 0x10:0xe32a2cac code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def 2 1, gran 1 processor eflags= interrupt enabled, resuep, IOPL = 0 current process= 27 (irq17: nge0) trap number= 12 panic: page fault ___ [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]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 5.3: panic page fault with nge driver
I've been told that this might be fixed in CURRENT. That's nice, but I am trying to run a production quality server and CURRENT is not recommended for that purpose. Any recommendations? By the way, is Questions the wrong list for my problem? sp0ng3b0b wrote: I am getting a page fault with a new install of FreeBSD 5.3 Release. Something changed with the nge driver in FreeBSD 5.3. I did not have this problem with 5.2.1. I just performed a clean install on a box that had been running 5.2.1 RELEASE for a few months. The box is an Instrusion Detection System. I have fiber taps in place on the network and use the rx ports of the nic to monitor the traffic. In 5.2.1, i would do this to bond ports and monitor them: # ifconfig nge0 media 1000baseSX mediaopt full-duplex promisc -arp up # ifconfig nge1 media 1000baseSX mediaopt full-duplex promisc -arp up # ngctl mkpeer fec dummy fec # ngctl msg fec0: add_iface '"nge0"' # ngctl msg fec0: add_iface '"nge1"' # ngctl msg fec0: set_mode_inet # ifconfig fec0 promisc -arp up However, when i set the media options for nge0, the machine panics and dies. The panic message is hand typed below. FreeBSD 5.3 RELEASE. Intel Pentium 4 3.06GHz CPU 1GB RAM 80GB Maxtor HD (1x) Intel 82801DB (ICH4) Pro/100 Ethernet (6x) NetGear GA621 fiber 1GB NIC Fatal trap 12: page fault while in kernel mode fault virtual address= 0x8 fault code= supervisor read, page not present instruction pointer= 0x8:0xc055a002 stack pointer= 0x10:0xe32a2c9c frame pointer= 0x10:0xe32a2cac code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def 2 1, gran 1 processor eflags= interrupt enabled, resuep, IOPL = 0 current process= 27 (irq17: nge0) trap number= 12 panic: page fault ___ [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]"
FreeBSD 5.3: panic page fault with nge driver
I am getting a page fault with a new install of FreeBSD 5.3 Release. Something changed with the nge driver in FreeBSD 5.3. I did not have this problem with 5.2.1. I just performed a clean install on a box that had been running 5.2.1 RELEASE for a few months. The box is an Instrusion Detection System. I have fiber taps in place on the network and use the rx ports of the nic to monitor the traffic. In 5.2.1, i would do this to bond ports and monitor them: # ifconfig nge0 media 1000baseSX mediaopt full-duplex promisc -arp up # ifconfig nge1 media 1000baseSX mediaopt full-duplex promisc -arp up # ngctl mkpeer fec dummy fec # ngctl msg fec0: add_iface '"nge0"' # ngctl msg fec0: add_iface '"nge1"' # ngctl msg fec0: set_mode_inet # ifconfig fec0 promisc -arp up However, when i set the media options for nge0, the machine panics and dies. The panic message is hand typed below. FreeBSD 5.3 RELEASE. Intel Pentium 4 3.06GHz CPU 1GB RAM 80GB Maxtor HD (1x) Intel 82801DB (ICH4) Pro/100 Ethernet (6x) NetGear GA621 fiber 1GB NIC Fatal trap 12: page fault while in kernel mode fault virtual address = 0x8 fault code = supervisor read, page not present instruction pointer = 0x8:0xc055a002 stack pointer = 0x10:0xe32a2c9c frame pointer = 0x10:0xe32a2cac code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def 2 1, gran 1 processor eflags= interrupt enabled, resuep, IOPL = 0 current process = 27 (irq17: nge0) trap number = 12 panic: page fault ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic: page fault
> On Mon, Nov 15, 2004 at 12:10:13AM -0500, kalin mintchev wrote: >> >> > On Sun, Nov 14, 2004 at 11:12:30PM -0500, kalin mintchev wrote: >> >> >> >> > >> >> > Follow my advice then.. >> >> >> >> about kernel debugging?! >> > >> > Not that specifically, but I told you three things to do in order, >> > starting with trying a later release. 4.6-RELEASE is very old by now, >> > and there have been literally hundreds of bugs fixed between it and >> > 4.10-release. We do release new versions of FreeBSD for a reason ;-) >> >> i'll upgrade anyway but what about the ulimit and it's -v flag?! > > cvsweb.freebsd.org shows that ulimit -v was added to FreeBSD 2 1/2 > years ago. right. found the -v flag with 'man sh' on 5.2.1 but it's not on the 4.6 ok... i hope it's there on 4.10 thank you Kris - i appreciate it. > > Kris > -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic: page fault
On Mon, Nov 15, 2004 at 12:10:13AM -0500, kalin mintchev wrote: > > > On Sun, Nov 14, 2004 at 11:12:30PM -0500, kalin mintchev wrote: > >> > >> > > >> > Follow my advice then.. > >> > >> about kernel debugging?! > > > > Not that specifically, but I told you three things to do in order, > > starting with trying a later release. 4.6-RELEASE is very old by now, > > and there have been literally hundreds of bugs fixed between it and > > 4.10-release. We do release new versions of FreeBSD for a reason ;-) > > i'll upgrade anyway but what about the ulimit and it's -v flag?! cvsweb.freebsd.org shows that ulimit -v was added to FreeBSD 2 1/2 years ago. Kris pgpsVjUzOPVf7.pgp Description: PGP signature
Re: panic: page fault
> On Sun, Nov 14, 2004 at 11:12:30PM -0500, kalin mintchev wrote: >> >> > >> > Follow my advice then.. >> >> about kernel debugging?! > > Not that specifically, but I told you three things to do in order, > starting with trying a later release. 4.6-RELEASE is very old by now, > and there have been literally hundreds of bugs fixed between it and > 4.10-release. We do release new versions of FreeBSD for a reason ;-) i'll upgrade anyway but what about the ulimit and it's -v flag?! > > Kris > -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic: page fault
On Sun, Nov 14, 2004 at 11:12:30PM -0500, kalin mintchev wrote: > > > > > Follow my advice then.. > > about kernel debugging?! Not that specifically, but I told you three things to do in order, starting with trying a later release. 4.6-RELEASE is very old by now, and there have been literally hundreds of bugs fixed between it and 4.10-release. We do release new versions of FreeBSD for a reason ;-) Kris pgpck4YRy7MJr.pgp Description: PGP signature
Re: panic: page fault
> > Follow my advice then.. about kernel debugging?! > > Kris > -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
