Jordan, Cy and co.,
I'll admit my concept of time was taken from me during lectures on special
relativity, but for all observers on the list, I added fdesc after the
crashes began. I didn't see any problem with trying it.
I'll add the mfs mounts back later and poke the system by running
"periodi
> MFS will not cause you problems. It's safe to leave it in.
I think it might be a little premature to reach that conclusion right
now; I've had panics with MFS in the past and also took note of the
fact when Andrew said his usage of fdesc post-dated the crashes. But
for that, it would be my pr
Jordan and list,
Right on time tonight - 02:06 while running "periodic daily".
The panic was exactly the same as before, so I won't repeat it. The
command being run at the time was "tee" again.
Just before the panic I had shut down all X and was running a "ps -axww ;
top | head -24" snapshot ev
> For better or worse, my box just obliged with a crash only 3h41m28s after
> booting my "DEBUG" kernel.
Well, that's paradoxically something of a hopeful sign. :)
> #3 0xc020abb9 in trap_pfault (frame=0xc7676d74, usermode=0, eva=108)
> at /home/src/sys/i386/i386/trap.c:844
> #4 0xc020a78f
Additional:
I'm running 4.1.1-STABLE cvsup'ed on September 28th at 04:13.
The box is a Gateway G6-266M with ? mobo, PII-266, 96MB, Quantum Fireball
ST6.4A (ata0-master), Iomega ZIP (ata1-master), Mitsumi(?) ATA FX240S
CD-ROM (ata1-slave), two Seagate/Compaq ST32171Ws off a Tekram DC-390F,
STB Ve
Jordan and list,
> If you could get a kernel crash dump, especially with a kernel with
> debugging symbols, that would help enormously! Thanks.
For better or worse, my box just obliged with a crash only 3h41m28s after
booting my "DEBUG" kernel.
I have found at least one interesting factor in t
This system is a PII-300, 128M RAM, an IDE boot drive with an array of
8 seagate baracuda UW drives connected to an Adaptec U2W card.
This system has been around as a test box. It is running a recent 4.1.1
kernel from the middle of last week for vinum testing. I have been
experiencing this p
On Thu, 28 Sep 2000, Mike Smith wrote:
> Please press the 'scroll lock' key to scroll upwards and report the real
> error message. Before you post it, take a few minutes to check the
> handbook section on kernel debugging and try giving us enough
> information to actually help you.
>
> You wo
Please press the 'scroll lock' key to scroll upwards and report the real
error message. Before you post it, take a few minutes to check the
handbook section on kernel debugging and try giving us enough
information to actually help you.
You wouldn't ring your doctor up and say "Hey doc, I hur
