linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jeremy Kusnetz" <JKusnetz@nrtc.org>
To: "Marcelo Tosatti" <marcelo.tosatti@cyclades.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: 2.4.23 is freezing my systems hard after 24-48 hours
Date: Thu, 18 Dec 2003 14:58:39 -0500	[thread overview]
Message-ID: <F7F4B5EA9EBD414D8A0091E80389450569D3F6@exchange.nrtc.coop> (raw)

> 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.

             reply	other threads:[~2003-12-18 19:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-18 19:58 Jeremy Kusnetz [this message]
2003-12-18 20:11 ` 2.4.23 is freezing my systems hard after 24-48 hours Ulrich Drepper
2003-12-18 20:43 ` Richard B. Johnson
     [not found] <F7F4B5EA9EBD414D8A0091E80389450513C09F@exchange.nrtc.coop>
2003-12-17 19:34 ` Philippe Troin
  -- strict thread matches above, loose matches on Subject: below --
2003-12-15 15:08 Jeremy Kusnetz
2003-12-16 16:12 ` Marcelo Tosatti
2003-12-12 21:41 Jeremy Kusnetz
2003-12-13 14:33 ` Marcelo Tosatti
2003-12-12 19:00 Jeremy Kusnetz
2003-12-12 21:26 ` Philippe Troin
2003-12-13  0:29   ` Keith Owens

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=F7F4B5EA9EBD414D8A0091E80389450569D3F6@exchange.nrtc.coop \
    --to=jkusnetz@nrtc.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).