Hi, Sorry for the cross post, but this seems more relevant in devel.
I haven't tried the 2.6.19 kernel, but what I did try is booting with the "nosmp" and "noapic" parameters, and this seems to have fixed the problem. So it appears that the problem was caused by SMP. Is this a known issue? If so, is it a hardware limitiation of the PVR cards, or an ivtv bug? Should I report this? Thanks. On 12/18/06, Hans Verkuil <[EMAIL PROTECTED]> wrote: > On Monday 18 December 2006 18:37, Edward Rosinzonsky wrote: > > Some more info: > > > > I'm using kernel 2.6.18-1.2849.fc6 (SMP, x86_64) on a dual-core > > opteron, with latest ivtv and mythtv from atrpms. > > Most likely cause is that you have a CPU frequency changer daemon > running. The PVR cards don't like that. The messages you see are due to > a crashed firmware. > > If that doesn't help, then you can try to upgrade to 2.6.19 and use the > ivtv from the subversion trunk repository. I'd be interested to hear if > you have the same problems with that version. > > Hans > > > > > On 12/12/06, Edward Rosinzonsky <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > > > I have ivtv 0.8.2 on FC6 x64 with a PVR-500, and every other time I > > > "Watch TV" in myth, mythbackend hangs, and I get the following > > > messages in dmesg: > > > > > > ivtv0 warning: 1000 ms time out waiting for firmware > > > ivtv0 warning: Failed api call 0x00000082 with result 0xfffffff0 > > > ivtv0 warning: ENC: Failed stopping capture -16 > > > ivtv0 warning: No Free Mailbox for cmd 0x000000db after 100 tries! > > > ivtv0 warning: Mailbox[0] 0x000000dc flags 0x00000003 > > > ivtv0 warning: Mailbox[1] 0x000000d9 flags 0x00000003 > > > ivtv0 warning: Mailbox[2] 0x000000c9 flags 0x00000003 > > > ivtv0 warning: Firmware UNRESPONSIVE when trying cmd 0x000000db!!! > > > ivtv0 warning: No Free Mailbox for cmd 0x000000dc after 100 tries! > > > ivtv0 warning: Mailbox[0] 0x000000dc flags 0x00000003 > > > ivtv0 warning: Mailbox[1] 0x000000dc flags 0x00000003 > > > ivtv0 warning: Mailbox[2] 0x000000dc flags 0x00000003 > > > ivtv0 warning: Firmware UNRESPONSIVE when trying cmd 0x000000dc!!! > > > ivtv0 warning: 1000 ms time out waiting for firmware > > > ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0 > > > ivtv0 warning: 1000 ms time out waiting for firmware > > > ivtv0 warning: Failed api call 0x000000c8 with result 0xfffffff0 > > > ivtv0 warning: init error 21. Code -16 > > > ivtv0 warning: 1000 ms time out waiting for firmware > > > ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0 > > > ivtv0 warning: 1000 ms time out waiting for firmware > > > ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0 > > > ivtv0 warning: 1000 ms time out waiting for firmware > > > ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0 > > > ivtv0 warning: 1000 ms time out waiting for firmware > > > ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0 > > > ivtv0 warning: 1000 ms time out waiting for firmware > > > ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0 > > > ivtv0 warning: 1000 ms time out waiting for firmware > > > ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0 > > > ivtv0 warning: 1000 ms time out waiting for firmware > > > ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0 > > > ivtv0 warning: 1000 ms time out waiting for firmware > > > ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0 > > > ivtv0 warning: 1000 ms time out waiting for firmware > > > ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0 > > > ivtv0 warning: 1000 ms time out waiting for firmware > > > ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0 > > > ivtv0 warning: 1000 ms time out waiting for firmware > > > ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0 > > > ivtv0 warning: 1000 ms time out waiting for firmware > > > ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0 > > > ivtv0 warning: 1000 ms time out waiting for firmware > > > ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0 > > > ivtv0 warning: 1000 ms time out waiting for firmware > > > ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0 > > > ivtv0 warning: 1000 ms time out waiting for firmware > > > ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0 > > > ivtv0 warning: 1000 ms time out waiting for firmware > > > ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0 > > > ivtv0 warning: 1000 ms time out waiting for firmware > > > ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0 > > > ivtv0 warning: 1000 ms time out waiting for firmware > > > ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0 > > > ivtv0 warning: 1000 ms time out waiting for firmware > > > ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0 > > > ivtv0 warning: 1000 ms time out waiting for firmware > > > ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0 > > > ivtv0 warning: 1000 ms time out waiting for firmware > > > ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0 > > > > > > > > > The exact same problem was discussed in August in this thread: > > > http://www.gossamer-threads.com/lists/ivtv/users/31538 > > > > > > The only workaround back then was to downgrade to 0.6.1. Is this > > > still the case? Thanks. > > > > _______________________________________________ > > ivtv-users mailing list > > [email protected] > > http://ivtvdriver.org/mailman/listinfo/ivtv-users > > _______________________________________________ > ivtv-users mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-users > _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
