From: "Linux regression tracking #update (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>,
linux-edac@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: [bug-report] rasdaemon doesnot report new records.
Date: Thu, 16 Feb 2023 14:59:03 +0100 [thread overview]
Message-ID: <43fadb7f-cdc0-eb4b-7d3e-6b754a5cc77a@leemhuis.info> (raw)
In-Reply-To: <1a78baae-eb78-5add-13b3-9526082160d9@leemhuis.info>
[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]
On 30.01.23 12:57, Linux kernel regression tracking (#adding) wrote:
> On 30.01.23 10:34, Harshit Mogalapalli wrote:
>>
>> Since kernel 6.1-rc6 rasdaemon fails to update the summary of the records.
>>
>> When we inject MCE errors, generally ras-mc-ctl --summary should be able
>> to read new errors, but starting from 6.1-rc6 the summary(count on
>> number of MCE records) doesnot udpate when we inject new mce errors.
>>
>> This started happening after this commit
>> 42fb0a1e84ff525ebe560e2baf9451ab69127e2b ("tracing/ring-buffer: Have
>> polling block on watermark") -- Commit landed first in 6.1-rc6, 6.1-rc5
>> kernel doesnot have this problem.
>>
>> On reverting this commit, rasdaemon works good(i.e It is able to read
>> the new mce records).
>>
>> This continues to happen on latest kernel(v6.2-rc6) as well.
>
> Thanks for the report. To be sure the issue doesn't fall through the
> cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression
> tracking bot:
>
> #regzbot ^introduced 42fb0a1e84ff525
> #regzbot title tracing/ring-buffer: rasdaemon does not report new records
> #regzbot ignore-activity
For the record, I in
https://lore.kernel.org/lkml/1e759e44f5e64b4e99096afd9e89b6dc@huawei.com/
was told that the mainline commit 3e46d910d8ac ("tracing: Fix poll() and
select() do not work on per_cpu trace_pipe and trace_pipe_raw") fixes
this on the kernel side. There apparently is a rasdaemon change to
improve things, too.
#regzbot fix: 3e46d910d8ac
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
#regzbot ignore-activity
prev parent reply other threads:[~2023-02-16 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 9:34 [bug-report] rasdaemon doesnot report new records Harshit Mogalapalli
2023-01-30 11:57 ` Linux kernel regression tracking (#adding)
2023-02-16 13:59 ` Linux regression tracking #update (Thorsten Leemhuis) [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=43fadb7f-cdc0-eb4b-7d3e-6b754a5cc77a@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=harshit.m.mogalapalli@oracle.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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).