From: Fengguang Wu <fengguang.wu@intel.com>
To: Jarod Wilson <jarod@redhat.com>
Cc: Josh Boyer <jwboyer@redhat.com>, Jarod Wilson <jarod@redhat.com>,
Mauro Carvalho Chehab <mchehab@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: genirq: Flags mismatch irq 4. 00000000 (serial) vs. 00000000 (lirc_sir)
Date: Tue, 3 Jul 2012 12:54:48 +0800 [thread overview]
Message-ID: <20120703045448.GA8639@localhost> (raw)
Hi Jarod,
Since commit 4b71ca6 ("[media] lirc_sir: make device registration work"),
I see warnings "IRQ handler type mismatch for IRQ 4" in the
samsung/v4l-fimc-next branch.
The warning is made more obvious by Thomas' commit in linux-next
f5d89470f9 ("genirq: Be more informative on irq type mismatch"):
[ 96.064731] genirq: Flags mismatch irq 4. 00000000 (serial) vs. 00000000 (lirc_sir)
[ 96.067097] Pid: 3941, comm: rc.local Not tainted 3.5.0-rc5+ #42
[ 96.068013] Call Trace:
[ 96.068013] [<ffffffff8110825c>] __setup_irq+0x36f/0x3e6
[ 96.068013] [<ffffffff8110719d>] ? kzalloc.constprop.34+0x1a/0x1c
[ 96.068013] [<ffffffff8117a022>] ? kmem_cache_alloc_trace+0x110/0x122
[ 96.068013] [<ffffffff811083a2>] request_threaded_irq+0xcf/0x10a
[ 96.068013] [<ffffffff817e1ecd>] ? serial8250_backup_timeout+0x112/0x112
[ 96.068013] [<ffffffff817e338a>] serial8250_startup+0x4f3/0x6b7
[ 96.068013] [<ffffffff817deea0>] uart_startup.part.6+0x86/0x178
[ 96.068013] [<ffffffff817dfa1c>] uart_open+0xf2/0x13e
[ 96.068013] [<ffffffff817c038c>] ? check_tty_count+0x4b/0xa8
[ 96.068013] [<ffffffff817c2369>] tty_open+0x306/0x492
[ 96.068013] [<ffffffff81187a5b>] chrdev_open+0x11f/0x14a
[ 96.068013] [<ffffffff810c3b14>] ? local_clock+0x19/0x52
[ 96.068013] [<ffffffff8118793c>] ? cdev_put+0x26/0x26
[ 96.068013] [<ffffffff81182b9b>] do_dentry_open+0x1dd/0x28a
[ 96.068013] [<ffffffff81182cb3>] finish_open+0x6b/0x81
[ 96.068013] [<ffffffff8119095a>] do_last+0x89d/0xa4b
[ 96.068013] [<ffffffff8118e428>] ? inode_permission+0xac/0xe0
[ 96.068013] [<ffffffff811950bc>] ? spin_lock+0x9/0xb
[ 96.068013] [<ffffffff8118e521>] ? link_path_walk+0xc5/0x49e
[ 96.068013] [<ffffffff81190bc7>] path_openat+0xbf/0x33b
[ 96.068013] [<ffffffff810de3a0>] ? trace_hardirqs_off_caller+0x1f/0x9e
[ 96.068013] [<ffffffff810c3b36>] ? local_clock+0x3b/0x52
[ 96.068013] [<ffffffff81191050>] do_filp_open+0x38/0x86
[ 96.068013] [<ffffffff82e9ff8a>] ? _raw_spin_unlock+0x28/0x3b
[ 96.068013] [<ffffffff8119b5df>] ? alloc_fd+0xe5/0xf7
[ 96.068013] [<ffffffff811837bd>] do_sys_open+0x6e/0xfb
[ 96.068013] [<ffffffff8118386b>] sys_open+0x21/0x23
[ 96.068013] [<ffffffff82ea6d29>] system_call_fastpath+0x16/0x1b
Thanks,
Fengguang
reply other threads:[~2012-07-03 4:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120703045448.GA8639@localhost \
--to=fengguang.wu@intel.com \
--cc=jarod@redhat.com \
--cc=jwboyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=tglx@linutronix.de \
/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.