openbmc Digest, Vol 41, Issue 79
刘锡伟
fyczy at 126.com
Mon Jan 21 14:28:33 AEDT 2019
Hi
1. I would like to ask any one how to generate BMC logging through phosphor-logging?
2. When to call the IpmiSelAdd and IpmiSelAddOem methods?
3. Write the log to journalctl through phosphor-sel-logger. Could you read it through the ipmiStorageGetSELInfo method of intel-ipmi-oem?
Thanks
At 2019-01-19 01:39:02, openbmc-request at lists.ozlabs.org wrote:
>Send openbmc mailing list submissions to
> openbmc at lists.ozlabs.org
>
>To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.ozlabs.org/listinfo/openbmc
>or, via email, send a message with subject or body 'help' to
> openbmc-request at lists.ozlabs.org
>
>You can reach the person managing the list at
> openbmc-owner at lists.ozlabs.org
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of openbmc digest..."
>
>
>Today's Topics:
>
> 1. couple questions for Event Log (???)
> 2. Re: Openbmc test Release tagging for Community Release (krtaylor)
> 3. Re: [PATCH v2 1/2] dt-binding: iio: add NPCM ADC
> documentation (Tomer Maimon)
> 4. Re: [PATCH] nbd:clear NBD_BOUND flag when NBD connection is
> closed (Adriana Kobylak)
> 5. Re: couple questions for Event Log (Bills, Jason M)
> 6. Using mmap against aspeed-lpc-ctrl device - weird bytes :D
> (Patrick Venture)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Fri, 18 Jan 2019 17:28:44 +0800 (CST)
>From: ??? <fyczy at 126.com>
>To: openbmc at lists.ozlabs.org
>Subject: couple questions for Event Log
>Message-ID: <5aff6ce7.7e70.168604a8925.Coremail.fyczy at 126.com>
>Content-Type: text/plain; charset="gbk"
>
>Hi
>
>1. How to debug the system event log, how to configure it, and what modules are related to the log function?
>
>2. When is the phosphor-sel-logger registration method (IpmiSelAdd, IpmiSelAddOem) invoked? How to use DBUS to read journalctl?
>
>3. Could anyone share a description of the yaml file about phosphor-logging?
>
>Thanks
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20190118/aa3807a1/attachment-0001.html>
>
>------------------------------
>
>Message: 2
>Date: Fri, 18 Jan 2019 09:07:52 -0600
>From: krtaylor <kurt.r.taylor at gmail.com>
>To: openbmc at lists.ozlabs.org
>Subject: Re: Openbmc test Release tagging for Community Release
>Message-ID: <ecb9f90c-958b-219b-160c-11ee09a72ecb at gmail.com>
>Content-Type: text/plain; charset=windows-1252; format=flowed
>
>On 1/17/19 10:38 AM, George Keishing wrote:
>> Hi All,
>>
>> We are going to tag a openbmc test release soon for the community master
>> release testing. So, expect 2.3 tag version soon there in a week time
>> from now, once the test code and master are stable.
>
>No, we are in the middle of a test cycle for the 2.6 release. We agreed
>and switched from the informal tags to a formal release process last
>June/July. Why do we need to tag master at an earlier level? Please come
>to a release planning meeting and let's talk about what you need.
>
>> As part of the release tagging in test, we are freezing any new changes
>> for now in test except for CI/CT fixes required to support testing the
>> Master 2.6 .
>
>I don't understand this at all. What is "release tagging in test"? We
>have a 2.6 branch and master (which is also at 2.6+ level).
>
>Kurt (krtaylor)
>
>
>------------------------------
>
>Message: 3
>Date: Fri, 18 Jan 2019 17:18:43 +0200
>From: Tomer Maimon <tmaimon77 at gmail.com>
>To: Joel Stanley <joel at jms.id.au>
>Cc: Jonathan Cameron <jic23 at kernel.org>, Hartmut Knaack
> <knaack.h at gmx.de>, Lars-Peter Clausen <lars at metafoo.de>, Peter
> Meerwald-Stadler <pmeerw at pmeerw.net>, Rob Herring
> <robh+dt at kernel.org>, Mark Rutland <mark.rutland at arm.com>, Nancy Yuen
> <yuenn at google.com>, Patrick Venture <venture at google.com>, Brendan
> Higgins <brendanhiggins at google.com>, Avi Fishman
> <avifishman70 at gmail.com>, linux-iio at vger.kernel.org, OpenBMC Maillist
> <openbmc at lists.ozlabs.org>, Linux Kernel Mailing List
> <linux-kernel at vger.kernel.org>, devicetree
> <devicetree at vger.kernel.org>
>Subject: Re: [PATCH v2 1/2] dt-binding: iio: add NPCM ADC
> documentation
>Message-ID:
> <CAP6Zq1j=oPdVXZKBteBcaLVZcvoU7M6YbfGhSCaC44Ld9AQ9Ag at mail.gmail.com>
>Content-Type: text/plain; charset="utf-8"
>
>Hi Joel,
>
>Thanks for bringing this to my attention,
>
>I think I will leave it the same way it is now because I will like to
>develop the reset driver and to handle the NPCM7xx SOC resets.
>
>Cheers,
>
>Tomer
>
>
>
>On Wed, 16 Jan 2019 at 01:21, Joel Stanley <joel at jms.id.au> wrote:
>
>> On Thu, 10 Jan 2019 at 03:44, Tomer Maimon <tmaimon77 at gmail.com> wrote:
>>
>> > +Required Node in the NPCM7xx BMC:
>> > +An additional register is present in the NPCM7xx SOC which is
>> > +assumed to be in the same device tree, with and marked as
>> > +compatible with "nuvoton,npcm750-rst".
>>
>> Is there a reason you don't include a phandle to the reset node?
>>
>> I think doing that would make more sense.
>>
>> > +adc: adc at f000c000 {
>> > + compatible = "nuvoton,npcm750-adc";
>> > + reg = <0xf000c000 0x8>;
>> > + interrupts = <GIC_SPI 0 IRQ_TYPE_LEVEL_HIGH>;
>> > + clocks = <&clk NPCM7XX_CLK_ADC>;
>> > +};
>>
>> > +
>> > +rst: rst at f0801000 {
>> > + compatible = "nuvoton,npcm750-rst", "syscon",
>> > + "simple-mfd";
>> > + reg = <0xf0801000 0x6C>;
>> > +};
>>
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20190118/cb3fb0a9/attachment-0001.html>
>
>------------------------------
>
>Message: 4
>Date: Fri, 18 Jan 2019 09:44:23 -0600
>From: Adriana Kobylak <anoo at linux.ibm.com>
>To: joel at jms.id.au, jk at ozlabs.org
>Cc: openbmc at lists.ozlabs.org, medadyoung at gmail.com
>Subject: Re: [PATCH] nbd:clear NBD_BOUND flag when NBD connection is
> closed
>Message-ID: <c2c5408cf1a715df1e7ac6447620b5de at linux.vnet.ibm.com>
>Content-Type: text/plain; charset=US-ASCII; format=flowed
>
>Hi Joel,
>
>Why has this patch been archived and marked as "Not Applicable"? -
>http://patchwork.ozlabs.org/patch/1011480/
>
>
>
>------------------------------
>
>Message: 5
>Date: Fri, 18 Jan 2019 09:51:26 -0800
>From: "Bills, Jason M" <jason.m.bills at linux.intel.com>
>To: openbmc at lists.ozlabs.org
>Subject: Re: couple questions for Event Log
>Message-ID: <7bf8dc07-5146-ffd9-870a-ba74c0cb36d9 at linux.intel.com>
>Content-Type: text/plain; charset=gbk; format=flowed
>
>On 1/18/2019 1:28 AM, ??? wrote:
>> Hi
>>
>> 1.How to debug the system event log, how to configure it, and what
>> modules are related to the log function?
>
>Can you provide more detail? Are you looking specifically for IPMI SEL
>or general BMC logging through phosphor-logging?
>
>>
>> 2.When is the phosphor-sel-logger registration method (IpmiSelAdd,
>> IpmiSelAddOem) invoked? How to use DBUS to read journalctl?
>
>phosphor-sel-logger runs as a service and exposes the IpmiSelAdd and
>IpmiSelAddOem methods on D-Bus. When either of those methods is
>invoked, the phosphor-sel-logger creates an IPMI SEL entry in the system
>journal using the provided data. The journal can then be parsed to
>extract the SEL entries as found in
>https://gerrit.openbmc-project.xyz/c/openbmc/intel-ipmi-oem/+/16280.
>
>journalctl is a command-line utility to read the system journal, so it
>isn't used over D-Bus. Details on journalctl can be found here:
>https://www.freedesktop.org/software/systemd/man/journalctl.html.
>
>If you want to read the journal in source, you can use the sd_journal
>APIs here:
>https://www.freedesktop.org/software/systemd/man/sd_journal.html#.
>Example usage is in the gerrit review above.
>
>>
>> 3.Could anyone share a description of the yaml file about phosphor-logging?
>>
>> Thanks
>>
>>
>>
>
>Thanks,
>-Jason
>
>
>------------------------------
>
>Message: 6
>Date: Fri, 18 Jan 2019 10:38:41 -0800
>From: Patrick Venture <venture at google.com>
>To: Joel Stanley <joel at jms.id.au>
>Cc: OpenBMC Maillist <openbmc at lists.ozlabs.org>
>Subject: Using mmap against aspeed-lpc-ctrl device - weird bytes :D
>Message-ID:
> <CAO=notxJck9xYXKv=BYADuZV1Ya771bS7Mc_-1OUfDp4iFTq2A at mail.gmail.com>
>Content-Type: text/plain; charset="UTF-8"
>
>Just to give you some context snippets:
>
>System DTS snippet:
>
>reserved-memory {
> #address-cells = <1>;
> #size-cells = <1>;
> ranges;
> lpc_mapped_memory: region at 98000000 {
> no-map;
> reg = <0x98000000 0x00800000>; /* 8MB */
> };
>};
>
>&lpc_ctrl {
> status = "okay";
> memory-region = <&lpc_mapped_memory>;
> flash = <&spi1>; // spi disabled, but needed for lpc_ctrl to probe
>};
>
>So, on the BMC, it receives the host's memory map address --> so it
>can configure the window:
>
>https://github.com/openbmc/phosphor-ipmi-flash/blob/master/lpc_aspeed.cpp#L42
>
>Then the host tool, mmap's to the host set-aside address, 4KiB, and
>tells the BMC to copy out the 4KiB:
>
>https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-ipmi-flash/+/17505
>
>Keep in mind, previously this was working by the BMC opening /dev/mem
>and mapping against lpc_mapped_memory -- but now we're opening
>aspeed-lpc-ctrl. In the code above, regionAddress ==
>lpc_mapped_memory, and regionSize is 64KiB.
>
>Can you take a look to at least sanity check this?
>
>It ends up copying out data that looks like this:
>
>00000000 0a 00 01 00 0a 00 01 00 0a 00 01 00 0a 00 01 00 |................|
>*
>00001000
>
>Patrick
>
>
>End of openbmc Digest, Vol 41, Issue 79
>***************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20190121/e27e56cb/attachment-0001.html>
More information about the openbmc
mailing list