At 7:50 PM -0500 1/29/03, Garance A Drosihn wrote:
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.
So, what should I do at this point to help pin this down?
To follow up on this... After cvsup-ing to the 5.0-current from
Feb 3rd, I can not reproduce the panic. Apparently the problem
was something that was fixed in the past week or so. There is
probably no need to look into these two panic reports.
--
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
