I have experienced this very same phenomenon. I am in X a lot, so I don't
notice it as much, but I have noticed it.
> I was getting this on some occasions with 1.2.3 and (more rarely)
> 1.3.10, and it usually meant impending doom :)
> BTW, I coudn't get 1.3.19 to boot once I compiled it. (Using lilo
> from a boot floppy and I _did_ have things set up right; I can
> still load my other kernels ok). I'm compiling 1.3.20 now
I have not been able to boot any kernel beyond 1.3.15. I was told it was
an init bug, so I downloaded and compiled init version 2.5. This, however,
resulted in the very same error: an EIP that 'pointed' to dead zero. I, also,
am compiling 1.3.20, in hopes this will help. I am certain, however, that you
will finish before me.
> 386/7dx33 8Mb ram, 1Mb trident 8900c, linux on /dev/hdb1 in 200
> Mb (less 16Mb swap), no ELF, ppp networking and SB Pro support,
> gcc 2.6.3.
>
> (Yeah I know, lame system, but I can't afford an upgrade at the
> moment :-( But linux still runs just great! :-)
I know the feeling:
386sx25 8Mb ram, 1Mb trident 8900cl, linux on /dev/hda2 (80mb), a5 (110mb),
and b5 (25mb), with swap on b1 (10mb). Total elf--kernel, libs, binaries.
SB-ASP-16: 0x330,0x220,irq10, Mitsumi-cdrom: 0x300,irq11, serial: irq 3,4,5.
gcc 2.7.0, init 2.5.
I will let the 'hardware experts' suggest a possible pattern, although I find
our systems somewhat similar. Any 'risky' tests I could perform would be
acceptable.
-- Todd Fries...tfries@umr.edu http://www.cs.umr.edu/~tfries