public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Chiang <achiang@hp.com>
To: Jens Axboe <jens.axboe@oracle.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: Mon, 26 Oct 2009 20:48:41 -0600	[thread overview]
Message-ID: <20091027024841.GA30509@ldl.fc.hp.com> (raw)
In-Reply-To: <20091026105419.GA10727@kernel.dk>

* 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.

Thanks,
/ac

---
diff --git a/drivers/pci/hotplug/acpiphp_glue.c b/drivers/pci/hotplug/acpiphp_glue.c
index 58d25a1..2caa447 100644
--- a/drivers/pci/hotplug/acpiphp_glue.c
+++ b/drivers/pci/hotplug/acpiphp_glue.c
@@ -797,9 +797,13 @@ static int power_on_slot(struct acpiphp_slot *slot)
 	struct list_head *l;
 	int retval = 0;
 
+	printk("%s\n", __func__);
+
 	/* if already enabled, just skip */
-	if (slot->flags & SLOT_POWEREDON)
+	if (slot->flags & SLOT_POWEREDON) {
+		printk("  slot %ld already powered on\n", slot->sun);
 		goto err_exit;
+	}
 
 	list_for_each (l, &slot->funcs) {
 		func = list_entry(l, struct acpiphp_func, sibling);
@@ -813,6 +817,8 @@ static int power_on_slot(struct acpiphp_slot *slot)
 				goto err_exit;
 			} else
 				break;
+		} else {
+			printk("  no _PS0\n");
 		}
 	}
 
@@ -1122,11 +1128,14 @@ static unsigned int get_slot_status(struct acpiphp_slot *slot)
 	struct list_head *l;
 	struct acpiphp_func *func;
 
+	printk("%s\n", __func__);
+
 	list_for_each (l, &slot->funcs) {
 		func = list_entry(l, struct acpiphp_func, sibling);
 
 		if (func->flags & FUNC_HAS_STA) {
 			status = acpi_evaluate_integer(func->handle, "_STA", NULL, &sta);
+			printk("  FUNC_HAS_STA status %d _STA %#lx\n", status, sta);
 			if (ACPI_SUCCESS(status) && sta)
 				break;
 		} else {
@@ -1134,6 +1143,7 @@ static unsigned int get_slot_status(struct acpiphp_slot *slot)
 						  PCI_DEVFN(slot->device,
 							    func->function),
 						  PCI_VENDOR_ID, &dvid);
+			printk("  reading config space dvid %#lx\n", dvid);
 			if (dvid != 0xffffffff) {
 				sta = ACPI_STA_ALL;
 				break;


  reply	other threads:[~2009-10-27  2:48 UTC|newest]

Thread overview: 40+ 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 [this message]
2009-10-27  8:26                       ` Jens Axboe
2009-10-27  8:34                         ` Jens Axboe
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

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=20091027024841.GA30509@ldl.fc.hp.com \
    --to=achiang@hp.com \
    --cc=greg@kroah.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=jens.axboe@oracle.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox