From: Andrew Morton <akpm@zip.com.au>
To: rwhron@earthlink.net
Cc: davej@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5.21 IDE 91
Date: Mon, 17 Jun 2002 01:40:48 -0700 [thread overview]
Message-ID: <3D0DA090.9F1B60BE@zip.com.au> (raw)
In-Reply-To: 20020615120511.GA30803@rushmore
rwhron@earthlink.net wrote:
>
> >> Recently, 2.5.20-dj[34] completed all my tests, whereas
> >> 2.5.{19,20,21} haven't. I realize breakage in the development series
> >> is expected and sometimes good. Nonetheless, "two thumbs up" for -dj.
>
> > That's interesting. What exactly was failing ? It'd be in everyones
> > interests to get those bits pushed to Linus sooner.
>
> tiobench.pl --size 2048 --numruns 3 --threads 128 # 384 MB ram in machine
>
> The ssh session running vmstat no longer updates. Console won't
> give a new "login" prompt with <Enter>. <sysrq T> prints a
> trace (which I haven't captured - it's really long with > 128 processes).
>
> Does <sysrq T> need any post processing to convert addresses to
> something more useful? I'll save it on 2.5.22 if it happens.
Well I dunno, Randy. Works fine here, on aic7xxx SCSI and hpt366 IDE.
>From your trace it would seem that writeout completion has not
occurred against one or more pages. Could be that the device
driver lost an interrupt, or it failed to deliver completion
for one or more BIO segments, or something screwed up at the
VFS level.
I am (of course ;)) disinclined to believe the latter, mainly
because of the amount of testing I do here. Eight-hour Cerberus
runs on quad CPU, five IDE disks and six SCSI disks all chugging
along, no probs.
Is it reproducible? Are you able to try it on a different machine?
On other disks in the same machine?
-
next prev parent reply other threads:[~2002-06-17 8:36 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-15 12:05 [PATCH] 2.5.21 IDE 91 rwhron
2002-06-17 8:40 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-18 13:24 rwhron
2002-06-17 13:16 rwhron
2002-06-16 16:36 rwhron
2002-06-16 13:03 rwhron
2002-06-16 11:05 rwhron
2002-06-16 10:52 rwhron
2002-06-15 21:00 rwhron
2002-06-15 21:00 ` William Lee Irwin III
2002-06-15 21:23 ` Andrew Morton
2002-06-15 11:41 rwhron
2002-06-15 11:50 ` Dave Jones
2002-06-15 10:42 rwhron
2002-06-15 17:17 ` Jens Axboe
2002-06-14 18:36 Andries.Brouwer
2002-06-14 17:09 Andries.Brouwer
2002-06-14 17:15 ` Martin Dalecki
2002-06-14 16:29 Hron, Randall
2002-06-14 23:32 ` Andrew Morton
2002-06-09 5:42 Linux 2.5.21 Linus Torvalds
2002-06-14 14:02 ` [PATCH] 2.5.21 IDE 91 Martin Dalecki
2002-06-14 15:17 ` Jens Axboe
2002-06-14 15:42 ` John Weber
2002-06-14 15:43 ` Dave Jones
2002-06-14 16:06 ` Bartlomiej Zolnierkiewicz
2002-06-14 16:33 ` Martin Dalecki
2002-06-14 17:56 ` Linus Torvalds
2002-06-14 15:56 ` Benjamin LaHaise
2002-06-14 16:04 ` Dave Jones
2002-06-14 17:23 ` Martin Dalecki
2002-06-14 16:09 ` Bartlomiej Zolnierkiewicz
2002-06-14 16:15 ` Martin Dalecki
2002-06-15 8:15 ` Jens Axboe
2002-06-14 16:43 ` Linus Torvalds
2002-06-14 16:47 ` Martin Dalecki
2002-06-15 8:19 ` Jens Axboe
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=3D0DA090.9F1B60BE@zip.com.au \
--to=akpm@zip.com.au \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rwhron@earthlink.net \
/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