9.0-RELEASE: Strange freezing and kernel panics on laptop
Hi, I'm in need of advice. I've recently installed FreeBSD 9.0-RELEASE on my laptop (a Dell Inspiron 1318) with a good deal of success. However, I've been experiencing a few hiccups, to say the least. The kernel is the GENERIC for the amd64 architecture that comes with the installation images (no funny compilation issues on my part): $ uname -a FreeBSD apeiron 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 Since I've installed it, the system has been freezing for apparently no reason and, once in a while, rebooting upon a kernel panic. The kernel panics come in two varieties: Fatal Trap 9: general protection fault while in kernel mode Fatal Trap 12: page fault while in kernel mode I have the dump files. [Concerning the Fatal Trap 12: I ran memtest86+ and everything turned out alright on the memory side.] As for the recurrent freezing, it seems to me (but this is a hunch) that it might be related to wireless card issues (since, for what I can recall, it happens some time after I start having connection issues). Also, every time I do a netif restart, the system just freezes after displaying two lines: bwn0: need multicast update callback TODO: need swap [In order not to raise side issues, I have a fully working LP PHY Broadcom 4312 (except for these issues), and I have hw.bwn.usedma=0 in loader.conf---but the freezing thing happens whether it is set to 1 or 0.] A quick inspection to log files reveals some pattern in /var/log/messages: === Feb 10 19:01:59 apeiron wpa_supplicant[464]: WPA: Group rekeying completed with 68:7f:74:e9:d6:91 [GTK=TKIP] Feb 10 19:22:02 apeiron kernel: bwn0: unexpected NULL ni Feb 10 19:27:07 apeiron syslogd: kernel boot file is /boot/kernel/kernel [...] Feb 10 19:27:07 apeiron savecore: reboot after panic: general protection fault Feb 10 19:27:07 apeiron savecore: writing core to vmcore.0 Feb 11 21:39:40 apeiron wpa_supplicant[464]: WPA: Group rekeying completed with 68:7f:74:e9:d6:91 [GTK=TKIP] Feb 11 21:39:47 apeiron kernel: bwn0: device timeout Feb 11 21:44:38 apeiron kernel: bwn0: unexpected NULL ni Feb 11 21:44:38 apeiron kernel: bwn0: unexpected NULL ni Feb 11 21:47:33 apeiron syslogd: kernel boot file is /boot/kernel/kernel Feb 12 17:23:47 apeiron wpa_supplicant[464]: WPA: Group rekeying completed with 68:7f:74:e9:d6:91 [GTK=TKIP] Feb 12 18:20:32 apeiron kernel: bwn0: device timeout Feb 12 18:22:23 apeiron kernel: bwn0: unexpected NULL ni Feb 12 18:31:49 apeiron syslogd: kernel boot file is /boot/kernel/kernel Feb 13 17:16:43 apeiron kernel: bwn0: device timeout Feb 13 17:21:39 apeiron kernel: bwn0: unexpected NULL ni Feb 13 17:22:40 apeiron syslogd: kernel boot file is /boot/kernel/kernel [...] Feb 13 17:22:40 apeiron savecore: reboot after panic: page fault Feb 13 17:22:40 apeiron savecore: writing core to vmcore.1 Feb 14 11:40:49 apeiron wpa_supplicant[464]: WPA: Group rekeying completed with 68:7f:74:e9:d6:91 [GTK=TKIP] Feb 14 12:02:23 apeiron kernel: bwn0: device timeout Feb 14 12:03:52 apeiron kernel: bwn0: unexpected NULL ni Feb 14 12:12:27 apeiron kernel: , 2265. Feb 14 12:13:10 apeiron syslogd: kernel boot file is /boot/kernel/kernel === As for the panics, they immediately follow two of the messages above, as you can appreciate in the quote. Maybe the following can help (or not!!). In /var/log/messages, the following two lines keep showing: acpi0: reservation of 0, 9f000 (3) failed acpi0: reservation of 10, 7f56d800 (3) failed Needless to say, this won't discourage me from using FreeBSD on my laptop, but it isn't very pleasant to have these kind of problems while working. Right now, the workaround I implemented is to use a Linksys wireless adapter I had sleeping in its box. However, being able to use the Broadcom card would be nice. Any help would be appreciated, if nothing else, to understand what's happening. Thanks! ___ 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
9.0-RELEASE: Strange freezing and kernel panics on laptop
Hi, I'm in need of advice. I've recently installed FreeBSD 9.0-RELEASE on my laptop (a Dell Inspiron 1318) with a good deal of success. However, I've been experiencing a few hiccups, to say the least. The kernel is the GENERIC for the amd64 architecture that comes with the installation images (no funny compilation issues on my part): $ uname -a FreeBSD apeiron 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 Since I've installed it, the system has been freezing for apparently no reason and, once in a while, rebooting upon a kernel panic. The kernel panics come in two varieties: Fatal Trap 9: general protection fault while in kernel mode Fatal Trap 12: page fault while in kernel mode I have the dump files. [Concerning the Fatal Trap 12: I ran memtest86+ and everything turned out alright on the memory side.] As for the recurrent freezing, it seems to me (but this is a hunch) that it might be related to wireless card issues (since, for what I can recall, it happens some time after I start having conection issues). Also, everytime I do a netif restart, the system just freezes after displaying two lines: bwn0: need multicast update callback TODO: need swap [In order not to raise side issues, I have a fully working LP PHY Broadcom 4312 (except for these issues), and I have hw.bwn.usedma=0 in loader.conf---but the freezing thing happens whether it is set to 1 or 0.] And that's about it. In particular, nothing shows in /var/log/messages. As for the panics, I'm clueless. Maybe the following can help (or not!!). In /var/log/messages, the following two lines keep showing: acpi0: reservation of 0, 9f000 (3) failed acpi0: reservation of 10, 7f56d800 (3) failed Needless to say, this won't discourage me from using FreeBSD on my laptop, but it isn't very funny to have these kind of problems while doing some work. Any help would be appreciated, if nothing else, to understand what's happening. Thanks! ___ 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: kernel panics involving NFS+RPCSEC_GSS
On Thu, Aug 18, 2011 at 3:25 PM, Clinton Adams clinton.ad...@gmail.com wrote: Hello, Kernel panics if clients hit the nfs server sufficiently hard - happens repeatedly with 13 clients logging in at the same approximate time, using nfsv4 mounted homes. server is running freebsd 8.2-RELEASE-p2. clients are linux 2.6.38-10 Running a memtest on the server now to rule out bad mem. The server has been used for samba, and it's only with the attempted switch to nfs that this problem has appeared. Err, wrong paste from another forum. Here's the trace from my server: Fatal trap 12: page fault while in kernel mode Fatal trap 12: page fault while in kernel mode cpuid = 0; cpuid = 2; apic id = 00apic id = 06 fault virtual address = 0x0 fault virtual address = 0x8 fault code = supervisor write data, page not present fault code = supervisor read data, page not present instruction pointer = 0x20:0x807db856 instruction pointer = 0x20:0x807dc0d7 stack pointer = 0x28:0xff8096c0d840 stack pointer = 0x28:0xff8096c17860 frame pointer = 0x28:0xff8096c0d860 frame pointer = 0x28:0xff8096c17a80 code segment= base 0x0, limit 0xf, type 0x1b code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= processor eflags= interrupt enabled, interrupt enabled, resume, resume, IOPL = 0IOPL = 0 current process = current process = 765 (nfsd: service)765 (nfsd: service) trap number = 12 trap number = 12 panic: page fault cpuid = 1 Uptime: 3h22m48s Physical memory: 2032 MB Dumping 406 MB: 391 375 359 343 327 311 295 279 263 247 231 215 199 183 167 151 135 119 103 87 71 55 39 23 7 Reading symbols from /boot/kernel/linux.ko...done. Loaded symbols for /boot/kernel/linux.ko Reading symbols from /boot/kernel/nfscommon.ko...done. Loaded symbols for /boot/kernel/nfscommon.ko Reading symbols from /boot/kernel/nfsd.ko...done. Loaded symbols for /boot/kernel/nfsd.ko Reading symbols from /boot/kernel/snp.ko...done. Loaded symbols for /boot/kernel/snp.ko #0 doadump () at pcpu.h:224 224 __asm(movq %%gs:0,%0 : =r (td)); (kgdb) list *0x807db856 0x807db856 is in svc_rpc_gss_forget_client (/usr/src/sys/rpc/rpcsec_gss/svc_rpcsec_gss.c:622). 617 struct svc_rpc_gss_client_list *list; 618 619 list = svc_rpc_gss_client_hash[client-cl_id.ci_id % CLIENT_HASH_SIZE]; 620 sx_xlock(svc_rpc_gss_lock); 621 TAILQ_REMOVE(list, client, cl_link); 622 TAILQ_REMOVE(svc_rpc_gss_clients, client, cl_alllink); 623 svc_rpc_gss_client_count--; 624 sx_xunlock(svc_rpc_gss_lock); 625 svc_rpc_gss_release_client(client); 626 } (kgdb) backtrace #0 doadump () at pcpu.h:224 #1 0x805cbabe in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:419 #2 0x805cbed3 in panic (fmt=0x0) at /usr/src/sys/kern/kern_shutdown.c:592 #3 0x808d239d in trap_fatal (frame=0xff0004c89460, eva=Variable eva is not available. ) at /usr/src/sys/amd64/amd64/trap.c:783 #4 0x808d275f in trap_pfault (frame=0xff8096c0d790, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:699 #5 0x808d2b5f in trap (frame=0xff8096c0d790) at /usr/src/sys/amd64/amd64/trap.c:449 #6 0x808bada4 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:224 #7 0x807db856 in svc_rpc_gss_forget_client (client=0xff001c015200) at atomic.h:158 #8 0x807dc0e3 in svc_rpc_gss (rqst=0xff0004a24000, msg=0xff8096c0db20) at /usr/src/sys/rpc/rpcsec_gss/svc_rpcsec_gss.c:642 #9 0x807d48f3 in svc_run_internal (pool=0xff0004ca6200, ismaster=0) at /usr/src/sys/rpc/svc.c:837 #10 0x807d50ab in svc_thread_start (arg=Variable arg is not available. ) at /usr/src/sys/rpc/svc.c:1200 #11 0x805a26f8 in fork_exit (callout=0x807d50a0 svc_thread_start, arg=0xff0004ca6200, frame=0xff8096c0dc40) at /usr/src/sys/kern/kern_fork.c:845 #12 0x808bb26e in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:565 #13 0x0080 in ?? () #14 0x7fffe6e0 in ?? () #15 0x002e in ?? () #16 0x in ?? () #17 0xfef4 in ?? () #18 0x in ?? () #19 0x009b in ?? () #20 0x7fffe6e0 in ?? () #21 0x0008 in ?? () #22 0x0003 in ?? () #23 0x
kernel panics involving NFS+RPCSEC_GSS
Hello,
Kernel panics if clients hit the nfs server sufficiently hard -
happens repeatedly with 13 clients logging in at the same approximate
time, using nfsv4 mounted homes.
server is running freebsd 8.2-RELEASE-p2. clients are linux 2.6.38-10
Running a memtest on the server now to rule out bad mem. The server
has been used for samba, and it's only with the attempted switch to
nfs that this problem has appeared.
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0xff80007bd260
fault code = supervisor read data, page not present
instruction pointer = 0x20:0x80e20939
stack pointer = 0x28:0xff80732baaa0
frame pointer = 0x28:0xff80732bab80
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 = 0 (wpi0 taskq)
trap number = 12
panic: page fault
cpuid = 0
Uptime: 12m21s
Physical memory: 4002 MB
#0 doadump () at pcpu.h:223
223 __asm __volatile(movq %%gs:0,%0 : =r (td));
(kgdb) list *0x80e20939
0x80e20939 is in wpi_newstate
(/usr/src/sys/modules/wpi/../../dev/wpi/if_wpi.c:2453).
2448device_printf(sc-sc_dev, could not configure\n);
2449return error;
2450}
2451
2452/* configuration has changed, set Tx power accordingly */
2453if ((error = wpi_set_txpower(sc, ni-ni_chan, 1)) != 0) {
2454device_printf(sc-sc_dev, could not set
Tx power\n);
2455return error;
2456}
2457
(kgdb) backtrace
#0 doadump () at pcpu.h:223
#1 0x8056f9c0 in boot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:416
#2 0x8056fe2d in panic (fmt=0x80917ba4 %s) at
/usr/src/sys/kern/kern_shutdown.c:579
#3 0x80842c20 in trap_fatal (frame=0xff0002a80740,
eva=Variable eva is not available.
)
at /usr/src/sys/amd64/amd64/trap.c:857
#4 0x80842fcc in trap_pfault (frame=0xff80732ba9f0, usermode=0)
at /usr/src/sys/amd64/amd64/trap.c:773
#5 0x80843618 in trap (frame=0xff80732ba9f0) at
/usr/src/sys/amd64/amd64/trap.c:499
#6 0x8082a6d3 in calltrap () at
/usr/src/sys/amd64/amd64/exception.S:224
#7 0x80e20939 in wpi_newstate (vap=0xff0005aca000,
nstate=IEEE80211_S_AUTH, arg=192)
at /usr/src/sys/modules/wpi/../../dev/wpi/if_wpi.c:2482
#8 0x806517dc in ieee80211_newstate_cb (xvap=Variable
xvap is not available.
)
at /usr/src/sys/net80211/ieee80211_proto.c:1654
#9 0x805a9ded in taskqueue_run (queue=0xff000314cd00)
at /usr/src/sys/kern/subr_taskqueue.c:239
#10 0x805aa052 in taskqueue_thread_loop (arg=Variable
arg is not available.
) at /usr/src/sys/kern/subr_taskqueue.c:360
#11 0x80548e4d in fork_exit (callout=0x805aa00c
taskqueue_thread_loop,
arg=0xff80003ab0b8, frame=0xff80732bac80) at
/usr/src/sys/kern/kern_fork.c:843
#12 0x8082abae in fork_trampoline () at
/usr/src/sys/amd64/amd64/exception.S:561
#13 0x in ?? ()
#14 0x in ?? ()
#15 0x in ?? ()
#16 0x in ?? ()
#17 0x in ?? ()
#18 0x in ?? ()
#19 0x in ?? ()
#20 0x in ?? ()
#21 0x in ?? ()
#22 0x in ?? ()
#23 0x in ?? ()
#24 0x in ?? ()
#25 0x in ?? ()
#26 0x in ?? ()
#27 0x in ?? ()
#28 0x in ?? ()
#29 0x in ?? ()
#30 0x in ?? ()
#31 0x in ?? ()
#32 0x in ?? ()
#33 0x in ?? ()
#34 0x in ?? ()
#35 0x in ?? ()
#36 0x in ?? ()
#37 0x01c71000 in ?? ()
#38 0x in ?? ()
#39 0x in ?? ()
#40 0xff000239ee40 in ?? ()
#41 0xff0003901000 in ?? ()
#42 0xff80732ba140 in ?? ()
#43 0xff80732ba0f8 in ?? ()
#44 0xff0002a80740 in ?? ()
#45 0x80592283 in sched_switch (td=0xff80003ab0b8,
newtd=0x805aa00c, flags=Variable flags is not available.
)
at /usr/src/sys/kern/sched_ule.c:1844
Previous frame inner to this frame (corrupt stack?)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions
Kernel panics?
Hi! I'm having a problem with an 8.1-RELEASE #0 amd64 machine. Three weeks ago, it had a kernel panic, which I was too tired to properly capture. On reboot, I forgot to run fsck in single user mode; about 12-14 hours later it crashed complaining that the background file system checks were inconsistent. A day later it crashed with a server double fault; I was unfortunately on the way to a meeting, along with all of my technical co-workers, so I wasn't able to see the screen, and it was being reported by someone who was poorly equipped to give a good report. A few days later, it had hung (it didn't respond to input), and I needed to hard restart. A few days later, the same thing happened. Last weekend, on Friday evening it complained about the hard disk controller disappearing (at least, as far back as I was able to go in the screen buffer). Saturday night, I finally got a kernel panic that I captured; after this, I turned on core dumps. However, last night, it crashed again, and tried to write out a core, but didn't succeed. The kernel panic from Saturday night was: panic: unknown cluster size cpuid = 0 Uptime: 1h49m37s Cannot dump. Device not defined or unavailable. aac0: shutting down controller... Fatal trap 12: page fault while in kernel mode cpuid = 9; apic id = 10 fault virtual address = 0x1d fault code= supervisor write data, page not present ... current process = 12 (irq256: em0) trap number = 12 done Last night's: Fatal trap 12: page fault while in kernel mode cpuid = 9; apic id = 11 fault virtual address = 0x8098f90e fault code= supervisor read data, page not present ... current process = 97530 (taper) trap number = 12 panic: page fault cpuid = 9 Uptime: 3d21h24m57s Physical memory: 12211MB Dumping 2942MB: Note that there was nothing after the Dumping 2942MB:; the cursor was sitting just after the colon. On reboot, it did not find any cores to save to disk (I did have to boot single user and fsck -y; is it possible that this interfered with the core dump? if so, how do I fix this?). I tried, this morning, to run memtest86, however both 3.5 and 3.4 just give loud annoying beeps, not displaying anything on screen (not even a menu; once I get past the boot loader from the memtest86 cd, it just starts beeping). Any suggestions? Thanks, Ricky The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Kernel panics?
On 11/04/10 12:35, Richard Morse wrote: Hi! I'm having a problem with an 8.1-RELEASE #0 amd64 machine. Looks like too many different problem all at once. Almost certainly there's a hardware problem somewhere. Try running memtest86 Three weeks ago, it had a kernel panic, which I was too tired to properly capture. On reboot, I forgot to run fsck in single user mode; about 12-14 hours later it crashed complaining that the background file system checks were inconsistent. A day later it crashed with a server double fault; I was unfortunately on the way to a meeting, along with all of my technical co-workers, so I wasn't able to see the screen, and it was being reported by someone who was poorly equipped to give a good report. A few days later, it had hung (it didn't respond to input), and I needed to hard restart. A few days later, the same thing happened. Last weekend, on Friday evening it complained about the hard disk controller disappearing (at least, as far back as I was able to go in the screen buffer). Saturday night, I finally got a kernel panic that I captured; after this, I turned on core dumps. However, last night, it crashed again, and tried to write out a core, but didn't succeed. The kernel panic from Saturday night was: panic: unknown cluster size cpuid = 0 Uptime: 1h49m37s Cannot dump. Device not defined or unavailable. aac0: shutting down controller... Fatal trap 12: page fault while in kernel mode cpuid = 9; apic id = 10 fault virtual address = 0x1d fault code= supervisor write data, page not present ... current process = 12 (irq256: em0) trap number = 12 done Last night's: Fatal trap 12: page fault while in kernel mode cpuid = 9; apic id = 11 fault virtual address = 0x8098f90e fault code= supervisor read data, page not present ... current process = 97530 (taper) trap number = 12 panic: page fault cpuid = 9 Uptime: 3d21h24m57s Physical memory: 12211MB Dumping 2942MB: Note that there was nothing after the Dumping 2942MB:; the cursor was sitting just after the colon. On reboot, it did not find any cores to save to disk (I did have to boot single user and fsck -y; is it possible that this interfered with the core dump? if so, how do I fix this?). I tried, this morning, to run memtest86, however both 3.5 and 3.4 just give loud annoying beeps, not displaying anything on screen (not even a menu; once I get past the boot loader from the memtest86 cd, it just starts beeping). Any suggestions? Thanks, Ricky The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ 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: Kernel panics?
On Thu, Nov 4, 2010 at 12:27 PM, Ivan Voras ivo...@freebsd.org wrote: Looks like too many different problem all at once. Almost certainly there's a hardware problem somewhere. Try running memtest86 On 11/04/10 12:35, Richard Morse wrote: Hi! I'm having a problem with an 8.1-RELEASE #0 amd64 machine. I think Mr. Morse said he ran memtest86 and it produced many loud beeps. This to me suggest that memtest86 is unable to preform it's tests. Have you tried swapping out the ram (same type, size/speed matters not as long as what goes in matches) and try memtest86 again? Did you know... If you play a Windows 2000 CD backwards, you hear satanic messages, but what's worse is when you play it forward ...it installs Windows 2000 -- Alfred Perlstein on chat at freebsd.org http://lists.freebsd.org/mailman/listinfo/freebsd-questions ___ 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
kernel panics
Where is the best place to report problems with kernel panics in FreeBSD 8.0 and to get help? I posted a message in this mailing list freebsd-questions, but if acutally never was published (?) ___ 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: kernel panics
On Fri, Jul 16, 2010 at 9:03 AM, n dhert ndhert...@gmail.com wrote: Where is the best place to report problems with kernel panics in FreeBSD 8.0 and to get help? Have a look at http://www.freebsd.org/send-pr.html Cheers I posted a message in this mailing list freebsd-questions, but if acutally never was published (?) ___ 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
kernel panics in 7.2-RELEASE
Hi, I have 7.2-RELEASE running on two older laptops and both have had a few kernel panics lately. Unfortunately the one that paniced today doesn't have debugging symbols, so I'm sure how useful any of output below will be. Joey % dmesg . . . Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor write, page not present instruction pointer = 0x20:0xc05e480b stack pointer = 0x28:0xe7228820 frame pointer = 0x28:0xe7228860 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 = 50277 (mtree) trap number = 12 panic: page fault . . . % sudo kgdb kernel /var/crash/vmcore.1 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...(no debugging symbols found)... Attempt to extract a component of a value that is not a structure pointer. Attempt to extract a component of a value that is not a structure pointer. Attempt to extract a component of a value that is not a structure pointer. Attempt to extract a component of a value that is not a structure pointer. #0 0xc0566ddb in doadump () ___ 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
kernel panics on a 5.4-STABLE
Hello Group
We have a FreeBSD 5.4-STABLE System which is booting once or
twice in a week without any meaningfull messages on the console
or in a logfile.
May 14 11:41:26 ldxp syslogd: kernel boot file is
/boot/kernel/kernel
May 14 11:41:26 ldxp savecore: reboot after panic: page fault
...
May 14 21:31:36 ldxp syslogd: kernel boot file is
/boot/kernel/kernel
May 14 21:31:36 ldxp savecore: reboot after panic: page fault
...
May 18 09:10:37 ldxp syslogd: kernel boot file is
/boot/kernel/kernel
May 18 09:10:37 ldxp savecore: reboot after panic: page fault
My first thought was RAM so I did a memtest86 over night but
everthing looks ok.
I was able to get and open a kernel dump but have no idea what
this stuff means :)
%sudo cat /var/crash/info.14
Dump header from device /dev/ar0s1b
Architecture: i386
Architecture Version: 16777216
Dump Length: 1073717248B (1023 MB)
Blocksize: 512
Dumptime: Sun May 18 09:03:50 2008
Hostname: ldxp.xxx.zz
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 5.4-STABLE #5: Mon Jan 14 11:21:51 CET
2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/LDXP
Panic String: page fault
Dump Parity: 3477207326
Bounds: 14
Dump Status: good
%
%sudo kgdb kernel.debug /var/crash/vmcore.14
[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.
#0 doadump () at pcpu.h:160
160 __asm __volatile(movl %%fs:0,%0 : =r (td));
(kgdb) bt
#0 doadump () at pcpu.h:160
#1 0xc04c5ae8 in boot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:412
#2 0xc04c5d7c in panic (fmt=0xc06279fc %s) at
/usr/src/sys/kern/kern_shutdown.c:568
#3 0xc0604c0c in trap_fatal (frame=0xe4aacc24, eva=36) at
/usr/src/sys/i386/i386/trap.c:817
#4 0xc06043f9 in trap (frame=
{tf_fs = -458620904, tf_es = -1068695536, tf_ds = 16,
tf_edi = -1041254912, tf_esi = -1041254912, tf_ebp = -458568584,
tf_isp = -458568624, tf_ebx = -1035129472, tf_edx = -1035799228,
tf_ecx = -1066880192, tf_eax = 0, tf_trapno = 12, tf_err = 0,
tf_eip = -1068615581, tf_cs = 8, tf_eflags = 65683, tf_esp = 68,
tf_ss = 0}) at /usr/src/sys/i386/i386/trap.c:255
#5 0xc05f4e4a in calltrap () at
/usr/src/sys/i386/i386/exception.s:140
#6 0xe4aa0018 in ?? ()
#7 0xc04d0010 in thread_single (mode=-1041254912) at
/usr/src/sys/kern/kern_thread.c:812
#8 0xc04e3ede in turnstile_wait (ts=0xc242f5c0, lock=0xc068b340,
owner=0xc24d2d80) at /usr/src/sys/kern/subr_turnstile.c:556
#9 0xc04bd499 in _mtx_lock_sleep (m=0xc068b340, td=0xc1efb600,
opts=0, file=0x0, line=0) at /usr/src/sys/kern/kern_mutex.c:552
#10 0xc04cbf8a in msleep (ident=0xc068b7e4, mtx=0xc068b340,
priority=68, wmesg=0xc0635a53 psleep, timo=500)
at /usr/src/sys/kern/kern_synch.c:239
#11 0xc05cee9c in vm_pageout () at
/usr/src/sys/vm/vm_pageout.c:1529
#12 0xc04b14d0 in fork_exit (callout=0xc05cec1c vm_pageout,
arg=0x0, frame=0xe4aacd38) at /usr/src/sys/kern/kern_fork.c:791
#13 0xc05f4eac in fork_trampoline () at
/usr/src/sys/i386/i386/exception.s:209
(kgdb)
Can anyone give me a hint where else to look for the problem?
tia
Philippe
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: how to capture freebsd 6.3 kernel panics
[EMAIL PROTECTED]@mgEDV.net wrote: hi, since i migrated from 6.2-REL to 6.3-REL i got several panics when copying much data from one volume to another. because of the copy-job taking several hours, i don't get a realistic chance to CATCH the stupid panic and see what's going on (or at least get an idea of). this is really frustrating me! is there a way to avoid the auto-reboot? is there a way to save the panic to disk? btw, there's no swap partition i could use as dump device. cheers... I recently had a system that would not dump to the swap partition for one reason or the other. I used an external USB hard disk, and it dumped there with no problems. With the current sizes of cheap usb flash drives, even that is probably an option. You may wish to explore this solution. Manolis ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
how to capture freebsd 6.3 kernel panics
hi, since i migrated from 6.2-REL to 6.3-REL i got several panics when copying much data from one volume to another. because of the copy-job taking several hours, i don't get a realistic chance to CATCH the stupid panic and see what's going on (or at least get an idea of). this is really frustrating me! is there a way to avoid the auto-reboot? is there a way to save the panic to disk? btw, there's no swap partition i could use as dump device. cheers... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: how to capture freebsd 6.3 kernel panics [solved]
On Fri, February 1, 2008 12:46, Manolis Kiagias wrote: [EMAIL PROTECTED]@mgEDV.net wrote: On Fri, February 1, 2008 11:54, Manolis Kiagias wrote: [EMAIL PROTECTED]@mgEDV.net wrote: hi, since i migrated from 6.2-REL to 6.3-REL i got several panics when copying much data from one volume to another. because of the copy-job taking several hours, i don't get a realistic chance to CATCH the stupid panic and see what's going on (or at least get an idea of). this is really frustrating me! is there a way to avoid the auto-reboot? is there a way to save the panic to disk? btw, there's no swap partition i could use as dump device. cheers... I recently had a system that would not dump to the swap partition for one reason or the other. I used an external USB hard disk, and it dumped there with no problems. With the current sizes of cheap usb flash drives, even that is probably an option. You may wish to explore this solution. Manolis well, although this is a good idea (and i'll keep it as my backup plan for now) , i rather like to prevent the server from rebooting and simply stay at the panic instead of analyzing crash dumps :) is there a way for that? Well, according to this: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-options.html compiling your kernel with options KDB will cause it to enter the debugger instead of automatic reboot. This is not something I ever tried myself but it maybe worth the trouble. Manolis yeah, in the mean time, i exactly did this. loaded /usr/src/sys, compiled with options KDB, options DDB and booted with that kernel. this gives me at least the option to SEE what happened... thx for the replies, guys! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: how to capture freebsd 6.3 kernel panics
is there a way to save the panic to disk? btw, there's no swap partition i could use as dump device. so there is no way to save ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Kernel Panics in 6.1 and 6.2 always Exim 4
-Original Message- From: Kris Kennaway [mailto:[EMAIL PROTECTED] Sent: Friday, September 21, 2007 5:20 PM To: Wil Hatfield Cc: freebsd-questions@freebsd.org Subject: Re: Kernel Panics in 6.1 and 6.2 always Exim 4 Wil Hatfield wrote: Well after a year we still haven't tracked down the kernel panic problems that are occuring on both our 6.1 and 6.2 machines for those we have had time to upgrade. It occurs on 6.1-RC, 6.1-RELEASE 6.1-STABLE, 6.2, you name it. We are noticing that all of the dumps are during Exim 4.6x runtime. I am suspicious of PR-97095 but would like others insights into the possibility. Well, as that PR says, the patch was committed after 6.1-RELEASE, therefore it is expected that older systems will have the problem. You only provided a trace from a 6.1 machine, so if you are saying that it still persists on an up-to-date RELENG_6 kernel, please file a new PR with the details. Kris Unfortunately when I upgraded the machine I have from 6.1-RELEASE to 6.2 it stopped dumping for me. So I have nothing to analyze. However, I still get the kernel panics I did before. Same frequency and always Exim. I bumped into a thread somewhere that said something about setting nmbclusters=0 might be a good workaround for this bug. Anybody heard anything about this or does it seem logical? Wil ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel Panics in 6.1 and 6.2 always Exim 4
Wil Hatfield wrote: -Original Message- From: Kris Kennaway [mailto:[EMAIL PROTECTED] Sent: Friday, September 21, 2007 5:20 PM To: Wil Hatfield Cc: freebsd-questions@freebsd.org Subject: Re: Kernel Panics in 6.1 and 6.2 always Exim 4 Wil Hatfield wrote: Well after a year we still haven't tracked down the kernel panic problems that are occuring on both our 6.1 and 6.2 machines for those we have had time to upgrade. It occurs on 6.1-RC, 6.1-RELEASE 6.1-STABLE, 6.2, you name it. We are noticing that all of the dumps are during Exim 4.6x runtime. I am suspicious of PR-97095 but would like others insights into the possibility. Well, as that PR says, the patch was committed after 6.1-RELEASE, therefore it is expected that older systems will have the problem. You only provided a trace from a 6.1 machine, so if you are saying that it still persists on an up-to-date RELENG_6 kernel, please file a new PR with the details. Kris Unfortunately when I upgraded the machine I have from 6.1-RELEASE to 6.2 it stopped dumping for me. So I have nothing to analyze. However, I still get the kernel panics I did before. Same frequency and always Exim. That is quite contrary to expectations, so you should follow up with the PR. Please try to at least take a photo of the panic traceback from DDB or something. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Kernel Panics in 6.1 and 6.2 always Exim 4
Well after a year we still haven't tracked down the kernel panic problems that are occuring on both our 6.1 and 6.2 machines for those we have had time to upgrade. It occurs on 6.1-RC, 6.1-RELEASE 6.1-STABLE, 6.2, you name it. We are noticing that all of the dumps are during Exim 4.6x runtime. I am suspicious of PR-97095 but would like others insights into the possibility. References http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2006-06/msg00011.html http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2006-06/msg00621.html http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2006-06/msg00636.html Here is my ditty: uname -a FreeBSD machine1.ourdomain.net 6.1-RC FreeBSD 6.1-RC #1: Tue Apr 11 23:19:28 PDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CUSTOM-KERNEL i386 dmesg Fatal trap 12: page fault while in kernel mode fault virtual address = 0x5c fault code = supervisor read, page not present instruction pointer = 0x20:0xc06ab64c stack pointer = 0x28:0xf7ab1b10 frame pointer = 0x28:0xf7ab1b2c 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 = 17074 (exim) trap number = 12 panic: page fault Uptime: 4d5h40m36s Dumping 1015 MB (2 chunks) chunk 0: 1MB (160 pages) ... ok chunk 1: 1015MB (259840 pages) 1000 984 968 952 936 920 904 888 872 856 840 824 808 792 776 760 744 728 712 696 680 664 648 632 616 600 584 568 552 536 520 504 488 472 456 440 424 408 392 376 360 344 328 312 296 280 264 248 232 216 200 184 168 152 136 120 104 88 72 56 40 24 8Copyright (c) 1992-2006 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.1-RC #1: Tue Apr 11 23:19:28 PDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CUSTOM-KERNEL Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.00GHz (2000.03-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf24 Stepping = 4 Features=0x3febfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,M CA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM real memory = 1065353216 (1016 MB) avail memory = 1032658944 (984 MB) MPTable: OEM0 PROD ioapic0: Assuming intbase of 0 ioapic0 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface cpu0 on motherboard pcib0: MPTable Host-PCI bridge pcibus 0 on motherboard pci0: PCI bus on pcib0 agp0: Intel 82845G (845G GMCH) SVGA controller mem 0xd000-0xd7ff,0xdc10-0xdc17 irq 16 at device 2.0 on pci0 agp0: detected 8060k stolen memory agp0: aperture size is 128M pci0: serial bus, USB at device 29.0 (no driver attached) pci0: serial bus, USB at device 29.1 (no driver attached) pci0: serial bus, USB at device 29.2 (no driver attached) pci0: serial bus, USB at device 29.7 (no driver attached) pcib1: MPTable PCI-PCI bridge at device 30.0 on pci0 pci1: PCI bus on pcib1 fxp0: Intel 82801DB (ICH4) Pro/100 Ethernet port 0xa000-0xa03f mem 0xdc00-0xdc000fff irq 20 at device 8.0 on pci1 miibus0: MII bus on fxp0 inphy0: i82562ET 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:10:dc:52:d4:3d isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH4 UDMA100 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xcc00-0xcc0f mem 0xdc181000-0xdc1813ff irq 16 at device 31.1 on pci0 ata0: ATA channel 0 on atapci0 ata1: ATA channel 1 on atapci0 pci0: serial bus, SMBus at device 31.3 (no driver attached) pci0: multimedia, audio at device 31.5 (no driver attached) pmtimer0 on isa0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] fdc0: Enhanced floppy controller at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: [FAST] ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppbus0: Parallel port bus on ppc0 plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: PNP0303 can't assign resources (port) unknown: PNP0c01 can't assign resources (memory) unknown: PNP0c02 can't assign resources (port) unknown: PNP0501 can't assign resources (port) unknown: PNP0700 can't assign resources (port) unknown: PNP0401 can't assign resources (port)
Re: Kernel Panics in 6.1 and 6.2 always Exim 4
On Sep 21, 2007, at 4:11 PM, Wil Hatfield wrote: IP Filter: v4.1.8 initialized. Default = block all, Logging = enabled ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled, default to deny, logging unlimited Do you really need to run both IPFW and IP Filter at the same time? Can you nix one of 'em? ad0: 76319MB WDC WD800BB-00CAA1 17.07W17 at ata0-master UDMA100 acd0: CDROM HL-DT-ST CD-ROM GCR-8480B/1.02 at ata1-master UDMA33 Trying to mount root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted g_vfs_done():md0[WRITE(offset=23527424, length=131072)]error = 28 g_vfs_done():md0[WRITE(offset=23805952, length=32768)]error = 28 errno 28 means: #define ENOSPC 28 /* No space left on device */ ...are you using a RAMDISK (md0 implies yes)? Is Exim filling it up? Are you using a malloc(9) based md, or a swap-based md? -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel Panics in 6.1 and 6.2 always Exim 4
Wil Hatfield wrote: Well after a year we still haven't tracked down the kernel panic problems that are occuring on both our 6.1 and 6.2 machines for those we have had time to upgrade. It occurs on 6.1-RC, 6.1-RELEASE 6.1-STABLE, 6.2, you name it. We are noticing that all of the dumps are during Exim 4.6x runtime. I am suspicious of PR-97095 but would like others insights into the possibility. Well, as that PR says, the patch was committed after 6.1-RELEASE, therefore it is expected that older systems will have the problem. You only provided a trace from a 6.1 machine, so if you are saying that it still persists on an up-to-date RELENG_6 kernel, please file a new PR with the details. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Exim 4.66 Causing Kernel Panics?
Anyone aware of a reason why a fresh build/install of exim 4.66 would cause kernel panics and reboots on my FreeBSD 6.1 machine? My machine, just out of the blue this morning, started rebooting every 3 minutes I narrowed it down to exim I think... As long as I never started up exim 4.66 the machine didn't have the problem... But as soon as I started it up, whammo... Panic and reboot. I've since rolled back to 4.63 and the problem seems to be resolved at least for the moment. The strangest thing is that I upgraded to 4.66 several days ago and the problem didn't show up until this morning. I'm not 100% sure the problem is exim but that's the only thing I could narrow it down to. Perhaps there is a new exim bug/exploit that I just didn't get hit with until today? I deleted the message queue just in case it was corrupt. ANY ideas from anyone as to what could be causing this (hardware perhaps?) would be appreciated. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Exim 4.66 Causing Kernel Panics?
On Tue, Mar 13, 2007 at 03:39:24PM -0700, Don O'Neil wrote: Anyone aware of a reason why a fresh build/install of exim 4.66 would cause kernel panics and reboots on my FreeBSD 6.1 machine? It shouldn't, of course. Please follow up with the panic in the usual way (developers handbook, PR, etc) Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Exim 4.66 Causing Kernel Panics?
On Mar 13, 2007, at 5:39 PM, Don O'Neil wrote: Anyone aware of a reason why a fresh build/install of exim 4.66 would cause kernel panics and reboots on my FreeBSD 6.1 machine? My machine, just out of the blue this morning, started rebooting every 3 minutes I narrowed it down to exim I think... As long as I never started up exim 4.66 the machine didn't have the problem... But as soon as I started it up, whammo... Panic and reboot. I'm running exim 4.66 on FreeBSD 6.2 without problems. This probably doesn't really help you much, but it should let you know that the problem isn't universal. Of course my instance of exim isn't actually doing anything at the moment, which might have something to do with it. -j ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
kernel panics and reboo
Morning List- For the last 5 days or so I've been getting pernel panics, almost like clockwork at 3:05am with one exception at 6L20am. The message showing up in the syslogs is: panic: pmap_enter: invalid page directory pdir=0x357063, va=0xffc0 The pdir and va addresses change. The one crash at 6am didn't have a syslog entry and had a different console message which I neglected to write down. I thought perhaps some faulty memory, but this isn't the case as I replaced it last night and had the same problem. Okay, so I thought cron job..but the only running is the daily job at 3:01 and newsyslog. The box has been up for about 3 months now without a hiccup. It's our SPAM / MAIL gateway and it doesn't always recover nicely. System info: FreeBSD 4.10 -REL intel Celeron chipset with 1 GB RAM Open ports: SSH (22), Postfix (25), Bind 9.2.3 (53) It doesn't seem like a hard drive going, but possibly the mobo? I just can't think of anything else besides hardware failure which would cause that to just start popping up??? Thanks list. Henrik -- Henrik Hudson [EMAIL PROTECTED] RTFM: Not just an acronym, it's the LAW! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
4.9 kernel panics and crashes
I've got a server that has been rebuilt from the board up that is crashing every few hours with various page faults. This is a FreeBSD 4.9 system with a P4 3.2G HT processor, 2G of DDR, 3ware 6400 controller, 2 Intel Fast100 ethernet cards on an Intel D865PERL motherboard. The server runs Exim 4.30 and clamav-devel out of a current ports cvs update. Here is one the current crashes: May 6 08:15:14 mail /kernel: May 6 08:15:14 mail /kernel: May 6 08:15:14 mail /kernel: Fatal trap 12: page fault while in kernel mode May 6 08:15:14 mail /kernel: fault virtual address = 0x8018 May 6 08:15:14 mail /kernel: fault code= supervisor read, page not present May 6 08:15:14 mail /kernel: instruction pointer = 0x8:0xc017aab8 May 6 08:15:14 mail /kernel: stack pointer = 0x10:0xe911acc8 May 6 08:15:14 mail /kernel: frame pointer = 0x10:0xe911acd4 May 6 08:15:14 mail /kernel: code segment = base 0x0, limit 0xf, type 0x1b May 6 08:15:14 mail /kernel: = DPL 0, pres 1, def32 1, gran 1 May 6 08:15:14 mail /kernel: processor eflags = interrupt enabled, resume, IOPL = 0 May 6 08:15:14 mail /kernel: current process = 7035 (tar) May 6 08:15:14 mail /kernel: interrupt mask= none May 6 08:15:14 mail /kernel: trap number = 12 May 6 08:15:14 mail /kernel: panic: page fault May 6 08:15:14 mail /kernel: May 6 08:15:14 mail /kernel: syncing disks... 128 14 1 May 6 08:15:14 mail /kernel: done May 6 08:15:14 mail /kernel: Uptime: 8m40s May 6 08:15:14 mail /kernel: twe0: failed to delete unit 0 May 6 08:15:14 mail /kernel: Automatic reboot in 15 seconds - press a key on the console to abort If anyone can offer advice, please email me. I am willing to try anything at this point. A side note, acpi has not been built into this kernel per warnings of instability. Many thanks in advance, Jeffrey ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Debugging kernel panics
I've recently cvsup'd from 4.8-STABLE to 4.9-PRERELEASE. After a reboot, my machine's kernel panics at the initialization of the xl1 device (a 3com nic). I've checked out the FAQ on the site, under advanced topics, regarding kernel panics, and read the relevant man pages. I have 2 swap partitions, ad0s1b, and ad2s1b. I have set dumpdev to ad2s1b in /etc/rc.conf and /boot/loader.conf. I've also built a debug kernel. However, it appears a kernel core is not being dumped on panic. I've manually executed savecore, with force option, and it wrote a 0 byte vmcore. Is there anywhere else I need to specify the dump device? Do I need to specify the full path instead of just the device? I've not had a kernel panic before, so I'm pretty much a newbie when it comes to that aspect. I have no custom code added to the kernel. Any help will be *greatly* appreciated. -Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Debugging kernel panics
On Tuesday, 9 September 2003 at 3:46:07 -0400, Michael Reynolds wrote: I've recently cvsup'd from 4.8-STABLE to 4.9-PRERELEASE. After a reboot, my machine's kernel panics at the initialization of the xl1 device (a 3com nic). I've checked out the FAQ on the site, under advanced topics, regarding kernel panics, and read the relevant man pages. I have 2 swap partitions, ad0s1b, and ad2s1b. I have set dumpdev to ad2s1b in /etc/rc.conf and /boot/loader.conf. I've also built a debug kernel. However, it appears a kernel core is not being dumped on panic. I've manually executed savecore, with force option, and it wrote a 0 byte vmcore. That probably means that there wasn't a dump there. You normally don't need to force it. Is there anywhere else I need to specify the dump device? No, that's all. Do I need to specify the full path instead of just the device? Ah, yes, of course. There's no way for the dump routines to guess a path. Try /dev/ad2s1b. I've not had a kernel panic before, so I'm pretty much a newbie when it comes to that aspect. I have no custom code added to the kernel. Any help will be *greatly* appreciated. A couple of other points: 1. Your swap partition needs to be at least fractionally larger than your real memory. The dump routines write a dump and a header. 2. You need enough space for the dump on /var/crash. Otherwise it won't save the dump. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers pgp0.pgp Description: PGP signature
kernel panics, lots of them
I have a box that has been having problems for months. Originally, there were problems that were corrected by replacing the mother board. Since then, and I'm not sure when this began, there have been kernel panics after several days of uptime. They can be after one day or three weeks, but they keep happening. So far, I've replaced an IDE cable and a boot time error disappeared, replaced RAM with no benefits, and cvsup'ed/make-world'ed with no benefits. I'm not sure what is causing the problems. Any suggestions of what I should do next? I still have 14 kernel panic dumps if anyone can think of tests that I should be running. Most of the panics appear to be page faults, but two of them were lockmgr issues. I'm considering replacing the mother board and/or the whole computer. Unfortunately, this is a fairly major server at my school (staff email, assorted web-based apps, web site, intranet, etc.) so I am trying to keep outage frequency and duration to a minimum. Any help is appreciated. TIA, Jaime ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panics, lots of them
[EMAIL PROTECTED] wrote: I have a box that has been having problems for months. Originally, there were problems that were corrected by replacing the mother board. What kind of problems did you have? And what hardware? It's quite possible to damage the CPU or even the power supply if the motherboard fails badly enough. Since then, and I'm not sure when this began, there have been kernel panics after several days of uptime. They can be after one day or three weeks, but they keep happening. Probably not a problem with cooling, then. Still sounds like flaky hardware, though, to me... So far, I've replaced an IDE cable and a boot time error disappeared, replaced RAM with no benefits, and cvsup'ed/make-world'ed with no benefits. I'm not sure what is causing the problems. Any suggestions of what I should do next? I still have 14 kernel panic dumps if anyone can think of tests that I should be running. Most of the panics appear to be page faults, but two of them were lockmgr issues. I'm considering replacing the mother board and/or the whole computer. Unfortunately, this is a fairly major server at my school (staff email, assorted web-based apps, web site, intranet, etc.) so I am trying to keep outage frequency and duration to a minimum. There is memtest and cpuburn in the ports; try running those and see whether you can get the system to crash. -Chuck ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panics, lots of them
On Thu, 27 Mar 2003, Chuck Swiger wrote: [EMAIL PROTECTED] wrote: I have a box that has been having problems for months. Originally, there were problems that were corrected by replacing the mother board. What kind of problems did you have? And what hardware? It's quite possible to damage the CPU or even the power supply if the motherboard fails badly enough. At the moment, i.e. with the new mother board, RAM, and cable, It has: P3 600MHz 256MB RAM (was 1 stick, now 2) Tyan mother board (Trinity 400) SCSI PCI card using sym0 driver (can't remember which card) 4 SCSI 18GB hard drives 1 SCSI DDS-4 DAT tape drive 1 EIDE 10GB hard drive 1 ethernet interface using fxp driver (Interl EtherExpress Pro/100) 1 PCI VGA card (can't remember what kind) 1 SCSI cable 1 80-pin EIDE cable There is memtest and cpuburn in the ports; try running those and see whether you can get the system to crash. Just to verify before I run these programs in the middle of the work day: The purpose of these programs is to try to crash the system, right? :) Thanks, Jaime ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel panics, lots of them
[EMAIL PROTECTED] wrote: [ ... ] There is memtest and cpuburn in the ports; try running those and see whether you can get the system to crash. Just to verify before I run these programs in the middle of the work day: The purpose of these programs is to try to crash the system, right? :) You should be prepared for the system to crash, yes. :-) Of course, the point of these tests is that your hardware _should_ be able to run them for days or weeks without any problems with system stability. But if the system cooling/memory timing/etc is marginal, these will probably cause the system to panic within a few hours, which helps confirm where the problem lies... -Chuck ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
