mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Florian Lohoff <flo@rfc822.org>
To: Andrew Morton <akpm@zip.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [CRASH] gdth / __block_prepare_write: zeroing uptodate buffer! / NMI Watchdog detected LOCKUP
Date: Tue, 26 Feb 2002 20:16:26 +0100	[thread overview]
Message-ID: <20020226191626.GA11283@paradigm.rfc822.org> (raw)
In-Reply-To: <20020226184043.GA10420@paradigm.rfc822.org> <3C7BDC57.A835D657@zip.com.au>
In-Reply-To: <3C7BDC57.A835D657@zip.com.au>

[-- Attachment #1: Type: text/plain, Size: 1524 bytes --]

On Tue, Feb 26, 2002 at 11:04:55AM -0800, Andrew Morton wrote:
> > __block_prepare_write: zeroing uptodate buffer!
> 
> Yup.   This happens when the disk fills up.  Andrea and I were
> discussing it over the weekend.   There's a new patch in the -aa
> kernels which doesn't quite fix it :(
> 
> We'll fix it in 2.4.19-pre somehow.  It's possible that this problem
> causes a chnuk of zeroes to be written into the file when you hit
> ENOSPC, which is rather rude.  But your file was truncated anyway.

I dont think the machine had full filesystems at all.

> SCSI error recovery deadlocked.
> 
> Now it's *just* conceivable that the __block_prepare_write() problem
> caused a junk request to be sent down to the driver, which caused
> the driver to enter recovery, which it then screwed up.   But I
> doubt it.
> 
> It's also conceivable that the NMI watchdog code itself caused
> problems also.   Back in the days when it was permanently enabled,
> some machines kept going silly until nmi watchdog was enabled.

I have seen a lot of deadlocks on these machines for the last months - I
never got ANY output - Nothing in the syslog, no oops. I am running
now with the nmi_watchdog for 4 weeks and have seen 10-15 crashes on 2
machines with no output. This was the first deadlock with some output 
at all which is very frustrating.

Flo
-- 
Florian Lohoff                  flo@rfc822.org             +49-5201-669912
Nine nineth on september the 9th              Welcome to the new billenium

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2002-02-26 19:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-26 18:40 Florian Lohoff
2002-02-26 19:04 ` Andrew Morton
2002-02-26 19:16   ` Florian Lohoff [this message]
2002-02-26 19:20     ` Andrew Morton
2002-02-26 19:32       ` Andrea Arcangeli
2002-02-27  3:27     ` T. A.
2002-02-27  9:36       ` Florian Lohoff
2002-02-26 19:31   ` Andrea Arcangeli
2002-02-26 19:27 ` Andrea Arcangeli

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=20020226191626.GA11283@paradigm.rfc822.org \
    --to=flo@rfc822.org \
    --cc=akpm@zip.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 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®