Mailing List Archive: ivtv: users

MSP3400 I/O Errors

Index | Next | Previous | View Threaded

phil at walston

Sep 23, 2007, 11:32 AM

Post #1 of 4 (881 views)
Permalink

MSP3400 I/O Errors

Using Debian with 2.6.20-7 custom kernel and IVTV 0.10.5 with ivtv-fb and
Xdriver for my PVR-350 which is used for a combined mythtv 0.20.2 frontend /
backend system. I'm getting odd messages shortly after startup and ivtv /
ivtv-fb initialization that look like this:

--snip--
msp3400 1-0040: I/O error #0 (read 0x10/0x200)
msp3400 1-0040: I/O error #1 (read 0x10/0x200)
msp3400 1-0040: I/O error #2 (read 0x10/0x200)
msp3400 1-0040: giving up, resetting chip. Sound will go off, sorry folks
:-|
msp3400 1-0040: chip reset failed
msp3400 1-0040: I/O error #0 (write 0x10/0x20)
msp3400 1-0040: I/O error #1 (write 0x10/0x20)
msp3400 1-0040: I/O error #2 (write 0x10/0x20)
msp3400 1-0040: giving up, resetting chip. Sound will go off, sorry folks
:-|
msp3400 1-0040: chip reset failed
msp3400 1-0040: I/O error #0 (write 0x12/0x08)
msp3400 1-0040: I/O error #1 (write 0x12/0x08)
msp3400 1-0040: I/O error #2 (write 0x12/0x08)
msp3400 1-0040: giving up, resetting chip. Sound will go off, sorry folks
:-|
msp3400 1-0040: chip reset failed
--snip--

The msp3400 I/O warnings go on indefinitely. Although this does seem to hang
my mythfrontend (with no apparent error messages in its logs), my myth
backed runs fine and captures video and audio with no issues. I've resisted
cross-posting this to mythtv-users since at this point it does seem pretty
msp3400 specific. But I have a nagging feeling that all is not right with
ivtv on my system. I'm hoping some of the IVTV pros can help set me down the
right debug path. Any ideas?

For the record, here's what dmesg reports for IVTV :

ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.10.5 (tagged release) loading
ivtv: Linux version: 2.6.20.7 mod_unload CYRIXIII
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 Hauppauge card (cx23415 based)
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:00:14.0[A] -> Link [LNKB] -> GSI 11 (level, low) ->
IRQ 11
ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Linux agpgart interface v0.101 (c) Dave Jones
parport_pc: VIA 686A/8231 detected
parport_pc: probing current configuration
parport_pc: Current parallel port base: 0x378
parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP]
parport_pc: VIA parallel port: io=0x378, irq=7
Real Time Clock Driver v1.12ac
ivtv0: loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
ivtv0: loaded v4l-cx2341x-dec.fw firmware (262144 bytes)
ivtv0: Encoder revision: 0x02060039
ivtv0: Decoder revision: 0x02020023
tveeprom 1-0050: Hauppauge model 48132, rev K268, serial# 9945480
tveeprom 1-0050: tuner model is LG TAPE H001F MK3 (idx 68, type 47)
tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 1-0050: audio processor is MSP4448 (idx 27)
tveeprom 1-0050: decoder processor is SAA7115 (idx 19)
tveeprom 1-0050: has radio, has IR receiver, has no IR transmitter
ivtv0: Autodetected Hauppauge WinTV PVR-350
tuner 1-0043: chip found @ 0x86 (ivtv i2c driver #0)
tda9887 1-0043: tda988[5/6/7] found @ 0x43 (tuner)
tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
saa7115 1-0021: saa7115 found (1f7115d0e100000) @ 0x42 (ivtv i2c driver #0)
saa7127 1-0044: saa7129 found @ 0x88 (ivtv i2c driver #0)
msp3400 1-0040: MSP4448G-A2 found @ 0x80 (ivtv i2c driver #0)
msp3400 1-0040: MSP4448G-A2 supports radio, mode is autodetect and
autoselect
ivtv0: Registered device video0 for encoder MPEG (4 MB)
ivtv0: Registered device video32 for encoder YUV (2 MB)
ivtv0: Registered device vbi0 for encoder VBI (1 MB)
ivtv0: Registered device video24 for encoder PCM audio (1 MB)
ivtv0: Registered device radio0 for encoder radio
ivtv0: Registered device video16 for decoder MPEG (1 MB)
ivtv0: Registered device vbi8 for decoder VBI (1 MB)
ivtv0: Registered device vbi16 for decoder VOUT
ivtv0: Registered device video48 for decoder YUV (1 MB)
ivtv0: loaded v4l-cx2341x-init.mpg firmware (155648 bytes)
tuner 1-0061: type set to 47 (LG NTSC (TAPE series))
ivtv0: Initialized Hauppauge WinTV PVR-350, card #0
ivtv: ==================== END INIT IVTV ====================

hverkuil at xs4all

Oct 12, 2007, 7:05 AM

Post #2 of 4 (746 views)
Permalink

Re: MSP3400 I/O Errors [In reply to]

On Sunday 23 September 2007 20:32:59 Philip Walston wrote:
> Using Debian with 2.6.20-7 custom kernel and IVTV 0.10.5 with ivtv-fb
> and Xdriver for my PVR-350 which is used for a combined mythtv 0.20.2
> frontend / backend system. I'm getting odd messages shortly after
> startup and ivtv / ivtv-fb initialization that look like this:
>
> --snip--
> msp3400 1-0040: I/O error #0 (read 0x10/0x200)
> msp3400 1-0040: I/O error #1 (read 0x10/0x200)
> msp3400 1-0040: I/O error #2 (read 0x10/0x200)
> msp3400 1-0040: giving up, resetting chip. Sound will go off, sorry
> folks
>
> :-|
>
> msp3400 1-0040: chip reset failed
> msp3400 1-0040: I/O error #0 (write 0x10/0x20)
> msp3400 1-0040: I/O error #1 (write 0x10/0x20)
> msp3400 1-0040: I/O error #2 (write 0x10/0x20)
> msp3400 1-0040: giving up, resetting chip. Sound will go off, sorry
> folks
>
> :-|
>
> msp3400 1-0040: chip reset failed
> msp3400 1-0040: I/O error #0 (write 0x12/0x08)
> msp3400 1-0040: I/O error #1 (write 0x12/0x08)
> msp3400 1-0040: I/O error #2 (write 0x12/0x08)
> msp3400 1-0040: giving up, resetting chip. Sound will go off, sorry
> folks
>
> :-|
>
> msp3400 1-0040: chip reset failed
> --snip--
>
> The msp3400 I/O warnings go on indefinitely. Although this does seem
> to hang my mythfrontend (with no apparent error messages in its
> logs), my myth backed runs fine and captures video and audio with no
> issues. I've resisted cross-posting this to mythtv-users since at
> this point it does seem pretty msp3400 specific. But I have a nagging
> feeling that all is not right with ivtv on my system. I'm hoping some
> of the IVTV pros can help set me down the right debug path. Any
> ideas?

Looks dubious to me. Do these warnings only happen during a capture? Do
they start immediately? How often do they appear? (i.e. at regular
intervals or randomly)

Regards,

Hans

_______________________________________________
ivtv-users mailing list
ivtv-users[at]ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

mcree at orcon

Oct 17, 2007, 1:45 PM

Post #3 of 4 (740 views)
Permalink

Re: MSP3400 I/O Errors [In reply to]

Right, regarding:

> On Sunday 23 September 2007 20:32:59 Philip Walston wrote:
>> msp3400 1-0040: I/O error #0 (read 0x10/0x200)
>> msp3400 1-0040: I/O error #1 (read 0x10/0x200)
>> msp3400 1-0040: I/O error #2 (read 0x10/0x200)
>> msp3400 1-0040: giving up, resetting chip. Sound will go off, sorry
>> folks

I have now seen these errors too. Just got them last night when I
upgraded the kernel to 2.6.23.1 (and of course the new ivtv driver
therein). Following the above errors I also saw the errors:

tda9887 0-0043: i2c i/o error: rc == -121 (should be 4)
tda9887 0-0043: i2c i/o error: rc == -121 (should be 4)
tuner 0-0061: i2c i/o error: rc == -121 (should be 4)

My ivtv installation, with a PVR-350 card use to work with kernel
2.6.22.3 and ivtv 1.0.1. Upgrading to kernel 2.6.23.1. and ivtv
1.0.3 has broken the installation, and I get the errors listed above
when I enter "cat /dev/video0 > somefile.mpg". The file somefile.mpg
is created but never gets beyond zero byte length.

I am running Debian testing (lenny) on a DEC/Compaq Alpha
architecture with a Hauppauge PVR-350.

Hans Verkuil wrote in reply to the original message:
> Looks dubious to me. Do these warnings only happen during a
> capture? Do
> they start immediately? How often do they appear? (i.e. at regular
> intervals or randomly)

For me, only on capture. I just use cat /dev/video0 for capturing.
Simple, but effective, until I upgraded the kernel...

There's a small possibility that I missed something in the kernel
config between 2.6.22.3 and 2.6.23.1. I did do a tidy up of the
config on upgrading to 2.6.23.1 to remove tons of modules that I've
never used to speed up compilation. A diff between the former and
latter configs didn't reveal any V4L modules that I might have
inadvertently not compiled.

For the pedants, here're the ivtv initialisation messages:

Oct 17 22:39:37 alpha kernel: ivtv: Start initialization, version 1.0.0
Oct 17 22:39:37 alpha kernel: ivtv0: Initializing card #0
Oct 17 22:39:37 alpha kernel: ivtv0: Autodetected Hauppauge card
(cx23415 based)
Oct 17 22:39:37 alpha kernel: ivtv0: Loaded v4l-cx2341x-enc.fw
firmware (376836 bytes)
Oct 17 22:39:37 alpha kernel: ivtv0: Loaded v4l-cx2341x-dec.fw
firmware (262144 bytes)
Oct 17 22:39:37 alpha kernel: ivtv0: Encoder revision: 0x02060039
Oct 17 22:39:37 alpha kernel: ivtv0: Decoder revision: 0x02020023
Oct 17 22:39:37 alpha kernel: tveeprom 0-0050: Hauppauge model 48139,
rev K257, serial# 2962352
Oct 17 22:39:37 alpha kernel: tveeprom 0-0050: tuner model is Philips
FM1216 ME MK3 (idx 57, type 38)
Oct 17 22:39:37 alpha kernel: tveeprom 0-0050: TV standards PAL(B/G)
PAL(I) SECAM(L/L') PAL(D/D1/K) (eeprom 0x74)
Oct 17 22:39:37 alpha kernel: tveeprom 0-0050: audio processor is
MSP4418 (idx 25)
Oct 17 22:39:37 alpha kernel: tveeprom 0-0050: decoder processor is
SAA7115 (idx 19)
Oct 17 22:39:37 alpha kernel: tveeprom 0-0050: has radio, has IR
receiver, has no IR transmitter
Oct 17 22:39:37 alpha kernel: ivtv0: Autodetected Hauppauge WinTV
PVR-350
Oct 17 22:39:37 alpha kernel: tuner 0-0043: chip found @ 0x86 (ivtv
i2c driver #0)
Oct 17 22:39:37 alpha kernel: tda9887 0-0043: tda988[5/6/7] found @
0x43 (tuner)
Oct 17 22:39:37 alpha kernel: tuner 0-0061: chip found @ 0xc2 (ivtv
i2c driver #0)
Oct 17 22:39:37 alpha kernel: saa7115 0-0021: saa7115 found
(1f7115d0e100000) @ 0x42 (ivtv i2c driver #0)
Oct 17 22:39:37 alpha kernel: saa7127 0-0044: saa7129 found @ 0x88
(ivtv i2c driver #0)
Oct 17 22:39:37 alpha kernel: msp3400 0-0040: MSP4418G-B3 found @
0x80 (ivtv i2c driver #0)
Oct 17 22:39:37 alpha kernel: msp3400 0-0040: MSP4418G-B3 supports
nicam and radio, mode is autodetect and autoselect
Oct 17 22:39:37 alpha kernel: tuner 0-0061: type set to 38 (Philips
PAL/SECAM multi (FM1216ME MK3))
Oct 17 22:39:37 alpha kernel: ivtv0: Registered device video0 for
encoder MPEG (4 MB)
Oct 17 22:39:37 alpha kernel: ivtv0: Registered device video32 for
encoder YUV (2 MB)
Oct 17 22:39:37 alpha kernel: ivtv0: Registered device vbi0 for
encoder VBI (1 MB)
Oct 17 22:39:37 alpha kernel: ivtv0: Registered device video24 for
encoder PCM audio (1 MB)
Oct 17 22:39:37 alpha kernel: ivtv0: Registered device radio0 for
encoder radio
Oct 17 22:39:37 alpha kernel: ivtv0: Registered device video16 for
decoder MPEG (1 MB)
Oct 17 22:39:37 alpha kernel: ivtv0: Registered device vbi8 for
decoder VBI (1 MB)
Oct 17 22:39:37 alpha kernel: ivtv0: Registered device vbi16 for
decoder VOUT
Oct 17 22:39:37 alpha kernel: ivtv0: Registered device video48 for
decoder YUV (1 MB)
Oct 17 22:39:37 alpha kernel: ivtv0: Loaded v4l-cx2341x-init.mpg
firmware (155648 bytes)
Oct 17 22:39:37 alpha kernel: ivtv0: Initialized card #0: Hauppauge
WinTV PVR-350
Oct 17 22:39:37 alpha kernel: ivtv: End initialization

Cheerio
Michael.

_______________________________________________
ivtv-users mailing list
ivtv-users[at]ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

mcree at orcon

Oct 22, 2007, 2:17 PM

Post #4 of 4 (723 views)
Permalink

Re: MSP3400 I/O Errors [In reply to]

On my investigation regarding:

On 18/10/2007, at 9:45 AM, Michael Cree wrote:
>> On Sunday 23 September 2007 20:32:59 Philip Walston wrote:
>>> msp3400 1-0040: I/O error #0 (read 0x10/0x200)
>>> msp3400 1-0040: I/O error #1 (read 0x10/0x200)
>>> msp3400 1-0040: I/O error #2 (read 0x10/0x200)
>>> msp3400 1-0040: giving up, resetting chip. Sound will go off, sorry
>>> folks
>
> I have now seen these errors too. Just got them last night when I
> upgraded the kernel to 2.6.23.1 (and of course the new ivtv driver
> therein). Following the above errors I also saw the errors:
>
> tda9887 0-0043: i2c i/o error: rc == -121 (should be 4)
> tda9887 0-0043: i2c i/o error: rc == -121 (should be 4)
> tuner 0-0061: i2c i/o error: rc == -121 (should be 4)

I have now verified that upgrading to latest v4l from the master v4l
development repository (as at thur 18 oct, commit 4ae65d0844cf)
resolves these issues.

So to summarise: On DEC/Compaq Alpha EV67 architecture, with PVR-350
card, running Debian testing, I found:

Ivtv from Kernel 2.6.22.3 runs fine.
Ivtv from Kernel 2.6.23.1 fails and leads to the errors listed above.

Installing latest v4l development repository on top of:

kernel 2.6.22.3 still runs fine.
kernel 2.6.23.1 now runs correctly. Above errors resolved.

It would therefore seem that there is some problem in the ivtv driver
included in kernel 2.6.23.1 that is exercised on my system. The
original poster observed these errors under debian kernel 2.6.20-7
with ivtv 0.10.5. Would I be right in thinking that ivtv 0.10.5
contains the same (or v. similar) ivtv driver as kernel 2.6.23.1?

Michael.

_______________________________________________
ivtv-users mailing list
ivtv-users[at]ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com