From: Jean Delvare <jdelvare@suse.de>
To: linux-pci@vger.kernel.org
Cc: Thomas Renninger <trenn@suse.de>,
Bjorn Helgaas <bhelgaas@google.com>, Borislav Petkov <bp@suse.de>,
Prarit Bhargava <prarit@redhat.com>
Subject: [PATCH 3/4] PCI: aer_inject: Log actual error causes
Date: Thu, 18 Feb 2016 13:52:46 +0100 [thread overview]
Message-ID: <20160218135246.076beae6@endymion> (raw)
In-Reply-To: <20160218130928.67dbf63b@endymion>
The aer_inject driver is very quiet. In most cases, it merely returns
an error code to user-space, leaving the user with little clue about
the actual reason for the failure.
So, log error messages for 4 of the most frequent causes of failure:
* Can't find the root port of the specified device.
* Device doesn't support AER.
* Root port doesn't support AER.
* AER device not found.
This gives the user a chance to understand why aer-inject failed.
Based on a preliminary patch by Thomas Renninger.
Signed-off-by: Jean Delvare <jdelvare@suse.de>
Cc: Borislav Petkov <bp@suse.de>
Cc: Thomas Renninger <trenn@suse.de>
Cc: Bjorn Helgaas <bhelgaas@google.com>
---
drivers/pci/pcie/aer/aer_inject.c | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
--- linux-4.5-rc4.orig/drivers/pci/pcie/aer/aer_inject.c 2016-02-18 12:50:56.927581343 +0100
+++ linux-4.5-rc4/drivers/pci/pcie/aer/aer_inject.c 2016-02-18 12:53:18.432587496 +0100
@@ -335,12 +335,14 @@ static int aer_inject(struct aer_error_i
return -ENODEV;
rpdev = pcie_find_root_port(dev);
if (!rpdev) {
+ dev_err(&dev->dev, "aer_inject: Root port not found\n");
ret = -ENODEV;
goto out_put;
}
pos_cap_err = pci_find_ext_capability(dev, PCI_EXT_CAP_ID_ERR);
if (!pos_cap_err) {
+ dev_err(&dev->dev, "aer_inject: Device doesn't support AER\n");
ret = -EPROTONOSUPPORT;
goto out_put;
}
@@ -351,6 +353,8 @@ static int aer_inject(struct aer_error_i
rp_pos_cap_err = pci_find_ext_capability(rpdev, PCI_EXT_CAP_ID_ERR);
if (!rp_pos_cap_err) {
+ dev_err(&rpdev->dev,
+ "aer_inject: Root port doesn't support AER\n");
ret = -EPROTONOSUPPORT;
goto out_put;
}
@@ -466,8 +470,10 @@ static int aer_inject(struct aer_error_i
goto out_put;
}
aer_irq(-1, edev);
- } else
+ } else {
+ dev_err(&rpdev->dev, "aer_inject: AER device not found\n");
ret = -ENODEV;
+ }
out_put:
kfree(err_alloc);
kfree(rperr_alloc);
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2016-02-18 12:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 12:09 [PATCH 0/4] PCI: aer_inject cleanups and verbosity Jean Delvare
2016-02-18 12:50 ` [PATCH 1/4] PCI: aer_inject: Fix error codes Jean Delvare
2016-02-18 12:52 ` [PATCH 2/4] PCI: aer_inject: Use dev_warn() Jean Delvare
2016-02-18 12:52 ` Jean Delvare [this message]
2016-02-18 12:54 ` [PATCH 4/4] PCI: aer_inject: Log error injections Jean Delvare
2016-03-08 21:53 ` [PATCH 0/4] PCI: aer_inject cleanups and verbosity Bjorn Helgaas
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=20160218135246.076beae6@endymion \
--to=jdelvare@suse.de \
--cc=bhelgaas@google.com \
--cc=bp@suse.de \
--cc=linux-pci@vger.kernel.org \
--cc=prarit@redhat.com \
--cc=trenn@suse.de \
/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.