From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI Update for 2.6.2-rc2
Date: Thu, 29 Jan 2004 17:31:46 -0800 [thread overview]
Message-ID: <10754263062112@kroah.com> (raw)
In-Reply-To: <1075426306325@kroah.com>
ChangeSet 1.1511, 2004/01/29 14:26:41-08:00, willy@debian.org
[PATCH] PCI Hotplug: Better reporting of PCI frequency / bus mode problems for acpi driver
When plugging a 33MHz card into a bus that's running at 66MHz, I'd like
to see a better error message than:
acpiphp_glue: notify_handler: unknown event type 0x5 for \_SB_.SBA0.PCI4.S2F0
The following patch would give us:
Device \_SB_.SBA0.PCI4.S2F0 cannot be configured due to a frequency mismatch
which I think is clearer.
drivers/pci/hotplug/acpiphp_glue.c | 15 +++++++++++++++
1 files changed, 15 insertions(+)
diff -Nru a/drivers/pci/hotplug/acpiphp_glue.c b/drivers/pci/hotplug/acpiphp_glue.c
--- a/drivers/pci/hotplug/acpiphp_glue.c Thu Jan 29 17:24:40 2004
+++ b/drivers/pci/hotplug/acpiphp_glue.c Thu Jan 29 17:24:40 2004
@@ -974,6 +974,21 @@
dbg("%s: Device eject notify on %s\n", __FUNCTION__, objname);
break;
+ case ACPI_NOTIFY_FREQUENCY_MISMATCH:
+ printk(KERN_ERR "Device %s cannot be configured due"
+ " to a frequency mismatch\n", objname);
+ break;
+
+ case ACPI_NOTIFY_BUS_MODE_MISMATCH:
+ printk(KERN_ERR "Device %s cannot be configured due"
+ " to a bus mode mismatch\n", objname);
+ break;
+
+ case ACPI_NOTIFY_POWER_FAULT:
+ printk(KERN_ERR "Device %s has suffered a power fault\n",
+ objname);
+ break;
+
default:
warn("notify_handler: unknown event type 0x%x for %s\n", type, objname);
break;
next prev parent reply other threads:[~2004-01-30 1:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-30 1:29 [BK PATCH] PCI update for 2.6.2-rc2 Greg KH
2004-01-30 1:31 ` [PATCH] PCI Update " Greg KH
2004-01-30 1:31 ` Greg KH
2004-01-30 1:31 ` Greg KH [this message]
2004-01-30 1:31 ` Greg KH
2004-01-30 1:31 ` Greg KH
2004-01-30 1:31 ` Greg KH
2004-01-30 1:31 ` Greg KH
2004-01-30 1:31 ` Greg KH
2004-01-30 1:31 ` Greg KH
2004-01-30 1:31 ` Greg KH
2004-01-30 1:31 ` Greg KH
2004-01-30 1:31 ` Greg KH
2004-01-30 1:31 ` Greg KH
2004-01-30 1:31 ` Greg KH
2004-01-30 1:31 ` Greg KH
2004-01-30 1:31 ` Greg KH
2004-01-30 12:26 ` Russell King
2004-01-31 0:23 ` 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=10754263062112@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.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