From: Alexis Bruemmer <alexisb@us.ibm.com>
To: malahal@us.ibm.com
Cc: linux-scsi@vger.kernel.org
Subject: Re: BUG in sas event handling mechanism???
Date: Fri, 22 Sep 2006 11:17:17 -0700 [thread overview]
Message-ID: <1158949037.5718.3.camel@alexis> (raw)
In-Reply-To: <20060922174046.GA18715@us.ibm.com>
On Fri, 2006-09-22 at 10:40 -0700, malahal@us.ibm.com wrote:
> I see a PORTE_BYTES_DMAED event, followed by a PHYE_LOSS_OF_SIGNAL event
> and then followed by a PORTE_BYTES_DMAED event on the same phy. The code
> seems to just drop the last event because of the not yet processed first
> event. So, it just processes the first two events in that order. In
> other words, the link doesn't get used at all!
I am seeing a very similar issue with hot-plugging on the x260 systems
with the internal expanders. If a disk is pulled and plugged back in
right away then the PORTE_BROADCAST_RCVD event that was triggered when
the disk is plugged back in is dropped, causing the disk to never be
rediscovered. If there is enough of a delay between unplugging and
plugging then both PORTE_BROADCAST_RCVD events are processed correctly.
Any ideas on what would cause these events to be dropped?
--Alexis
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2006-09-22 18:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 17:40 BUG in sas event handling mechanism??? malahal
2006-09-22 18:17 ` Alexis Bruemmer [this message]
2006-09-22 18:32 ` malahal
2006-09-22 18:47 ` Luben Tuikov
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=1158949037.5718.3.camel@alexis \
--to=alexisb@us.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=malahal@us.ibm.com \
/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