> I got the following on a not quite fully setup current-i386 system - it's
> close though ... While supping sources
> 
> _Debugger(f8711200,fa484d90,f8154976,f81547d8,f81547b8) at _Debugger+0x4
> _panic(f81547d8,f81547b8,8180,41a21,f86e80d4) at _panic+0x46
> _ffs_valloc(fa484db8,fa484e10,fa484e24,fa484ee0,25) at _ffs_valloc+0x12e
> _ufs_makeinode(8180,f8726980,fa484ef0,fa484f04,fa484e84) at
> _ufs_makeinode+0x78
> _ufs_create(fa484e10) at _ufs_create+0x25
> _vn_open(fa484ee0,602,180,f819dd88,f8708a00) at _vn_open+0xd8
> _sys_open(f8708a00,fa484f88,fa484f80,0,2569c0) at _sys_open+0x97
> _syscall() at _syscall+0x154
> --- syscall (number 5) ---
> 0x4006d9a7

While my call traceback varies, I'm suffering from a rash of ffs_valloc()
panic's on a Pentium 133 system running 1.2.  What's interesting is that
it also tends to be paired (usually just after) my "/var/cron/log" file
getting turned into scrambled eggs.  I took my disk out of a running
Pentium 120 system that had an Adaptec AHA2940 in it and put it into this
system that has an Adaptec 3940 in it (only using the first channel).

If anyone has any ideas - or knows why "/var/cron/log" is continually getting
wiped out (i.e., "fsck" on "/var" keeps finding that "/var/cron/log" is
mangled every few days, and torches it) - I'd appreciate hearing from you.
Are there any changes in 1.2.1 that might address this?

	- Greg