regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Bug 212389 - Kernel panic on VIA Nano L2200
Date: Thu, 13 Oct 2022 14:57:59 +0200	[thread overview]
Message-ID: <bbee1e7c-8ae1-aebf-30ce-1060cb2220a9@leemhuis.info> (raw)

Hi, this is your Linux kernel regression tracker speaking.

I noticed a regression report in bugzilla.kernel.org I'd like to add to
the tracking: https://bugzilla.kernel.org/show_bug.cgi?id=212389

> I ran into this issue after upgrading my debian kernel from 4.19 to
> 5.10. Debian bugreport:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979765
> 
> It probably started with kernel 5.8, when the Zhaoxin PMU driver was
> added, but I've not tested that. The problem also occurs with
> upstream linux kernels and I re-tested today with upstream
> 5.12.0-rc4
> 
> No panic occurs when kernel boot parameter
> 'initcall_blacklist=init_hw_perf_events' is used.

See the ticket for more details.

#regzbot introduced: v4.19..v5.10
https://bugzilla.kernel.org/show_bug.cgi?id=212389
#regzbot monitor:
https://lore.kernel.org/all/20210607013109.7870-1-CodyYao-oc@zhaoxin.com/
#regzbot ignore-activity

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.



                 reply	other threads:[~2022-10-13 12:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bbee1e7c-8ae1-aebf-30ce-1060cb2220a9@leemhuis.info \
    --to=regressions@leemhuis.info \
    --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).