From: kylin <fierykylin@gmail.com>
To: rajesh.shah-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-newbie-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-hotplug-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
dkumar-QByN7dn/BetQWC9lL0RKGQC/G2K4zDHf@public.gmane.org
Subject: Re: Re: Problem while inserting pciehp (PCI Express Hot-plug) driver
Date: Sat, 30 Jul 2005 16:20:30 +0000 [thread overview]
Message-ID: <87ab37ab0507300920570b0ea6@mail.gmail.com> (raw)
In-Reply-To: <b115cb5f0507241949da02aa7@mail.gmail.com>
n the latest update of the Intel's E7520 MCH,the very NOTFIX entry
caught my eye:
//////////////////////
PCI Express Hot-Plug MSI interrupt issue
////////////////////
Problem:
During a link down state, the MCH will not send MSI interrupts to the
front side bus. In general
MSI messages need not be delivered when the link is down, but in the
event that MSI interrupt routing is used on Hot-Plug events, the
processor will wait indefinitely for this interrupt. Waiting for
command complete interrupts is a normal part of the steps in the
orderly removal process, and link down will occur at the point that
power is removed from the slot. Subsequent accesses to the slot
control register to update indicators and power control will not
generate the expected MSI interrupts from the MCH until slot power is
restored, and the link is back up.
Implication:
Hot-Plug software written to wait for command complete interrupts will
hang in MSI interrupt mode.
Workaround:
Run in either of the other two interrupt modes (the "legacy" method
using the MCHGPE# to signal
hot-plug interrupts to the ICH or "native" interrupt mode using PCI
interrupts (INTA#)).
Alternatively in MSI mode, software may poll for command complete
rather than wait for MSI, or implement the command complete timeout to
continue to the next slot control update rather than repeat the
current slot control update
I wonder if i can workaround the MSI using the polling way on the
server geared by E7520 and the firmware with no OSC implemented
--
we who r about to die,salute u!
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id\x16492&opÌk
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2005-07-30 16:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050725021747.67869.qmail@web34405.mail.mud.yahoo.com>
[not found] ` <20050725021747.67869.qmail-6mNr3ekj/EivuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2005-07-25 2:49 ` Re: Problem while inserting pciehp (PCI Express Hot-plug) driver Rajat Jain
[not found] ` <b115cb5f0507241949da02aa7-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2005-07-27 18:29 ` Kristen Accardi
2005-07-28 10:45 ` Rajat Jain
2005-07-28 17:00 ` Kristen Accardi
[not found] ` <b115cb5f05072803451836055c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2005-07-29 0:52 ` Rajesh Shah
2005-07-29 10:23 ` Rajat Jain
2005-07-30 16:20 ` kylin [this message]
[not found] ` <87ab37ab0507300920570b0ea6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2005-08-03 17:49 ` Rajesh Shah
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=87ab37ab0507300920570b0ea6@mail.gmail.com \
--to=fierykylin@gmail.com \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=dkumar-QByN7dn/BetQWC9lL0RKGQC/G2K4zDHf@public.gmane.org \
--cc=linux-hotplug-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-newbie-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rajesh.shah-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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;
as well as URLs for NNTP newsgroup(s).