From: "Robert Crocombe" <rcrocomb@gmail.com>
To: "Stefan Richter" <stefanr@s5r6.in-berlin.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux1394-devel <linux1394-devel@lists.sourceforge.net>,
"Ingo Molnar" <mingo@elte.hu>
Subject: Re: ieee1394: host adapter disappears on 1394 bus reset
Date: Mon, 27 Nov 2006 13:34:23 -0700 [thread overview]
Message-ID: <e6babb600611271234u5bb09ef1j1e26d68548770e88@mail.gmail.com> (raw)
In-Reply-To: <456B2DD0.4060500@s5r6.in-berlin.de>
[-- Attachment #1: Type: text/plain, Size: 4834 bytes --]
Robert Crocombe wrote:
> this is in 2.6.16-rt29 which has proved to be the easiest to provoke.
> I actually couldn't get 2.6.18 to break earlier this morning (few
> hundred resets).
Okay, I got the problem to occur again with 2.6.18. I will attach my
config in case you wish to scrutinize for any boneheadedness on my
part.
I provoked the problem both with and without the additional read of
IntMaskSet. Amazingly, I lost host1 on the bus reset that occured
after this sequence:
rmmod ohci1394
rmmod ieee1394
make
make modules_install
modprobe ohci1394
which followed my adding the extra register read line. Here's the
entirety of the host1 stuff (I did a s/.*host[^1].*//g in vim). I
snipped some of the self ID chatter.
Nov 27 13:06:35 spanky kernel: ieee1394: nodemgr and IRM functionality disabled
Nov 27 13:06:35 spanky kernel: ohci1394: fw-host1: Remapped memory
spaces reg 0xffffc20000058000
Nov 27 13:06:36 spanky kernel: ohci1394: fw-host1: Soft reset finished
Nov 27 13:06:36 spanky kernel: ohci1394: fw-host1: Iso contexts reg:
000000a8 implemented: 0000000f
Nov 27 13:06:36 spanky kernel: ohci1394: fw-host1: Iso contexts reg:
00000098 implemented: 000000ff
Nov 27 13:06:36 spanky kernel: ohci1394: fw-host1: Receive DMA ctx=0 initialized
Nov 27 13:06:36 spanky kernel: ohci1394: fw-host1: Receive DMA ctx=0 initialized
Nov 27 13:06:36 spanky kernel: ohci1394: fw-host1: Transmit DMA ctx=0
initialized
Nov 27 13:06:36 spanky kernel: ohci1394: fw-host1: Transmit DMA ctx=1
initialized
Nov 27 13:06:36 spanky kernel: ohci1394: fw-host1: physUpperBoundOffset=00000000
Nov 27 13:06:36 spanky kernel: ohci1394: fw-host1: OHCI-1394 1.1
(PCI): IRQ=[98] MMIO=[f9ffe000-f9ffe7ff] Max Packet=[4096] IR/IT
contexts=[4/8]
Nov 27 13:06:37 spanky kernel: ohci1394: fw-host1: IntEvent: 00020010
Nov 27 13:06:37 spanky kernel: ohci1394: fw-host1: irq_handler: Bus
reset requested
Nov 27 13:06:37 spanky kernel: ohci1394: fw-host1: Cancel request received
Nov 27 13:06:37 spanky kernel: ohci1394: fw-host1: Got RQPkt interrupt
status=0x00008409
Nov 27 13:06:37 spanky kernel: ohci1394: fw-host1: Single packet rcv'd
Nov 27 13:06:37 spanky kernel: ohci1394: fw-host1: IntEvent: 00010000
Nov 27 13:06:37 spanky kernel: ohci1394: fw-host1: SelfID interrupt
received (phyid 1, not root)
Nov 27 13:06:37 spanky kernel: ohci1394: fw-host1: SelfID packet
0x807fc494 received
Nov 27 13:06:38 spanky kernel: ohci1394: fw-host1: SelfID packet
0x817fc494 received
Nov 27 13:06:38 spanky kernel: ohci1394: fw-host1: SelfID for this
node is 0x817fc494
Nov 27 13:06:39 spanky kernel: ohci1394: fw-host1: SelfID packet BLAH
...15 more SelfID...
Nov 27 13:06:40 spanky kernel: ohci1394: fw-host1: SelfID complete
Nov 27 13:06:40 spanky kernel: ohci1394: fw-host1: PhyReqFilter=0000000000000000
Nov 27 13:06:40 spanky kernel: ohci1394: fw-host1: IntEventClear
00000000 IntEventSet 04508000 IntMaskSet 838301f3
Nov 27 13:06:40 spanky kernel: ohci1394: fw-host1: IntEvent: 00020010
Nov 27 13:06:40 spanky kernel: ohci1394: fw-host1: irq_handler: Bus
reset requested
Nov 27 13:06:40 spanky kernel: ohci1394: fw-host1: Cancel request received
Nov 27 13:06:40 spanky kernel: ohci1394: fw-host1: Got RQPkt interrupt
status=0x00008409
Nov 27 13:06:40 spanky kernel: ohci1394: fw-host1: Single packet rcv'd
Nov 27 13:06:41 spanky kernel: ohci1394: fw-host1: IntEvent: 00010000
Nov 27 13:06:42 spanky kernel: ohci1394: fw-host1: SelfID interrupt
received (phyid 1, not root)
Nov 27 13:06:42 spanky kernel: ohci1394: fw-host1: SelfID packet
0x807fc494 received
Nov 27 13:06:42 spanky kernel: ohci1394: fw-host1: SelfID packet
0x817fc496 received
Nov 27 13:06:42 spanky kernel: ohci1394: fw-host1: SelfID for this
node is 0x817fc496
Nov 27 13:06:42 spanky kernel: ohci1394: fw-host1: SelfID packet BLAH
...15 more SelfID...
Nov 27 13:06:43 spanky kernel: ohci1394: fw-host1: SelfID complete
Nov 27 13:06:43 spanky kernel: ohci1394: fw-host1: PhyReqFilter=0000000000000000
Nov 27 13:06:44 spanky kernel: ohci1394: fw-host1: IntEventClear
00000000 IntEventSet 6ffdc33f IntMaskSet 00000000
with the bad IntMaskSet again.
I don't know if the host loss when I didn't have the additional read
is meaningful, but there it is simply:
Nov 27 13:04:39 spanky kernel: ohci1394: fw-host2: SelfID packet
0x823fc4f8 rf8c43f8c
.
.
.
Nov 27 13:06:30 spanky kernel: ohci1394: fw-host2: Soft reset finished
with 2 minutes and ~30 bus resets in between.
Oh, poop. 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.
--
Robert Crocombe
rcrocomb@gmail.com
[-- Attachment #2: 2.6.18_00_config.bz2 --]
[-- Type: application/x-bzip2, Size: 6457 bytes --]
next prev parent reply other threads:[~2006-11-27 20:34 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 [this message]
2006-11-27 22:34 ` Stefan Richter
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=e6babb600611271234u5bb09ef1j1e26d68548770e88@mail.gmail.com \
--to=rcrocomb@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=mingo@elte.hu \
--cc=stefanr@s5r6.in-berlin.de \
/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®