From: Marc Gonzalez <marc.w.gonzalez@free.fr>
To: Neil Armstrong <neil.armstrong@linaro.org>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: Pierre-Hugues Husson <phh@phh.me>,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/3] Fix G12 PMU conflict
Date: Mon, 27 Mar 2023 17:25:49 +0200 [thread overview]
Message-ID: <e2026259-3372-d1ee-d0aa-1376361a71cb@free.fr> (raw)
In-Reply-To: <20230327120932.2158389-1-mgonzalez@freebox.fr>
On 27/03/2023 14:09, Marc Gonzalez wrote:
> Move the PMU DT node & adjust the register offsets.
>
> Marc Gonzalez (3):
> arm64: dts: meson-g12-common: specify full DMC range
> perf/amlogic: resolve conflict between canvas & pmu
> perf/amlogic: adjust register offsets
Hmmm... the perf driver doesn't like my setup... :(
# perf record -a -F 1009 --call-graph fp -B curl -o /dev/null http://192.168.1.254:8095/fixed/1G
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 1024M 0 8342k 0 0 7564k 0 0:02:18 0:00:01 0:02:17 7563k
[ 1036.936099] SError Interrupt on CPU1, code 0x00000000bf000000 -- SError
[ 1036.936116] CPU: 1 PID: 61 Comm: kworker/u9:0 Not tainted 6.2.0 #449
[ 1036.936122] Hardware name: SEI Robotics SEI510 (DT)
[ 1036.936126] Workqueue: brcmf_wq/mmc2:0001:1 brcmf_sdio_dataworker
[ 1036.936144] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 1036.936150] pc : brcmf_sdiod_skbuff_read+0x28/0xa0
[ 1036.936159] lr : brcmf_sdiod_recv_chain+0xe4/0x160
[ 1036.936166] sp : ffff80000a18bc00
[ 1036.936169] x29: ffff80000a18bc00 x28: ffff8000087d31a0 x27: ffff8000087d2e60
[ 1036.936177] x26: ffff000004990b00 x25: 0000000000000009 x24: ffff8000087d31a0
[ 1036.936184] x23: ffff000004998500 x22: 0000000000008000 x21: ffff000000873278
[ 1036.936192] x20: 000000000000c100 x19: ffff000000872800 x18: 0000000000000000
[ 1036.936199] x17: ffff80005df77000 x16: ffff80000800c000 x15: 0000000000000000
[ 1036.936205] x14: 0000000000000002 x13: 0000000000077f7a x12: 0000000000000068
[ 1036.936213] x11: 00000000000000c0 x10: 0000000000000068 x9 : fffffc0000150800
[ 1036.936220] x8 : fffffc0000150801 x7 : ffff80005df77000 x6 : ffff000004998500
[ 1036.936227] x5 : ffff0000008bc000 x4 : 000000000000c103 x3 : ffff000004998500
[ 1036.936233] x2 : 0000000000008000 x1 : 0000000000000002 x0 : ffff000000872800
[ 1036.936243] Kernel panic - not syncing: Asynchronous SError Interrupt
[ 1036.936247] CPU: 1 PID: 61 Comm: kworker/u9:0 Not tainted 6.2.0 #449
[ 1036.936252] Hardware name: SEI Robotics SEI510 (DT)
[ 1036.936255] Workqueue: brcmf_wq/mmc2:0001:1 brcmf_sdio_dataworker
[ 1036.936262] Call trace:
[ 1036.936264] dump_backtrace.part.0+0xe0/0xf0
[ 1036.936273] show_stack+0x18/0x30
[ 1036.936280] dump_stack_lvl+0x68/0x84
[ 1036.936288] dump_stack+0x18/0x34
[ 1036.936294] panic+0x184/0x344
[ 1036.936301] nmi_panic+0xac/0xb0
[ 1036.936308] arm64_serror_panic+0x6c/0x80
[ 1036.936314] do_serror+0x58/0x60
[ 1036.936318] el1h_64_error_handler+0x30/0x50
[ 1036.936324] el1h_64_error+0x64/0x68
[ 1036.936330] brcmf_sdiod_skbuff_read+0x28/0xa0
[ 1036.936336] brcmf_sdiod_recv_chain+0xe4/0x160
[ 1036.936343] brcmf_sdio_dataworker+0x898/0x23d0
[ 1036.936348] process_one_work+0x1cc/0x320
[ 1036.936354] worker_thread+0x14c/0x450
[ 1036.936359] kthread+0xfc/0x100
[ 1036.936364] ret_from_fork+0x10/0x20
[ 1036.936371] SMP: stopping secondary CPUs
[ 1036.936378] Kernel Offset: disabled
[ 1036.936379] CPU features: 0x00000,01000100,0000420b
[ 1036.936384] Memory Limit: none
[ 1037.149180] ---[ end Kernel panic - not syncing: Asynchronous SError Interrupt ]---
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2023-03-27 15:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 12:09 [PATCH v2 0/3] Fix G12 PMU conflict Marc Gonzalez
2023-03-27 12:09 ` [PATCH v2 1/3] arm64: dts: meson-g12-common: specify full DMC range Marc Gonzalez
2023-03-27 12:09 ` [PATCH v2 2/3] perf/amlogic: resolve conflict between canvas & pmu Marc Gonzalez
2023-03-27 12:44 ` Marc Gonzalez
2023-03-27 14:12 ` Neil Armstrong
2023-03-28 11:56 ` Marc Gonzalez
2023-03-27 12:09 ` [PATCH v2 3/3] perf/amlogic: adjust register offsets Marc Gonzalez
2023-03-27 14:17 ` Neil Armstrong
2023-03-27 15:12 ` Will Deacon
2023-03-27 15:27 ` Neil Armstrong
2023-03-27 14:15 ` (subset) [PATCH v2 0/3] Fix G12 PMU conflict Neil Armstrong
2023-03-27 15:25 ` Marc Gonzalez [this message]
2023-03-27 15:36 ` Marc Gonzalez
2023-03-27 15:52 ` Marc Gonzalez
2023-03-29 0:01 ` Marc Gonzalez
2023-03-27 15:31 ` (subset) " Neil Armstrong
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=e2026259-3372-d1ee-d0aa-1376361a71cb@free.fr \
--to=marc.w.gonzalez@free.fr \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=phh@phh.me \
/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