← Back to team overview

group.of.nepali.translators team mailing list archive

[Bug 1773410] Re: Redpine: Observed kernel panic while when running wireless tests in regression mode

 

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: linux (Ubuntu Xenial)
       Status: New => Confirmed

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1773410

Title:
  Redpine: Observed kernel panic while when running wireless tests in
  regression mode

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed

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_scan_done+0xb0/0xc0 [cfg80211]
         [ 1171.913971]  __ieee80211_scan_completed+0xb1/0x390 [mac80211]
         [ 1171.914078]  ieee80211_scan_work+0x7e/0x480 [mac80211]
         [ 1171.914098]  process_one_work+0x142/0x3d0
         [ 1171.914111]  worker_thread+0x229/0x440
         [ 1171.914122]  kthread+0xf5/0x130
         [ 1171.914132]  ? process_one_work+0x3d0/0x3d0
         [ 1171.914140]  ? kthread_associate_blkcg+0x90/0x90
         [ 1171.914152]  ret_from_fork+0x35/0x40

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773410/+subscriptions