Public bug reported: [Impact] call trace after unloading mtk_rng module
[Fix] https://patchwork.linuxtv.org/project/linux-media/patch/20230515141610.v2.1.I0d1657be3fea5870f797e975a7aa490291e17993@changeid/#147177 [Test] 1. modprobe -r mtk_rng 2. modprobe mtk_rng [Where problems could occur] none. the chance should be low. LP: #2072842 ** Affects: linux-mtk (Ubuntu) Importance: Undecided Assignee: Jian Hui Lee (jianhuilee) Status: New ** Affects: linux-mtk (Ubuntu Jammy) Importance: Undecided Assignee: Jian Hui Lee (jianhuilee) Status: New ** Also affects: linux-mtk (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-mtk (Ubuntu) Assignee: (unassigned) => Jian Hui Lee (jianhuilee) ** Changed in: linux-mtk (Ubuntu Jammy) Assignee: (unassigned) => Jian Hui Lee (jianhuilee) ** Description changed: [Impact] call trace after unloading mtk_rng module [Fix] https://patchwork.linuxtv.org/project/linux-media/patch/20230515141610.v2.1.I0d1657be3fea5870f797e975a7aa490291e17993@changeid/#147177 - [Test] 1. modprobe -r mtk_rng 2. modprobe mtk_rng [Where problems could occur] none. the chance should be low. + + LP: #2072842 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081696 Title: [g1200] Call trace appeared when reload mtk_rng module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-mtk/+bug/2081696/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
