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: <20091014081309.GM9228@kernel.dk>
Date:	Wed, 14 Oct 2009 10:13:09 +0200
From:	Jens Axboe <jens.axboe@...cle.com>
To:	Alex Chiang <achiang@...com>
Cc:	Mark Lord <lkml@....ca>, Greg KH <greg@...ah.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	jbarnes@...tuousgeek.org, linux-pci@...r.kernel.org
Subject: Re: pci-express hotplug

On Tue, Oct 13 2009, Alex Chiang wrote:
> * Jens Axboe <jens.axboe@...cle.com>:
> > > > >> On Mon, Oct 12 2009, Greg KH wrote:
> > > > >>> Can you try the acpiphp driver instead?  That's usually the
> > > > >>> driver you want to use for "modern" systems (i.e. anything
> > > > >>> made in the past 5 years.)
> > > > >>
> > > > >> I should have mentioned that I tried that too. It doesn't
> > > > >> complain, but I don't see my cards anywhere afterwards. I'm
> > > > >> a hotplug newbie, do I need to do anything else?
> > > 
> > > Can you modprobe acpiphp with debug=1? And send the output?
> > 
> > acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
> > acpiphp_glue: found PCI-to-PCI bridge at PCI 0000:00:05.0
> > acpiphp_glue: found ACPI PCI Hotplug slot 1 at PCI 0000:08:00
> > acpiphp: Slot [1] registered
> > acpiphp_glue: found PCI-to-PCI bridge at PCI 0000:00:07.0
> > acpiphp_glue: found ACPI PCI Hotplug slot 2 at PCI 0000:0b:00
> > acpiphp: Slot [2] registered
> > acpiphp_glue: found PCI-to-PCI bridge at PCI 0000:80:07.0
> > acpiphp_glue: found ACPI PCI Hotplug slot 6 at PCI 0000:84:00
> > acpiphp: Slot [6] registered
> > acpiphp_glue: found PCI-to-PCI bridge at PCI 0000:80:09.0
> > acpiphp_glue: found ACPI PCI Hotplug slot 7 at PCI 0000:87:00
> > acpiphp: Slot [7] registered
> > acpiphp_glue: Bus 0000:87 has 1 slot
> > acpiphp_glue: Bus 0000:84 has 1 slot
> > acpiphp_glue: Bus 0000:0b has 1 slot
> > acpiphp_glue: Bus 0000:08 has 1 slot
> > acpiphp_glue: Total 4 slots
> 
> You mentioned in another mail that you echoed 1 into the various
> slots' power files.
> 
> Did you do that after modprobing acpiphp with debug=1?
> 
> If so, there should be debug output when you try and turn them
> on.

It produces:

acpiphp: enable_slot - physical_slot = 1
acpiphp_glue: acpiphp_enable_slot: Slot status is not ACPI_STA_ALL
acpiphp: enable_slot - physical_slot = 2
acpiphp_glue: acpiphp_enable_slot: Slot status is not ACPI_STA_ALL
acpiphp: enable_slot - physical_slot = 6
acpiphp_glue: acpiphp_enable_slot: Slot status is not ACPI_STA_ALL
acpiphp: enable_slot - physical_slot = 7
acpiphp_glue: acpiphp_enable_slot: Slot status is not ACPI_STA_ALL

I have a card in one of the slots only this time.

> Also, quick dummy check, you are trying to power on populated
> slots, right? :)

Yes :-)

> Can you send the output of lspci -vv? And I like the output of
> lspci -vt as well... Both before and after loading acpiphp
> please.

Send privately.

-- 
Jens Axboe

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ