[DELL][BIONICS] Observed firmware assert during backgroung scan.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned | ||
Bionic |
New
|
Undecided
|
Unassigned | ||
linux-oem (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bionic |
Invalid
|
Undecided
|
Ganapathi Raju Kondraju |
Bug Description
SRU Justification:
------------------
Impact:
-------
Observed firmware assert(non responsive state) just 2 min after connection.
Test case:
----------
1) Power up the device, Redpine modules are loaded by default, Nmcli initiates the connection and device starts background scan after connection. After 2-3 min issue will be replicated.
Result:
-------
Observed firmware assert while performing background scan.
Root cause analysis:
-------
There is a redundant null check for ssid info while preparing
probe request in background scan case, which blocks the probe request pkt
length update, leads to assert no-71(if probe-req-length is 0 or greater
the max probe length 120) in firmware.
Fix:
----
Removed the redundant null check.
Regression Potential:
-------
This is observed just 2 min after connection, fixed and checked the driver stability. Every thing ran smooth.
summary: |
- [DELL][BIONICS] Observed firmware assert during backgroung scanning. + [DELL][BIONICS] Observed firmware assert during backgroung scan. |
tags: | added: patch |
Changed in linux-oem (Ubuntu Bionic): | |
status: | New → Fix Committed |
Changed in linux-oem (Ubuntu Bionic): | |
status: | Invalid → Fix Committed |
assignee: | nobody → Ganapathi Raju Kondraju (ganapathiraju) |
Changed in linux-oem (Ubuntu Bionic): | |
status: | Fix Committed → Invalid |
Changed in linux-oem (Ubuntu): | |
status: | New → Invalid |
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 1848318
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.