From: Li Zefan <lizf@cn.fujitsu.com>
To: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: Ingo Molnar <mingo@elte.hu>, Yinghai Lu <yinghai@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] tip tree - No irq handler for vector (irq -1)
Date: Fri, 29 Jan 2010 09:14:22 +0800 [thread overview]
Message-ID: <4B62366E.6040207@cn.fujitsu.com> (raw)
In-Reply-To: <1264709113.2849.14.camel@sbs-t61.sc.intel.com>
Suresh Siddha wrote:
> Zefan,
>
> I have posted a fix for this.
>
> http://marc.info/?l=linux-kernel&m=126420641021426&w=2
>
> Can you please check if this indeed fixes your issue?
>
Yes, it works. Thanks!
But I still saw this:
do_IRQ: 1.48 No irq handler for vector (irq -1)
next prev parent reply other threads:[~2010-01-29 1:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 7:59 [BUG] tip tree - No irq handler for vector (irq -1) Li Zefan
2010-01-28 20:05 ` Suresh Siddha
2010-01-29 1:14 ` Li Zefan [this message]
2010-01-29 1:18 ` Suresh Siddha
2010-01-29 1:24 ` Li Zefan
2010-01-29 3:14 ` Jin Dongming
2010-01-29 6:51 ` Suresh Siddha
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=4B62366E.6040207@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=suresh.b.siddha@intel.com \
--cc=yinghai@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