mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Golds <jgolds@resilience.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Deadlock with linux kernel
Date: Fri, 26 Oct 2001 11:42:37 -0700	[thread overview]
Message-ID: <3BD9AE9D.53D53936@resilience.com> (raw)
In-Reply-To: <Pine.LNX.4.33L.0110261537170.22127-100000@duckman.distro.conectiva>

Rik van Riel wrote:
> 
> On Fri, 26 Oct 2001, Jeff Golds wrote:
> 
> > I've been having this problem since 2.4.6 and just attributed it to VM
> > issues.  However, I've been trying all the latest kernels (2.4.9-acXX,
> > 2.4.10-acXX, 2.4.12-acXX and 2.4.13) and am still getting a deadlock
> > scenario someplace.  In fact, my system hung up in about 2 minutes after
> > booting the 2.4.13 kernel.
> 
> Since your system hangs just after boot, while you still
> have free ram and tons of swap, in kernels with 3 different
> VM subsystems ... I'm pretty sure this isn't a VM problem.

No, it only hung just after boot one time.  However, I was doing a
kernel build when it hung (I was trying to make a new kernel to try out
as I had just rebooted).

Most times, the machine will stay up for a day or two then lock during a
kernel build.

-Jeff

-- 
Jeff Golds
Sr. Software Engineer
jgolds@resilience.com

  reply	other threads:[~2001-10-26 17:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-26 18:33 Jeff Golds
2001-10-26 17:38 ` Rik van Riel
2001-10-26 18:42   ` Jeff Golds [this message]
2001-10-26 18:50     ` Mika Liljeberg
2001-10-26 19:16       ` John Gluck
2001-10-26 17:44 ` Alan Cox
2001-10-26 18:44   ` Jeff Golds
2001-10-26 18:52     ` Andreas Dilger
     [not found] <fa.e6tgf0v.g6kp2s@ifi.uio.no>
     [not found] ` <fa.dja9fnv.cka9g7@ifi.uio.no>
2001-10-29  2:08   ` 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=3BD9AE9D.53D53936@resilience.com \
    --to=jgolds@resilience.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    /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

all inboxes | Powered by JetHome®