Carl Page wrote: > Thanks for your suggestion. Turned on block_dump and when the disk > activity starts, the dmesg output is full of this sort of thing > > ivtv-osd: OSD: REG_DECSG1LEN wait failed > ivtv: DMA Registers State: xfer: 0x00000000, state: 0x00000003 dec_addr: > 0x16b2c 0cc enc_addr: 0x00000000 control: 0x00000003 > ivtv: DMA DEC Buffers: > 0x13ea8000:0x015208c0:0x80001000 > ivtv: DMA ENC Buffers: > 0x00000000:0x00000000:0x00000000 > 0x00000000:0x00000000:0x00000000 > 0x00000000:0x00000000:0x00000000 > 0x00000000:0x00000000:0x00000000 > 0x4004200d:0x24800006:0x04910b10 > 0x0100ad0d:0xc8600038:0x0100510d > 0x5a58412c:0x52283344:0x80c60c0c > 0x200682f4:0x39240000:0x110005c4 > syslogd(3568): dirtied inode 820785 (messages) on dm-0 > syslogd(3568): dirtied inode 820785 (messages) on dm-0 > syslogd(3568): WRITE block 17999640 on dm-0
^^^ these are the lines we are looking for. Looks like John was right. Syslogd is doing all the disk activity. Might want to turn down/off debugging output. --Brian > ivtv-osd: OSD: REG_DECSG1LEN wait failed > ivtv: DMA Registers State: xfer: 0x00000000, state: 0x00000003 dec_addr: > 0x16b2c 0cc enc_addr: 0x00000000 control: 0x00000003 > ivtv: DMA DEC Buffers: > 0x13ea8000:0x015208c0:0x80001000 > ivtv: DMA ENC Buffers: > 0x00000000:0x00000000:0x00000000 > 0x00000000:0x00000000:0x00000000 > 0x00000000:0x00000000:0x00000000 > 0x00000000:0x00000000:0x00000000 > 0x4004200d:0x24800006:0x04910b10 > 0x0100ad0d:0xc8600038:0x0100510d > 0x5a58412c:0x52283344:0x80c60c0c > 0x200682f4:0x39240000:0x110005c4 > > > Before the disk activity starts, there's no ivtv-osd or ivtv messages. > These blocks repeat themselves over and over while the disk is thrashing. > > > Brian Jackson wrote: > >> Carl Page wrote: >> >>> Hi, >>> >>> After much pain and anguish, I finally have X working on TV-out through >>> my PVR-350. :) >>> >>> However, for some time, since I first managed to copy video0 to video16 >>> and see some fuzzy TV being output from my PVR-350, I've noticed that >>> after two-three minutes of TV output, my hard-disk starts going crazy. >>> When I enable TV-out, it's fine for a few minutes, then I hear the disk >>> start up and looking at gkrellm I see the disk throughput go through the >>> roof. It stays like that until I disable TV-out. >>> >>> The same thing is happening when I use X through the PVR's TV-out. I >>> start X windows and after a few minutes, the hard disk starts thrashing. >>> >>> My system is an AMD Athlon64 3000+, running FC3. The hard-disk is a new >>> 160Gb Seagate Barrucade 7. I see no reason why it should need to go >>> near the disk when all it's doing is displaying a TV picture. >>> >>> Any thoughts people? >> >> >> >> If you have a recent(ish) kernel, you can use part of laptop mode to >> see what is >> using the disk. Read /usr/src/linux/Documentation/laptop-mode.txt and >> look for >> block_dump. There's a way to get the kernel to report all disk read >> and write >> operations. That'll at least tell you what process is doing it or help >> you >> narrow things down a little hopefully. -- Stuff for sale -- http://www.brianandsara.net/temp/forsale.html Gentoo Linux -- http://www.gentoo.org IVTV -- http://ivtv.writeme.ch ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
