Software Archive
Read-only legacy content

Probably data corruption

Fabio_R_1
Beginner
1,812 Views

 

Executive summary.

Stability issue (probably) related to data corruption. (App and services hang)

Apps suddenly disappears and still missing after factory reset.

Tablet stops booting after few days of normal usage. (stuck with Intel logo right after Android boot animation)

Re-flash always fixes every issue until next instability.

We think there is a data corruption problem behind every issue, possibly caused by BIOS or eMMC Firmware bug or Kernel bug.

Technical information

Tablets' specs are:

9.7" display 4:3 (2048x1536)

SoC Intel Bay Trail Z3736F

2GB DDR3 Samsung

32 GB eMMC storage 

3G by Fibocom H350

AP6630 Wi-Fi/BT module

G-sensor Kyonix

8.000 mAh LiPo battery

 

I attach some logs.

Why happen this issue ? System BIOS problems ?

Thanks for your help.

0 Kudos
5 Replies
Alexander_W_Intel
1,812 Views

Hi,

it looks like your file system get's mounted read only at some point. This us usually caused by file system errors. Reflashing usually recreates the file system so if the errors come again multiple times you might have a hardware related issue. I think it's unlikely that a BIOS or eMMC Firmware bug is causing this as it would be came up during manufacturer tests or would be seen by more people. 

What is the name of the tablet?

Thanks,
Alex

0 Kudos
Fabio_R_1
Beginner
1,812 Views

Hi Alexander, you're very kind, really.

The tablet is a variant of Teclast X98 Air 3G. Factory wrote us that there isn't hardware issue, but the issue is caused by some apk that you saw in the _App_list.txt

What do you mean when you say <<you might have a hardware related issue>> ?

You mean eMMC (Foresee  NCEFBS98-32G) issue or board issue ?

Can you exclude from our logs that there is an issue caused by our apk ?

Thanks a lot for your precious support.

Bye.


F. 

 

 

0 Kudos
Alexander_W_Intel
1,812 Views

Hi,

Normal applications (not root) should not be able to cause the file system to be remount read only. In the case it happens the next time, can you connect with adb to it and copy the output of "dmesg"? 

Are you working for an OEM?

Thanks,
Alex

0 Kudos
Fabio_R_1
Beginner
1,812 Views

Hi Alex,

in attached you will find complete output : catlog and dmesg.

Yes, i working for an OEM.

Factory wrote us that the problem is lowmemorykill  :-)

Thanks for your attention.

F.

0 Kudos
Alexander_W_Intel
1,812 Views

Hi,

can you send me an email to alexander.weggerle@intel.com? 

The dmesg output is from a fresh booted device and not from one which is actually showing the error :-). Interesting is the dmesg output when the problem appears the first time. 

Thanks,
Alex

0 Kudos
Reply