public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bob Tracy <rct@gherkin.frus.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: 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: Thu, 4 Dec 2008 08:30:23 -0600	[thread overview]
Message-ID: <20081204143023.GA2240@gherkin.frus.com> (raw)
In-Reply-To: <20081202192834.GA26259@gherkin.frus.com>

On Tue, Dec 02, 2008 at 01:28:34PM -0600, 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 :-).

2.6.28-rc7 without the SCSI update panics as the prior -rcX kernels did.
With the update applied, life is good (so far).  I can at least type
"sync" at the command prompt and get away with it :-).  With a current
uptime of less than 5 minutes, I need to let the patched -rc7 soak a
bit.  Otherwise, I'm willing to call it "good."

-- 
------------------------------------------------------------------------
Bob Tracy          |  "I was a beta tester for dirt.  They never did
rct@frus.com       |   get all the bugs out." - Steve McGrew on /.
------------------------------------------------------------------------

      parent reply	other threads:[~2008-12-04 14:30 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
2008-12-04 14:30   ` Bob Tracy [this message]

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=20081204143023.GA2240@gherkin.frus.com \
    --to=rct@gherkin.frus.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox