From: Aristeu Rozanski <aris@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Andy Lutomirski <luto@amacapital.net>,
Mauro Carvalho Chehab <m.chehab@samsung.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Tony Luck <tony.luck@intel.com>,
linux-edac <linux-edac@vger.kernel.org>
Subject: Re: [PATCH] sb_edac: Fix detection on SNB machines
Date: Mon, 9 Feb 2015 09:20:58 -0500 [thread overview]
Message-ID: <20150209142058.GC20645@redhat.com> (raw)
In-Reply-To: <20150209121717.GD24769@pd.tnic>
On Mon, Feb 09, 2015 at 01:17:17PM +0100, Borislav Petkov wrote:
> From: Borislav Petkov <bp@suse.de>
> Subject: [PATCH] sb_edac: Fix detection on SNB machines
>
> d0585cd815fa ("sb_edac: Claim a different PCI device") changed the
> probing of sb_edac to look for PCI device 0x3ca0:
>
> 3f:0e.0 System peripheral: Intel Corporation Xeon E5/Core i7 Processor Home Agent (rev 07)
> 00: 86 80 a0 3c 00 00 00 00 07 00 80 08 00 00 80 00
> ...
>
> but we're matching for 0x3ca8, i.e. PCI_DEVICE_ID_INTEL_SBRIDGE_IMC_TA
> in sbridge_probe() therefore the probing fails.
>
> Changing it to probe for 0x3ca0 (PCI_DEVICE_ID_INTEL_SBRIDGE_IMC_HA0),
> .i.e., the 14.0 device, fixes the issue and driver loads successfully
> again:
>
> [ 2449.013120] EDAC DEBUG: sbridge_init:
> [ 2449.017029] EDAC sbridge: Seeking for: PCI ID 8086:3ca0
> [ 2449.022368] EDAC DEBUG: sbridge_get_onedevice: Detected 8086:3ca0
> [ 2449.028498] EDAC sbridge: Seeking for: PCI ID 8086:3ca0
> [ 2449.033768] EDAC sbridge: Seeking for: PCI ID 8086:3ca8
> [ 2449.039028] EDAC DEBUG: sbridge_get_onedevice: Detected 8086:3ca8
> [ 2449.045155] EDAC sbridge: Seeking for: PCI ID 8086:3ca8
> ...
>
> Add a debug printk while at it to be able to catch the failure in the
> future and dump driver version on successful load.
>
> Fixes: d0585cd815fa ("sb_edac: Claim a different PCI device")
> Cc: stable@vger.kernel.org # 3.18
> Cc: Tony Luck <tony.luck@intel.com>
> Cc: Andy Lutomirski <luto@amacapital.net>
> Cc: Mauro Carvalho Chehab <m.chehab@samsung.com>
> Signed-off-by: Borislav Petkov <bp@suse.de>
> ---
> drivers/edac/sb_edac.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/edac/sb_edac.c b/drivers/edac/sb_edac.c
> index 63aa6730e89e..1acf57ba4c86 100644
> --- a/drivers/edac/sb_edac.c
> +++ b/drivers/edac/sb_edac.c
> @@ -2447,7 +2447,7 @@ static int sbridge_probe(struct pci_dev *pdev, const struct pci_device_id *id)
> rc = sbridge_get_all_devices(&num_mc, pci_dev_descr_ibridge_table);
> type = IVY_BRIDGE;
> break;
> - case PCI_DEVICE_ID_INTEL_SBRIDGE_IMC_TA:
> + case PCI_DEVICE_ID_INTEL_SBRIDGE_IMC_HA0:
> rc = sbridge_get_all_devices(&num_mc, pci_dev_descr_sbridge_table);
> type = SANDY_BRIDGE;
> break;
> @@ -2460,8 +2460,11 @@ static int sbridge_probe(struct pci_dev *pdev, const struct pci_device_id *id)
> type = BROADWELL;
> break;
> }
> - if (unlikely(rc < 0))
> + if (unlikely(rc < 0)) {
> + edac_dbg(0, "couldn't get all devices for 0x%x\n", pdev->device);
> goto fail0;
> + }
> +
> mc = 0;
>
> list_for_each_entry(sbridge_dev, &sbridge_edac_list, list) {
> @@ -2474,7 +2477,7 @@ static int sbridge_probe(struct pci_dev *pdev, const struct pci_device_id *id)
> goto fail1;
> }
>
> - sbridge_printk(KERN_INFO, "Driver loaded.\n");
> + sbridge_printk(KERN_INFO, "%s\n", SBRIDGE_REVISION);
>
> mutex_unlock(&sbridge_edac_lock);
> return 0;
looks good to me
Acked-by: Aristeu Rozanski <aris@redhat.com>
--
Aristeu
next prev parent reply other threads:[~2015-02-09 14:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 11:50 [PATCH] sb_edac: Fix detection on SNB machines Borislav Petkov
2015-02-05 12:37 ` Borislav Petkov
2015-02-08 16:54 ` Andy Lutomirski
2015-02-08 18:19 ` Borislav Petkov
2015-02-09 12:17 ` Borislav Petkov
2015-02-09 14:20 ` Aristeu Rozanski [this message]
2015-02-09 15:23 ` Mauro Carvalho Chehab
2015-02-09 15:33 ` Andy Lutomirski
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=20150209142058.GC20645@redhat.com \
--to=aris@redhat.com \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=m.chehab@samsung.com \
--cc=tony.luck@intel.com \
/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.