On Friday, 26. November 2004 08:25, Xin LI wrote:
> On Fri, Nov 26, 2004 at 06:00:43AM +0100, Michael Nottebrock wrote:
> > This came out of thin air, I have no idea what caused it and how to
> > reproduce it, but I had crash dumps enabled, so here goes... Could this
> > be a sign of a hdd going ba
On Fri, Nov 26, 2004 at 06:00:43AM +0100, Michael Nottebrock wrote:
> This came out of thin air, I have no idea what caused it and how to reproduce
> it, but I had crash dumps enabled, so here goes... Could this be a sign of a
> hdd going bad?
It's possible. Will you please post the output of `
This came out of thin air, I have no idea what caused it and how to reproduce
it, but I had crash dumps enabled, so here goes... Could this be a sign of a
hdd going bad?
Backtrace:
IdlePTD at physical address 0x005e9000
initial pcb at physical address 0x004ce4a0
panicstr: ffs_blkfree: bad size
