Redpine: Observed kernel panic while running wireless tests in regression mode
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Critical
|
Unassigned | ||
Xenial |
Fix Released
|
Critical
|
Unassigned |
Bug Description
SRU Justification
-----------------
Impact:
Kernel freezes/panic when running wireless tests in regression
Test case:
1. Keep a wrong access-point name in sta.conf file and run the nmcli.
2. There will be continuous scan will be happen and do remove the module using rmmod.sh script.
3. When soft scan is happening in redpine driver, before connection. Some times, we have observed
a kernel panic. like below
[ 1171.913244] BUG: unable to handle page request at 00000000001067e38
[ 1171.913248] IP: cfg80211_
[ 1171.913971] __ieee80211_
[ 1171.914078] ieee80211_
[ 1171.914098] process_
[ 1171.914111] worker_
[ 1171.914122] kthread+0xf5/0x130
[ 1171.914132] ? process_
[ 1171.914140] ? kthread_
[ 1171.914152] ret_from_
Fix:
scan work function keeps running even after cancel_hw_scan() call.
Issue is resolved by calling cancel_work_sync().
Regression potential:
Ran driver_crash.sh for 100 times and didn't see the issue.
This bug is for tracking purposes only, please don't triage.
CVE References
description: | updated |
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
importance: | Undecided → Critical |
Changed in linux (Ubuntu Xenial): | |
status: | New → Confirmed |
importance: | Undecided → Critical |
summary: |
- Redpine: Observed kernel panic while when running wireless tests in + Redpine: Observed kernel panic while running wireless tests in regression mode |
Changed in linux (Ubuntu Xenial): | |
status: | Confirmed → Fix Committed |
Changed in linux (Ubuntu): | |
status: | Confirmed → Fix Released |
tags: | added: cscc |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1773410
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.