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:12:51 -0400 [thread overview]
Message-ID: <47D80F13.7040304@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.
>
> I have bisected the hang down to this commit:
>
> 0a3c33d77ff7ad5b988997536a8f09c49e35ad20 is first bad commit
> commit 0a3c33d77ff7ad5b988997536a8f09c49e35ad20
> Author: Mark Lord <lkml@rtr.ca>
> Date: Wed Nov 28 15:11:28 2007 -0800
>
> PCIE: fix PCIe Hotplug so that it works with ExpressCard slots on Dell notebooks (and others?) in conjunction with modparam of pciehp_force=1.
..
In this case, the bisection is probably not perfect,
because that original patch had a couple of bugs that
were fixed by a subsequent follow-up patch.
It is all rather fuzzy right now, because this work was all completed
at the merge window for the *previous* kernel, but has now sat bit-rotting
for nearly 6 months since I last looked at it.
That said, I'm building the latest 2.6.25-rc* to retest with here,
and hopefully we can work this out without much more fuss.
Cheers
--
Mark Lord
Real-Time Remedies Inc.
mlord@pobox.com
next prev parent reply other threads:[~2008-03-12 17:13 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 [this message]
2008-03-12 17:34 ` Mark Lord
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=47D80F13.7040304@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox