From: Mark Lord <mlord@pobox.com>
To: Alex Chiang <achiang@hp.com>,
mlord@pobox.com, kristen.c.accardi@intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [regression] pciehp hang on hp ia64 rx6600
Date: Wed, 12 Mar 2008 13:34:38 -0400 [thread overview]
Message-ID: <47D8142E.6060305@pobox.com> (raw)
In-Reply-To: <20080312064755.GA31493@ldl.fc.hp.com>
Alex Chiang wrote:
> Hi Mark, Kristin,
>
> On my hp ia64 rx6600, 'modprobe pciehp' causes lockups and a
> system hang on 2.6.25-rc4. My system often hangs when only pciehp
> is loaded and my console is sitting idle, but I can accelerate
> the hang 100% of the time by immediately doing a 'modprobe
> acpiphp' right afterwards.
..
Does this patch fix things for you?
* * *
Invoke pciehp_enable_slot() at startup only when pciehp_force=1.
Some HP equipment apparently cannot cope with it otherwise.
This restores the (previously working) 2.6.24 behaviour here,
while allowing machines that need a kick to use pciehp_force=1.
Signed-off-by: Mark Lord <mlord@pobox.com>
---
--- linux-2.6.25-rc5-git2/drivers/pci/hotplug/pciehp_core.c 2008-03-12 13:21:46.000000000 -0400
+++ linux/drivers/pci/hotplug/pciehp_core.c 2008-03-12 13:23:54.000000000 -0400
@@ -467,7 +467,7 @@
t_slot = pciehp_find_slot(ctrl, ctrl->slot_device_offset);
t_slot->hpc_ops->get_adapter_status(t_slot, &value); /* Check if slot is occupied */
- if (value) {
+ if (value && pciehp_force) {
rc = pciehp_enable_slot(t_slot);
if (rc) /* -ENODEV: shouldn't happen, but deal with it */
value = 0;
next prev parent reply other threads:[~2008-03-12 17:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 6:47 [regression] pciehp hang on hp ia64 rx6600 Alex Chiang
2008-03-12 17:12 ` Mark Lord
2008-03-12 17:34 ` Mark Lord [this message]
2008-03-17 19:53 ` Alex Chiang
2008-03-17 20:04 ` [PATCH] pciehp dont enable slot unless forced Mark Lord
2008-03-17 21:13 ` Kristen Carlson Accardi
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=47D8142E.6060305@pobox.com \
--to=mlord@pobox.com \
--cc=achiang@hp.com \
--cc=kristen.c.accardi@intel.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.