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-09 21:28:38
|
On Wed, May 09, 2012 at 08:21:29AM +0200, Clemens Ladisch wrote: > Lluís Batlle i Rossell wrote: > > # lsfirewirephy > > timeout > > timeout > > (This should work directly after booting, before any hang.) Yes, they work fine. > All these symptoms indicate that the FireWire interrupt just isn't reported > anymore. Ok. > > 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. > > So this is probably not related with the VT6315 itself but with the system's > interrupt routing. Sometimes, this is caused by ACPI problems; try updating > the BIOS, if possible. I run the latest BIOS available two weeks ago. I wanted to get k8-powernow, and hence updated the bios. But I really did not notice any change other than the 'nicer' bios configuration and boot screens. I also run the latest microcode in the cpu. :) > What is the entire output of dmesg immediately after booting? What are the > outputs of "cat /proc/interrupt" and "dmesg | tail" when it hangs? I attach the dmesg, but it does not have the firewire camera connected now. 'dmesg | tail' when it hangs does not have any additional line. I attach the full dmesg (after a pm-suspend and awake), and the /proc/interrupts. Now gzipped. Regards, Lluís. |