From: Andrew Morton <akpm@zip.com.au>
To: Ville Herva <vherva@niksula.hut.fi>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org,
Jani Forssell <jani.forssell@viasys.com>,
sak@iki.fi
Subject: Re: Via KT133 pci corruption: stock 2.4.18pre2 oopses as well
Date: Wed, 09 Jan 2002 13:00:53 -0800 [thread overview]
Message-ID: <3C3CAF85.8BD5E2E1@zip.com.au> (raw)
In-Reply-To: <20020108215818.J1331@niksula.cs.hut.fi> <E16O2fD-0007Vn-00@the-village.bc.nu> <20020108221315.U1200@niksula.cs.hut.fi> <20020109144549.L1331@niksula.cs.hut.fi>, <20020109144549.L1331@niksula.cs.hut.fi>; from vherva@niksula.hut.fi on Wed, Jan 09, 2002 at 02:45:49PM +0200 <20020109172604.N1331@niksula.cs.hut.fi>
Ville Herva wrote:
>
> >>EIP; c0131ce0 <sync_page_buffers+10/b0> <=====
Looks like a corrupted `next' pointer in the page's buffer_head
ring. Your report is identical to Todd Eigenschink's repeatable
oops. http://www.uwsg.iu.edu/hypermail/linux/kernel/0112.3/0689.html
In another thread, yesterday, we were discussing the elusive
"end_request: buffer-list destroyed" crash.
I am able to trigger this in around ten minutes on 2.4.13 and
later kernels. However 2.4.13-pre6 ran the test for nine hours
and did not fail.
I've put the 2.4.13-pre6 -> 2.4.13 diff at http://www.zip.com.au/~akpm/1.gz
MAINTAINERS | 6 ++
Makefile | 2
arch/i386/kernel/smp.c | 58 +++++++++++-----------------
drivers/message/i2o/i2o_block.c | 44 ++++++++-------------
drivers/message/i2o/i2o_config.c | 1
drivers/message/i2o/i2o_core.c | 39 ++++++++++++++++---
drivers/message/i2o/i2o_lan.c | 4 +
drivers/message/i2o/i2o_pci.c | 14 ++++++
drivers/message/i2o/i2o_proc.c | 16 +++----
drivers/message/i2o/i2o_scsi.c | 17 ++++++--
drivers/scsi/dpt_i2o.c | 14 +++---
drivers/sound/ymfpci.c | 52 +++++++++++--------------
fs/buffer.c | 54 ++++++++++++++++----------
fs/ntfs/fs.c | 1
include/linux/fs.h | 3 -
include/linux/locks.h | 2
include/linux/mm.h | 17 ++++----
include/linux/slab.h | 2
include/linux/swap.h | 4 -
kernel/exit.c | 13 +-----
mm/highmem.c | 4 -
mm/page_alloc.c | 39 +++++++++----------
mm/swap.c | 4 -
mm/vmscan.c | 80 ++++++++++++++++++++++-----------------
There were VM changes, and a messy, complex and undocumented
change to sync_page_buffers(), which was the point at which
I ceased to understand that function. The patch was never Cc'ed
to the mailing list, was never explained. This sort of thing
makes it very hard for other developers to hunt down bugs.
Probably, the bug lies elsewhere and perhaps my bug is different
from yours and Todd's. It is timing-related, and the VM and
buffer changes may just have triggered it.
I have a debug patch from Jens to try tonight.
It could just be some random memory scribbler. Dunno yet. It's
awfully repeatable.
-
next prev parent reply other threads:[~2002-01-09 21:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-08 19:58 2.2.21pre2 oops Ville Herva
2002-01-08 20:16 ` Alan Cox
2002-01-08 20:13 ` Ville Herva
2002-01-09 12:45 ` Ville Herva
2002-01-09 15:26 ` Via KT133 pci corruption: stock 2.4.18pre2 oopses as well Ville Herva
2002-01-09 21:00 ` Andrew Morton [this message]
2002-01-09 21:57 ` Ville Herva
2002-01-09 23:30 ` Martin Josefsson
2002-01-10 0:19 ` Daniel J Blueman
2002-01-10 0:41 ` Martin Josefsson
2002-01-10 1:04 ` Daniel J Blueman
2002-01-10 5:34 ` Ville Herva
2002-01-10 12:01 ` Henrique de Moraes Holschuh
2002-01-10 12:56 ` Martin Josefsson
2002-01-10 13:37 ` Ville Herva
2002-01-09 23:33 ` Daniel J Blueman
2002-01-10 6:34 ` Ville Herva
2002-01-10 6:40 ` 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=3C3CAF85.8BD5E2E1@zip.com.au \
--to=akpm@zip.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jani.forssell@viasys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sak@iki.fi \
--cc=vherva@niksula.hut.fi \
/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