Lee McLoughlin wrote:
| Pieter Immelman wrote:
| >
| > Hi,
| >
| > $happy_exim_users++ :)
| > Had to upgrade our SunOS4 box (due the weird kernel panics triggered by
| > exim somehow) to something newer, but I'm back here.
|
| Hey thats odd! I had to do the same thing for the same reason. I was
| running exim on a Sparc Station 2 running Sunos 4.1.3u1 and was getting
| memory parity errors - but only ever in exim. So I moved it to an
| almost identical box running Solaris 2.6 and the problems went away.
|
| Mind you there could be some bad memory in the Sunos 4 box but nothing
| else seems to tickle it.
Had a similar thing earlier when I was still running an EFnet IRC server
on it. Machine would be fine for days or weeks and then all of a sudden
it would panic and take the box down. Convinced that it's an O/S bug,
but had no idea where to even start looking. Anyway, that box is now
running Solaris 2.5.1. Hope I'll be more lucky with that. ;)
FYI, here's the message I sent to the list about my exim panic problem
to compare to yours:
> I'm a bit worried here. Our system panic's due to something that exim
> does. Not sure if it's really exim or the system itself, but I've had
> 2 panic's in the last 5 days and I'm hoping that someone here have seen
> something similar or can point me to a solution.
>
> System: SunOS 4.1.3_U1 running Exim 1.61
>
> Jun 9 10:41:25 aztec vmunix: BAD TRAP: cpu=0 type=9 rp=f119dd4c addr=20 mmu_fsr=326 rw=1
> Jun 9 10:41:25 aztec vmunix: MMU sfsr=326: Invalid Address on supv data fetch at level 3
> Jun 9 10:41:25 aztec vmunix: regs at f119dd4c:
> Jun 9 10:41:25 aztec vmunix: psr=409010c2 pc=f001f90c npc=f001f910
> Jun 9 10:41:25 aztec vmunix: y: a0000000 g1: f001f900 g2: 8000000 g3: ffffff00
> Jun 9 10:41:25 aztec vmunix: g4: 0 g5: f119e000 g6: 0 g7: 0
> Jun 9 10:41:25 aztec vmunix: o0: 5f000 o1: 0 o2: 2 o3: f119de04
> Jun 9 10:41:25 aztec vmunix: o4: 60000 o5: 5d000 sp: f119dd98 ra: fb14f534
> Jun 9 10:41:25 aztec vmunix: pid 13552, `exim': Data access exception
> Jun 9 10:41:25 aztec vmunix: kernel read fault at addr=0x20, pme=0x0
> Jun 9 10:41:25 aztec vmunix: MMU sfsr=326: Invalid Address on supv data fetch at level 3
> Jun 9 10:41:25 aztec vmunix: rp=0xf119dd4c, pc=0xf001f90c, sp=0xf119dd98, psr=0x409010c2, context=0x7c
> Jun 9 10:41:25 aztec vmunix: g1-g7: f001f900, 8000000, ffffff00, 0, f119e000, 0, 0
> Jun 9 10:41:25 aztec vmunix: Begin traceback... sp = f119dd98
> Jun 9 10:41:25 aztec vmunix: Called from f005fafc, fp=f119ddf8, args=0 ff67318c 0 1 f119debc 0
> Jun 9 10:41:25 aztec vmunix: Called from f0062428, fp=f119de58, args=ff67318c 0 1 f119debc 3 ef7a6000
> Jun 9 10:41:25 aztec vmunix: Called from f00ee6d0, fp=f119dec0, args=f119dfe0 3b0 f014a068 f014a418 f076ffb4 f119dfe0
> Jun 9 10:41:25 aztec vmunix: Called from f0005cd0, fp=f119df58, args=f119e000 f119dfb4 f119dfe0 f119e000 f119e000 f119dfb4
> Jun 9 10:41:25 aztec vmunix: Called from 34d50, fp=effff8a0, args=2 0 1 effff948 effff944 0
> Jun 9 10:41:25 aztec vmunix: End traceback...
> Jun 9 10:41:25 aztec vmunix: panic on cpu 0: Data access exception
> Jun 9 10:41:25 aztec vmunix: syncing file systems... done
Ciao,
-- pi
--
*** Exim information can be found at
http://www.exim.org/ ***
