From: Mark Lord <kernel@teksavvy.com>
To: Andy Walls <awalls@radix.net>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
linux-media@vger.kernel.org, ivtv-devel@ivtvdriver.org
Subject: Re: cx18: Unable to find blank work order form to schedule incoming mailbox ...
Date: Tue, 02 Mar 2010 10:00:21 -0500 [thread overview]
Message-ID: <4B8D2805.4030808@teksavvy.com> (raw)
In-Reply-To: <1267533630.3123.17.camel@palomino.walls.org>
On 03/02/10 07:40, Andy Walls wrote:
..
>>> 3. The work handler kernel thread, cx18-0-in, got killed, if that's
>>> possible, or the processor it was running on got really bogged down.
>> ..
..
One thing from the /var/log/messages output:
12:55:59 duke kernel: IRQ 18/cx18-0: IRQF_DISABLED is not guaranteed on shared IRQs
Which is a result of the code doing this:
retval = request_irq(cx->pci_dev->irq, cx18_irq_handler,
IRQF_SHARED | IRQF_DISABLED,
cx->v4l2_dev.name, (void *)cx);
I'm not at the MythTV box right now, but it is likely that this IRQ
really is shared with other devices.
Does the driver *really* rely upon IRQF_DISABLED (to avoid races in the handler)?
If so, then this could be a good clue.
If not, then that IRQF_DISABLED should get nuked.
Cheers
next prev parent reply other threads:[~2010-03-02 15:00 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 16:07 cx18: Unable to find blank work order form to schedule incoming mailbox Mark Lord
2010-03-02 1:34 ` Andy Walls
2010-03-02 5:57 ` Mark Lord
2010-03-02 12:40 ` Andy Walls
2010-03-02 15:00 ` Mark Lord [this message]
2010-03-03 1:05 ` Andy Walls
2010-03-15 2:48 ` cx18: "missing audio" for analog recordings Mark Lord
2010-03-15 11:51 ` Andy Walls
2010-03-16 4:49 ` Mark Lord
2010-03-16 11:11 ` Andy Walls
2010-04-10 22:28 ` Mark Lord
2010-04-10 22:54 ` Andy Walls
2010-04-11 0:58 ` Andy Walls
2010-04-11 3:21 ` Mark Lord
2010-04-11 4:56 ` Andy Walls
2010-04-11 5:03 ` [ivtv-devel] " Andy Walls
2010-04-11 11:47 ` Andy Walls
2010-04-11 13:24 ` Mark Lord
2010-04-11 19:01 ` Andy Walls
2010-04-11 20:52 ` Mark Lord
2010-04-12 20:08 ` Mark Lord
2010-04-12 21:17 ` Andy Walls
2010-04-13 2:22 ` Mark Lord
2010-04-13 2:30 ` Mark Lord
2010-04-13 2:34 ` Mark Lord
2010-04-13 10:35 ` Andy Walls
2010-04-13 12:42 ` Mark Lord
2010-04-14 1:45 ` Andy Walls
2010-04-14 4:32 ` Mark Lord
2010-04-14 4:34 ` Mark Lord
2010-04-14 22:26 ` Mark Lord
2010-04-15 4:46 ` Andy Walls
2010-04-15 5:16 ` Mark Lord
2010-04-15 14:15 ` Mark Lord
2010-04-17 4:43 ` Andy Walls
2010-04-17 12:09 ` Mark Lord
2010-04-17 13:01 ` Mark Lord
2010-04-17 17:18 ` Andy Walls
2010-04-17 17:03 ` Andy Walls
2010-04-16 12:59 ` Andy Walls
2010-04-17 12:18 ` Mark Lord
2010-04-17 17:37 ` Andy Walls
2010-04-16 13:15 ` Andy Walls
2010-04-16 13:29 ` Andy Walls
2010-04-11 19:49 ` Darren Blaber
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=4B8D2805.4030808@teksavvy.com \
--to=kernel@teksavvy.com \
--cc=awalls@radix.net \
--cc=hverkuil@xs4all.nl \
--cc=ivtv-devel@ivtvdriver.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox