Re: Delete files let FreeBSD crashes.
On Wed, 29 Feb 2012 09:24:55 +0800 netroby hufeng1...@gmail.com wrote: Thanks . I had resolved the problem : 1. restart FreeBSD to single user mode. 2. umount all device then run fsck -f 3. after finished the fsck, restart FreeBSD , return to normal mode. 4. delete the broken directory, and restore the data from backup. 5. every thing seems ok now. netroby That's all well and good, but just for future reference, when you boot into single-user mode, the root partition will already be mounted read-only. It's not necessary to mount any other partitions before running fsck, and in fact, it is advised *not* to do so. -- Conrad J. Sabatier conr...@cox.net ___ 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: Delete files let FreeBSD crashes.
On 3 Mar 2012, at 16:37, Conrad J. Sabatier conr...@cox.net wrote: On Wed, 29 Feb 2012 09:24:55 +0800 netroby hufeng1...@gmail.com wrote: Thanks . I had resolved the problem : 1. restart FreeBSD to single user mode. 2. umount all device then run fsck -f 3. after finished the fsck, restart FreeBSD , return to normal mode. 4. delete the broken directory, and restore the data from backup. 5. every thing seems ok now. netroby That's all well and good, but just for future reference, when you boot into single-user mode, the root partition will already be mounted read-only. It's not necessary to mount any other partitions before running fsck, and in fact, it is advised *not* to do so. You misread his message, he said he *u*mounted partitions. ___ 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: Delete files let FreeBSD crashes.
On Sat, 3 Mar 2012 17:06:29 +0100 Damien Fleuriot m...@my.gd wrote: On 3 Mar 2012, at 16:37, Conrad J. Sabatier conr...@cox.net wrote: On Wed, 29 Feb 2012 09:24:55 +0800 netroby hufeng1...@gmail.com wrote: Thanks . I had resolved the problem : 1. restart FreeBSD to single user mode. 2. umount all device then run fsck -f 3. after finished the fsck, restart FreeBSD , return to normal mode. 4. delete the broken directory, and restore the data from backup. 5. every thing seems ok now. netroby That's all well and good, but just for future reference, when you boot into single-user mode, the root partition will already be mounted read-only. It's not necessary to mount any other partitions before running fsck, and in fact, it is advised *not* to do so. You misread his message, he said he *u*mounted partitions. Whoops, he sure did, didn't he? What was I thinking? :-) Conrad, skulking quietly off into a corner, red-faced -- Conrad J. Sabatier conr...@cox.net ___ 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: Delete files let FreeBSD crashes.
On 2/28/12 8:11 AM, netroby wrote: i installed freebsd 9 on virtualbox, when i try to delete a directory with following command: rm -rf ./zf2 the system will halt , then restart. i had using fsck -y to check the filesystem, but seems not work. following the output: *** HALT *** You're not running fsck on a MOUNTED device are you ? If you are, kindly stop doing so to prevent damage to your system. ___ 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: Delete files let FreeBSD crashes.
Thanks . I had resolved the problem : 1. restart FreeBSD to single user mode. 2. umount all device then run fsck -f 3. after finished the fsck, restart FreeBSD , return to normal mode. 4. delete the broken directory, and restore the data from backup. 5. every thing seems ok now. netroby -- http://www.netroby.com 在 2012年2月28日 下午4:09，Damien Fleuriot m...@my.gd写道： On 2/28/12 8:11 AM, netroby wrote: i installed freebsd 9 on virtualbox, when i try to delete a directory with following command: rm -rf ./zf2 the system will halt , then restart. i had using fsck -y to check the filesystem, but seems not work. following the output: *** HALT *** You're not running fsck on a MOUNTED device are you ? If you are, kindly stop doing so to prevent damage to your system. ___ 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
Delete files let FreeBSD crashes.
i installed freebsd 9 on virtualbox, when i try to delete a directory with following command: rm -rf ./zf2 the system will halt , then restart. i had using fsck -y to check the filesystem, but seems not work. following the output: - bsd# cd /root/repos/ bsd# ls -l total 8 drwxr-xr-x 12 root wheel 1024 Feb 28 14:26 httpd drwxr-xr-x 4 root wheel 512 Feb 28 14:53 zf2 bsd# fsck -y ** /dev/ada0p2 (NO WRITE) USE JOURNAL? no ** Skipping journal, falling through to full fsck SETTING DIRTY FLAG IN READ_ONLY MODE UNEXPECTED SOFT UPDATE INCONSISTENCY ** Last Mounted on / ** Root file system ** Phase 1 - Check Blocks and Sizes INCORRECT BLOCK COUNT I=332256 (2688 should be 768) CORRECT? no 1393793 DUP I=332265 UNEXPECTED SOFT UPDATE INCONSISTENCY 1393794 DUP I=332265 UNEXPECTED SOFT UPDATE INCONSISTENCY 1402537 DUP I=332266 UNEXPECTED SOFT UPDATE INCONSISTENCY INTERNAL ERROR: dups with softupdates UNEXPECTED SOFT UPDATE INCONSISTENCY ** Phase 1b - Rescan For More DUPS 1402537 DUP I=331641 UNEXPECTED SOFT UPDATE INCONSISTENCY 1393793 DUP I=332080 UNEXPECTED SOFT UPDATE INCONSISTENCY 1393794 DUP I=332080 UNEXPECTED SOFT UPDATE INCONSISTENCY ** Phase 2 - Check Pathnames DUP/BAD I=331641 OWNER=root MODE=100600 SIZE=3011 MTIME=Feb 28 14:59 2012 FILE=/root/.history UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no DUP/BAD I=332080 OWNER=root MODE=100600 SIZE=9115 MTIME=Feb 28 14:58 2012 FILE=/root/.viminfo UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no DIRECTORY CORRUPTED I=332254 OWNER=root MODE=40755 SIZE=512 MTIME=Feb 28 14:33 2012 DIR=? UNEXPECTED SOFT UPDATE INCONSISTENCY SALVAGE? no MISSING '.' I=332254 OWNER=root MODE=40755 SIZE=512 MTIME=Feb 28 14:33 2012 DIR=? UNEXPECTED SOFT UPDATE INCONSISTENCY FIX? no DIRECTORY CORRUPTED I=332277 OWNER=root MODE=40755 SIZE=512 MTIME=Feb 28 14:33 2012 DIR=? UNEXPECTED SOFT UPDATE INCONSISTENCY SALVAGE? no MISSING '.' I=332277 OWNER=root MODE=40755 SIZE=512 MTIME=Feb 28 14:33 2012 DIR=? UNEXPECTED SOFT UPDATE INCONSISTENCY FIX? no UNALLOCATED I=332089 OWNER=root MODE=0 SIZE=0 MTIME=Feb 28 14:51 2012 NAME=/root/repos/zf2/.git/objects/pack/tmp_pack_KboUfa UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no SETTING DIRTY FLAG IN READ_ONLY MODE UNEXPECTED SOFT UPDATE INCONSISTENCY SETTING DIRTY FLAG IN READ_ONLY MODE UNEXPECTED SOFT UPDATE INCONSISTENCY DIRECTORY CORRUPTED I=332275 OWNER=root MODE=40755 SIZE=512 MTIME=Feb 28 14:33 2012 DIR=? UNEXPECTED SOFT UPDATE INCONSISTENCY SALVAGE? no MISSING '.' I=332275 OWNER=root MODE=40755 SIZE=512 MTIME=Feb 28 14:33 2012 DIR=? UNEXPECTED SOFT UPDATE INCONSISTENCY FIX? no DIRECTORY CORRUPTED I=426347 OWNER=root MODE=40755 SIZE=512 MTIME=Feb 28 14:33 2012 DIR=? UNEXPECTED SOFT UPDATE INCONSISTENCY SALVAGE? no MISSING '.' I=426347 OWNER=root MODE=40755 SIZE=512 MTIME=Feb 28 14:33 2012 DIR=? UNEXPECTED SOFT UPDATE INCONSISTENCY FIX? no BAD INODE NUMBER FOR '.' I=426361 OWNER=root MODE=40755 SIZE=512 MTIME=Feb 28 14:33 2012 DIR=? UNEXPECTED SOFT UPDATE INCONSISTENCY FIX? no BAD TYPE VALUE I=426374 OWNER=root MODE=100644 SIZE=4289 MTIME=Feb 28 14:33 2012 FILE=?/pngtest UNEXPECTED SOFT UPDATE INCONSISTENCY FIX? no BAD TYPE VALUE I=426375 OWNER=root MODE=100644 SIZE=11439 MTIME=Feb 28 14:33 2012 FILE=?/zlib UNEXPECTED SOFT UPDATE INCONSISTENCY FIX? no BAD TYPE VALUE I=426376 OWNER=root MODE=100644 SIZE=5444 MTIME=Feb 28 14:33 2012 FILE=?/libpng UNEXPECTED SOFT UPDATE INCONSISTENCY FIX? no UNALLOCATED I=439236 OWNER=root MODE=0 SIZE=0 MTIME=Feb 28 14:33 2012 NAME=/root/repos/zf2/library/Zend/Feed/Writer/AbstractFeed.php UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no UNALLOCATED I=439237 OWNER=root MODE=0 SIZE=0 MTIME=Feb 28 14:33 2012 NAME=/root/repos/zf2/library/Zend/Feed/Writer/Deleted.php UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no UNALLOCATED I=439238 OWNER=root MODE=0 SIZE=0 MTIME=Feb 28 14:33 2012 NAME=/root/repos/zf2/library/Zend/Feed/Writer/Entry.php UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no ** Phase 3 - Check Connectivity UNREF DIR I=441064 OWNER=root MODE=40755 SIZE=1024 MTIME=Feb 28 14:51 2012 RECONNECT? no UNREF DIR I=441056 OWNER=root MODE=40755 SIZE=512 MTIME=Feb 28 14:51 2012 RECONNECT? no UNREF DIR I=426361 OWNER=root MODE=40755 SIZE=512 MTIME=Feb 28 14:33 2012 RECONNECT? no UNREF DIR I=426347 OWNER=root MODE=40755 SIZE=512 MTIME=Feb 28 14:33 2012 RECONNECT? no UNREF DIR I=332275 OWNER=root MODE=40755 SIZE=512 MTIME=Feb 28 14:33 2012 RECONNECT? no UNREF DIR I=363375 OWNER=root MODE=40755 SIZE=512 MTIME=Feb 28 14:51 2012 RECONNECT? no UNREF DIR I=332277 OWNER=root MODE=40755 SIZE=512 MTIME=Feb 28 14:33 2012 RECONNECT? no UNREF DIR I=332254 OWNER=root MODE=40755 SIZE=512 MTIME=Feb 28 14:33 2012 RECONNECT? no UNREF DIR I=332253 OWNER=root MODE=40755 SIZE=512 MTIME=Feb 28 14:33 2012 RECONNECT? no ** Phase 4 - Check Reference Counts UNREF FILE I=194795 OWNER=operator MODE=100400 SIZE=2048 MTIME=Feb 28 13:11 2012
FreeBSD crashes
Hi! A while back I wrote about some problems I was having with FreeBSD crashing randomly. I then disappeared for a while, due to a variety of issues, but I'm still having problems. The computer in question is a general-purpose server -- it runs listservs, websites, databases (both MySQL and PostgreSQL), and Amanda to back up a few other computers. None of this is high volume -- load averages are all less than 1. It has two Intel Xeon processors, with a total of 16 virtual cpus. It runs FreeBSD 8.1, using the amd64 branch in order to access 12G of RAM. It has an Adaptec 5805 RAID card, and is using the Adaptec aac driver 2.2.9-17911 (which is also the flashed BIOS version), and has one array, which is a RAID 10 array. Note that I'm not using the aacu driver, but most of the crashes happened when I was. Based on the randomness of the crashes, I suspect that it's a hardware problem. I have tried to enable core dumps, but it has never succeeded in actually writing one out -- it looks like it has a second crash when it tries to save the core. This leads me to suspect that it might be a problem with the RAID card, but I'm not sure. Is there some way that I can use the information provided during the kernel panics to determine where the problem is? I have photographs of almost all of them. There are a few crashes that didn't result in kernel panics; instead there were a few gibberish characters (from the 128 ASCII codes) on the screen. I have pictures of these as well. Thanks for any suggestions, 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: FreeBSD crashes
I hope someone can help me. I have started to experience seemingly random crashes causing FreeBSD to shutdown and power off the machine. The only trace I can find as far as the reason for the crash is concerned are the following excerpts from /var/log/messages: Mar 23 11:52:36 myhostname kernel: 22NNMIMN NIMIMII IISISSSAAA A 20,22 200E,0,I, S EIEEASI ISAAS f Aff ff Mar 23 11:52:36 myhostname kernel: f Mar 23 11:52:36 myhostname kernel: Mar 23 11:52:36 myhostname kernel: f Mar 23 11:52:36 myhostname kernel: 22 Mar 23 11:52:36 myhostname kernel: f Mar 23 11:52:36 myhostname kernel: Mar 23 11:52:47 myhostname syslogd: exiting on signal 15 Mar 23 13:04:32 myhostname syslogd: kernel boot file is /boot/kernel/kernel True. In the meantime, I've started reading the temperature sensors with freeipmi and graphing them with munin. On a side note, the hardware in question is Dell Poweredge 1750 and I've found following two threads which might be related: Nino, This morning, I received the same crash for the first time. I'm also on 6.1-RELEASE-p1. Generic kernel+SMP option. Also on a Dell 1750. The only difference is that I am not running IPFW. Apr 21 00:49:53 lucky kernel: 22NMNNINMM IMIII S AIIIS SAA S 2A0, 2E20I,20S ,AE0 I,E SEfIAISf S Apr 21 00:49:53 lucky kernel: AA Apr 21 00:49:53 lucky kernel: Apr 21 00:49:53 lucky kernel: 222f f Apr 21 00:49:53 lucky kernel: 2fff Apr 21 00:49:53 lucky kernel: f Apr 21 00:49:53 lucky kernel: Apr 21 01:00:22 lucky kernel: 22NNNMM2MIINI M SS SAA IA S A 2022,020, 0,E,I EESIEISASA AI SffAfff Apr 21 01:00:22 lucky kernel: f Apr 21 01:00:22 lucky kernel: 2 Apr 21 01:00:22 lucky kernel: 2ff Apr 21 01:22:41 lucky syslogd: kernel boot file is /boot/kernel/kernel Dan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD crashes
Yep, it's definitely a NMI (interleaved from several CPUs at once) which most likely means hardware failure. Hello Kris, thanks for confirming my doubts! Regards, -- Nino ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD crashes
n j wrote: I hope someone can help me. I have started to experience seemingly random crashes causing FreeBSD to shutdown and power off the machine. The only trace I can find as far as the reason for the crash is concerned are the following excerpts from /var/log/messages: Mar 23 11:52:36 myhostname kernel: 22NNMIMN NIMIMII IISISSSAAA A 20,22 200E,0,I, S EIEEASI ISAAS f Aff ff Mar 23 11:52:36 myhostname kernel: f Mar 23 11:52:36 myhostname kernel: Mar 23 11:52:36 myhostname kernel: f Mar 23 11:52:36 myhostname kernel: 22 Mar 23 11:52:36 myhostname kernel: f Mar 23 11:52:36 myhostname kernel: Mar 23 11:52:47 myhostname syslogd: exiting on signal 15 Mar 23 13:04:32 myhostname syslogd: kernel boot file is /boot/kernel/kernel Small update: I have received some feedback that this seemingly random junk is related to ipfw (http://www.freebsd.org/cgi/query-pr.cgi?pr=116458). However, I have also received information that this junk might not be completely random and could be, in fact, related to NMI (non-maskable interrupt) which would suggest hardware error. Any thoughts on this? Yep, it's definitely a NMI (interleaved from several CPUs at once) which most likely means hardware failure. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD crashes
Hello everyone, I hope someone can help me. I have started to experience seemingly random crashes causing FreeBSD to shutdown and power off the machine. The only trace I can find as far as the reason for the crash is concerned are the following excerpts from /var/log/messages: Mar 23 11:52:36 myhostname kernel: 22NNMIMN NIMIMII IISISSSAAA A 20,22 200E,0,I, S EIEEASI ISAAS f Aff ff Mar 23 11:52:36 myhostname kernel: f Mar 23 11:52:36 myhostname kernel: Mar 23 11:52:36 myhostname kernel: f Mar 23 11:52:36 myhostname kernel: 22 Mar 23 11:52:36 myhostname kernel: f Mar 23 11:52:36 myhostname kernel: Mar 23 11:52:47 myhostname syslogd: exiting on signal 15 Mar 23 13:04:32 myhostname syslogd: kernel boot file is /boot/kernel/kernel Apr 1 12:46:11 myhostname kernel: 22NNMMII IISSANANM M II22 0I0,ISS, AA EEIISSAA 220f0ff,f, Apr 1 12:46:12 myhostname kernel: Apr 1 12:46:12 myhostname kernel: E Apr 1 12:46:12 myhostname kernel: Apr 1 12:46:12 myhostname kernel: 22EIISSAA Apr 1 12:46:12 myhostname kernel: Apr 1 12:46:21 myhostname syslogd: exiting on signal 15 Apr 1 12:54:00 myhostname syslogd: kernel boot file is /boot/kernel/kernel The system is up-to-date 6.3-RELEASE-p1. Does any of this garbage look familiar to anyone? Thanks for any clues, -- Nino ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD crashes
I hope someone can help me. I have started to experience seemingly random crashes causing FreeBSD to shutdown and power off the machine. The only trace I can find as far as the reason for the crash is concerned are the following excerpts from /var/log/messages: Mar 23 11:52:36 myhostname kernel: 22NNMIMN NIMIMII IISISSSAAA A 20,22 200E,0,I, S EIEEASI ISAAS f Aff ff Mar 23 11:52:36 myhostname kernel: f Mar 23 11:52:36 myhostname kernel: Mar 23 11:52:36 myhostname kernel: f Mar 23 11:52:36 myhostname kernel: 22 Mar 23 11:52:36 myhostname kernel: f Mar 23 11:52:36 myhostname kernel: Mar 23 11:52:47 myhostname syslogd: exiting on signal 15 Mar 23 13:04:32 myhostname syslogd: kernel boot file is /boot/kernel/kernel Small update: I have received some feedback that this seemingly random junk is related to ipfw (http://www.freebsd.org/cgi/query-pr.cgi?pr=116458). However, I have also received information that this junk might not be completely random and could be, in fact, related to NMI (non-maskable interrupt) which would suggest hardware error. Any thoughts on this? -- Nino ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD crashes
In response to n j [EMAIL PROTECTED]: I hope someone can help me. I have started to experience seemingly random crashes causing FreeBSD to shutdown and power off the machine. The only trace I can find as far as the reason for the crash is concerned are the following excerpts from /var/log/messages: Mar 23 11:52:36 myhostname kernel: 22NNMIMN NIMIMII IISISSSAAA A 20,22 200E,0,I, S EIEEASI ISAAS f Aff ff Mar 23 11:52:36 myhostname kernel: f Mar 23 11:52:36 myhostname kernel: Mar 23 11:52:36 myhostname kernel: f Mar 23 11:52:36 myhostname kernel: 22 Mar 23 11:52:36 myhostname kernel: f Mar 23 11:52:36 myhostname kernel: Mar 23 11:52:47 myhostname syslogd: exiting on signal 15 Mar 23 13:04:32 myhostname syslogd: kernel boot file is /boot/kernel/kernel Small update: I have received some feedback that this seemingly random junk is related to ipfw (http://www.freebsd.org/cgi/query-pr.cgi?pr=116458). However, I have also received information that this junk might not be completely random and could be, in fact, related to NMI (non-maskable interrupt) which would suggest hardware error. Any thoughts on this? I suspect you're going to have to get crash dumps in order to get any real answers: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html Based purely on the symptom that the crashes started occurring unrelated to any other activity, I would guess that you've got a hardware issue. Have you tried running things like cpuburn and memtest to see if you can reproduce it? -- Bill Moran http://www.potentialtech.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 crashes
Mar 23 11:52:36 myhostname kernel: 22NNMIMN NIMIMII IISISSSAAA A 20,22 200E,0,I, S EIEEASI ISAAS f Aff ff Mar 23 11:52:36 myhostname kernel: f Mar 23 11:52:36 myhostname kernel: Mar 23 11:52:36 myhostname kernel: f Mar 23 11:52:36 myhostname kernel: 22 Mar 23 11:52:36 myhostname kernel: f Mar 23 11:52:36 myhostname kernel: Mar 23 11:52:47 myhostname syslogd: exiting on signal 15 Mar 23 13:04:32 myhostname syslogd: kernel boot file is /boot/kernel/kernel Small update: I have received some feedback that this seemingly random junk is related to ipfw (http://www.freebsd.org/cgi/query-pr.cgi?pr=116458). However, I have also received information that this junk might not be completely random and could be, in fact, related to NMI (non-maskable interrupt) which would suggest hardware error. Any thoughts on this? -- it says NMI and ISA , just repeats letters a bit ;) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD crashes
In response to n j [EMAIL PROTECTED]: I suspect you're going to have to get crash dumps in order to get any real answers: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html I already started digging through this part of handbook, though I'm not sure I'll be able to read anything useful from the crash dump as I'm no kernel programming expert. But, the next time the machine crashes, dumpdev/dumpdir will hopefully do their part - we'll see. Even if it doesn't help you, it will provide details that you can post with your question so that people can help you more effectively. -- Bill Moran http://www.potentialtech.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 crashes
I suspect you're going to have to get crash dumps in order to get any real answers: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html I already started digging through this part of handbook, though I'm not sure I'll be able to read anything useful from the crash dump as I'm no kernel programming expert. But, the next time the machine crashes, dumpdev/dumpdir will hopefully do their part - we'll see. Based purely on the symptom that the crashes started occurring unrelated to any other activity, I would guess that you've got a hardware issue. Have you tried running things like cpuburn and memtest to see if you can reproduce it? No, not yet. However, I already got advice to try cpuburn, so that is probably what I'll try first thing tomorrow, as there is possibility temperature might be the reason for the unexpected crash (true, it's not very likely as there are other machines in the same server room with the same hardware and this is the only machine that powered off, though it's the only one running FreeBSD). I'll also try memtest. Thanks for the suggestions! Regards, -- Nino ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD crashes
Even if it doesn't help you, it will provide details that you can post with your question so that people can help you more effectively. True. In the meantime, I've started reading the temperature sensors with freeipmi and graphing them with munin. On a side note, the hardware in question is Dell Poweredge 1750 and I've found following two threads which might be related: http://lists.freebsd.org/pipermail/freebsd-smp/2005-November/001016.html http://lists.freebsd.org/pipermail/freebsd-stable/2005-November/019932.html Even if not the same as the problem at hand, it shows that Dell has stability issues with running FreeBSD, not to mention that there are no hw.acpi.thermal.* knobs whatsoever in sysctl output on this machine. Regards, -- Nino ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD crashes on my laptop...
Hello... I am running FreeBSD 6.1-RELEASE (AMD64) on an Acer Ferrari 3400 laptop... Specs... Mobile AMD athlon 3000+ 128mb ATI radeon 9700... I install it and everything seems to get detected and all... but then... it suddenly crashes... system just shuts down... no error appears on the screen... Well, this has been consistenly happening generally when I'm installing some port... Once it was KDE, other times it was Opera and most recently it was VLC... Once it crashed even when I ran the command find / vimrc. I know the syntax of the comand may not be correct, it was just traversing through all the directories and it crashed (I was tryin to find the default vimrc file). All this when I was running X under window-maker... Also it crashed once when it was in GNOME and the computer was idle for like 30mins or so and it crashed (Gnome installs during the installation process, not the ports way) So, I figure X might be the problem... So the next time I boot, I dont start X and I make VLC and it crashes around the same place I expect it to... Is it the laptop? How can I debug something like this.. get the log files or somethin just before the crash... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD crashes on my laptop...
First of all, ensure that you are not having a temperature issue check the cooler of the laptop, maybe it is crossing to the other world... Ahmed Parkar escribió: Hello... I am running FreeBSD 6.1-RELEASE (AMD64) on an Acer Ferrari 3400 laptop... Specs... Mobile AMD athlon 3000+ 128mb ATI radeon 9700... I install it and everything seems to get detected and all... but then... it suddenly crashes... system just shuts down... no error appears on the screen... Well, this has been consistenly happening generally when I'm installing some port... Once it was KDE, other times it was Opera and most recently it was VLC... Once it crashed even when I ran the command find / vimrc. I know the syntax of the comand may not be correct, it was just traversing through all the directories and it crashed (I was tryin to find the default vimrc file). All this when I was running X under window-maker... Also it crashed once when it was in GNOME and the computer was idle for like 30mins or so and it crashed (Gnome installs during the installation process, not the ports way) So, I figure X might be the problem... So the next time I boot, I dont start X and I make VLC and it crashes around the same place I expect it to... Is it the laptop? How can I debug something like this.. get the log files or somethin just before the crash... ___ 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: FreeBSD crashes on my laptop...
Are the crashes always with X running? ATI support is not good for X. -Derek At 01:15 AM 7/29/2006, Ahmed Parkar wrote: Hello... I am running FreeBSD 6.1-RELEASE (AMD64) on an Acer Ferrari 3400 laptop... Specs... Mobile AMD athlon 3000+ 128mb ATI radeon 9700... I install it and everything seems to get detected and all... but then... it suddenly crashes... system just shuts down... no error appears on the screen... Well, this has been consistenly happening generally when I'm installing some port... Once it was KDE, other times it was Opera and most recently it was VLC... Once it crashed even when I ran the command find / vimrc. I know the syntax of the comand may not be correct, it was just traversing through all the directories and it crashed (I was tryin to find the default vimrc file). All this when I was running X under window-maker... Also it crashed once when it was in GNOME and the computer was idle for like 30mins or so and it crashed (Gnome installs during the installation process, not the ports way) So, I figure X might be the problem... So the next time I boot, I dont start X and I make VLC and it crashes around the same place I expect it to... Is it the laptop? How can I debug something like this.. get the log files or somethin just before the crash... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Crashes
Hello dear Subscribers! I have mail-server (~ 2 users, exim/cyrrus imap/webmail/LDAP auth) under FreeBSD 5.2 box with last patches. After 3 weeks of normal fly it`s crash twice a day. systat -vmstat at ssh-console before crash shows this: 1 usersLoad 0.25 0.14 0.12 Mar 7 19:27 Mem:KBREALVIRTUAL VN PAGER SWAP PAGER Tot Share TotShareFree in out in out Act 3832485716 1355036 8340 713528 count All 1309940 26832 235812467152 pages 2824 zfod Interrupts Proc:r p d s wCsw Trp Sys Int Sof Flt 2470 cow2007 total 14 470486605 36239 701122723 2785 651 7136 280936 wire1: atkb 342280 act 180 8: rtc 50.2%Sys 3.6%Intr 7.5%User 0.0%Nice 38.6%Idl 685692 inact 9: acpi ||||||||||cache 13: npx =++746492 freestray 1 daefr 15: ata Namei Name-cacheDir-cache 741 prcfr 1452 30: em0 Calls hits% hits% react 235 49: ahd 173348 162134 94 pdwak 50: ahd pdpgs 140 0: clk Disks da0 da1 da2 pass0 pass1 pass2 pass3 intrn KB/t 10.81 11.37 0.00 0.00 0.00 0.00 0.00204096 buf tps 164 5 0 0 0 0 0 1094 dirtybuf MB/s 1.73 0.06 0.00 0.00 0.00 0.00 0.00161230 desiredvnodes % busy 13 1 0 0 0 0 0 47511 numvnodes 37 freevnodes Can you tell me, why system used so much name-cache and network card interrupts, I think it`s a cause of crash :-( Any comments ? My system configuration: FreeBSD mail.domain.com 5.2-RELEASE FreeBSD 5.2-RELEASE #10: Sun Mar 7 09:47:36 VLAT 2004 [EMAIL PROTECTED] :/usr/src/sys/i386/compile/MAIL i386 CPU: Intel(R) Xeon(TM) CPU 2.40GHz (2392.29-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf25 Stepping = 5 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Hyperthreading: 2 logical CPUs real memory = 2147418112 (2047 MB) avail memory = 2078699520 (1982 MB) ACPI APIC Table: INTEL SWV25 FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs acpi0: INTEL SWV25on motherboard pcibios: BIOS version 2.10 Using $PIR table, 19 entries at 0x800f3630 acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 acpi_cpu0: CPU on acpi0 acpi_cpu1: CPU on acpi0 acpi_cpu2: CPU on acpi0 acpi_cpu3: CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pci0: unknown at device 0.1 (no driver attached) pcib1: ACPI PCI-PCI bridge at device 3.0 on pci0 pcib1: could not get PCI interrupt routing table for \\_SB_.PCI0.P0P5 - AE_NOT_FOUND pci2: ACPI PCI bus on pcib1 pci2: base peripheral, interrupt controller at device 28.0 (no driver attached) pcib2: ACPI PCI-PCI bridge at device 29.0 on pci2 pci4: ACPI PCI bus on pcib2 ahd0: Adaptec AIC7902 Ultra320 SCSI adapter port 0x4000-0x40ff,0x3800-0x38ff mem 0xfe9d-0xfe9d1fff irq 50 at device 7.0 on pci4 aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs ahd1: Adaptec AIC7902 Ultra320 SCSI adapter port 0x3400-0x34ff,0x3000-0x30ff mem 0xfe9e-0xfe9e1fff irq 49 at device 7.1 on pci4 aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs pci2: base peripheral, interrupt controller at device 30.0 (no driver attached) pcib3: ACPI PCI-PCI bridge at device 31.0 on pci2 pci3: ACPI PCI bus on pcib3 em0: Intel(R) PRO/1000 Network Connection, Version - 1.7.19 port 0x2040-0x207f mem 0xfe6c-0xfe6d irq 30 at device 7.0 on pci3 em0: Speed:N/A Duplex:N/A em1: Intel(R) PRO/1000 Network Connection, Version - 1.7.19 port 0x2000-0x203f mem 0xfe6e-0xfe6f irq 31 at device 7.1 on pci3 em1: Speed:N/A Duplex:N/A pci0: unknown at device 3.1 (no driver attached) pci0: serial bus, USB at device 29.0 (no driver attached) pci0: serial bus, USB at device 29.1 (no driver attached) pcib4: ACPI PCI-PCI bridge at device 30.0 on pci0 pci1: ACPI PCI bus on pcib4 pci1: display, VGA at device 12.0 (no driver attached) isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH3 UDMA100 controller port 0x3a0-0x3af,0-0x3,0-0x7,0-0x3,0-0x7 at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] pci0: serial bus, SMBus at device 31.3 (no driver attached) atkbdc0: Keyboard
