public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Ryan Hope <rmh3093@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: PCIEHP breakage in 2.6.26-rc1,2.6.26-rc2,2.6.26-rc3
Date: Mon, 19 May 2008 12:12:26 -0600	[thread overview]
Message-ID: <20080519181226.GD2638@parisc-linux.org> (raw)
In-Reply-To: <48f7fe350805191047rc5f6f01t2d786380a7dbe199@mail.gmail.com>

On Mon, May 19, 2008 at 01:47:35PM -0400, Ryan Hope wrote:
> My kernel, and numerous other people have reported to me that their
> kernels hang at boot if CONFIG_HOTPLUG_PCI_PCIE=Y
> 
> If this is set to M or N. The kernel boots fine.
> 
> When I build pciehp as a module, and try to modprobe it after the
> kernel boots, modprobe never returns. I can cancel the operation with
> ctrl+c and then when i run dmesg there are messages that look like the
> module did get inserted.
> Further more, lsmod shows that the module was loaded.
> 
> Seems like there is a small bug in here somehwhere.

You're not giving us much to go on here ...

 - Does your hardware have hotpluggable PCIe slots?
 - What was the last version of the kernel that did work?
 - What messages do you see in dmesg?
 - Can you run 'ps' and get the wchan for the modprobe process to see
   where it's hanging?

-- 
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

      reply	other threads:[~2008-05-19 18:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-19 17:47 PCIEHP breakage in 2.6.26-rc1,2.6.26-rc2,2.6.26-rc3 Ryan Hope
2008-05-19 18:12 ` Matthew Wilcox [this message]

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=20080519181226.GD2638@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=rmh3093@gmail.com \
    /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