From: "Tim Pepper" <tpepper@vato.org>
To: Alexander Sandler <ASandler@store-age.com>, arjan@fenrus.demon.nl
Cc: "Linux Kernel Mailing List \(E-mail\)" <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.17: Bug?
Date: Mon, 4 Feb 2002 10:45:25 -0800 [thread overview]
Message-ID: <20020204104525.A30033@vato.org> (raw)
In-Reply-To: <BDE817654148D51189AC00306E063AAE054620@exchange.store-age.com>
In-Reply-To: <BDE817654148D51189AC00306E063AAE054620@exchange.store-age.com>; from ASandler@store-age.com on Mon, Feb 04, 2002 at 11:12:27AM +0200
On Mon 04 Feb at 11:12:27 +0200 ASandler@store-age.com done said:
> No no no no.
>
> This is a bug. For me, it took two hours to get released
> from that. There is no such thing two hours timeout.
> And who said this is only two hours? I spoke with Arjan van de Ven
> and he told me that it may take for up to 14 hours.
>
> Anyway, Arjan told me that he fixed this bug in the version that
> will be out with 2.4.18.
We're talking about different things. Looking at the original post I see
I missed that the concern was the hung process not the "long" error retry.
Anybody have a link to what Arjan fixed? I used to have occasional hangs like
this but they seemed to have gone away with qlogic's latest (4.46.12beta)
driver.
t.
--
*********************************************************
* tpepper@vato dot org * Venimus, Vidimus, *
* http://www.vato.org/~tpepper * Dolavimus *
*********************************************************
next parent reply other threads:[~2002-02-04 18:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BDE817654148D51189AC00306E063AAE054620@exchange.store-age.com>
2002-02-04 18:45 ` Tim Pepper [this message]
2002-02-04 20:43 ` 2.4.17: Bug? Arjan van de Ven
2002-02-05 19:02 Alexander Sandler
-- strict thread matches above, loose matches on Subject: below --
2002-02-03 16:31 Alexander Sandler
2002-02-03 16:04 Alexander Sandler
2002-02-03 16:26 ` arjan
2002-02-04 0:24 ` Tim Pepper
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=20020204104525.A30033@vato.org \
--to=tpepper@vato.org \
--cc=ASandler@store-age.com \
--cc=arjan@fenrus.demon.nl \
--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