John Harvey wrote:
--- Duncan Webb <[EMAIL PROTECTED]> wrote:
John Harvey wrote:
Can you also determine if it's the same cmd (ie
0x000060).
What do you mean the same cmd? Do you mean each time
it crashes?
0x000060 isn't an ioctl command, is it a X driver
command?
The video is being played with mplayer.
If you look at the dmesg log provided the code was
issuing cmd 0x000060 to the firmware. This is setting
the colorkey. If this is always the problem then that
would point very closely to the area of code with the
problem.
I now have some more information that may help. First, I use Freevo and
it's configured to use mplayer as the video player. Something has now
crashed after 66 hour uptime and mplayer has been started 190 times.
What happened is that mplayer won't play another mpeg video correctly,
sound is okay but the screen is pure blue, exiting mplayer the screen
redisplays the menu and subsequent plays give sound and a blue screen.
This time the kernel log shows:
Jun 27 13:13:59 elf kernel: ivtv0-osd warning: Need to adjust to width
720 src_w 720 dst_w 720 src_x 0 dst_x 0
Jun 27 13:13:59 elf kernel: ivtv0-osd warning: Need to adjust to height
576 src_h 576 dst_h 576 src_y 0 dst_y 0
Jun 27 13:13:59 elf kernel: ivtv0-osd warning: Source video: Interlaced
Jun 27 13:13:59 elf kernel: ivtv0 warning: Enable video output
Jun 27 15:10:44 elf kernel: ivtv0 warning: No Free Mailbox for cmd
0x00000060 after 100 tries!
Jun 27 15:10:44 elf kernel: ivtv0 warning: Mailbox[0] 0x00000060 flags
0x00000003
Jun 27 15:10:44 elf kernel: ivtv0 warning: Mailbox[1] 0x00000060 flags
0x00000003
Jun 27 15:10:44 elf kernel: ivtv0 warning: Firmware UNRESPONSIVE when
trying cmd 0x00000060!!!
Jun 27 15:10:44 elf kernel: ivtv0-osd warning: Need to adjust to width
720 src_w 720 dst_w 720 src_x 0 dst_x 0
Jun 27 15:10:44 elf kernel: ivtv0-osd warning: Need to adjust to height
576 src_h 576 dst_h 576 src_y 0 dst_y 0
Jun 27 15:10:44 elf kernel: ivtv0-osd warning: Source video: Interlaced
I upgraded the ivtv drivers to 0.4.6 and have attached the log for your
inspection.
Myth has been running here using the ivtv X driver
for about 2 months
without crashing.
That's stable enough and my guess is that your using
an Intel based
system. I use an AMD64 based system running only
64bit libs.
Nope its an amd system (but not 64).
Here's the infomation about the video that was playing:
--- Video Information
---
Video Codec Type(e.g. "DIV3"): MPEG2_Video
Video Codec Name(e.g. "DivX 3, Low-Motion"): MPEG-2
Duration (hh:mm:ss): 00:05:00
Frame Count: 7499
Frame Width (pixels): 720
Frame Height (pixels): 576
Pixel Aspect Ratio ("SAR"):
Display Aspect Ratio ("DAR"): 1.333
Frames Per Second: 25.0
Video Bitrate (kbps): 4500
MPEG-4 ("MPEG-4" or ""):
B-VOP ("B-VOP" or ""):
QPel ("QPel" or ""):
GMC ("GMC" or ""):
H264 ("H264" or ""):
MPEG-2 ("MPEG-2" or ""): MPEG-2
Interlaced ("I/L" or ""): I/L
Progressive ("Prog" or ""):
Top Frame First ("TFF" or ""): TFF
Bottom Frame First ("BFF" or ""):
3:2 Pulldown ("3:2" or ""):
Picture-per-field ("PPF" or ""):
ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.4.6 (development snapshot compiled on Mon 26 Jun 2006 10:50:06
CEST) loading
ivtv: Linux version: 2.6.15.6-elf-r1 preempt gcc-4.0
ivtv: In case of problems please include the debug info between
ivtv: the START INIT IVTV and END INIT IVTV lines, along with
ivtv: any module options, when mailing the ivtv-users mailinglist.
ivtv0: Autodetected WinTV PVR 350 card (cx23415 based)
ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
GSI 18 sharing vector 0xC1 and IRQ 18
ACPI: PCI Interrupt 0000:05:06.0[A] -> Link [APC1] -> GSI 16 (level, low) ->
IRQ 18
ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
tveeprom: ivtv version
tveeprom: Hauppauge: model = 48139, rev = K257, serial# = 8105690
tveeprom: tuner = Philips FM1216 ME MK3 (idx = 57, type = 38)
tveeprom: tuner fmt = PAL(B/G) PAL(I) SECAM(L/L') PAL(D/K) (eeprom = 0x74, v4l2
= 0x00400e17)
tveeprom: audio processor = MSP4418 (type = 19)
tveeprom: decoder processor = SAA7115 (type = 13)
ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50]
tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #0
ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61]
saa7115 0-0021: saa7115 found @ 0x42 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=saa7115, addr=21]
saa7127 0-0044: ivtv driver
saa7127 0-0044: saa7129 found @ 0x88 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=saa7127, addr=44]
msp3400 0-0040: chip=MSP4418G-B3 +nicam +simple +simpler +radio mode=simpler
msp3400 0-0040: msp34xxg daemon started
ivtv0: i2c attach to card #0 ok [client=MSP4418G-B3, addr=40]
tda9887 0-0043: (ivtv) chip found @ 0x86 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=tda9887, addr=43]
ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
ivtv0: loaded v4l-cx2341x-dec.fw firmware (262144 bytes)
ivtv0: Encoder revision: 0x02050032
ivtv0: Decoder revision: 0x02020023
ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
ivtv0: Allocate DMA encoder YUV stream: 161 x 12960 buffers (2048KB total)
ivtv0: Allocate DMA encoder VBI stream: 80 x 26208 buffers (2048KB total)
ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total)
ivtv0: Create encoder radio stream
ivtv0: Allocate DMA decoder MPEG stream: 16 x 65536 buffers (1024KB total)
ivtv0: Allocate DMA decoder VBI stream: 512 x 2048 buffers (1024KB total)
ivtv0: Create decoder VOUT stream
ivtv0: Allocate DMA decoder YUV stream: 20 x 51840 buffers (1024KB total)
ivtv0: loaded v4l-cx2341x-init.mpg firmware (155648 bytes)
tuner: type set to 38 (Philips PAL/SECAM multi (FM1216ME MK3)) by ivtv i2c
driver #0
ivtv0: Initialized WinTV PVR 350, card #0
ivtv: ==================== END INIT IVTV ====================
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
