Subject: Re: FireWire broken after suspend/resume in -current
To: None <rhialto@falu.nl>
From: KIYOHARA Takashi <kiyohara@kk.iij4u.or.jp>
List: current-users
Date: 01/07/2007 03:13:51
Hi! rhialto,

apologize slowly response.  ;-)


From: Rhialto <rhialto@falu.nl>
Date: Thu, 4 Jan 2007 22:30:55 +0100

> If I suspend and resume a -current kernel (cvs updated today, but it
> also happened with one from 31 december), the firewire interface doesn't
> work anymore.

I know this a problem.


> My previous kernel from around 7 december would completely hang when
> resuming, so I can't say how that one would have reacted.

hmm...  It is not believed from me.  This problem existed from older.


> fw_rcv: unknown response RRESQ(6) src=0xffc0 tl=0x1 rt=1 data=0x20042e04
> try ad-hoc work around!!
> no use...
> ieee1394if0: split transaction timeout dst=0xffc0 tl=0x7 state=3
> fw_rcv: unknown response RRESQ(6) src=0xffc0 tl=0x2 rt=1 data=0x34393331
> try ad-hoc work around!!
> no use...
> ieee1394if0: split transaction timeout dst=0xffc0 tl=0x8 state=3
> fw_rcv: unknown response RRESQ(6) src=0xffc0 tl=0x3 rt=1 data=0x2a0ff00
> try ad-hoc work around!!
> no use...
> ieee1394if0: split transaction timeout dst=0xffc0 tl=0x9 state=3


I will not make progress because I am busy though I try the solution of
this problem.  X-<

Thanks,
--
kiyohara