firewire not detected on resume from suspend
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-source-2.6.15 (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
After resuming from suspend, firewire devices are no longer detected. Unplugging and replugging the firewire cable has no effect.
The following messages were found in /var/log/kern.log after suspending and resuming with a mounted firewire mass storage device.
ohci1394: fw-host0: Running dma failed because Node ID is not valid
ieee1394: sbp2: aborting sbp2 command
ohci1394: fw-host0: Running dma failed because Node ID is not valid
ohci1394: fw-host0: Running dma failed because Node ID is not valid
ieee1394: sbp2: aborting sbp2 command
ohci1394: fw-host0: Running dma failed because Node ID is not valid
ieee1394: sbp2: reset requested
ieee1394: sbp2: Generating sbp2 fetch agent reset
ohci1394: fw-host0: Running dma failed because Node ID is not valid
ohci1394: fw-host0: Running dma failed because Node ID is not valid
ieee1394: sbp2: aborting sbp2 command
ohci1394: fw-host0: Running dma failed because Node ID is not valid
ieee1394: sbp2: reset requested
ieee1394: sbp2: Generating sbp2 fetch agent reset
ohci1394: fw-host0: Running dma failed because Node ID is not valid
Note: the original reporter indicated the bug was in package 'linux-
This is tracked as an upstream bug at http:// bugzilla. kernel. org/show_ bug.cgi? id=7072 . You could add your e-mail address there if you are interested in latest news. Don't expect a fix soon.
As a workaround, mark ohci1394 (and perhaps the other IEEE 1394 drivers) to be unloaded before suspend. I don't know though how to do this in Ubuntu.