[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Aieee Seti



Dear List

Occasionally - about every week - my Alpha crashes with the following:

Unable to handle kernel paging request at virtual address 0000000000000240
CPU 0 setiathome(1386): Oops 1
pc = [<fffffffc0021ceb4>] ra = [<fffffffc0021ceb4>] ps = 0007 Not tainted
v0 = 0000000000000000  t0 = 0000000000000000  t1 = fffffffc0021d0a0
t2 = 0000000000000000  t3 = fffffc00fe8d4000  t4 = 00000000000001b2
t5 = ffffffffffffffff  t6 = 0000000000000008  t7 = fffffc00e9074000
s0 = 0000000000000000  s1 = 0000000000000002  s2 = fffffc00fff17800
s3 = fffffc00fff178c0  s4 = 0000000000000003  s5 = fffffc00005a95f0
s6 = 0000000000000000
a0 = fffffc00fe8d4040  a1 = 0000000000000000  a2 = 0000000000000000
a3 = 0000000000000001  a4 = 0000000000000000  a5 = 0000000000000001
t8 = 000000000000001f  t9 = fffffc00005e6960  t10= 0000000000000001
t11= 0000000000000000  pv = fffffffc001fc2c0  at = 0000040000000000
gp = fffffffc0022fa78  sp = fffffc00e9077e28
Trace:fffffc00003186a4 fffffc00003197c8 fffffc000032ae3c fffffc0000319ff4 fffffc00003135b8 Code: 27ba0001 23bd2bdc c3ffffc6 47ff041f 2ffe0000 d340003d <b0090240> c3ffffbb
Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing

Since this is the first time I could catch the error, I don't know wether it is allways caused by setiathome. Is it really caused by seti? What should I do?

Thank you, Adrian.



Reply to: