The smartctl tests on the three drives came back saying they were checked
100% without error; bad sectors have always caused an error and an aborted
scan at the point of trouble for me in the past.
I 'thought' I recalled seeing a panic along the lines of ffs_free or
something related to
Something like the following should use the power of sysctl. physmem and
usermem in place of realmem may be of use too. Just wish I knew proper values
nad logic to tweak kern.ipc.shmmax and similar paramaters.
int realmem;
char* realmem_mib_name = hw.realmem;
For the encrypted DVDs, have you set a region for the drive to match? How are
you accessing them? Further hardware information may help (people better at
this than I) identify issues; what SATA controller connects the drive. Last I
checked, my promise controller cards seem to have incomplete
The FreeBSD Developers' Handbook describes how to get panic information (and
dig out further details).
http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html#KERNELDEBUG-OBTAIN
Was there any output before ad7: FAILURE - device detached? Losing the drive
in the
The keyboard works in some apps but not others? What video driver (and have
you tried vesa if not using it to see if the problem can still be
reproduced)? All x11 related drivers were rebuilt too? Output from the xorg
logfile and your xorg.conf may be helpful. Maybe there is other relevant
After one of the last crashes, the system would lock up a short time after
rebooting. I found the problem caused by background fsck locking up the
system. I took the partition out of the startup check for now. I 'think' I
was installing a port during the last crash, but it has been a while.
I do not know where I should ask for help but I have core files from July
24, 23, 21 (x2), 19, 16 (x2) and May 17. All of the July crashes appear
similar. The May crash was unrelated but shows that things were relatively
stable until the first of these glitches. I am currently using the
