mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Robert Crocombe <rcrocomb@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	linux1394-devel <linux1394-devel@lists.sourceforge.net>
Subject: Re: ieee1394: host adapter disappears on 1394 bus reset
Date: Mon, 27 Nov 2006 23:34:53 +0100	[thread overview]
Message-ID: <456B680D.2000703@s5r6.in-berlin.de> (raw)
In-Reply-To: <e6babb600611271234u5bb09ef1j1e26d68548770e88@mail.gmail.com>

Robert Crocombe wrote:
...
> Nov 27 13:06:37 spanky kernel: ohci1394: fw-host1: IntEvent: 00020010

busReset + RQPkt (packet sent)

...
> Nov 27 13:06:37 spanky kernel: ohci1394: fw-host1: IntEvent: 00010000

selfIDcomplete

...
> Nov 27 13:06:40 spanky kernel: ohci1394: fw-host1: IntEventClear
> 00000000 IntEventSet   04508000 IntMaskSet    838301f3

IntEventSet = phyRegRcvd + cycleLost + cycleSynch + selfIDcomplete2

> Nov 27 13:06:40 spanky kernel: ohci1394: fw-host1: IntEvent: 00020010
...
> Nov 27 13:06:41 spanky kernel: ohci1394: fw-host1: IntEvent: 00010000
...
> Nov 27 13:06:44 spanky kernel: ohci1394: fw-host1: IntEventClear
> 00000000 IntEventSet   6ffdc33f IntMaskSet    00000000

IntEventSet = vendorSpecific + softInterrupt + ack_tardy + phyRegRcvd +
cycleTooLong + unrecoverableError + cycleInconsistent + cycleLost +
cycle64Seconds + cycleSynch + phy + regAccessFail + selfIDComplete +
selfIDComplete2 + [reserved...?] + lockRespErr + postedWriteErr + RSPkt
+ RQPkt + ARRS + ARRQ + respTxComplete + reqTxComplete

(The bit 00004000 is not standardized and shouldn't be there. Whatever.)

That's a lot of stuff that happened right before this last print macro.
Maybe ages were spent in hpsb_selfid_complete. I will try to work on
getting non-critical parts out of hpsb_selfid_complete issue during the
week, but I don't know how fast I can do this and if this will help in
the first place.

...
> I didn't mention that I have:
> 
> options ieee1394 disable_nodemgr=1
> options ohci1394 phys_dma=0
> 
> in my /etc/modprobe.conf.  The Linux adapters are functioning as
> simulated peripherals to a piece of control hardware that always has a
> dest address of 0x0000 0000 0000 on all packets so I needed to get rid
> of posted writes and any bickering over bus master.

Posted writes are still enabled. phys_dma=0 disables only the physical
response unit. You have to change the source if you want to disable
posted writes. See the top of ohci_initialize. Should this be a module
load parameter too?
-- 
Stefan Richter
-=====-=-==- =-== ==-==
http://arcgraph.de/sr/

  reply	other threads:[~2006-11-27 22:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-22 15:31 Robert Crocombe
2006-11-22 21:44 ` Stefan Richter
2006-11-23  0:28   ` Robert Crocombe
2006-11-27 15:39     ` Robert Crocombe
2006-11-27 17:11       ` Stefan Richter
2006-11-27 17:46         ` Robert Crocombe
2006-11-27 18:26           ` Stefan Richter
2006-11-27 20:34             ` Robert Crocombe
2006-11-27 22:34               ` Stefan Richter [this message]
2006-11-28 19:07                 ` Robert Crocombe
2006-11-28 20:14                   ` Stefan Richter
2006-11-27 18:29         ` MMIO write ordering (was Re: ieee1394: host adapter disappears on 1394 bus reset) 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=456B680D.2000703@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=rcrocomb@gmail.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

all inboxes | Powered by JetHome®