[Bug 48317] firewire not detected on resume from suspend

Stoic Jed stoicjed at hotmail.com
Wed Jun 7 15:12:26 UTC 2006


Public bug reported:

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-
image-2.6.15-21-686'; however, that package was not published in Ubuntu.

** Affects: linux-source-2.6.15 (Ubuntu)
     Importance: Medium
         Status: Unconfirmed

-- 
firewire not detected on resume from suspend
https://launchpad.net/bugs/48317




More information about the kernel-bugs mailing list