Bug 8403 - loops of "ieee1394: Current remote IRM is not 1394a-2000 compliant, resetting."
loops of "ieee1394: Current remote IRM is not 1394a-2000 compliant, resetting."
Status: REJECTED WILL_NOT_FIX
Product: Drivers
Classification: Unclassified
Component: IEEE1394
i386 Linux
: P2 normal
Assigned To: drivers_ieee1394
:
Depends on:
Blocks: 10046
  Show dependency treegraph
 
Reported: 2007-04-29 05:56 UTC by Stefan Richter
Modified: 2009-01-14 09:11 UTC (History)
0 users

See Also:
Kernel Version: all
Tree: Mainline
Regression: ---


Attachments

Description Stefan Richter 2007-04-29 05:56:44 UTC
If two or more Linux PCs are connected to the same bus, ieee1394's nodemgr
repeatedly fails to detect that the present IRM is 1394a compliant and resets
the bus to become IRM itself.  This results in many resets and makes traffic on
the bus impossible before the bus settles down.

Workaround:  Load ieee1394 by "modprobe ieee1394 disable_irm=1" on N-1 of N nodes.
Comment 1 Stefan Richter 2008-02-19 12:25:08 UTC
There are currently no resources to fix this in drivers/ieee1394/.
drivers/firewire/ is not known to feature this problem.
Comment 2 Stefan Richter 2009-01-14 09:11:49 UTC
Clarification:
Current drivers/firewire/ is known to work correctly in this regard.

Note You need to log in before you can comment on or make changes to this bug.