On Wednesday 14 September 2005 02:17, Stefan Richter wrote: > Jan De Luyck wrote: > > after putting my laptop into S3 and reviving it at home, the firewire > > interface was unusable, no response when plugging in my external disk, > > loading sbp2 manually didn't trigger anything. > > [...] > > > I saw this thread: > > http://marc.theaimsgroup.com/?l=linux1394-user&m=111262313930798&w=2 > > tho I'm not sure if it's relevant to this. > > IEEE 1394 power management (i.e. management of bus power consumption or > of other nodes' internal power states) is not related to ACPI suspend/ > resume of the local controller AFAICS. I thought so. It was the only thing even remotely relevant I found on the mailinglists tho. > According to your log, the cause is to be looked for in ohci1394's > purely hardware related parts or perhaps even outside of the ieee1394 > subsystem. I've attached the lspci -vvx before and after suspending to S3. There are a lot of differences, but I have no idea how to interprete them :/ Here's what the diff gives: devilkin@precious:/tmp$ diff -Nur before-s3 after-s3 --- before-s3 2005-09-14 07:05:58.797920320 +0200 +++ after-s3 2005-09-14 07:05:10.226304328 +0200 @@ -1,16 +1,15 @@ 0000:02:07.0 FireWire (IEEE 1394): Texas Instruments TSB43AB21 IEEE-1394a-2000 Controller (PHY/Link) (prog-if 10 [OHCI]) Subsystem: Acer Incorporated [ALI]: Unknown device 001f - Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- + Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR-