All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Leckey <bleckey@tpg.com.au>
To: linux-kernel@vger.kernel.org
Subject: System lockup.
Date: Mon, 21 Oct 2002 10:02:50 +1000	[thread overview]
Message-ID: <3DB3442A.7050002@tpg.com.au> (raw)

I have a terminal server that's supporting up to 240 lines.  It's a 
2.4.17 kernel, and is running squid, and using the reiser file system to 
store log files, squid cache and other data.  About every day or so, the 
machine locks up.  The screen is blank, keyboard doesn't respond, the 
serial console I set up shows no 'dying gasp' and there is nothing in 
any of the system logs.

This doesn't appear to be related to load as it has happened both during 
the busiest times and during the low times.

I'm still servicing interrupts from our serial devices (on IRQ 11), so 
it seems interrupts are still happening.

Beyond this, however, I have no idea where to go from here.  If anyone 
has any hints on what the problem might be, or even a way to gather more 
information, I would be grateful.

-- 
Bill Leckey - Senior Software Design Engineer
TPG Research and Development
Ph: +61 2 62851711
Fax: +61 2 62853939


             reply	other threads:[~2002-10-20 23:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-21  0:02 Bill Leckey [this message]
2002-10-21 11:30 ` System lockup Alan Cox
2002-10-21 21:44   ` Bill Leckey
2002-10-27 22:26   ` Bill Leckey
  -- strict thread matches above, loose matches on Subject: below --
2004-08-13 22:53 system lockup Mike Waychison
2004-08-13 23:23 ` Ian Pratt
2004-08-13 23:59   ` Mike Waychison
2004-08-14  0:20     ` Ian Pratt
2004-08-14  8:32     ` Keir Fraser
2004-08-16 13:59       ` Mark Williamson
2007-02-27  1:20 Roman Mashak

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=3DB3442A.7050002@tpg.com.au \
    --to=bleckey@tpg.com.au \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.