public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Kirby <sim@netnation.com>
To: linux-kernel@vger.kernel.org
Subject: Lockups with 2.4.12?
Date: Tue, 16 Oct 2001 11:22:59 -0700	[thread overview]
Message-ID: <20011016112259.A2206@netnation.com> (raw)

Has anybody else been seeing random lockups with 2.4.12?  We've seen a
few servers stop responding and our backup server die nightly with
2.4.12, but 2.4.10pre10 seems to be fine.  I was only at the console once
where I could actually see Oopses, but the scrollback overflowed with
Oopses so I couldn't find the first one.  Nothing was saved to disk.  The
stack trace of the oldest Oops I could find showed a program in
sys_rt_sigaction.

I'll try to track this down a bit more, I'm just wondering if anybody
else is having similar problems.

Simon-

[  Stormix Technologies Inc.  ][  NetNation Communications Inc. ]
[       sim@stormix.com       ][       sim@netnation.com        ]
[ Opinions expressed are not necessarily those of my employers. ]

             reply	other threads:[~2001-10-16 18:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-16 18:22 Simon Kirby [this message]
     [not found] <fa.gl1qslv.d68lbj@ifi.uio.no>
2001-10-16 21:57 ` Lockups with 2.4.12? Sam Varshavchik

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=20011016112259.A2206@netnation.com \
    --to=sim@netnation.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox