Re: Problems in 3.3.x with via VT6315

[Clemens L. <cl...@la...>]

Lluís Batlle i Rossell wrote:
> On Tue, May 08, 2012 at 02:00:15PM +0200, Clemens Ladisch wrote:
>> Lluís Batlle i Rossell wrote:
>>> here we have two computers, both with VT6315, running all x86_64, one is an
>>> intel i7 and the other an amd Phenom II.
>>>
>>> The I7 runs 2.6.35 and dc1394 cameras work perfectly in it.
>>> The Phenom II runs 3.3.4 and dc1394 cameras work for a short seconds, and hang.
>>> Then the process hangs too. Killing the process leaves it <defunct> (unrelated
>>> to the parent accepting it or not).
>>
>> Apparently, the driver is waiting for the hardware to do something.
>>
>> When this happens, are there any messages in the system log (see the output of
>> dmesg)?
>
> Nothing there. I only get some lines if I disconnect the camera, but the process
> remains <defunct>.

Try executing (as root)
  echo w > /proc/sysrq-trigger
when this happens; this should output a list of blocked tasks to the system log.

> Another thing I could not find anywhere is that in the 2.6.35 computer, I get
> /dev/raw1394 and /dev/video1394-0. In the 3.3.x computer, I don't get any such
> device node, and I don't have any modules named raw1394 or video1394.

The FireWire stack was completely rewritten.  Check that your libraw1394 package
is recent enough (current is 2.0.8, but 2.0.6 or newer should work).  In any
case, this library could not cause the kernel to lock up.


Regards,
Clemens