From: "Timothy D. Lenz" <tlenz@vorgon.com>
To: linux-media@vger.kernel.org
Subject: Re: tuner XC5000 race condition??
Date: Mon, 26 Apr 2010 12:50:38 -0700 [thread overview]
Message-ID: <4BD5EE8E.5070603@vorgon.com> (raw)
In-Reply-To: <4BD5E1FF.8030704@vorgon.com>
On 4/26/2010 11:57 AM, Timothy D. Lenz wrote:
>
>
> On 4/25/2010 6:00 PM, Andy Walls wrote:
>> On Mon, 2010-04-26 at 10:44 +1000, Dmitri Belimov wrote:
>>> Hi
>>>
>>> Sometimes tuner XC5000 crashed on boot. This PC is dual-core.
>>> It can be race condition or multi-core depend problem.
>>>
>>> Add mutex for solve this problem is correct?
>>
>> Dmitri,
>>
>> This problem may be related to the firmware loading race described here:
>>
>> https://bugzilla.kernel.org/show_bug.cgi?id=15294
>>
>> I still have not fixed that bug yet.
>>
>> But for your problem, perhaps you can try:
>>
>> echo 120> /sys/class/firmware/timeout
>>
>> as root in the initialization scripts to lengthen the firmware loading
>> timeout to 120 seconds. Maybe that will work around the crash.
>>
>> I'll try and look at what is going on in your crash dumps, if I have
>> time.
>>
>> Regards,
>> Andy
>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-media" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
> Could this problem also be related to the tuner problem I've been having
> with one tuner stop tuning? Because it is on a Athlon64 x2 (dual core).
> I put up logs with debug on. First set was I think about 24hrs with no
> crash, then the file ext new and new2 where each copied out after the
> tuner was found crashed.
>
> http://24.255.17.209:2400/vdr/logs/
>
> The computer hosting these logs, I hope to take down for a short while,
> maybe a few hours to switch it over to raid boot. So if you can't
> connect, try again later.
Keep forgetting, reply on this list doesn't go to the list unless you
reply all or manually change the address:(
Could this problem also be related to the tuner problem I've been having
with one tuner stop tuning? Because it is on a Athlon64 x2 (dual core).
I put up logs with debug on. First set was I think about 24hrs with no
crash, then the file ext new and new2 where each copied out after the
tuner was found crashed.
prev parent reply other threads:[~2010-04-26 19:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 0:44 tuner XC5000 race condition?? Dmitri Belimov
2010-04-26 1:00 ` Andy Walls
[not found] ` <4BD5E1FF.8030704@vorgon.com>
2010-04-26 19:50 ` Timothy D. Lenz [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=4BD5EE8E.5070603@vorgon.com \
--to=tlenz@vorgon.com \
--cc=linux-media@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.