Re: Problems in 3.3.x with via VT6315
Brought to you by:
aeb,
bencollins
From: Stefan R. <st...@s5...> - 2012-05-08 18:28:59
|
On May 08 Lluís Batlle i Rossell wrote: > On Tue, May 08, 2012 at 06:31:36PM +0200, Lluís Batlle i Rossell wrote: > > 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] One potential cause for never timing out would be if the controller never gives us an AT-req IRQ ('asynchronous request transmitted' interrupt). That would be a chip bug against which our drivers are currently not protected. JMicron JMB38x is known to behave that way; I have particularly observed it with Coriander (IIDC capture application). However, I have not yet heard of VIA VT6315 behaving this way. (The old driver stack would time out even after missing AT-req IRQ, as would earlier versions of the newer driver stack --- at the risk of races with transaction completion though.) I'm not saying that this is what happens, just suggesting it as a possibility. After # echo 2 > /sys/module/firewire_ohci/parameters/debug the driver will log all AT and AR events that do happen; alas it won't reveal a case when upper layers inserted a request but the controller did not raise AT-req. To detect that, we would have to modify the driver to log request insertion too. > Sorry, but before I told you the phenomII was running 3.3.4, but it is running > 3.3.5. > > I updated the i7 machine to 3.3.5 too, and there it does not hang. Same chipset, > same kernel, but in the phenomII it hangs (any of the two cameras we have, > colour and mono), and in the i7 not. > > Annoying... Any idea from this confusion? :) That's curious. Maybe these are two different chip revisions? lspci would possibly still show them with same revision number; a look at the actual chip may or may not tell more. Are these PCIe cards which you could swap between the two PCs? -- Stefan Richter -=====-===-- -=-= -=--- http://arcgraph.de/sr/ |