From: Jens Axboe <jens.axboe@oracle.com>
To: Bob Tracy <rct@gherkin.frus.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PATCH] SCSI fixes for 2.6.28-rc7
Date: Wed, 3 Dec 2008 14:10:52 +0100 [thread overview]
Message-ID: <20081203131052.GS18255@kernel.dk> (raw)
In-Reply-To: <20081202192834.GA26259@gherkin.frus.com>
On Tue, Dec 02 2008, Bob Tracy wrote:
> On Tue, Dec 02, 2008 at 10:58:56AM -0600, James Bottomley wrote:
> > This is quite a hefty update for so late. It includes a slew of block
> > timer related fixes (we moved to using block timers when the 2.6.28
> > merge window opened). The bad news is that I still don't think we have
> > all the block timer related bugs caught and fixed. There's also a slew
> > of zfcp (s390 driver) fixes and a few miscellaneous others (including
> > another regression bugzilla fix, the hang in starved list processing).
>
> I'll give this a try. None of the 2.6.28-rcX versions I've tried have
> lasted more than a few hours at best before panicing with a block layer
> timeout. My test system uses the aic7xxx driver with a 2930U2 adapter.
> I didn't report the regression relative to 2.6.27 because I figured
> something this major was going to get caught without another "me too"
> report that I was too busy to generate and provide the necessary
> diagnostic and followup on anyway :-).
Please also try -git tomorrow, with this and the block pull hopefully
going in later today, I hope that's the end of it. If not, please do
write a proper report!
--
Jens Axboe
next prev parent reply other threads:[~2008-12-03 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 16:58 [GIT PATCH] SCSI fixes for 2.6.28-rc7 James Bottomley
2008-12-02 19:28 ` Bob Tracy
2008-12-03 13:10 ` Jens Axboe [this message]
2008-12-04 14:30 ` Bob Tracy
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=20081203131052.GS18255@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rct@gherkin.frus.com \
--cc=torvalds@linux-foundation.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.