2.4.18 Crash interpretation: Known problem?
 

Hi , just looking for some info about a crash:
This is a 2.4.18 kernel running mostly some scripts
and perl scripts. FS is Reiser.
below is /var/log/messages
Any ideas
1) what exactly caused the crash?
2) does this mean hardware(HD) is going to give us more problems soon?

Thanks, svar

Sep 14 23:44:51 q5 -- MARK --
Sep 14 23:59:01 q5 /USR/SBIN/CRON[5144]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly)
Sep 15 00:00:00 q5 /USR/SBIN/CRON[5148]: (root) CMD ( test -x /usr/lib/secchk/security-control.sh && /usr/lib/secchk/security-control.sh daily &)
Sep 15 00:14:01 q5 /USR/SBIN/CRON[5486]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.daily)
Sep 15 00:19:55 q5 run-crons[5489]: logrotate returned 1
Sep 15 00:22:10 q5 su: (to nobody) root on none
Sep 15 00:22:10 q5 su: pam_unix2: session started for user nobody, service su
Sep 15 00:27:24 q5 kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Sep 15 00:28:08 q5 last message repeated 4 times
Sep 15 00:32:33 q5 kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Sep 15 00:32:33 q5 kernel: VM: killing process kdeinit
Sep 15 00:33:08 q5 kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Sep 15 00:33:16 q5 last message repeated 3 times
Sep 15 00:33:16 q5 kernel: VM: killing process kdeinit
Sep 15 00:33:18 q5 kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Sep 15 00:33:45 q5 last message repeated 3 times
Sep 15 00:34:53 q5 kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Sep 15 00:34:53 q5 kernel: VM: killing process kdeinit
Sep 15 00:34:55 q5 kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Sep 15 00:35:41 q5 kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Sep 15 00:35:42 q5 kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Sep 15 00:47:17 q5 kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Sep 15 00:47:44 q5 last message repeated 4 times
Sep 15 00:47:44 q5 kernel: VM: killing process perl
Sep 15 00:50:54 q5 su: pam_unix2: session finished for user nobody, service su
Sep 15 00:59:00 q5 /USR/SBIN/CRON[5803]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly)
Sep 15 01:00:00 q5 /USR/SBIN/CRON[5808]: (root) CMD ( test -x /usr/lib/secchk/security-control.sh && /usr/lib/secchk/security-control.sh weekly &)
Sep 15 01:24:54 q5 -- MARK --
Sep 15 01:40:31 q5 /USR/SBIN/CRON[5807]: (root) MAIL (mailed 97 bytes of output but got status 0x0001 )
Sep 15 01:59:00 q5 /USR/SBIN/CRON[6226]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly)
Sep 15 02:24:55 q5 -- MARK --
Sep 15 02:44:55 q5 -- MARK --
Sep 15 02:59:00 q5 /USR/SBIN/CRON[6308]: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly)

My first hunch would be some app taking memory and not releasing it back, causing a memory leak. When memory gets tight, and provided the kernel needs some and can't swap it out, then it'll start killing apps to survive. As far as I read (little, I don't need no KDE) (older) KDE/KDE apps seemed to be somewhat notorious for being that.
I guesstimate chances this is hardware related to be small.

Yes, turns out this was the case: Just some datastructure getting too big memory wise.
Thanks,
svar