All of lore.kernel.org
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: Sudeep Holla <sudeep.holla@kernel.org>
Cc: Jassi Brar <jassisinghbrar@gmail.com>,
	 Adam Young <admiyo@os.amperecomputing.com>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	 rmikey@meta.com, kernel-team@meta.com
Subject: Re: [PATCH] mailbox: pcc: Free the channel before unmapping the shared memory
Date: Thu, 13 Aug 2026 01:18:58 -0700	[thread overview]
Message-ID: <an19sQf5myJJnRq3@gmail.com> (raw)
In-Reply-To: <20260813-furry-seriema-of-prestige-af2a76@sudeepholla>

Hello Sudeep,

On Thu, Aug 13, 2026 at 03:57:29AM +0100, Sudeep Holla wrote:
> On Wed, Aug 12, 2026 at 05:36:03AM -0700, Breno Leitao wrote:
> > I am seeing a crash on PCC that is related to a an shared memory being
> > unmapped before the IRQ is disabled, and the IRQ kicks in and hits the
> > unmapped (NULL) address. This is a summary of what I see on my box:
> > 
> > 	scmi_protocol scmi_dev.1: Message for 1 type 0 is not expected!
> > 	Unable to handle kernel NULL pointer dereference at virtual address 0000000000000004
> > 	 __handle_irq_event_percpu+0x1c4/0x9e0
> > 	 handle_irq_event+0x98/0x218
> > 	 handle_fasteoi_irq+0x230/0x750
> > 	 generic_handle_domain_irq+0xac/0x138
> > 	 gic_handle_irq+0x344/0x740
> > 	 call_on_irq_stack+0x30/0x48
> > 
> 
> Just curious as how are you testing ACPI PCC + SCMI using upstream and
> on which platform ?

I am using Arm AGI CPU with the latest SCMI patches that are being under
discussion in the mailing list.

--breno


  reply	other threads:[~2026-08-13  8:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-12 12:36 [PATCH] mailbox: pcc: Free the channel before unmapping the shared memory Breno Leitao
2026-08-13  2:57 ` Sudeep Holla
2026-08-13  8:18   ` Breno Leitao [this message]
2026-08-13 10:45     ` Sudeep Holla
2026-08-13 10:54 ` Sudeep Holla

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=an19sQf5myJJnRq3@gmail.com \
    --to=leitao@debian.org \
    --cc=admiyo@os.amperecomputing.com \
    --cc=jassisinghbrar@gmail.com \
    --cc=kernel-team@meta.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmikey@meta.com \
    --cc=sudeep.holla@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.