From: Jens Axboe <jens.axboe@oracle.com>
To: Alex Chiang <achiang@hp.com>
Cc: Mark Lord <lkml@rtr.ca>, Greg KH <greg@kroah.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
jbarnes@virtuousgeek.org, linux-pci@vger.kernel.org
Subject: Re: pci-express hotplug
Date: Tue, 27 Oct 2009 09:34:19 +0100 [thread overview]
Message-ID: <20091027083419.GU10727@kernel.dk> (raw)
In-Reply-To: <20091027082635.GS10727@kernel.dk>
On Tue, Oct 27 2009, Jens Axboe wrote:
> On Mon, Oct 26 2009, Alex Chiang wrote:
> > * Jens Axboe <jens.axboe@oracle.com>:
> > > > > 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
> > > >
> > > > Hm, so for some reason, firmware on your machine is telling us
> > > > that it doesn't think cards are present and/or enabled.
> > > >
> > > > Unfortunately, I don't know why your firmware would be saying
> > > > that. We could add some more debug printks to see what firmware
> > > > thinks about your system... Or we could just wait and see what
> > > > happens after you get your hardware replaced.
> >
> > Let's try and find out why firmware is telling us that we didn't
> > get ACPI_STA_ALL.
> >
> > Can you please apply this debug patch and send the output? Again,
> > please modprobe with debug=1.
>
> acpiphp: enable_slot - physical_slot = 1
> power_on_slot
> no _PS0
> no _PS0
> no _PS0
> no _PS0
> no _PS0
> no _PS0
> no _PS0
> no _PS0
> get_slot_status
> reading config space dvid 0xffffffff
> reading config space dvid 0xffffffff
> reading config space dvid 0xffffffff
> reading config space dvid 0xffffffff
> reading config space dvid 0xffffffff
> reading config space dvid 0xffffffff
> reading config space dvid 0xffffffff
> reading config space dvid 0xffffffff
> acpiphp_glue: acpiphp_enable_slot: Slot status is not ACPI_STA_ALL
Since this is a new board and BIOS, below is the info from loading
acpiphp with debug enabled and acpi debug enabled.
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
get_slot_status
get_slot_status
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
get_slot_status
get_slot_status
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
get_slot_status
get_slot_status
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
get_slot_status
get_slot_status
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
acpiphp: Slot [1] unregistered
acpiphp: release_slot - physical_slot = 1
acpiphp: Slot [2] unregistered
acpiphp: release_slot - physical_slot = 2
acpiphp: Slot [6] unregistered
acpiphp: release_slot - physical_slot = 6
acpiphp: Slot [7] unregistered
acpiphp: release_slot - physical_slot = 7
--
Jens Axboe
next prev parent reply other threads:[~2009-10-27 8:34 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 12:06 pci-express hotplug Jens Axboe
2009-10-12 14:52 ` Greg KH
2009-10-12 14:57 ` Jens Axboe
2009-10-12 15:00 ` Mark Lord
2009-10-12 15:06 ` Jens Axboe
2009-10-12 21:48 ` Alex Chiang
2009-10-13 8:29 ` Jens Axboe
2009-10-13 17:27 ` Alex Chiang
2009-10-14 8:13 ` Jens Axboe
2009-10-20 19:07 ` Alex Chiang
2009-10-26 10:54 ` Jens Axboe
2009-10-27 2:48 ` Alex Chiang
2009-10-27 8:26 ` Jens Axboe
2009-10-27 8:34 ` Jens Axboe [this message]
2009-10-27 15:15 ` Alex Chiang
2009-10-28 9:18 ` Jens Axboe
2009-10-28 19:55 ` Alex Chiang
2009-10-29 18:55 ` Jens Axboe
2009-10-28 20:46 ` Alex Chiang
2009-10-28 21:39 ` Alex Chiang
2009-10-29 8:57 ` Jens Axboe
2009-10-27 6:31 ` Kenji Kaneshige
2009-10-27 8:27 ` Jens Axboe
2009-10-27 8:36 ` Jens Axboe
2009-10-27 8:46 ` Kenji Kaneshige
2009-10-28 6:15 ` Kenji Kaneshige
2009-10-28 9:23 ` Jens Axboe
2009-10-29 7:44 ` Kenji Kaneshige
2009-10-29 8:58 ` Jens Axboe
2009-10-29 9:23 ` Kenji Kaneshige
2009-10-29 9:24 ` Jens Axboe
2009-11-02 5:27 ` Kenji Kaneshige
2009-10-13 3:19 ` Kenji Kaneshige
2009-10-13 8:31 ` Jens Axboe
2009-10-13 10:48 ` Kenji Kaneshige
2009-10-13 11:25 ` Jens Axboe
2009-10-14 5:26 ` Kenji Kaneshige
2009-10-14 8:47 ` Jens Axboe
2009-10-15 5:41 ` Kenji Kaneshige
2009-10-15 9:42 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2016-01-18 22:04 PCI-Express Hotplug lifelong0811 at 126.com
2016-01-19 0:27 ` Greg KH
2016-01-21 1:06 ` lifelong0811 at 126.com
2016-01-21 1:15 ` Greg KH
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=20091027083419.GU10727@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=achiang@hp.com \
--cc=greg@kroah.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lkml@rtr.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.