Jump to content


Photo

[2.6.32.9 kernel]: Working, call for testing

* * * * * 2 votes

  • Please log in to reply
60 replies to this topic

#41
errmsg

errmsg

    Regular

  • Members
  • PipPip
  • 55 posts
  • Gender:Male
  • Location:Kiev
  • Interests:Kernel
  • Devices:Liquid A1 hw_version=6
  • Twitter:@RomanYepishev
I gave that kmsg another look and I am afraid I was not able to find anything extremely wrong there, as if the system continued to work (or was halted completely @ 50177.672251 which was around 2013-06-20 08:50:07 UTC. Could you please share the list of installed applications and dmesg output after a fresh phone restart to make sure we have the same hardware configuration?
I believe I am missing the conditions to reproduce this issue.

Additonally please share bootmode_info the data from /sys/kernel/debug/acer_smem on the device after the crash:
# mount -t debugfs nodev /sys/kernel/debug
# cd /sys/kernel/debug/acer_smem
# cat bootmode_info

It would show the reason of system startup/restart in hex, as in
magic_num_1: a4bc385f
apps_boot_reason: 77665500

0x77665500 is "bootloader", see arch/arm/mach-msm/pm.c.

Edited by errmsg, 20 June 2013 - 05:51 PM.

  • 2
My Acer Liquid Wiki
Share your knowledge because your hard drives are mortal.

#42
zabulus

zabulus

    Newbie

  • Members
  • Pip
  • 24 posts
I've faced wake on lock problem again, but in this case the phone waked after some time. Ican confirm that problem is relates to wifi module. There was a open WIFI in cafe, and phone had problems with waking up, turns on after 10-20 seconds after power button pressed. I've turned WIFI down and unlocking got work back. I'll paste dmesg some time later, have problems with driver.

  • 0

#43
errmsg

errmsg

    Regular

  • Members
  • PipPip
  • 55 posts
  • Gender:Male
  • Location:Kiev
  • Interests:Kernel
  • Devices:Liquid A1 hw_version=6
  • Twitter:@RomanYepishev
Having performed a cleanup for android-msm-2.6.32 branch of codeaurora tree, here's another build of 2.6.32 which can be flashed on the device.
  • Device will wake up only when Power button is pressed (earlier it would wake up on all the hardware buttons)
  • Removed I2C lockup handling by acer. I've been testing this for 2 days and found no lockups, YMMV

I haven't done any more investigation of WiFi lockup since I can't get it reproduced for now.

  • 1
My Acer Liquid Wiki
Share your knowledge because your hard drives are mortal.

#44
errmsg

errmsg

    Regular

  • Members
  • PipPip
  • 55 posts
  • Gender:Male
  • Location:Kiev
  • Interests:Kernel
  • Devices:Liquid A1 hw_version=6
  • Twitter:@RomanYepishev
I believe I have finally reproduced the bug with lockup and it's not wifi issue, at least not immediately related.
I2C bus becomes broken which breaks everything that speaks I2C protocol - touchscreen, battery, AVR (keypad & LCD/Keypad LEDs), compass... and other stuff. I got it in the last kernel revision where I took out the I2C bus restart. Well, that means I need to put the code back in and make sure next time something like this happens I have much more debug info there.

Attached File  meme.jpg   41.45KB   4 downloads

Edited by errmsg, 24 June 2013 - 04:30 PM.

  • 3
My Acer Liquid Wiki
Share your knowledge because your hard drives are mortal.

#45
errmsg

errmsg

    Regular

  • Members
  • PipPip
  • 55 posts
  • Gender:Male
  • Location:Kiev
  • Interests:Kernel
  • Devices:Liquid A1 hw_version=6
  • Twitter:@RomanYepishev
@zabulus (and other interested parties) - could you please test this build: acer_a1-kernel-2013-06-25-2.6.32.9-i2c-g9319eb1-dirty-update.zip - it has Acer's changes (and a new default splashscreen :) ) which relate to resetting the bus only, and the bus suspend/transaction finish checks are dropped.
In case of bus failure it will print a message with "[bug #20]" text to help understanding whether that's actually that i2c bus bug or not.

It looks like some A1 component can drive MSM i2c bus into a problem and that component is no longer present in A4 - no workarounds there.

  • 0
My Acer Liquid Wiki
Share your knowledge because your hard drives are mortal.

#46
zabulus

zabulus

    Newbie

  • Members
  • Pip
  • 24 posts

"[bug #20]"

This text should appear in kmsg, am I right?

  • 0

#47
errmsg

errmsg

    Regular

  • Members
  • PipPip
  • 55 posts
  • Gender:Male
  • Location:Kiev
  • Interests:Kernel
  • Devices:Liquid A1 hw_version=6
  • Twitter:@RomanYepishev

This text should appear in kmsg, am I right?


Yes, that's correct. When I2C bus status becomes 0x2100 (an error condition, according to acer) it will print the message about this.

  • 0
My Acer Liquid Wiki
Share your knowledge because your hard drives are mortal.

#48
zabulus

zabulus

    Newbie

  • Members
  • Pip
  • 24 posts
Here is another crash using the latest "dirty" build. WiFi was turned off I've just made a call, tried to reply and phone had crashed.
http://pastebin.com/vQndpfpG
I was unable to mount acer_smem and dump the bootmode_info after crash.
"mount: No such device"

  • 0

#49
errmsg

errmsg

    Regular

  • Members
  • PipPip
  • 55 posts
  • Gender:Male
  • Location:Kiev
  • Interests:Kernel
  • Devices:Liquid A1 hw_version=6
  • Twitter:@RomanYepishev

Here is another crash using the latest "dirty" build. WiFi was turned off I've just made a call, tried to reply and phone had crashed.
http://pastebin.com/vQndpfpG
I was unable to mount acer_smem and dump the bootmode_info after crash.
"mount: No such device"


Hm, that's not good.
# cat /proc/version                                                            
Linux version 2.6.32.9-i2c-g9319eb1-dirty (abuild@biff) (gcc version 4.4.0 (GCC) ) #6 PREEMPT Tue Jun 25 08:10:44 UTC 2013
# mount -t debugfs nodev /sys/kernel/debug
# cd /sys/kernel/debug/acer_smem
# cat bootmode_info
magic_num_1: 1ef6f906
apps_boot_reason: 927e9b54

But what's even worse is the kernel not being aware about the reboot happening.

I will fix these in my init version as it looks like persist.radio is not readable/modifiable by rild: - These are uid 10001, which is the second non-privileged app user, not rild.
[  501.337006] init: sys_prop: permission denied uid:10001  name:persist.radio.mcc.ecclist
[  501.337827] init: sys_prop: permission denied uid:10001  name:persist.radio.mcc.ecclist.cata
[  501.350902] init: sys_prop: permission denied uid:10001  name:persist.radio.mcc.ecclist2
[  501.351303] init: sys_prop: permission denied uid:10001  name:persist.radio.mcc.ecclist2.cata

By any chance, just a stab in the dark, do you happen to be a "life:)" (MCC 255 MNC 06) subscriber?

Edited by errmsg, 26 June 2013 - 07:58 PM.

  • 0
My Acer Liquid Wiki
Share your knowledge because your hard drives are mortal.

#50
zabulus

zabulus

    Newbie

  • Members
  • Pip
  • 24 posts

Hm, that's not good.

# cat /proc/version
Linux version 2.6.32.9-i2c-g9319eb1-dirty (abuild@biff) (gcc version 4.4.0 (GCC) ) #6 PREEMPT Tue Jun 25 08:10:44 UTC 2013
# mount -t debugfs nodev /sys/kernel/debug
# cd /sys/kernel/debug/acer_smem
# cat bootmode_info
magic_num_1: 1ef6f906
apps_boot_reason: 927e9b54

But what's even worse is the kernel not being aware about the reboot happening.

I will fix these in my init version as it looks like persist.radio is not readable/modifiable by rild: - These are uid 10001, which is the second non-privileged app user, not rild.
[ 501.337006] init: sys_prop: permission denied uid:10001 name:persist.radio.mcc.ecclist
[ 501.337827] init: sys_prop: permission denied uid:10001 name:persist.radio.mcc.ecclist.cata
[ 501.350902] init: sys_prop: permission denied uid:10001 name:persist.radio.mcc.ecclist2
[ 501.351303] init: sys_prop: permission denied uid:10001 name:persist.radio.mcc.ecclist2.cata

By any chance, just a stab in the dark, do you happen to be a "life:)" (MCC 255 MNC 06) subscriber?

I've tried to mount from the terminal emulator on the phone, beacuse of troubles with the driver on home PC. I'll try to dump debug info via adb from another PC where drivers and adb works. Yes it was a problem with terminal emulator. Here is output:
magic_num_1: 00000003
apps_boot_reason: 90020000
Yes I do, it is a "life:)" cell provider.

Edited by zabulus, 27 June 2013 - 04:25 AM.

  • 0

#51
errmsg

errmsg

    Regular

  • Members
  • PipPip
  • 55 posts
  • Gender:Male
  • Location:Kiev
  • Interests:Kernel
  • Devices:Liquid A1 hw_version=6
  • Twitter:@RomanYepishev

Yes I do, it is a "life:)" cell provider.

Welcome to the club - Acer Liquid E Issues (ru). I wonder whether you were experiencing this earlier. I plugged in my life:) SIM yesterday, did some tests and found that I am no longer able to reproduce the crash on incoming call. It looks like that depends on Base Station, and currently I live in a completely different location from where I had this issue regularly (neither Acer nor life:) were helpful). Since the linux kernel is not aware about the reboot, there were no warnings of any kind in the logs, I believe it is a baseband CPU crash, leading to complete system reboot.

Have you ever had such kind of an issue before?

About the apps_boot_reason - now I need to find the reason/description mapping.

I am waiting for the parts to arrive to build a serial connector for these extra 5 pins in the USB port (our Liquid devices have a Nexus One-style debugging facility via its 10-pin mini USB) to debug this kind of baseband failure, but I can't get it to crash at this location, so that's would be a bit hard.

  • 1
My Acer Liquid Wiki
Share your knowledge because your hard drives are mortal.

#52
zabulus

zabulus

    Newbie

  • Members
  • Pip
  • 24 posts

Welcome to the club - Acer Liquid E Issues (ru). I wonder whether you were experiencing this earlier. I plugged in my life:) SIM yesterday, did some tests and found that I am no longer able to reproduce the crash on incoming call. It looks like that depends on Base Station, and currently I live in a completely different location from where I had this issue regularly (neither Acer nor life:) were helpful). Since the linux kernel is not aware about the reboot, there were no warnings of any kind in the logs, I believe it is a baseband CPU crash, leading to complete system reboot.

Have you ever had such kind of an issue before?

About the apps_boot_reason - now I need to find the reason/description mapping.

I am waiting for the parts to arrive to build a serial connector for these extra 5 pins in the USB port (our Liquid devices have a Nexus One-style debugging facility via its 10-pin mini USB) to debug this kind of baseband failure, but I can't get it to crash at this location, so that's would be a bit hard.

Ahaha, phone is even worse that I've imaginated.
Restarts on outgoing call, you've described in blog, I had earlier reproduced only on CM7-based firmwares. On CM9 worked fine.

  • 0

#53
zabulus

zabulus

    Newbie

  • Members
  • Pip
  • 24 posts
http://pastebin.com/KrSH1jTs
H
ere is another crash reproduced on hang call.

  • 0

#54
errmsg

errmsg

    Regular

  • Members
  • PipPip
  • 55 posts
  • Gender:Male
  • Location:Kiev
  • Interests:Kernel
  • Devices:Liquid A1 hw_version=6
  • Twitter:@RomanYepishev

http://pastebin.com/KrSH1jTs
Here is another crash reproduced on hang call.

Yes, looks like a baseband failure and APPS CPU is perfectly unaware. I guess I need to experiment with various reset switches in the kernel. I remember I've seen the possibility to reboot MODEM CPU only but leave APPS as is. Don't know whether it works but will check this nevertheless.

I've built a serial debug cable so it should be possible to get some more information regarding early kernel failures and hopefully at least some kind of info about the AMSS crash.

Posted Image


Yeah, my device lost the rubber cover for the miniUSB port :(

  • 1
My Acer Liquid Wiki
Share your knowledge because your hard drives are mortal.

#55
Ma7moud

Ma7moud

    Addict

  • Members
  • PipPipPipPipPip
  • 558 posts
  • Gender:Male
  • Location:Egypt
  • Devices:Acer Liquid A1
  • Twitter:@9_CanZ

Yeah, my device lost the rubber cover for the miniUSB port

:(


Mine too, a long time ago

Edited by Ma7moud, 01 July 2013 - 04:46 PM.

  • 0
Phone : Acer Liquid A1 (Color: Red)
BIN : 4.002.14.EMEA.GEN1

Recovery: TWRP
ROM : CM 7.2 (Ainillia version) (128MHz ~ 960MHz - Smartass V2) (Thanks lupohirp, Thepasto, Ainillia and the team)

#56
Mura88

Mura88

    Regular

  • Members
  • PipPip
  • 53 posts
  • Devices:Acer Liquid E Total Black

Mine too, a long time ago



Mine too ... I think we are a family larger than expected !!!

  • 0
Acer Liquid E@MaxPower: LNP 1.9.2 (2.3.7) /ADW Launcher EX 1.3.3.56 /Overclock 998Mhz/V6 Script 512HP [6-12-75-90-95-125]
now Acer Liquid E 512MB Black Best Rom: LiquidNext 1.6.1 (2.3.4)
ex Htc Magic 32A 288MB Black Best Rom: Ginger Yoshi 1.2 (2.3.4) + farmatito Kernel

#57
errmsg

errmsg

    Regular

  • Members
  • PipPip
  • 55 posts
  • Gender:Male
  • Location:Kiev
  • Interests:Kernel
  • Devices:Liquid A1 hw_version=6
  • Twitter:@RomanYepishev
Another kernel build - acer_a1-kernel-2013-07-03-2.6.32.9-gc8bbbee-update.zip. The only visible change is that all 11 MTD partitions from atag are provided to the kernel.
I've set the default timeout policy to reset the MODEM instead of APPS processor but it works in a weird way. Using reset-modem module I tried to reset modem/reset complete chip and each time APPS processor was restarted as well. I don't have a Qualcomm development board and it does not look like somebody has written anything about these reset options, so it looks like it's not possible to recover properly from the firmware bug acer left us with.

The fact that the CM9+ builds are OK may mean that it is a bug triggered by rild.

  • 2
My Acer Liquid Wiki
Share your knowledge because your hard drives are mortal.

#58
zabulus

zabulus

    Newbie

  • Members
  • Pip
  • 24 posts
Here is another bug with WiFi. When I turn on WiFi and try to browse, it turns off after a while. After 30 secs connects to the wifi spot again and so on.
Logcat and kmsg:
http://pastebin.com/YGExaHVF
http://pastebin.com/UtBFMEhg
In log look at records for 6:00-7:00 AM

  • 0

#59
alboz83

alboz83

    Enthusiast

  • Members
  • PipPipPip
  • 252 posts
  • Gender:Male
  • Devices:Samsung Galaxy Nexus
Guys my old but immortal acer liquid now is in the hand of my girlfriend. I flashed CM7 remix V4b but the battery drain is high and she tell me that she is not well. I see this kernel but i don't understant if is stable and if all works. And it's for froyo stock only, right? Thanks

  • 0

#60
errmsg

errmsg

    Regular

  • Members
  • PipPip
  • 55 posts
  • Gender:Male
  • Location:Kiev
  • Interests:Kernel
  • Devices:Liquid A1 hw_version=6
  • Twitter:@RomanYepishev

Guys my old but immortal acer liquid now is in the hand of my girlfriend. I flashed CM7 remix V4b but the battery drain is high and she tell me that she is not well. I see this kernel but i don't understant if is stable and if all works. And it's for froyo stock only, right? Thanks

Hello, yes, nobody has yet used this kernel to build a ROM so it is only usable with FroYo stock distro. You may also want to check whether the battery is about to die as this may not depend on the ROM.

  • 0
My Acer Liquid Wiki
Share your knowledge because your hard drives are mortal.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users