public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Cc: Yinghai Lu <yinghai@kernel.org>,
	linux-pci@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	ACPI Devel Mailing List <linux-acpi@vger.kernel.org>,
	Len Brown <lenb@kernel.org>,
	Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: Hot plug issue on 2.6.38
Date: Tue, 22 Mar 2011 01:07:19 +0100	[thread overview]
Message-ID: <201103220107.19893.rjw@sisk.pl> (raw)
In-Reply-To: <20110321235403.GA4092@xanatos>

On Tuesday, March 22, 2011, Sarah Sharp wrote:
> On Mon, Mar 21, 2011 at 11:51:12PM +0100, Rafael J. Wysocki wrote:
> > On Monday, March 21, 2011, Sarah Sharp wrote:
> > > I compiled 2.6.38 with CONFIG_PCI_MMCONFIG=y, and I'm no longer getting
> > > "irq nobody cared" messages.  However, PCI express hot plug seems to
> > > just not work for the xHCI PCI device.  Nothing appears in dmesg when I
> > > plug in the Express Card, and the device doesn't appear in lspci.
> > > However, I can get the card to show up if I run
> > > 
> > > 	echo 1 > /sys/bus/pci/rescan
> > > 
> > > PCI hot-remove doesn't seem to work either.  The xHCI driver notices the
> > > device got removed when the debugging polling loop runs, but the
> > > driver's PCI remove functions are never called.  A rescan of the bus
> > > doesn't help, and the device still shows up in lspci (although all the
> > > registers are read as 0xffff). dmesg and lspci after the device has been
> > > removed is attached.
> > > 
> > > I've tried turning on all the PCI config options that look relavant; my
> > > .config is attached.  I've turned on PCI debug too.  The only thing that
> > > looks PCI related that I don't have turned on is ACPI_PCI_SLOT.  Do I
> > > need that?
> > > 
> > > I'm not sure how to debug this hot plug issue further.
> > 
> > Well, we still don't seem to call the _OSC on this machine.  At least your
> > dmesg output doesn't indicate so.
> > 
> > Do you have the patch from:
> > 
> > https://patchwork.kernel.org/patch/604371/
> > 
> > applied?
> 
> No, it was just 2.6.38.  When I applied that patch, PCI hot plug worked!

Cool. :-)

> dmesg is attached.  Can the patch get queued for 2.6.38 stable, or is it
> just a hack?

It's not a hack and it's goint to -stable, but it hasn't been merged by
Linus yet (AFAICS).

Thanks,
Rafael

      reply	other threads:[~2011-03-22  0:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-05 21:54 [RFT][PATCH] PCI / ACPI: Do not require MSI support for PCIe native features Rafael J. Wysocki
2011-03-14 18:26 ` Sarah Sharp
2011-03-14 20:02   ` Rafael J. Wysocki
2011-03-14 20:19     ` Sarah Sharp
2011-03-14 20:37       ` Rafael J. Wysocki
2011-03-14 23:47         ` Sarah Sharp
2011-03-15  0:00           ` Rafael J. Wysocki
2011-03-15 19:05             ` Sarah Sharp
2011-03-17  0:19               ` Rafael J. Wysocki
2011-03-17  5:23                 ` Yinghai Lu
2011-03-17 21:22                   ` Rafael J. Wysocki
2011-03-17 21:56                     ` Sarah Sharp
2011-03-21 22:28                       ` Hot plug issue on 2.6.38 Sarah Sharp
2011-03-21 22:34                         ` Matthew Garrett
2011-03-21 23:31                           ` Sarah Sharp
2011-03-21 23:41                             ` Rafael J. Wysocki
2011-03-21 22:51                         ` Rafael J. Wysocki
2011-03-21 23:54                           ` Sarah Sharp
2011-03-22  0:07                             ` Rafael J. Wysocki [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=201103220107.19893.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=jbarnes@virtuousgeek.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=sarah.a.sharp@linux.intel.com \
    --cc=yinghai@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