From: Fengguang Wu <fengguang.wu@intel.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jet Chen <jet.chen@intel.com>, Su Tao <tao.su@intel.com>,
Yuanhan Liu <yuanhan.liu@intel.com>, LKP <lkp@01.org>,
linux-kernel@vger.kernel.org
Subject: Re: [dummy-irq] genirq: Flags mismatch irq 0. 00000080 (dummy_irq) vs. 00015a20 (timer)
Date: Mon, 8 Sep 2014 17:22:28 +0800 [thread overview]
Message-ID: <20140908092228.GA24801@localhost> (raw)
In-Reply-To: <alpine.LNX.2.00.1409081114290.5523@pobox.suse.cz>
On Mon, Sep 08, 2014 at 11:15:37AM +0200, Jiri Kosina wrote:
> On Mon, 8 Sep 2014, Fengguang Wu wrote:
>
> > This patch is found to trigger a call trace dump during kernel boot.
> > Can it be possibly fixed? Thanks!
>
> Hi Fengguang,
>
> from the dmesg it's obvious that dummy-irq is requesting IRQ#0 by default.
> This has been fixed back in 2013 via commit a7b594b490. Are you sure you
> have that commit applied?
Ah yes! Sorry I looked at the wrong line of the table.. it becomes
obvious when listing the dummy_irq line alone: it no longer shows up
in next-20140905.
+------------------------------------------------------+------------+------------+---------------+
| | 4c6e22b8a9 | 54f69b92f0 | next-20140905 |
+------------------------------------------------------+------------+------------+---------------+
| genirq:Flags_mismatch_irq.(dummy_irq)vs.(timer) | 0 | 20 | |
prev parent reply other threads:[~2014-09-08 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-08 9:12 [dummy-irq] genirq: Flags mismatch irq 0. 00000080 (dummy_irq) vs. 00015a20 (timer) Fengguang Wu
2014-09-08 9:15 ` Jiri Kosina
2014-09-08 9:22 ` Fengguang Wu [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=20140908092228.GA24801@localhost \
--to=fengguang.wu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jet.chen@intel.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=tao.su@intel.com \
--cc=yuanhan.liu@intel.com \
/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