> Which tells us precisely nothing.  Saying "a message like" is no good.
> You need to follow the procedure in linux/REPORTING-BUGS, including the
> _exact_ message, run through ksymoops if necessary.

Ok, for your enlightenment:
-- Versions installed: (if some fields are empty or look
-- unusual then possibly you have very old versions)
Linux pangea 2.2.16-raid #1 SMP Sat Sep 23 17:57:25 PDT 2000 i686
unknown
Kernel modules         2.3.19
Gnu C                  2.95.2
Gnu Make               3.79.1
Binutils               2.10.91
Linux C Library        2.1.96
Dynamic linker         ldd (GNU libc) 2.1.96
Procps                 2.0.6
Mount                  2.10o
Net-tools              2.05
Kbd                    0.99
Sh-utils               2.0i
Modules Loaded         snd-pcm-oss snd-pcm-plugin snd-mixer-oss raid1
parport_probe parport_pc lp parport snd-card-ens1371 snd-ens1371 snd-pcm
snd-timer snd-ac97-codec snd-mixer snd-rawmidi snd-seq-device snd
soundcore lockd sunrpc ne2k-pci 8390 nls_cp437 vfat fat


the modules is useless because i cant do any work on 2.4.0test10, it
crashes before i can do anything useful.

Included is oops.txt and oops_rpt.txt.

A the time I took a snapshot of ksyms and modules from /proc only module
'md' was loaded... but when I start the raid array with raidstart
/dev/md0 it might have loaded other modules to handle RAID1 personality,
im not sure.  Either way the oops.txt with full trace and the report
from ksymoops is there.


My own experiments have shown this bug dissapears if I do not have SMP
compiled in...

And a final note, I applied the alpha raid patches to kernel 2.2.16 to
produce this raid array (just a simple mirror for /home), so the
question is, could it be the array data itself? perhaps mkraid under
2.4.0test10 would be good? Either way I dont think a hardcrash is a
reasonable response ;-)

-ryan