From: Srihari Vijayaraghavan <sriharivijayaraghavan@yahoo.com.au>
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PROBLEM] kernel BUG at include/linux/blkdev.h:601
Date: Fri, 1 Jul 2005 10:48:00 +1000 (EST) [thread overview]
Message-ID: <20050701004801.50905.qmail@web52607.mail.yahoo.com> (raw)
In-Reply-To: <20050630153717.GB2243@suse.de>
--- Jens Axboe <axboe@suse.de> wrote:
> On Thu, Jun 30 2005, Srihari Vijayaraghavan wrote:
> > --- Srihari Vijayaraghavan
> > <sriharivijayaraghavan@yahoo.com.au> wrote:
> [...]
> > 2.6.13-rc1 (plus Hugh's get_request patch) doesn't
> > suffer from this problem, unlike 2.6.12 and
> 2.6.12-git
> > releases.
>
> That's a little strange, as there should be no
> changes in this area so
> far. Are you 100% sure?
Absolutely. 2.6.12 and 2.6.12-git9 crash within
minutes/seconds; OTOH, 2.6.13-rc1 (plus Hugh's patch)
survives this torture test for hours (despite
generating 30+ MB of kernel/IDE error messages :). No
OOPS, no BUGs, no panics, just truck load of error
messages.
I haven't tested whether earlier releases of 2.6
suffer from this (such as 2.6.10, 2.6.11 ..) or other
hardware combinations exhibit the same problem etc.
Tell me, if you want me to.
Thanks
Hari
____________________________________________________
Do you Yahoo!?
Try Yahoo! Photomail Beta: Send up to 300 photos in one email!
http://au.photomail.mail.yahoo.com
next prev parent reply other threads:[~2005-07-01 0:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-30 2:17 Srihari Vijayaraghavan
2005-06-30 15:37 ` Jens Axboe
2005-07-01 0:48 ` Srihari Vijayaraghavan [this message]
2005-07-01 8:02 ` Jens Axboe
2005-07-01 12:35 ` Srihari Vijayaraghavan
-- strict thread matches above, loose matches on Subject: below --
2005-06-29 5:19 Srihari Vijayaraghavan
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=20050701004801.50905.qmail@web52607.mail.yahoo.com \
--to=sriharivijayaraghavan@yahoo.com.au \
--cc=axboe@suse.de \
--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®