From: Corey Minyard <minyard@acm.org>
To: Meelis Roos <mroos@linux.ee>, openipmi-developer@lists.sourceforge.net
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fix NULL device in ipmi_si error message
Date: Wed, 6 Jun 2018 09:04:14 -0500 [thread overview]
Message-ID: <14953c8b-e461-15d1-798f-39a1adbac0a6@acm.org> (raw)
In-Reply-To: <alpine.LRH.2.21.1806061604580.20960@math.ut.ee>
On 06/06/2018 08:11 AM, Meelis Roos wrote:
> I noticed that 4.17.0 logs the follwing during ipmi_si setup:
>
> ipmi_si 0000:01:04.6: probing via PCI
> (NULL device *): Could not setup I/O space
> ipmi_si 0000:01:04.6: [mem 0xf5ef0000-0xf5ef00ff] regsize 1 spacing 1 irq 21
>
> Fix the "NULL device *) by moving io.dev assignment before its potential
> use by ipmi_pci_probe_regspacing().
>
> Result:
> ipmi_si 0000:01:04.6: probing via PCI
> ipmi_si 0000:01:04.6: Could not setup I/O space
> ipmi_si 0000:01:04.6: [mem 0xf5ef0000-0xf5ef00ff] regsize 1 spacing 1 irq 21
Looks good, queued for next release.
It does raise the question of why the I/O space setup is failing on some
system (other have
reported this, too). I'm working on that.
Thanks,
-corey
> Signed-off-by: Meelis Roos <mroos@linux.ee>
>
> diff --git a/drivers/char/ipmi/ipmi_si_pci.c b/drivers/char/ipmi/ipmi_si_pci.c
> index f54ca6869ed2..022e03634ce2 100644
> --- a/drivers/char/ipmi/ipmi_si_pci.c
> +++ b/drivers/char/ipmi/ipmi_si_pci.c
> @@ -120,6 +120,8 @@ static int ipmi_pci_probe(struct pci_dev *pdev,
> }
> io.addr_data = pci_resource_start(pdev, 0);
>
> + io.dev = &pdev->dev;
> +
> io.regspacing = ipmi_pci_probe_regspacing(&io);
> io.regsize = DEFAULT_REGSIZE;
> io.regshift = 0;
> @@ -128,8 +130,6 @@ static int ipmi_pci_probe(struct pci_dev *pdev,
> if (io.irq)
> io.irq_setup = ipmi_std_irq_setup;
>
> - io.dev = &pdev->dev;
> -
> dev_info(&pdev->dev, "%pR regsize %d spacing %d irq %d\n",
> &pdev->resource[0], io.regsize, io.regspacing, io.irq);
>
>
prev parent reply other threads:[~2018-06-06 14:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 13:11 Meelis Roos
2018-06-06 14:04 ` Corey Minyard [this message]
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=14953c8b-e461-15d1-798f-39a1adbac0a6@acm.org \
--to=minyard@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
--cc=openipmi-developer@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®