public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Kristian Hoegsberg <krh@bitplanet.net>,
	linux1394-devel@lists.sourceforge.net,
	linux-scsi@vger.kernel.org, bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bug 9734] New: I/O error when inserting a second firewire	sata disk
Date: Sun, 13 Jan 2008 10:06:32 +0100	[thread overview]
Message-ID: <4789D498.5070103@s5r6.in-berlin.de> (raw)
In-Reply-To: <1200186705.3656.83.camel@localhost.localdomain>

James Bottomley wrote:
> Firewire list cc'd

It's indeed a problem in the firewire stack.

...
>> now we attach another sata disk to the second port of the pci firewire B
>> controller:
>>
>> Jan 12 16:50:49 x3400 kernel: firewire_sbp2: orb reply timed out, rcode=0x11
>> Jan 12 16:50:49 x3400 kernel: sd 11:0:0:0: [sdc] Result: hostbyte=DID_BUS_BUSY
>> driverbyte=DRIVER_OK,SUGGEST_OK
> 
> Best I can tell, this is the source of the problem.  The sbp2 driver is
> replying DID_BUS_BUSY until that gets sorted out, which seems to be
> never.

When something was plugged in or out at the same bus, fw-sbp2 has to
reconnect == renew the login to each logical unit.  The syslog in the
report is inconclusive whether that happened or failed.  There should be
one of
	"reconnected to ... LUN ... (... retries)"
or	"failed to reconnect to ..."
logged eventually.  As long as the reconnect didn't succeed, fw-sbp2
quits newly enqueued commands with DID_BUS_BUSY.

I need a bit spare time and a way to reproduce this or similar things to
get to the cause of this.  (I had random reconnect problems with fw-sbp2
now and then, but not yet 100% reproducible ones like the reporter has.)

The last tested kernel in the report, 2.6.24-rc7, already contains the
latest and greatest firewire code as far as problem at hand is concerned.

> So, first pass analysis indicates the error to be in the firewire
> subsystem.  I'm guessing from the message that it's actually
> drivers/firewire, not drivers iee1934?

Yes.

As a side note, the old sbp2 driver does not quit commands with
DID_BUS_BUSY between bus reset and reconnect.  Instead it blocks the
Scsi_Host in order to not receive commands during that time at all.

The time from bus reset to successful reconnect is typically circa a
second, on bigger buses with lots of protocol activity after bus reset
perhaps a few seconds.  (Could IMO still be optimized, in both of the
drivers/ieee1394 and drivers/firewire implementations.)
-- 
Stefan Richter
-=====-==--- ---= -==-=
http://arcgraph.de/sr/

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace

  reply	other threads:[~2008-01-13  9:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-12 15:47 [Bug 9734] New: I/O error when inserting a second firewire sata disk bugme-daemon
2008-01-12 16:02 ` [Bug 9734] " bugme-daemon
2008-01-13  1:11 ` [Bug 9734] New: " James Bottomley
2008-01-13  9:06   ` Stefan Richter [this message]
2008-02-03  2:10     ` Stefan Richter
2008-01-19 13:20   ` Stefan Richter
2008-01-19 20:47     ` Stefan Richter

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=4789D498.5070103@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=krh@bitplanet.net \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    /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