RE: 2.4.23 is freezing my systems hard after 24-48 hours

[Jeremy Kusnetz]

> Please try the NMI oopser.

Okay, the box just crashed.  It's acting differently then the previous crashes.  The previous crashed would lock up hard, no network, no output to screen, no sysrq.  I don't know if the NMI-watchdog is what's letting it get this far.

This is the output to screen:

BUG IN DYNAMIC LINKER ld.so: ../sysdeps/i386/dl-machine.h: 391: elf_machine_lazy_rel: Assertion `((reloc->r_info) & 0xff) == 7' failed!

It just streams this error over and over on the console, and you also get this message back if you attempt to ssh to the box.

Again, I don't know if this is the same thing that was happening before, but all my other boxes that are running 2.4.22 have been doing so without any issue for about 5 days now, this one died after 50 hours.

Also I was getting this in syslog:

Dec 17 11:26:27 realserver6 inetd[92]: pid 4152: exit status 127
 Dec 17 11:26:48 realserver6 inetd[92]: pid 4217: exit status 127
 Dec 17 11:27:27 realserver6 inetd[92]: pid 4375: exit status 127
 Dec 17 11:27:48 realserver6 inetd[92]: pid 4450: exit status 127
 Dec 17 11:27:49 realserver6 inetd[92]: pid 4462: exit status 127
 Dec 17 11:27:52 realserver6 init: Id "c1" respawning too fast: disabled for 5 minutes
 Dec 17 11:27:52 realserver6 inetd[92]: pid 4480: exit status 127
 Dec 17 11:27:52 realserver6 inetd[92]: pid 4481: exit status 127
 Dec 17 11:28:27 realserver6 inetd[92]: pid 4591: exit status 127


Again I've never seen this with other kernels, yet everything else the same.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/