At 9:49 PM -0500 1/28/03, Garance A Drosihn wrote:
Hmm, well, I finally got my first actual system panic which wasn't
obviously caused by my own screwing around. On the console I have:
free inode /usr/cvs/net/64 had 0 blocks
panic: Negative bio_offset (-19038208) on bio 0xce51be28
cpuid = 0; lapic.id = 01000000
Debugger("panic")
Stopped at Debugger+0x55: xchgl %ebx,in_Debugger.0
It looks like the sequence which generated that panic can be
repeated to generate other panics. My sequence was:
use sysinstall to remove and then recreate the
new UFS2 partition, 3100 meg in size,
mounted on /usr/cvs/net
pushd /usr/cvs/net-old
tar cf - ./ | (popd; cd /usr/cvs/net; tar xpf -)
and again I got a panic, although not quite the same panic.
It also seemed like it happened much sooner in the process.
This time it says:
free inode /usr/cvs/net/64 had 0 blocks
mode = 0177777, inum = 78, fs = /usr/cvs/net
panic: ffs_valloc: dup alloc
cpuid = 0; lapic.id = 01000000
Debugger("panic")
Stopped at Debugger+0x55: xchgl %ebx,in_Debugger.0
The first panic was while doing a 'mkdir'. There's no mkdir
in the traceback this time. It looks like the system was in
the middle of an open() call (syscall 5).
It's interesting that all three panics mentioned /usr/cvs/net/64,
even though the source directory has no file-or-directory
named '64' in it.
I expect that some system dumps would be more useful than me
typing in backtraces, so I set up dumpdev and dumpdir in rc.conf,
rebooted, and tried again. The system panic'ed again, looking
about the same as the second panic. I typed 'panic' in the
debugger, it says
panic: from debugger
cpuid = 1; lapic.id = 00000000
boot() called on cpu#1
Uptime: 6m8s
Dumping 511 MB
ata0: resetting devices
I let it sit there, well, for about 20 minutes, before deciding
that nothing is happening and I powered the machine off and on
to get it back. There was no dump in the dump-dir. I've tried
this a number of times now, and it seems I never get a dump. My
dumpdir is on a UFS1 partition, I'm using it instead of /var
because my /var is 256meg and this partition is over 1 gig.
So, what should I do at this point to help pin this down?
--
Garance Alistair Drosehn = [EMAIL PROTECTED]
Senior Systems Programmer or [EMAIL PROTECTED]
Rensselaer Polytechnic Institute or [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
