🚀 go-pugleaf

In <4og9lq$en@jedi.apana.org.au> cdewick@jedi.apana.org.au (Craig Dewick) writes:

>In the few months I've had the 4/200 board, it has sporadically suffered
>serious failures, giving BAD TRAP and DATA FAULT exceptions, sometimes
>several within a short period, sometimes only one in a period of several
>weeks. I have suspected many causes for these strange failures, and so far
>I haven't really deduced what the problem might be. 

Ok, not more than 10 minutes ago this machine failed again, actually twice 
within a very short time, and this time the console messages were saved to 
/var/log/syslog, so here they are, in case someone can pinpoint a possible 
cause:

Jun  3 19:45:17 jedi vmunix: BAD TRAP
Jun  3 19:45:17 jedi vmunix: pid 13898, `zterma': Text fault
Jun  3 19:45:17 jedi vmunix: kernel read fault at addr=0x0, pme=0x0
Jun  3 19:45:17 jedi vmunix: Bus Error Reg 80<INVALID>
Jun  3 19:45:17 jedi vmunix: pc=0x0, sp=0xf8100f40, psr=0xcc2, context=0x5
Jun  3 19:45:17 jedi vmunix: g1-g7: 0, 2, ffffff80, 0, f83a3000, 0, 0
Jun  3 19:45:17 jedi vmunix: Begin traceback... sp = f8100f40
Jun  3 19:45:17 jedi vmunix: Called from f8006b70, fp=f8100fa0, args=f83a2a54 1000 40 ff0eec00 0 ff0eef38
Jun  3 19:45:17 jedi vmunix: Called from f80e5984, fp=f83a2aa0, args=c00 ce5 e5 7 7 f8133800
Jun  3 19:45:17 jedi vmunix: End traceback...
Jun  3 19:45:17 jedi vmunix: panic: Text fault
Jun  3 19:45:17 jedi vmunix: BAD TRAP
Jun  3 19:45:17 jedi vmunix: pid 13898, `zterma': Text fault
Jun  3 19:45:17 jedi vmunix: kernel read fault at addr=0x0, pme=0x0
Jun  3 19:45:17 jedi vmunix: Bus Error Reg 80<INVALID>
Jun  3 19:45:17 jedi vmunix: pc=0x0, sp=0xf8100c60, psr=0xcc3, context=0x5
Jun  3 19:45:17 jedi vmunix: g1-g7: 0, 2, fce42af0, fce2c1e8, f83a3000, 0, f8126400
Jun  3 19:45:17 jedi vmunix: Begin traceback... sp = f8100c60
Jun  3 19:45:17 jedi vmunix: Called from f8006b70, fp=f8100cc0, args=f8100d1c 1000 40 21 400de4 a0
Jun  3 19:45:17 jedi vmunix: Called from f80b5fbc, fp=f8100d68, args=400de6 f812c000 fce2bd7c f812c000 ffffffff f8125f90
Jun  3 19:45:17 jedi vmunix: Called from f8046514, fp=f8100dc8, args=80 f811d115 f83a2aa0 f811d115 f8113400 f8100e10
Jun  3 19:45:17 jedi vmunix: Called from f80bb828, fp=f8100e28, args=f811d115 f8100ef4 0 80 7c081 f83a2aa0
Jun  3 19:45:17 jedi vmunix: Called from f8006b04, fp=f8100e98, args=1 f8100ef4 0 80 3 3
Jun  3 19:45:17 jedi vmunix: Called from f80aa4fc, fp=f8100f40, args=f8139330 ff0eef38 1 7 7 f8133800
Jun  3 19:45:17 jedi vmunix: Called from f8006b70, fp=f8100fa0, args=f83a2a54 1000 40 ff0eec00 0 ff0eef38
Jun  3 19:45:17 jedi vmunix: Called from f80e5984, fp=f83a2aa0, args=c00 ce5 e5 7 7 f8133800
Jun  3 19:45:17 jedi vmunix: End traceback...
Jun  3 19:45:17 jedi vmunix: panic: Text fault
Jun  3 19:45:17 jedi vmunix: 00264 low-memory static kernel pages
Jun  3 19:45:17 jedi vmunix: 00291 additional static and sysmap kernel pages
Jun  3 19:45:17 jedi vmunix: 00000 dynamic kernel data pages
Jun  3 19:45:17 jedi vmunix: 00144 additional user structure pages
Jun  3 19:45:17 jedi vmunix: 00000 segmap kernel pages
Jun  3 19:45:17 jedi vmunix: 00000 segvn kernel pages
Jun  3 19:45:17 jedi vmunix: 00070 current user process pages
Jun  3 19:45:17 jedi vmunix: 00121 user stack pages
Jun  3 19:45:17 jedi vmunix: 00890 total pages (890 chunks)
Jun  3 19:45:17 jedi vmunix: 
Jun  3 19:45:17 jedi vmunix: dumping to vp fce0f644, offset 205312

Then the reboot starts. The machine is still running now (I'm typing this
on it) that it's rebooted happily and fixed up the damage the crash did to
the root filesystem. 

Does anyone intimately familiar with 4/200 machines and the interactions
between the kernel and the hardware know what this means? 

Regards,

Craig.
-- 
             Craig Dewick. Send email to 'cdewick@jedi.apana.org.au'
                 The Core Matrix Foundation - Sydney, Australia
                        http://jedi.apana.org.au/core.html
 Always striving for a secure long-term future in an insecure short-term world