From: Frederic CAND <frederic.cand@anevia.com>
To: Linux DVB Mailing List <linux-dvb@linuxtv.org>
Subject: Re: [linux-dvb] cx88-blackbird mailbox timeout
Date: Wed, 29 Oct 2008 15:36:09 +0100 [thread overview]
Message-ID: <490874D9.6080708@anevia.com> (raw)
In-Reply-To: <4906E9CA.90003@anevia.com>
Frederic CAND a écrit :
> Dear all,
> I'm using one of the latest snapshots with my hauppauge hvr1300. I'm
> encoutering an issue, where randomly the mpeg ps device does not contain
> any sound track at all. I insist on the random side of the thing. If I
> completly power off my computer, no card can be affected by this bug, or
> any other card can be. But when a card is affected, it is until the
> computer is powered off. Unloading / reloading the modules won't fix.
>
> Other thing, on closing an mpeg device affected by this bug, the dmesg
> will contain :
>
> cx88[2]/2-bb: ERROR: API Mailbox timeout
>
> then, opening the device again will show this message :
> [62153.237112] cx88[2]/2-bb: ERROR: Mailbox appears to be in use (7)
> [62155.868701] cx88[2]/2-bb: Firmware upload successful.
> [62155.872299] cx88[2]/2-bb: Firmware version is 0x02060039
>
> Any idea ?
>
So if anyone is interested, the cause of this issue is the following "fix" :
http://linuxtv.org/hg/v4l-dvb/rev/93e265de2a56
when reverse applying it, I got the sound track in all my mpeg devices,
and then "api mailbox timeout" message never appeared afterwards.
I can prepare a patch if you want. Who should I send it to ?
--
CAND Frederic
Product Manager
ANEVIA
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
prev parent reply other threads:[~2008-10-29 14:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 10:30 [linux-dvb] cx88-blackbird mailbox timeout Frederic CAND
2008-10-29 14:36 ` Frederic CAND [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=490874D9.6080708@anevia.com \
--to=frederic.cand@anevia.com \
--cc=linux-dvb@linuxtv.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox