Re: No core dump after panic
Well, this means that, since your previous kernel panicked but was not able to save a coredump, when you boot up from another kernel there is simply nothing there for savecore to recover. As a result savecore is reporting that there is nothing to recover for you. But that's the way to set it up. And you can ignore the "unable to open bounds file" message; it means that the bounds file wasn't there but it created it for you automatically. SC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: No core dump after panic
On 3/22/07, Rajkumar S <[EMAIL PROTECTED]> wrote: On 3/22/07, Simon Chang <[EMAIL PROTECTED]> wrote: > Check out "man savecore" for a list of flags. Thanks, I will check that out. I have reinstalled and now starting from scratch to see if I can get the core dump of a panic. dumpdev="/dev/ad2s1b" dumpdir="/var/crash" savecore_flags="-v -z" hw.physmem: 508989440 Device 1K-blocks UsedAvail Capacity /dev/ad2s1b7680000 768000 0% /dev/ad2s1d989M7.9M902M 1%/var My kernel panics immediately on boot up, before the disks are probed. After panic I boot with a different kernel to extract the core. But I get the following error during boot up. Checking for core dump on /dev/ad2s1b... unable to open bounds file, using 0 checking for kernel dump on device /dev/ad2s1b mediasize = 786432000 sectorsize = 512 magic mismatch on last dump header on /dev/ad2s1b savecore: no dumps found Any idea? raj ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: No core dump after panic
On 3/22/07, Simon Chang <[EMAIL PROTECTED]> wrote: Check out "man savecore" for a list of flags. Thanks, I will check that out. Have you submitted a formal PR? I have to say that I have not had experience with that device or driver. What other responses have you gotten from people? Yes, 110663, Sam Leffler the author of the driver has responded. I hope he will fix this problem. raj ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: No core dump after panic
I did not use /var/crash because /var was small than RAM. So I manually changed the crash directory to /usr partition. I do not know how to set savecore flag. Check out "man savecore" for a list of flags. You normally set them in /etc/rc.conf by putting in a line like: savecore_flags="-v -z", where -v puts in extra debugging information and -z compresses the coredump so that you save some space. The panic happens only when safenet driver is complied in., GENERIC freebsd kernel boots up fine. I am using Axiomtek NA-1281A* I have reported the details about the panic in another mail+, Have you submitted a formal PR? I have to say that I have not had experience with that device or driver. What other responses have you gotten from people? SC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: No core dump after panic
Hi, Thanks for your reply! On 3/21/07, Simon Chang <[EMAIL PROTECTED]> wrote: From what you are saying it sounds like you are getting the panic on bootup. Is that correct? Yes. immediately on boot up. In looking through your config I don't see anything that really stands out (although I would use "/var/crash" for dumpdir, and you didn't specify savecore_flags). I did not use /var/crash because /var was small than RAM. So I manually changed the crash directory to /usr partition. I do not know how to set savecore flag. What else have you tried to get this kernel to boot? Do you have another kernel you were able to boot from? What about your exact hardware config? The panic happens only when safenet driver is complied in., GENERIC freebsd kernel boots up fine. I am using Axiomtek NA-1281A* I have reported the details about the panic in another mail+, raj * http://www.axiomtek.com.tw/Products/ViewProduct.asp?view=179 + http://lists.freebsd.org/pipermail/freebsd-questions/2007-March/145020.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: No core dump after panic
Hey there, From what you are saying it sounds like you are getting the panic on bootup. Is that correct? In looking through your config I don't see anything that really stands out (although I would use "/var/crash" for dumpdir, and you didn't specify savecore_flags). What else have you tried to get this kernel to boot? Do you have another kernel you were able to boot from? What about your exact hardware config? More information would be helpful. SC ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
No core dump after panic
Hi, I am trying to get core dump of a kernel panic relating to safenet driver, so that I can file a meaning full PR or even try to debug myself. But I am not getting a core dump after panic. I have gone thorough the developers manual and I believe I have taken care of all the usual stuff. rc.conf dumpdev="/dev/ad2s1b" dumpdir="/usr/local/crash" sysctl hw.physmem hw.physmem: 508989440 swapinfo Device 1K-blocks UsedAvail Capacity /dev/ad2s1b 10485760 1048576 0% df -h | grep usr$ /dev/ad2s1f6.8G1.2G5.1G18%/usr The panic occurs before the disk drivers are loaded, ie just after network is probed. Could that be the reason? last couple of lines in dmesg while panic is as follows. rl7: port 0xac00-0xacff mem 0xf6007000-0xf60070ff i2miibus7: on rl7 rlphy7: on miibus7 rlphy7: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl7: Ethernet address: 00:60:e0:04:29:e4 safe0 mem 0xf612-0xf6121fff irq 5 at device 10.0 on pci0 safe0: cannot allocate DMA tag device_attach: safe0 attach returned 6 re0: port 0xb000-0xb0ff mem 0xf6120re0: could not allocate dma tag Fatal trap 12: page fault while in kernel mode fault virtual address = 0x60 fault code = supervisor read, page not present instruction pointer = 0x20:0xc0570ea5 stack pointer = 0x28:0xc0c20bd0 frame pointer = 0x28:0xc0c20be4 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) trap number = 12 panic: page fault Uptime: 1s raj ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
