Installed a kernel based on yesterday's src/ tree. The kernel panicked and the generated core seems to be corrupt. Is there a known issue with getting core dumps on x86_64 freebsd? The top of the core.txt.0 file shows
troutmask.apl.washington.edu dumped core - see /usr/tmp/vmcore.0 Fri Aug 27 11:26:26 PDT 2010 FreeBSD troutmask.apl.washington.edu 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r211766M: Tue Aug 24 14:52:25 PDT 2010 ka...@troutmask.apl.washington.edu:/usr/obj/usr/src/sys/SPEW amd64 panic: page fault GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Cannot access memory at address 0xffffff01ffffffe0 (kgdb) #0 0x0000000000000000 in ?? () Cannot access memory at address 0x0 (kgdb) If anyone wants the entire content of core.txt.0, simply request it. My was doing the following when the panic occurred: 1) Running rsync via cron to back up /usr/home accounts from /dev/ad6s1f to /dev/ad4s1f. Both file systems use softupdates+journaling. 2) Building ports/www/firefox (which is version 3.6.8) 3) Running the GCC dejagnu testsuite for the gfortran compiler 4) Using firefox-3.5.11 to view a site that drives the Xorg srever to 90% CPU usage. -- Steve _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
