993098 - [Tarako] kernel enters sysdump when searching for networks under Wi-Fi and disconnecting USB cable

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Vendcom, defect)

Description

[Tony Nguyen]

Attachment: sysdump.tgz

When inside the Settings App I disabled and enabled the Wi-Fi switch to refresh the "Available networks" list. While the list was refreshing, I pulled out the USB cable.

Prerequisite:
- Have device connected with USB cable to a computer

Steps to Repro:
1. Update Tarako to BuildID: 20140407004001
2. Navigate to Settings App
3. Tap on Wi-Fi
4. Tap on switch to disable/enable Wi-Fi
5. While DUT is searching for Wi-Fi, disconnect the USB cable

Actual Results:
DUT enters sysdump

Expected
DUT doesn't enter sysdump

See Attached: sysdump.tgz

Comment 1

[Jason Smith [:jsmith]]

What do you mean by entering sysdump here? Screenshot?

Comment 2

[John Hammink]

FWIW, I've tried testing this on two devices (one using PVT build; the other using Taipei build) and am unable to repro this.   Tony, could you provide more information?  A video could be helpful.

Gaia      fbf194db193f12b0db070c87bc99f6bb42e28dc0
Gecko     0acb0c844e4ce40dcc625496bbe6ecb8d899ef05
BuildID   20140407060052
Version   28.1
ro.build.version.incremental=83

Comment 3

[Tony Nguyen]

Attachment: sysdump.core.00

The DUT went to a black screen with red text displaying that it was doing a sysdump to the SD card. I've been unable to reproduce the issue after further investigating with the same Tarako device and therefore cannot provide a video or screenshot. 

There was also a sysdump.core.00 file in the SD card that I didn't attach and will be attaching it now in hopes that it will provide additional information.

Comment 4

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

He has a system dump.  I asked him to file this bug so that OEM can take a look at the system dump.

Steve can you pass this to the vendor please to look at the dump?

Comment 5

[Steven Yang [:styang]]

Hi Alan, could you help to take a look? please ni? James.Zhang if it's caused by partners' module. thanks!

Comment 6

[Alan Huang]

This sounds like a ram dump.

Comment 7

[James Zhang (Spreadtrum)]

Loop Xinhe and Lianxiang, it's system dump.

Comment 8

[James Zhang (Spreadtrum)]

We need sysdump.core.01_0x00000000-0x07ffffff_dump.lst.

If you found "Crash key" keywords in the file, see bug 994802. The crash key is for debug only to catch system lockup.

Comment 9

[Peter Bylenga [:PBylenga]]

That file, sysdump.core.01_0x00000000-0x07ffffff_dump.lst, is attachment 8402868 [details].  It's been compressed in order to attach it due to size.

Comment 10

[Zhou Lianxiang]

(In reply to Peter Bylenga from comment #9)
> That file, sysdump.core.01_0x00000000-0x07ffffff_dump.lst, is attachment
> 8402868 [details].  It's been compressed in order to attach it due to size.

The file sysdump.core.01_0x00000000-0x07ffffff_dump.lst is very large, it is about 128m, the attachment only 45b. We can not parse the crash without sysdump file.

Comment 11

[BMO Automation]

Firefox OS is not being worked on