Closed Bug 814279 Opened 12 years ago Closed 6 years ago

[wifi] Wifi goes crazy after being plugged in

Categories

(Firefox OS Graveyard :: Wifi, defect, P1)

x86
Gonk (Firefox OS)
defect

Tracking

(blocking-basecamp:-)

RESOLVED WONTFIX
B2G C3 (12dec-1jan)
blocking-basecamp -

People

(Reporter: mrbkap, Unassigned)

References

Details

(Keywords: foxfood, unagi)

Attachments

(1 file)

I've only seen this once on my Unagi device and once (I think) on Faramarz's Unagi. I left my phone plugged in and connected to the Mozilla Guest network overnight. The next morning, I turned the screen on to find us connected but without DHCP and that DHCP was off entirely. Logcat showed the following:

  * After a couple of hours, the phone seemed to go into a semi-hibernated mode. There's a timer that runs in the wifi code that's supposed to fire every 5 seconds. This timer was firing once an hour (at the same time as a bunch of some other Gecko activity, such as RIL waking up).
  * When I turned the screen on, things woke up. It appeared that the interface had disabled itself. As a result (?) wpa_supplicant thought that the network had gotten extremely weak and activated the SeamLess roaming code, which disconnected us. Then, when the SeamLess code realized that there was no other network to connect to, it reconnected to the original network, except that DHCP failed. The final link of failure is that the "reassociate" command didn't cause us to disconnect and reconnect, it simply reauthenticated and so we didn't try to start DHCP.

The final sentence there is a separate bug in its own right, which I'll file separately. I'm filing this bug to investigate the odd frozen-in-time behavior that I saw on my Unagi while it was plugged in.

I suspect that the reason that we failed to run DHCP was that the network interface was in a bad (not RUNNING) state. That also needs investigation.
Severity: critical → normal
Attached file logcat
Here's the full logcat showing the sequence of events.
blocking-basecamp: ? → +
Blake, are you investigating?  Do we have enough info to continue to block on it?
Flags: needinfo?(mrbkap)
Assigning to Blake while he investigates/consults with our friends.
Assignee: nobody → mrbkap
Waiting on more information from our friends now.
Flags: needinfo?(mrbkap)
Component: General → Wifi
Target Milestone: --- → B2G C3 (12dec-1jan)
With not a lot of traction, dropping as a blocker for now.  If this can be reproduced or we get worrying info from the friends, renom.
blocking-basecamp: + → -
Assignee: mrbkap → nobody
blocking-b2g: --- → backlog
blocking-b2g: backlog → ---
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: