What caused this kernel panic?
#0 doadump () at pcpu.h:159
#1 0xc04d9efb in boot (howto=260) at ../../../kern/kern_shutdown.c:397
#2 0xc04da221 in panic (fmt=0xc060106c %s) at
../../../kern/kern_shutdown.c:553
#3 0xc05dd308 in trap_fatal (frame=0xe83ef980, eva=28) at
../../../i386/i386/trap.c:809
#4 0xc05dd04b in trap_pfault (frame=0xe83ef980, usermode=0, eva=28) at
../../../i386/i386/trap.c:727
#5 0xc05dcca5 in trap (frame=
{tf_fs = -1068761064, tf_es = -398589936, tf_ds = 16777232, tf_edi =
-993459960, tf_esi = -1037469184, tf_ebp = -398526004, tf_isp = -398526036,
tf_ebx = -1031939584, tf_edx = 0, tf_ecx = -1037239168, tf_eax = 4,
tf_trapno = 12, tf_err = 2, tf_eip = -1068763929, tf_cs = 8, tf_eflags =
66118, tf_esp = -1031939584, tf_ss = -1037469184})
at ../../../i386/i386/trap.c:417
#6 0xc05cb7da in calltrap () at ../../../i386/i386/exception.s:140
#7 0xc04c0018 in kern_execve (td=0xc2297a00, fname=0x0, argv=0x0,
envv=0xc27dda10, mac_p=0xc27dda00)
at ../../../kern/kern_exec.c:242
#8 0xc05087b1 in ttwakeup (tp=0xc2297a00) at ../../../kern/tty.c:2370
#9 0xc0507414 in ttymodem (tp=0xc27dda00, flag=0) at
../../../kern/tty.c:1625
#10 0xc050b0ff in ptcopen (dev=0xc2297a00, flag=3, devtype=8192, td=0x0) at
linedisc.h:136
#11 0xc04a231a in spec_open (ap=0xe83efa84) at
../../../fs/specfs/spec_vnops.c:207
#12 0xc04a205f in spec_vnoperate (ap=0x0) at
../../../fs/specfs/spec_vnops.c:118
#13 0xc053813d in vn_open_cred (ndp=0xe83efbe4, flagp=0xe83efce4, cmode=0,
cred=0xc3c16980, fdidx=0) at vnode_if.h:228
#14 0xc0537d22 in vn_open (ndp=0x0, flagp=0xe83efce4, cmode=0, fdidx=6) at
../../../kern/vfs_vnops.c:91
#15 0xc0531e3b in kern_open (td=0xc22cfc80, path=0x0, pathseg=UIO_USERSPACE,
flags=3, mode=0)
at ../../../kern/vfs_syscalls.c:957
#16 0xc0531d54 in open (td=0xc22cfc80, uap=0x0) at
../../../kern/vfs_syscalls.c:926
#17 0xc05dd613 in syscall (frame=
{tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = -1077943301, tf_esi =
673008685, tf_ebp = -1077943272, tf_isp = -398525068, tf_ebx = 673015904,
tf_edx = 673008700, tf_ecx = 674465260, tf_eax = 5, tf_trapno = 12, tf_err =
2, tf_eip = 673977623, tf_cs = 31, tf_eflags = 662, tf_esp = -1077943364,
tf_ss = 47}) at ../../../i386/i386/trap.c:1001
#18 0xc05cb82f in Xint0x80_syscall () at ../../../i386/i386/exception.s:201
#19 0x002f in ?? ()
#20 0x002f in ?? ()
#21 0x002f in ?? ()
#22 0xbfbfe3fb in ?? ()
#23 0x281d4c2d in ?? ()
#24 0xbfbfe418 in ?? ()
#25 0xe83efd74 in ?? ()
#26 0x281d6860 in ?? ()
#27 0x281d4c3c in ?? ()
#28 0x283385ec in ?? ()
#29 0x0005 in ?? ()
#30 0x000c in ?? ()
#31 0x0002 in ?? ()
#32 0x282c1517 in ?? ()
#33 0x001f in ?? ()
#34 0x0296 in ?? ()
#35 0xbfbfe3bc in ?? ()
#36 0x002f in ?? ()
#37 0x in ?? ()
#38 0x in ?? ()
#39 0x in ?? ()
#40 0x in ?? ()
#41 0x148e3000 in ?? ()
#42 0xc2831a98 in ?? ()
#43 0xc22cfc80 in ?? ()
#44 0xe83efaac in ?? ()
#45 0xe83efa94 in ?? ()
#46 0xc1e7d4b0 in ?? ()
#47 0xc04ea503 in sched_switch (td=0x281d4c2d, newtd=0x281d6860,
flags=Cannot access memory at address 0xbfbfe428
) at ../../../kern/sched_4bsd.c:865
Panicstring: page fault
uname -pr
5.3-RELEASE-p5 i386
Please advice.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
What caused this ?
Hi all, I have had a server freeze after about 7 days of uptime. When I got to the terminal the screen was full of this message :- swap_pager: indefinite wait buffer: device: ad0s1f, blkno: 663, size 20480 swap_pager: indefinite wait buffer: device: ad0s1f, blkno: 4096, size 329 The keyboard was frozen but an attempt at another terminal produced something like this :- fatal trap 12: page fault while in kernel mode fault virtual address = 0x2 falt code = supervisor read, page not present IP, FP, S Pointers = various hex panic page fault I ended up rpessing reset. Any offerrs ? Thanks ! I read this on a site and checked the cables / did an entire surface scan with no bad results although elsewhere suggests the disc is on its way out. I dont mind buying another but would like 2nd opinions :) --- What does the error ``swap_pager: indefinite wait buffer:'' mean? This means that a process is trying to page memory to disk, and the page attempt has hung trying to access the disk for more than 20 seconds. It might be caused by bad blocks on the disk drive, disk wiring, cables, or any other disk I/O-related hardware. If the drive itself is actually bad, you will also see disk errors in /var/log/messages and in the output of dmesg. Otherwise, check your cables and connections. Custom PC North West Open Source Solutions http://www.cpcnw.co.uk ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
What caused my box to die?
Well, I'm just about done rebuilding my box after a major crash and burn. Now that things are slowing down, I'd like to get some input on what might have caused the crash. I'm wondering if I stumbled on some obscure bug, or maybe a known bug that hasn't ever been fixed. Let me describe the scenario before and after the crash: I had 3 machines on my LAN at the time. The network config is simple: DSL Modem -- Gateway (also my workstation) -- Switch -- Laptop and test machine My gateway was running FreeBSD 4.7. Just before the crash, I was copying movies via FTP from the gateway to the laptop. At the same time, I was copying a single movie from the test machine to the gateway. I looked over at the test machine and noticed the transfer had died, and tried to reestablish connection with the gateway. The LAN link was dead on both the test machine and the laptop, which I found to be extremely strange (this had never happened before). So, I went over to the gateway (which was still running), and I decided to check to see if the gateway was even on the internet. I typed 'ping ftp.cdrom.com' and pressed Enter. IMMEDIATELY after I pressed Enter, the box completely froze up. I waited about 60 seconds to see if it would unfreeze, but it was no use. I hard reset the box, and upon reboot the machine was unable to boot from /. In addition, several of my partitions on ad0 were completely hosed. At this point I got pissed off and just powered down all machines and decided to wait until the next morning to mess with fixing anything. However, the next morning, the test machine wouldn't even turn on. This is the 2nd time its done that, so I have a feeling it's just a bad coincidence. After removing the internal cables and plugging them back in, the machine started back up and worked fine. The only change to the machine that I can think of is I added 1gb of Kingston Value RAM to the box a few days prior. However, the RAM had been working perfectly for a few days before the crash, and for a few days since I rebuilt the machine. Is there a port to thoroughly examine the RAM and make sure its OK? The fact that I had 2 large file transfers going at the time of the problem really seems strange to me, because thats the first time I had even done that with this gateway (the laptop is brand new). Perhaps something went wrong with my ipf/ipnat? Anyhow, if you took the time to read this entire message and have some theories, I'm all ears. I'd like to do whatever I can to avoid this problem in the future. I'm now running FreeBSD 4.8 on the box with a custom kernel. Seems to be working perfectly. Thanks. -- Adam [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What caused my box to die?
You might want to take a look at http://www.memtest86.com/ for a tool to test RAM. Raphael Le Jeudi, 29 mai 2003, à 21:49 Europe/Zurich, Adam a écrit : Well, I'm just about done rebuilding my box after a major crash and burn. Now that things are slowing down, I'd like to get some input on what might have caused the crash. I'm wondering if I stumbled on some obscure bug, or maybe a known bug that hasn't ever been fixed. Let me describe the scenario before and after the crash: I had 3 machines on my LAN at the time. The network config is simple: DSL Modem -- Gateway (also my workstation) -- Switch -- Laptop and test machine My gateway was running FreeBSD 4.7. Just before the crash, I was copying movies via FTP from the gateway to the laptop. At the same time, I was copying a single movie from the test machine to the gateway. I looked over at the test machine and noticed the transfer had died, and tried to reestablish connection with the gateway. The LAN link was dead on both the test machine and the laptop, which I found to be extremely strange (this had never happened before). So, I went over to the gateway (which was still running), and I decided to check to see if the gateway was even on the internet. I typed 'ping ftp.cdrom.com' and pressed Enter. IMMEDIATELY after I pressed Enter, the box completely froze up. I waited about 60 seconds to see if it would unfreeze, but it was no use. I hard reset the box, and upon reboot the machine was unable to boot from /. In addition, several of my partitions on ad0 were completely hosed. At this point I got pissed off and just powered down all machines and decided to wait until the next morning to mess with fixing anything. However, the next morning, the test machine wouldn't even turn on. This is the 2nd time its done that, so I have a feeling it's just a bad coincidence. After removing the internal cables and plugging them back in, the machine started back up and worked fine. The only change to the machine that I can think of is I added 1gb of Kingston Value RAM to the box a few days prior. However, the RAM had been working perfectly for a few days before the crash, and for a few days since I rebuilt the machine. Is there a port to thoroughly examine the RAM and make sure its OK? The fact that I had 2 large file transfers going at the time of the problem really seems strange to me, because thats the first time I had even done that with this gateway (the laptop is brand new). Perhaps something went wrong with my ipf/ipnat? Anyhow, if you took the time to read this entire message and have some theories, I'm all ears. I'd like to do whatever I can to avoid this problem in the future. I'm now running FreeBSD 4.8 on the box with a custom kernel. Seems to be working perfectly. Thanks. -- Adam [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: What caused my box to die?
On Thu, 2003-05-29 at 17:08, Raphaël Marmier wrote: You might want to take a look at http://www.memtest86.com/ for a tool to test RAM. I actually just got done running that. It didn't turn up any errors. Also, I thought I'd mention that my two NIC's are Linksys (dc0) and 3com (xl0). The Linksys is connected to the DSL modem, and the 3com to the switch. -- Adam [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What caused my box to die?
On 29 May 2003 15:49:00 -0400 Adam [EMAIL PROTECTED] wrote: Well, I'm just about done rebuilding my box after a major crash and burn. Now that things are slowing down, I'd like to get some input on what might have caused the crash. I'm wondering if I stumbled on some obscure bug, or maybe a known bug that hasn't ever been fixed. Let me describe the scenario before and after the crash: The things that you describe sound like hardware-induced problems. I was having similar problems last month, and the solution finally was a new motherboard. Dmesg reported hard disk errors, but installing another hard disk didn't solve the problem. The machine would periodically freeze, files would get trashed, etc. Intermittent problems like this are hard to diagnose - the only thing worse than bad hardware is half-bad hardware. I installed a new motherboard, and the problems went away. Of course, your mileage may vary. good luck, Robert ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Panic out of dqget() (was: What caused this Panic)
On Thursday, 6 February 2003 at 19:21:18 -0500, Simon wrote: On Tue, 28 Jan 2003 14:16:39 +1030, Greg 'groggy' Lehey wrote: On Monday, 27 January 2003 at 22:29:15 -0500, Simon wrote: Hi, I just had a server panic due to something wrong with disk quotas, I guess. panic: dqget: free dquot isn't Can someone please explain what the above is about. Yes, it means that the kernel found a discrepancy in quota allocation, in the function dqget() (/usr/src/sys/ufs/ufs/ufs_quota.c). Possibly that's not enough for you. To find out more, we need a dump. Even then, it could be difficult. A little information on the circumstances could help. I have the dump now. I've sent this to freebsd-bugs. I'm not sure if that was the right place. It's a good first step. How should I proceed to have someone debug this? The core dump is 2GB If you don't get an answer to your message, send a PR (use send-pr for this). In view of the size of the dump, you probably want to consider giving somebody access to the dumps on your machine. They'll also need access to the source code. You *did* build a kernel with debug symbols, right? 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 Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers msg18456/pgp0.pgp Description: PGP signature
What caused this Panic
Hi, I just had a server panic due to something wrong with disk quotas, I guess. panic: dqget: free dquot isn't Can someone please explain what the above is about. Thank you, Simon To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
What caused this Panic
Hi, I just had a server panic due to something wrong with disk quotas, I guess. panic: dqget: free dquot isn't Can someone please explain what the above is about. Thank you, Simon To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Panic out of dqget() (was: What caused this Panic)
On Monday, 27 January 2003 at 22:29:15 -0500, Simon wrote: Hi, I just had a server panic due to something wrong with disk quotas, I guess. panic: dqget: free dquot isn't Can someone please explain what the above is about. Yes, it means that the kernel found a discrepancy in quota allocation, in the function dqget() (/usr/src/sys/ufs/ufs/ufs_quota.c). Possibly that's not enough for you. To find out more, we need a dump. Even then, it could be difficult. A little information on the circumstances could help. 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 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
