From: Jens Axboe <jens.axboe@oracle.com>
To: "Miller, Mike (OS Dev)" <Mike.Miller@hp.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"coldwell@redhat.com" <coldwell@redhat.com>
Subject: Re: [GIT PULL] block bits for 2.6.29-rc5
Date: Fri, 20 Feb 2009 17:53:54 +0100 [thread overview]
Message-ID: <20090220165354.GB29783@kernel.dk> (raw)
In-Reply-To: <0F5B06BAB751E047AB5C87D1F77A77885CA670E6F8@GVW0547EXC.americas.hpqcorp.net>
On Fri, Feb 20 2009, Miller, Mike (OS Dev) wrote:
>
>
> > -----Original Message-----
> > From: Jens Axboe [mailto:jens.axboe@oracle.com]
> > Sent: Friday, February 20, 2009 10:41 AM
> > To: Andrew Morton
> > Cc: torvalds@linux-foundation.org;
> > linux-kernel@vger.kernel.org; Miller, Mike (OS Dev)
> > Subject: Re: [GIT PULL] block bits for 2.6.29-rc5
> >
> > On Thu, Feb 19 2009, Andrew Morton wrote:
> > > On Wed, 18 Feb 2009 15:41:06 +0100
> > > Jens Axboe <jens.axboe@oracle.com> wrote:
> > >
> > > > @@ -3404,6 +3601,24 @@ static int __devinit
> > cciss_init_one(struct pci_dev *pdev,
> > > > int dac, return_code;
> > > > InquiryData_struct *inq_buff = NULL;
> > > >
> > > > + if (reset_devices) {
> > > > + /* Reset the controller with a PCI power-cycle */
> > > > + if (cciss_hard_reset_controller(pdev) ||
> > cciss_reset_msi(pdev))
> > > > + return -ENODEV;
> > > > +
> > > > + /* Some devices (notably the HP Smart Array 5i
> > Controller)
> > > > + need a little pause here */
> > > > + schedule_timeout_uninterruptible(30*HZ);
> > >
> > > little!
> >
> > That does qualify as the understatement of the day :-)
> >
> > > Perhaps we should do a printk("no, your machine is not dead") here.
> >
> > Perhaps we should shrink it to something a little more
> > tolerable and put it in the noop loop instead. 30 seconds is insane...
>
> Some of these controllers do take a long time to recover from the
> reset because the firmware has to re-initialize. The firmware guys
> claim that's only a few seconds but that's not true.
>
> Granted, the 5i is old as dirt. Don't know how many are still out
> there running newer kernels.
So a small improvement would be to do that delay only for 5i. Or how
about just being a little more relaxed, ala the below? It's still 30
seconds in total, but that's now worst case. Will the 5i crap itself if
we attempt to talk to it too soon?
diff --git a/drivers/block/cciss.c b/drivers/block/cciss.c
index d2cb67b..b5a0611 100644
--- a/drivers/block/cciss.c
+++ b/drivers/block/cciss.c
@@ -3611,11 +3611,15 @@ static int __devinit cciss_init_one(struct pci_dev *pdev,
schedule_timeout_uninterruptible(30*HZ);
/* Now try to get the controller to respond to a no-op */
- for (i=0; i<12; i++) {
+ for (i=0; i<30; i++) {
if (cciss_noop(pdev) == 0)
break;
- else
- printk("cciss: no-op failed%s\n", (i < 11 ? "; re-trying" : ""));
+
+ schedule_timeout_uninterruptible(HZ);
+ }
+ if (i == 30) {
+ printk(KERN_ERR "cciss: controller seems dead\n");
+ return -EBUSY;
}
}
--
Jens Axboe
next prev parent reply other threads:[~2009-02-20 16:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 14:41 [GIT PULL] block bits for 2.6.29-rc5 Jens Axboe
2009-02-19 18:54 ` Christoph Hellwig
2009-02-19 18:55 ` Jens Axboe
2009-02-20 7:26 ` Jens Axboe
2009-02-24 13:45 ` Christoph Hellwig
2009-02-20 1:07 ` Andrew Morton
2009-02-20 16:40 ` Jens Axboe
2009-02-20 16:50 ` Miller, Mike (OS Dev)
2009-02-20 16:53 ` Jens Axboe [this message]
2009-02-20 18:51 ` Miller, Mike (OS Dev)
2009-02-23 11:09 ` Jens Axboe
2009-02-23 15:00 ` Miller, Mike (OS Dev)
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=20090220165354.GB29783@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=Mike.Miller@hp.com \
--cc=akpm@linux-foundation.org \
--cc=coldwell@redhat.com \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).