From: Chuck Ebbert <cebbert@redhat.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: "No handler for vector" patches don't work on some systems
Date: Fri, 09 Mar 2007 12:24:40 -0500 [thread overview]
Message-ID: <45F19858.3070604@redhat.com> (raw)
In-Reply-To: <m1slce4b8r.fsf@ebiederm.dsl.xmission.com>
Eric W. Biederman wrote:
> Chuck Ebbert <cebbert@redhat.com> writes:
>>
>> So far I've tried the simple "survive having no handler
>> for a vector" patch and the preliminary 3-patch series
>> that was in -mm for a while, and neither work on the
>> Dell PowerEdge 29xx and 19xx systems. These servers
>> have the Intel 5000X chipset with the 6700PXH PCI Hub
>> with dual independent PCI-X busses, each with its own
>> I/OxAPIC with 24 interrupts. The fixes do work on
>> "simple" systems but not on these high-end ones.
>
>
> I would very much like to know if what I merged linus's tree helps.
> It is a little more conservative, than my earlier patches. I need
> a way to reproduce this or to work closely with someone who is, because
> this sounds like it has a different cause and I need to start with
> that assumption.
Was that merged or is it still in -mm? The last thing I see in
arch/x86_64/irq.c is:
[PATCH] x86-64: survive having no irq mapping for a vector
And we tried that one.
next prev parent reply other threads:[~2007-03-09 17:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 16:18 "No handler for vector" patches don't work on some systems Chuck Ebbert
2007-03-09 16:45 ` Eric W. Biederman
2007-03-09 17:24 ` Chuck Ebbert [this message]
2007-03-09 17:45 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2007-03-09 16:16 Chuck Ebbert
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=45F19858.3070604@redhat.com \
--to=cebbert@redhat.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@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.