linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Heckmann <mh@nadir.org>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.21 smp: system lockup
Date: Mon, 14 Jul 2003 16:32:59 -0400	[thread overview]
Message-ID: <20030714203258.GA6959@nadir.org> (raw)
In-Reply-To: <20030712171001.GA18262@nadir.org>

Hi there,

just realised that I forgot to run ksymoops over the sysrq+t output.

the resolved output is attached. (it's big, so I had to gzip it.i sorry ). 

Also, I was wondering if the deadlock I encountered might whave been the 
IO-pausing under SMP systems that people have been talking about? 

thanks in advance.

-m

On Sat, Jul 12, 2003 at 01:10:02PM -0400, Marc Heckmann wrote:
> Hi,
> 
> I recently experienced a lockup on an SMP 2.4.21 kernel (vanilla).
> 
> The machine was under very heavy IO at the time. (a full backup was in
> progress). gzipped Alt+sysrq+t output is attached. I forgot
> Alt+sysrq+P unfortunatly.
> 
> iptables was still functional, it still responded to pings, but
> everything else was locked up. obviously sysrq was still working. I
> managed to reboot it with sysrq+b over the serial line.
> 
> the machine has been in production for a while and has run in the past
> for almost 2 months w/o any problems, so I don't believe it's hardware
> related.
> 
> A similar lockup happened once with the redhat 2.4.20-13.9 kernel. I
> blamed that on all the extra patches present and switched to 2.4.21
> hoping that it would alleviate the problem.
> 
> PS: I'm not an linux-kernel so please CC me directly.
> 
> -m



  reply	other threads:[~2003-07-14 20:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-12 17:10 2.4.21 smp: system lockup Marc Heckmann
2003-07-14 20:32 ` Marc Heckmann [this message]
2003-07-14 20:37   ` Marc Heckmann

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=20030714203258.GA6959@nadir.org \
    --to=mh@nadir.org \
    --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;
as well as URLs for NNTP newsgroup(s).