From: Andrew Morton <akpm@zip.com.au>
To: Florian Lohoff <flo@rfc822.org>
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 11:04:55 -0800 [thread overview]
Message-ID: <3C7BDC57.A835D657@zip.com.au> (raw)
In-Reply-To: <20020226184043.GA10420@paradigm.rfc822.org>
Florian Lohoff wrote:
>
> Hi,
> i have been looking for deadlocks we are experiencing on a couple of
> SMP machines (Dual Celeron and Dual PIII). After a night stressing a
> spare machine with dbench/bonnie++/tcpspray the machine locked up 30
> minutes after i killed the test. The last messages on the console were:
>
> __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.
> 15 times - Machine was answering ping first but stopped after a couple
> of minutes. Another couple of minutes later the nmi_watchdog stepped in
> and produced an oops:
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.
Bottom line: I don't know why you got a SCSI error, and the lockup
is possibly a bug in the scsi layer.
-
next prev parent reply other threads:[~2002-02-26 19:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 18:40 [CRASH] gdth / __block_prepare_write: zeroing uptodate buffer! / NMI Watchdog detected LOCKUP Florian Lohoff
2002-02-26 19:04 ` Andrew Morton [this message]
2002-02-26 19:16 ` Florian Lohoff
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=3C7BDC57.A835D657@zip.com.au \
--to=akpm@zip.com.au \
--cc=flo@rfc822.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.