public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <andrewm@uow.edu.au>
To: Jeff Lessem <Jeff.Lessem@Colorado.EDU>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Too much memory causes crash when reading/writing to disk
Date: Wed, 18 Jul 2001 00:00:54 +1000	[thread overview]
Message-ID: <3B544516.FF6643E8@uow.edu.au> (raw)
In-Reply-To: <200107171322.HAA245907@ibg.colorado.edu>

Jeff Lessem wrote:
> 
> I tried the patch, but the machine came up in a very confused state.
> It couldn't mount proc, and other badness.

hmm..

> I made the patch against
> 2.4.6, because 2.4.7-pre6 doesn't boot at all (I guess I should send
> another message about that problem).

If it's locking up just after printing out the `NET3' banner,
don't bother - known problem with softirqs.  It'll be fixed
in the next kernel.


> >Also (but separately) try enabling the NMI watchdog with
> >the `nmi_watchdog=1' kernel boot parameter.
> 
> This worked, and I recreated the crash:

Wouldn't have a clue.  It isn't spinning on a lock.
It almost looks as if the timer interrupt isn't getting
cleared, and the CPU is never leaving the interrupt.  But
that would cause the timer interrupt count to increase like
crazy and the NMI would never have kicked in.  Nice one.

For interest's sake, could you please try booting with the
`noapic' option, and also send another NMI watchdog trace?

Thanks.

  reply	other threads:[~2001-07-17 13:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-17 13:22 Too much memory causes crash when reading/writing to disk Jeff Lessem
2001-07-17 14:00 ` Andrew Morton [this message]
2001-07-17 16:15   ` Jeff Lessem
2001-07-18  0:31     ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2001-07-20 16:17 Matt_Domsch
2001-07-19 12:36 Jeff Lessem
2001-07-18 16:17 Jeff Lessem
2001-07-19  6:33 ` Andrew Morton
2001-07-16 15:39 Jeff Lessem
2001-07-17  1:07 ` Andrew Morton

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=3B544516.FF6643E8@uow.edu.au \
    --to=andrewm@uow.edu.au \
    --cc=Jeff.Lessem@Colorado.EDU \
    --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