linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Vipin K Parashar <vipin@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
	Vasant Hegde <hegdevasant@linux.vnet.ibm.com>,
	linuxppc-dev@lists.ozlabs.org
Cc: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Subject: Re: [PATCH v5] powerpc/pseries: Limit EPOW reset event warnings
Date: Tue, 1 Dec 2015 14:41:04 +0530	[thread overview]
Message-ID: <565D6428.9080602@linux.vnet.ibm.com> (raw)
In-Reply-To: <1448941585.9027.4.camel@ellerman.id.au>



On Tuesday 01 December 2015 09:16 AM, Michael Ellerman wrote:
> On Mon, 2015-11-30 at 17:31 +0530, Vipin K Parashar wrote:
>> On Thursday 26 November 2015 02:50 PM, Vasant Hegde wrote:
>>> On 11/18/2015 02:12 PM, Vipin K Parashar wrote:
>>>> Kernel prints respective warnings about various EPOW events for
>>>> user information/action after parsing EPOW interrupts. At times
>>>> below EPOW reset event warning is seen to be flooding kernel log
>>>> over a period of time.
>>>>
>>>> May 25 03:46:34 alp kernel: Non critical power or cooling issue cleared
>>>> May 25 03:46:52 alp kernel: Non critical power or cooling issue cleared
>>>> May 25 03:53:48 alp kernel: Non critical power or cooling issue cleared
>>>> May 25 03:55:46 alp kernel: Non critical power or cooling issue cleared
>>>> May 25 03:56:34 alp kernel: Non critical power or cooling issue cleared
>>>> May 25 03:59:04 alp kernel: Non critical power or cooling issue cleared
>>>> May 25 04:02:01 alp kernel: Non critical power or cooling issue cleared
>>>>
>>> @Michael,
>>>    I think above log is raising some concern. We have been asked by multiple
>>> people on this. Hence I think we should avoid these duplicate messages.
>> Hi Michael,
>>            Please do let know if you have some suggestions with this patch.
>
> It seems OK to me. I actually had it in my testing tree and was about to merge
> it when Vasant replied with comments.
>
> So if you two can agree on a final patch I'll merge it.

Thanks Michael, I will send out next revision for this addressing 
Vasant's comment.

>
> cheers
>

      reply	other threads:[~2015-12-01  9:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-18  8:42 [PATCH v5] powerpc/pseries: Limit EPOW reset event warnings Vipin K Parashar
2015-11-26  9:20 ` Vasant Hegde
2015-11-30 12:01   ` Vipin K Parashar
2015-12-01  3:46     ` Michael Ellerman
2015-12-01  9:11       ` Vipin K Parashar [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=565D6428.9080602@linux.vnet.ibm.com \
    --to=vipin@linux.vnet.ibm.com \
    --cc=hegdevasant@linux.vnet.ibm.com \
    --cc=kamalesh@linux.vnet.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    /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;
as well as URLs for NNTP newsgroup(s).