From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: bugme-daemon@bugzilla.kernel.org
Cc: linux-scsi@vger.kernel.org
Subject: Re: [Bug 12759] scsi: aic7xxx hang since v2.6.28-rc1 ...
Date: Sat, 14 Mar 2009 17:51:04 -0500 [thread overview]
Message-ID: <1237071064.3907.76.camel@localhost.localdomain> (raw)
In-Reply-To: <20090314211820.D47F9108047@picon.linux-foundation.org>
On Sat, 2009-03-14 at 14:18 -0700, bugme-daemon@bugzilla.kernel.org
wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=12759
>
>
> rjw@sisk.pl changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Status|NEW |CLOSED
> Resolution| |CODE_FIX
>
>
>
>
> ------- Comment #1 from rjw@sisk.pl 2009-03-14 14:18 -------
> The problem seems to have been fixed, closing.
Actually, I don't think the problem is gone, it's just gone into hiding
again. What seems to happen is that as we alter code in scsi_lib.c,
particularly along the completion paths, it reappears and then
disappears again. It looks like some obscure timing related bug,
possibly in the aic7xxx driver, or possibly in the mid-layer
I've rebuilt my main SCSI test box to be aic7xxx based to see if we can
somehow find it again and debug it.
So, I'd like this bug left open against SCSI please, but you can
probably remove it as a current regression (I think it's probably been
hiding for a very long time).
James
next prev parent reply other threads:[~2009-03-14 22:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 22:50 [Bug 12759] New: scsi: aic7xxx hang since v2.6.28-rc1 bugme-daemon
2009-03-14 21:18 ` [Bug 12759] " bugme-daemon
2009-03-14 22:51 ` James Bottomley [this message]
2009-03-14 22:52 ` bugme-daemon
2009-03-15 0:17 ` bugme-daemon
2009-03-15 0:18 ` bugme-daemon
[not found] <bug-12759-11613@https.bugzilla.kernel.org/>
2012-05-30 14:14 ` bugzilla-daemon
2012-08-29 17:12 ` bugzilla-daemon
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=1237071064.3907.76.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).