Cannot get kernel core dump

[Pietro Cerutti]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Toomas Aas wrote:
| Hello!
|
| I'm trying to report a problem which involves kernel panic, but I
cannot get a
| core dump. The system is 7.0-STABLE from June 18th.
|
| I've set the following in /etc/rc.conf (and of course rebooted, even
several
| times):
| dumpdev="/dev/ad0s1b"
| dumpdir="/home/crash"
|
| The machine has 512 MB RAM and swap partition is also 512 MB, but
according to
| dumpon(8) this shouldn't be a problem, because hw.physmem is still
somewhat
| smaller than the swap partition:
|
| bsd# sysctl hw.physmem
| hw.physmem: 527863808
|
| bsd# swapinfo
| Device          1K-blocks     Used    Avail Capacity
| /dev/ad0s1b        524288        0   524288     0%
|
| /home partition, where I've created the crash directory, has 55 GB
free space.
|
| When the machine boots up, it dutifully reports:
| kernel dumps on /dev/ad0s1b
|
| Then I "do the thing" that causes the panic. System prints the panic
message
| and hangs. Only thing left to do is press the reset button. On next
boot, the
| log says
| savecore: no dumps found
|
| When the system panics and prints the panic message, it doesn't say
anything
| about saving the coredump. I haven't had a kernel panic for a long
time, but
| I seem to remember that in the past there was some kind of message to
that
| effect.
|
| Are there known conditions under which the core dump really isn't
recorded, or
| am I simply missing something obvious?

Yes, if the panic occurs before the filesystem supposed to contain the
crash dumps is mounted. Is it the case?

|
| --
| Toomas
| _______________________________________________
| freebsd-questions at freebsd.org mailing list
| http://lists.freebsd.org/mailman/listinfo/freebsd-questions
| To unsubscribe, send any mail to
"freebsd-questions-unsubscribe at freebsd.org"


- --
Pietro Cerutti
gahr at FreeBSD.org

PGP Public Key:
http://gahr.ch/pgp

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)

iEYEAREKAAYFAkhiVTgACgkQwMJqmJVx9454AwCgowIDacy0X33iBwbC0QRVCYjw
zGcAnig8zjnlrq1njlwqO7pJOGIyOV3O
=4wCh
-----END PGP SIGNATURE-----