From: patchwork-bot+linux-arm-msm@kernel.org
To: Stanimir Varbanov <stanimir.varbanov@linaro.org>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] venus: pm_helpers: Fix kernel module reload
Date: Tue, 29 Dec 2020 20:15:31 +0000 [thread overview]
Message-ID: <160927293170.13751.13847382083773191602.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201101130052.20974-1-stanimir.varbanov@linaro.org>
Hello:
This patch was applied to qcom/linux.git (refs/heads/for-next):
On Sun, 1 Nov 2020 15:00:52 +0200 you wrote:
> After initial kernel module load during kernel boot and removing
> the module and try to load it again an Unable to handle kernel
> paging request is observed:
>
> Unable to handle kernel paging request at virtual address ffffa44f7416eae0
> Mem abort info:
> ESR = 0x96000047
> EC = 0x25: DABT (current EL), IL = 32 bits
> SET = 0, FnV = 0
> EA = 0, S1PTW = 0
> Data abort info:
> ISV = 0, ISS = 0x00000047
> CM = 0, WnR = 1
> swapper pgtable: 4k pages, 48-bit VAs, pgdp=000000008147c000
> [ffffa44f7416eae0] pgd=000000017df9f003, p4d=000000017df9f003,
> pud=000000017df9e003, pmd=000000017df9b003, pte=0000000000000000
> Internal error: Oops: 96000047 [#1] PREEMPT SMP
> Modules linked in: venus_core(+) snd_soc_wsa881x regmap_sdw af_alg
> snd_soc_wcd934x soundwire_qcom gpio_wcd934x q6asm_dai q6routing
> q6adm q6afe_dai snd_soc_hdmi_codec q6afe q6asm q6dsp_common q6cor
> display_connector rmtfs_mem drm ip_tables x_tables ipv6
> [last unloaded: venus_core]
> CPU: 6 PID: 889 Comm: modprobe Tainted: G W 5.10.0-rc1+ #8
> Hardware name: Thundercomm Dragonboard 845c (DT)
> pstate: 80400085 (Nzcv daIf +PAN -UAO -TCO BTYPE=--)
> pc : queued_spin_lock_slowpath+0x1dc/0x3c8
> lr : do_raw_spin_lock+0xc0/0x118
> sp : ffff8000142cb7b0
> x29: ffff8000142cb7b0 x28: 0000000000000013
> x27: ffffa44f72de5690 x26: 0000000000000003
> x25: ffff17c2d00f8080 x24: ffff17c2c0d78010
> x23: ffff17c2c0d4f700 x22: ffff17c2d00f8080
> x21: 0000000000000000 x20: ffffa44f74148000
> x19: ffff17c2c0d4f8f8 x18: 0000000000000000
> x17: 0000000000000000 x16: ffffa44f7342f158
> x15: 0000000000000040 x14: ffffa44f746e8320
> x13: 0000000000000228 x12: 0000000000000020
> x11: 0000000000000000 x10: 00000000001c0000
> x9 : 0000000000000000 x8 : ffff17c33d746ac0
> x7 : ffff17c2c109b000 x6 : ffffa44f7416eac0
> x5 : ffff17c33d746ac0 x4 : 0000000000000000
> x3 : ffff17c2c0d4f8f8 x2 : ffffa44f7416eae0
> x1 : ffffa44f7416eae0 x0 : ffff17c33d746ac8
> Call trace:
> queued_spin_lock_slowpath+0x1dc/0x3c8
> do_raw_spin_lock+0xc0/0x118
> _raw_spin_lock_irqsave+0x80/0x14c
> __pm_runtime_resume+0x38/0xb8
> device_link_add+0x3b8/0x5d0
> core_get_v4+0x268/0x2d8 [venus_core]
> venus_probe+0x108/0x458 [venus_core]
> platform_drv_probe+0x54/0xa8
> really_probe+0xe4/0x3b0
> driver_probe_device+0x58/0xb8
> device_driver_attach+0x74/0x80
> __driver_attach+0x58/0xe8
> bus_for_each_dev+0x70/0xc0
> driver_attach+0x24/0x30
> bus_add_driver+0x150/0x1f8
> driver_register+0x64/0x120
> __platform_driver_register+0x48/0x58
> qcom_venus_driver_init+0x20/0x1000 [venus_core]
> do_one_initcall+0x84/0x458
> do_init_module+0x58/0x208
> load_module+0x1ec0/0x26a8
> __do_sys_finit_module+0xb8/0xf8
> __arm64_sys_finit_module+0x20/0x30
> el0_svc_common.constprop.0+0x7c/0x1c0
> do_el0_svc+0x24/0x90
> el0_sync_handler+0x180/0x188
> el0_sync+0x174/0x180
> Code: 91002100 8b0200c2 f861d884 aa0203e1 (f8246828)
>
> [...]
Here is the summary with links:
- venus: pm_helpers: Fix kernel module reload
https://git.kernel.org/qcom/c/9215f6bb4705
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2020-12-29 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 13:00 [PATCH] venus: pm_helpers: Fix kernel module reload Stanimir Varbanov
2020-11-03 7:43 ` Rajendra Nayak
2020-12-29 20:15 ` patchwork-bot+linux-arm-msm [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=160927293170.13751.13847382083773191602.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-arm-msm@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=stanimir.varbanov@linaro.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 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).