mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Corey Minyard <minyard@acm.org>
To: Meelis Roos <mroos@linux.ee>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
	Colin Ian King <colin.king@canonical.com>
Subject: Re: ipmi null pointer oops in 4.15-rc2+ on HP DL360G6
Date: Thu, 7 Dec 2017 11:25:22 -0600	[thread overview]
Message-ID: <d70c1ac3-5adc-10b2-d59d-3c5c8a2e5066@acm.org> (raw)
In-Reply-To: <alpine.LRH.2.21.1712071741530.5807@math.ut.ee>

On 12/07/2017 09:43 AM, Meelis Roos wrote:
>>> Tried current 4.15 git on HP DL360G6 (working fine in 4.14), got null
>>> pointer dereference oops from ipmi_pci_probe (or so it seems from the
>>> backtrace).
>> I have a fix for this at https://bugzilla.kernel.org/show_bug.cgi?id=197999,
>> but
>> the reported hasn't reported if the patch there fixes the issue.  If you could
>> test
>> this, that would be very helpful.
> It works. no errors. I hve not tested if ipmi communication actually
> works though.

Ok.  I added pci support to the qemu IPMI stuff and tested it myself.  
But thanks,
I'll add your "Tested by".  It's good to have more testers.

-corey

> $ dmesg |grep -i pmi
> [    0.000000] ACPI: SPMI 0x00000000D761F2C0 000040 (v05 HP     ProLiant 00000001 \xd2?   0000162E)
> [    4.563949] ipmi message handler version 39.2
> [    4.578919] ipmi device interface
> [    4.580438] IPMI System Interface driver.
> [    4.580503] ipmi_si dmi-ipmi-si.0: ipmi_platform: probing via SMBIOS
> [    4.580561] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
> [    4.580618] ipmi_si: Adding SMBIOS-specified kcs state machine
> [    4.580687] ipmi_si IPI0001:00: ipmi_platform: probing via ACPI
> [    4.580758] ipmi_si IPI0001:00: [io  0x0ca2-0x0ca3] regsize 1 spacing 1 irq 0
> [    4.580817] ipmi_si dmi-ipmi-si.0: Removing SMBIOS-specified kcs state machine in favor of ACPI
> [    4.580894] ipmi_si: Adding ACPI-specified kcs state machine
> [    4.580964] ipmi_platform: probing via SPMI
> [    4.581018] ipmi_si: SPMI: io 0xca2 regsize 2 spacing 2 irq 0
> [    4.581074] (NULL device *): SPMI-specified kcs state machine: duplicate
> [    4.581142] ipmi_si 0000:01:04.6: probing via PCI
> [    4.581282] ipmi_si 0000:01:04.6: [mem 0xf5ef0000-0xf5ef00ff] regsize 1 spacing 1 irq 21
> [    4.581356] ipmi_si: Adding PCI-specified kcs state machine
> [    4.581428] ipmi_si: Trying PCI-specified kcs state machine at mem address 0xf5ef0000, slave address 0x0, irq 21
> [    5.112453] ipmi_si 0000:01:04.6: Using irq 21
> [    5.127593] ipmi_si 0000:01:04.6: Found new BMC (man_id: 0x00000b, prod_id: 0x2000, dev_id: 0x11)
> [    5.139340] ipmi_si 0000:01:04.6: IPMI kcs interface initialized
> [    5.148318] IPMI SSIF Interface driver
> [    6.126894] ACPI Error: SMBus/IPMI/GenericSerialBus write requires Buffer of length 66, found length 32 (20170831/exfield-427)
> [    6.127233] ACPI Error: Method parse/execution failed \_SB.PMI0._PMM, AE_AML_BUFFER_LIMIT (20170831/psparse-550)
>
>

      reply	other threads:[~2017-12-07 17:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-05 13:08 Meelis Roos
2017-12-05 13:24 ` Corey Minyard
2017-12-07 15:43   ` Meelis Roos
2017-12-07 17:25     ` 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=d70c1ac3-5adc-10b2-d59d-3c5c8a2e5066@acm.org \
    --to=minyard@acm.org \
    --cc=colin.king@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mroos@linux.ee \
    /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®