[cobalt-users] Spontanious rebooting Raq 3i

[Blaeu business intelligence <rob@xxxxxxxxx>]

The raq reboots overnight now and a
while. Since the frequency is increasing I would like to ask your opinion.

I have upgraded RAM in the Raq3i recently to 512 MB and didn't have the
problems before. (BUFFALO MEMORY 256MB ECC PC100 SDRAM DIM
)
The reboots are time coincident with the cron.daily jobs around 04:52
AM, just after the scheduled backups. So it could be slocate.cron,
tmpwatch, or vacuumdb which is causing the crash.
My guess is it has either to do with the RAM, or the disk is getting
old, or the latest Kernel (2.2.16C32_III) is instabel.

/etc/cron.daily
/etc/cron.daily/awebalizer.pl
/etc/cron.daily/logcheck
/etc/cron.daily/logrotate
/etc/cron.daily/makewhatis.cron
/etc/cron.daily/ntpdate.auto
/etc/cron.daily/scheduled-backup.site2
/etc/cron.daily/scheduled-backup.site1
/etc/cron.daily/scheduled-backup.home
/etc/cron.daily/scheduled-backup.site5
/etc/cron.daily/scheduled-backup.site8
/etc/cron.daily/scheduled-backup.site6
/etc/cron.daily/scheduled-backup.site9
/etc/cron.daily/scheduled-backup.site7
/etc/cron.daily/scheduled-backup.site4
/etc/cron.daily/scheduled-backup.site11
/etc/cron.daily/scheduled-backup.site10
/etc/cron.daily/scheduled-backup.site12
/etc/cron.daily/slocate.cron
/etc/cron.daily/tmpwatch
/etc/cron.daily/vacuumdb

I hooked up a VT100 terminal, since logcheck didn't capture the events
detailed enough. Here is the exerpt:

"Unable to handle kernel paging request at virtual address 04000011
Unable to handle kernel paging request at virtual address 20000011
current->tss.cr3 = 00101000, %cr3 = 00101000
*pde = 00000000
Oops: 0000
CPU:    0
EIP:    0010:[<c010a444>]
EFLAGS: 00010002
eax: c0261e58   ebx: 00000000   ecx: 00000000   edx: c0261e58
esi: c02480a0   edi: 20000001   ebp: 00000000   esp: c0261e10
ds: 0018   es: 0018   ss: 0018
Process swapper (pid: 0, process nr: 0, stackpage=c0261000)
Stack: c0272000 c02480a0 c0261e50 c010a238 00000000 c0261e58 c02480a0
00000000
         00000000 c0272004 c010a5b8 00000000 c0261e58 00000000 c02750a0
c02750a1
         0000001d c010a25c 00000000 c02703fd c02703f9 c02750a0 c02750a1
0000001d
Call Trace: [<c010a238>] [<c010a5b8>] [<c010a25c>] [<c011382b>]
[<c010eb54>] [<c
01faf0a>] [<c01a5178>]
         [<c0109405>] [<c010a444>] [<c010a238>] [<c010a5b8>] [<c010a25c>]
[<c01078
55>] [<c0106000>] [<c0107878>]
         [<c01092f0>] [<c0106000>] [<c010607f>] [<c0106000>] [<c0100175>]
Code: 8b 47 10 50 8b 54 24 1c 52 8b 06 ff d0 83 c4 0c eb 3d 89 f6
Aiee, killing interrupt handler
Kernel panic: Attempted to kill the idle task!
disabling network interfaces.
alloc_skb called nonatomically from interrupt c018f341
alloc_skb called nonatomically from interrupt c018f341
alloc_skb called nonatomically from interrupt c0193666
alloc_skb called nonatomically from interrupt c0193666
Rebooting in 5 seconds.."

Please let me know what you think,

Thanks in advance,
Rob van Eijk
Rotterdam, The Netherlands