Roger Heflin wrote: > ...what PCI latency message is it... # fgrep -i latency /var/log/dmesg.0 [33.177423] PCI: Setting latency timer of device 0000:00:08.0 to 64 [35.988363] PCI: Setting latency timer of device 0000:00:02.0 to 64 [36.153209] PCI: Setting latency timer of device 0000:00:02.1 to 64 [36.313148] PCI: Setting latency timer of device 0000:00:02.2 to 64 [38.837823] PCI: Setting latency timer of device 0000:00:0d.0 to 64 [38.897106] PCI: Setting latency timer of device 0000:00:04.0 to 64 [60.710413] ivtv0: Unreasonably low latency timer, setting to 64 (was 32) [61.096095] PCI: Setting latency timer of device 0000:00:06.0 to 64 [67.561088] ivtv1: Unreasonably low latency timer, setting to 64 (was 32)
I looked into this back when I first deployed the system in the Fall of 2006, and I don't recall what I found, but I'm pretty sure I never implemented any fixes. > ...and how often does it lockup... It locks up some of the time when I transcode using mencoder, and once when using ffmpeg. I used mencoder to transcode only rarely, and stopped using it because of this. I was hoping the problem would go away when I upgraded Ubuntu from Fiesty to Gutsy, which I did a few weeks ago, but I haven't tried mencoder again. I have, however, found that ffmpeg now generates an error when ran from nuvexport. I need to dig into that. > ...and what exactly do the lockups look like? Black screen or normal looking but frozen screen. Unresponsive to network connections or existing ssh connections. > My Sempron has a VIA chipset. NVIDIA nForce2 chipset. > I know if you have too many dimms and/or are running them too fast > things get unstable (a crash a week under heavy load). When the system was originally built the RAM wouldn't run stable at the manufacturer's specified parameters, but I backed off on them, and the system otherwise runs stable. It seems unlikely to be a RAM issue, as I've had other occasions to stress the RAM that didn't involve transcoding, which didn't result in lockups. Lately, with RAM being so cheap, I've been thinking about replacing the 1 GB of RAM with 2 GB and faster, though I suspect this board is old enough that it requires the less popular and more expensive DDR RAM rather than DDR2. -Tom ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Mvpmc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mvpmc-users mvpmc wiki: http://mvpmc.wikispaces.com/
