linux-kernel - Re: Hot plug issue on 2.6.38

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110321235403.GA4092@xanatos>
Date:	Mon, 21 Mar 2011 16:54:14 -0700
From:	Sarah Sharp <sarah.a.sharp@...ux.intel.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Yinghai Lu <yinghai@...nel.org>, linux-pci@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	ACPI Devel Mailing List <linux-acpi@...r.kernel.org>,
	Len Brown <lenb@...nel.org>,
	Matthew Garrett <mjg59@...f.ucam.org>
Subject: Re: Hot plug issue on 2.6.38

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!
dmesg is attached.  Can the patch get queued for 2.6.38 stable, or is it
just a hack?

Sarah Sharp

View attachment "dmesg.txt" of type "text/plain" (125697 bytes)