Re: Problems in 3.3.x with via VT6315
Brought to you by:
aeb,
bencollins
From: Lluís B. i R. <vi...@vi...> - 2012-05-08 16:31:51
|
On Tue, May 08, 2012 at 06:28:50PM +0200, Lluís Batlle i Rossell wrote: > On Tue, May 08, 2012 at 05:30:34PM +0200, Clemens Ladisch wrote: > > Lluís Batlle i Rossell wrote: > > > SysRq : Show Blocked State > > > task PC stack pid father > > > cc1394 D ffffffff81407520 0 5918 5880 0x00000005 > > > Call Trace: > > > [<ffffffff813c8baf>] schedule+0x3f/0x60 > > > [<ffffffffa0106fcd>] fw_device_op_release+0x18d/0x250 [firewire_core] > > (BTW: what is the output of lsfirewirephy?) > > I notice that, let's say, my /usr/include/linux is from 2.6.35, and I've all > built with those headers. Is the public API of the kernel changed at 3.3.x, for > firewire? Should I rebuild all the libdc/libraw code with newer headers? > > Or simply getting the newer firewire-cdev header files would be enough, building > jujuutils with them? > > I'll try this later. Hm this was fast. I have the jujutils built: # lsfirewirephy timeout timeout Does this mean much? Regards, Lluís. |