Related
Hey everyone,
I am having a strange problem with my sd-ext (ext4) partition for some time now.
The ROM I am using is ICS for Desire by Sandvold (Amarullz and a2sd), but I don't know whether this is strictly ROM related or not.
I have been getting some mass FCs over and over again, across different versions flashed after full wipes.
Today I found out that the problem is that the sd-ext partition is not properly mounted (read-only), but here is the weird part: it is properly mounted (read-write) using the recovery and is also properly mounted before I unlock the sim-card.
When I unlock the sim-card or otherwise change the connectivity (WLAN, mobile data, airplane mode) it remounts sd-ext as read-only.
I have already tried reformatting and repartioning the sd-card.
Any idea why the system is doing that or how I can prevent that from happening?
Thanks
\Update1:
Here is a part of dmesg, showing the error when I unlock the sim-card after a fresh reboot:
Code:
<6>[ 182.512451] active wake lock PowerManagerService
<6>[ 182.512481] active wake lock vbus_present
<6>[ 182.512481] active wake lock SMD_DS, time left 35
<6>[ 182.512481] [R] early_suspend end
<6>[ 190.756866] batt: 74%, 3884 mV, 290 mA (210 avg), 29.8 C, 1008 mAh
<3>[ 191.665740] mmc1: Data CRC error
<3>[ 191.665954] msmsdcc_data_err: opcode 0x00000019
<3>[ 191.666168] msmsdcc_data_err: blksz 512, blocks 16
<3>[ 191.666595] mmc1: DMA channel flushed (0x80000004)
<3>[ 191.666839] Flush data: 0000c003 3b2d8018 00000000 00400040 00370035 00008003
<6>[ 191.667266] mmc1: Controller has been re-initialiazed
<3>[ 191.672515] mmcblk0: error -84 transferring data, sector 6710376, nr 16, card status 0x900
<3>[ 191.672973] mmc1: Data timeout
<6>[ 191.673217] mmc1: Controller has been re-initialiazed
<3>[ 191.673797] end_request: I/O error, dev mmcblk0, sector 6710376
<3>[ 191.674041] end_request: I/O error, dev mmcblk0, sector 6710384
<3>[ 191.679138] Aborting journal on device mmcblk0p2-8.
<0>[ 191.687255] journal commit I/O error
<2>[ 191.726745] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:276: Detected aborted journal
<2>[ 191.727478] EXT4-fs (mmcblk0p2): Remounting filesystem read-only
<3>[ 191.984802] binder: 1268: binder_alloc_buf, no vma
<6>[ 191.985046] binder: 206:339 transaction failed 29201, size 4-0
<6>[ 191.985412] binder: send failed reply for transaction 79996 to 1268:1268
The weird thing is that I have been running the phone without any problem in airplane mode + WLAN for a whole day, until I tried to reactivate mobile connection again and do some tests with it.
It seems that the system only has a problem with the journal when it uses the mobile connection.
\Update2:
Here the dmesg message before I unlock the sim-card. No error message for sd-ext:
Code:
<6>[ 13.084991] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: noauto_da_alloc,data=ordered,commit=15,barrier=1,nouser_xattr,errors=continue
4EXT is also unable to find any errors with the sd-ext partition (I have used the recovery to format and partition the sd-card).
\Update3:
Ok I just reformatted and repartitioned the sdcard again using gparted and reflashed the ROM with a full wipe.
I am getting the same error again.
Hey guys, was just wondering..
What hardware changes are made in new WFS's ??
I think, there is something new in screen or GPU, because:
- CWM recovery 5.0.2.x recovery is with blank screen
- CWM Recovey 6.0.x.x doesn't work at all
- CM7 and CM9 build-in kernels doesn't start
- after replace kernel CM's roms starts, but touchscreen and 4 bottom buttons doesn't work
- old versions of CM7 starts, but screen is blank all the time (rom and touch works - I see this in [email protected])
I think there are changes in BOOT section of CM's - I wonder if it is possible to replace boot section and kernel from stock 2.3.5 rom.
Maybe then touchscreen will be working.
Maybe HTC provides some technical data about hardware changes in WFS's ???
dmesg log
As is described here http://forum.xda-developers.com/showpost.php?p=29846194&postcount=31 with adb shell dmesg command I got this log file.Hope it helps.I can't yet post in dev section.And thank you,Marchelius because I was planning to try CM7,but for now I stay with same ROM as you.I put other 2 dmesg logs which was made in recovery.
Bravo!
sorinaugusto said:
As is described here http://forum.xda-developers.com/showpost.php?p=29846194&postcount=31 with adb shell dmesg command I got this log file.Hope it helps.I can't yet post in dev section.And thank you,Marchelius because I was planning to try CM7,but for now I stay with same ROM as you.I put other 2 dmesg logs which was made in recovery.
Click to expand...
Click to collapse
This should help narrow down the issue so the community can come up with a fix for these devices. Which kernel/ROMs are users of these devices able to use without display issues?
WoefulDerelict said:
This should help narrow down the issue so the community can come up with a fix for these devices. Which kernel/ROMs are users of these devices able to use without display issues?
Click to expand...
Click to collapse
I think every stock GB will be work. I tried 2.13 and 2.26 stock roms and works fine.
EQDKP roms works too - I tried v4.7 v4,0 and v5.0 deodexed. I think, roms like wildchild etc. will be work OK.
I used kernels : Dust, Jikantu and Cake - all of them work OK
With AOKP, CM7 and CM9 i tried Cake kernel - after replace roms starts, but still is problem with screen.
I tried replace boot.img from stock rom and apply to CM9 - flashed OK, but roms doesn't work - still had startup logo and phone freeze after few minutes.
More logs would be really helpful!
marchelius said:
I think every stock GB will be work. I tried 2.13 and 2.26 stock roms and works fine.
EQDKP roms works too - I tried v4.7 v4,0 and v5.0 deodexed. I think, roms like wildchild etc. will be work OK.
I used kernels : Dust, Jikantu and Cake - all of them work OK
With AOKP, CM7 and CM9 i tried Cake kernel - after replace roms starts, but still is problem with screen.
I tried replace boot.img from stock rom and apply to CM9 - flashed OK, but roms doesn't work - still had startup logo and phone freeze after few minutes.
Click to expand...
Click to collapse
So, ROMS based around the stock HTC kernels and software boot without display issues but, completely custom firmware and kernels are a mixed bag? As I understand it Dust, Jikantu and Cake kernels are extended drop-in replacements for ROMs based around the stock GB releases and those all work fine. Have you managed to get any CM7 ports working with a replacement kernel? Are all the AOKP ports you've tried ICS based?
I don't imagine you'll have much luck plugging a GB kernel into an ICS rom like CM9. There were a number of changes in the way Android expects it's hardware to be presented between Gingerbread and Ice Cream Sandwich that would keep it from working properly; however, most of the work is still based off the kernel source released by HTC.
In your experiments with AOKP, CM7 and CM9 you say that after replacing the kernel with one that worked in a stock GB ROM it booted but, the display still didn't properly initialise? Could you still poke the device through ADB? If it's responsive a logcat and dmesg would be extremely helpful.
---------- Post added at 04:20 PM ---------- Previous post was at 03:53 PM ----------
There are two types of log you can generate that would be extremely helpful in tracking down this issue: dmesg and logcat. In this situation dmesg is likely our greatest ally. Dmesg contains all of the kernel degugging messages which will allow developers to look for errors from the kernel regarding the display. Logs from healthy systems and broken systems can be equally utilitarian in tracking down what's happening with your devices.
You can pull a dmesg from any device that has successfully booted and has adb running even if it hasn't initialised the display properly. The basic command looks like this.
Code:
adb shell dmesg
To make it easier to share this information you can redirect the output to a text file in the working directory using >. This works in both windows and *nix. Should you choose you can also specify a path for the command to drop the file into.
Code:
adb shell dmesg > dmesg.txt
If users wouldn't mind naming them dmesgDisplayOK.txt and dmesgDislayFAIL.txt depending on if the display was properly initialised when the log was generated I'd certainly appreciate it.
If you've successfully booted a ROM the system will also supply logcat data which can be collected by the following command. As with the previous command this will also direct the output to the specified location. Most recovery software doesn't start logcat.
Code:
adb logcat > logcat.txt
As with dmesg I'd appreciate easily identifiable names like logcatDisplayOK.txt and logcatDisplayFAIL.txt to help developers.
If you've booted a recovery distribution most keep their own logs. This file is most often hidden in /tmp and called recovery.log. You can pull this file using the following command and it will drop it into your current working directory. Should you choose it will also accept a destination path.
Code:
adb pull /tmp/recovery.log
The more information about the software you were running at the time the logs were generated you can include the better.
Points of interest...
When browsing the recovery logs submitted by sorinaugusto I've spotted 3 points of interest.
The first revolves around the Cypress C8YC_TMA touch-screen driver. This is the digitiser that handles touch input and I believe it is common to all WFS devices. I can see it being used in the first log, which if I don't miss my guess if from a happy functioning ROM boot, and it isn't complaining; however, in recovery it generates this:
Code:
<6>[ 6.278259] cy8c_ts_init: enter
<7>[ 6.278686] cy8c_ts_probe: enter
<6>[ 6.278869] marvel_ts_cy8c_power():
<6>[ 6.337188] CY8CTMA340 0-0067: buf: 11, 0, 0, 15
<6>[ 6.337402] CY8CTMA340 0-0067: application verion = 15, x_channel = F, y_channel = A
<6>[ 6.476348] CY8CTMA340 0-0067: orient: 0
<6>[ 6.476654] input_set_abs_params: mix_x 0, max_x 1023, min_y 0, max_y 940
<6>[ 6.477264] input: cy8c-touchscreen as /devices/virtual/input/input1
<6>[ 6.477905] CY8CTMA340 0-0067: Start touchscreen cy8c-touchscreen in interrupt mode
<3>[ 6.478393] msm_i2c msm_i2c.0: error, status c8 (48,81,00)(67,00,00)(cnt:1,pos:0)
<3>[ 6.478790] msm_i2c msm_i2c.0: Error during data xfer (-5)(48,81,00)
<3>[ 6.489501] msm_i2c msm_i2c.0: error, status c8 (48,81,00)(48,81,00)(cnt:1,pos:0)
<3>[ 6.490264] msm_i2c msm_i2c.0: Error during data xfer (-5)(48,81,00)
<3>[ 6.500762] msm_i2c msm_i2c.0: error, status 43c8 (48,81,00)(48,81,00)(cnt:1,pos:0)
<3>[ 6.501007] msm_i2c msm_i2c.0: Error during data xfer (-5)(48,81,00)
<3>[ 6.511474] msm_i2c msm_i2c.0: error, status 83c8 (48,81,00)(48,81,00)(cnt:1,pos:0)
<3>[ 6.511871] msm_i2c msm_i2c.0: Error during data xfer (-5)(48,81,00)
<3>[ 6.522186] msm_i2c msm_i2c.0: error, status 83c8 (48,81,00)(48,81,00)(cnt:1,pos:0)
<3>[ 6.522583] msm_i2c msm_i2c.0: Error during data xfer (-5)(48,81,00)
<3>[ 6.532867] msm_i2c msm_i2c.0: error, status 83c8 (48,81,00)(48,81,00)(cnt:1,pos:0)
<3>[ 6.533264] msm_i2c msm_i2c.0: Error during data xfer (-5)(48,81,00)
<3>[ 6.543762] msm_i2c msm_i2c.0: error, status 83c8 (48,81,00)(48,81,00)(cnt:1,pos:0)
<3>[ 6.543975] msm_i2c msm_i2c.0: Error during data xfer (-5)(48,81,00)
<3>[ 6.554443] msm_i2c msm_i2c.0: error, status 83c8 (48,81,00)(48,81,00)(cnt:1,pos:0)
<3>[ 6.554840] msm_i2c msm_i2c.0: Error during data xfer (-5)(48,81,00)
<3>[ 6.565155] msm_i2c msm_i2c.0: error, status 83c8 (48,81,00)(48,81,00)(cnt:1,pos:0)
<3>[ 6.565551] msm_i2c msm_i2c.0: Error during data xfer (-5)(48,81,00)
<3>[ 6.575866] msm_i2c msm_i2c.0: error, status 83c8 (48,81,00)(48,81,00)(cnt:1,pos:0)
<3>[ 6.576263] msm_i2c msm_i2c.0: Error during data xfer (-5)(48,81,00)
<3>[ 6.587097] i2c_write_block retry over 10
The second blob relates directly to the display. Sadly these are the only complaints I'm spotting and it doesn't help me pinpoint the problem.
Code:
<4>[ 10.137237] [DISP]msmfb_pan_display timeout rerequest vsync
<4>[ 10.467163] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
<4>[ 11.117218] [DISP]msmfb_pan_display timeout rerequest vsync
<4>[ 11.447174] [DISP]msmfb_pan_display timeout waiting for frame start, 2 1
The final group of issues that caught my eye is probably the least transparent.
Code:
<3>[ 65.897521] BUG: sleeping function called from invalid context at mm/slab.c:3102
<3>[ 65.897521] in_atomic(): 1, irqs_disabled(): 128, pid: 0, name: swapper
<4>[ 65.897521] Backtrace:
<4>[ 65.897521] [<c0036a3c>] (dump_backtrace+0x0/0x114) from [<c0405ea0>] (dump_stack+0x18/0x1c)
<4>[ 65.897521] r7:000000d0 r6:000080d0 r5:da8000c0 r4:c051ed70
<4>[ 65.897521] [<c0405e88>] (dump_stack+0x0/0x1c) from [<c006ac48>] (__might_sleep+0x108/0x128)
<4>[ 65.897521] [<c006ab40>] (__might_sleep+0x0/0x128) from [<c00d87f8>] (kmem_cache_alloc+0x34/0x108)
<4>[ 65.897521] r4:c051dde0
<4>[ 65.897521] [<c00d87c4>] (kmem_cache_alloc+0x0/0x108) from [<c00d4950>] (__get_vm_area_node+0xac/0x128)
<4>[ 65.897521] r7:000000d0 r6:00002000 r5:00000001 r4:c051dde0
<4>[ 65.897521] [<c00d48a4>] (__get_vm_area_node+0x0/0x128) from [<c00d4a68>](get_vm_area_caller+0x4c/0x58)
<4>[ 65.897521] [<c00d4a1c>] (get_vm_area_caller+0x0/0x58) from [<c0039718>] (__arm_ioremap_pfn_caller+0x64/0x164)
<4>[ 65.897521] [<c00396b4>] (__arm_ioremap_pfn_caller+0x0/0x164) from [<c0039898>] (__arm_ioremap_caller+0x60/0x68)
<4>[ 65.897521] [<c0039838>] (__arm_ioremap_caller+0x0/0x68) from [<c00398b4>] (__arm_ioremap+0x14/0x18)
<4>[ 65.897521] r5:00000001 r4:c055f9e4
<4>[ 65.897521] [<c00398a0>] (__arm_ioremap+0x0/0x18) from [<c003c250>] (__msm_ioremap+0x28/0x2c)
<4>[ 65.897521] [<c003c228>] (__msm_ioremap+0x0/0x2c) from [<c003d118>] (write_to_strongly_ordered_memory+0x48/0x6c)
<4>[ 65.897521] [<c003d0d0>] (write_to_strongly_ordered_memory+0x0/0x6c) from[<c003c220>] (l2x0_suspend+0x12c/0x134)
<4>[ 65.897521] r5:00000001 r4:00000002
<4>[ 65.897521] [<c003c0f4>] (l2x0_suspend+0x0/0x134) from [<c0058118>] (msm_sleep+0x2d4/0x598)
<4>[ 65.897521] [<c0057e44>] (msm_sleep+0x0/0x598) from [<c005869c>] (arch_idle+0x294/0x420)
<4>[ 65.897521] [<c0058408>] (arch_idle+0x0/0x420) from [<c0033a74>] (default_idle+0x28/0x30)
<4>[ 65.897521] [<c0033a4c>] (default_idle+0x0/0x30) from [<c02d1df4>] (cpufreq_idle+0x20/0x6c)
<4>[ 65.897521] [<c02d1dd4>] (cpufreq_idle+0x0/0x6c) from [<c0033d38>] (cpu_idle+0x50/0xa8)
<4>[ 65.897521] r7:c051fa00 r6:c055f844 r5:c051fa08 r4:c051c000
<4>[ 65.897521] [<c0033ce8>] (cpu_idle+0x0/0xa8) from [<c0402c1c>] (rest_init+0xc0/0xe4)
<4>[ 65.897521] r7:c051fa00 r6:c0028014 r5:00000000 r4:c051c000
<4>[ 65.897521] [<c0402b5c>] (rest_init+0x0/0xe4) from [<c0008a24>] (start_kernel+0x288/0x2ec)
<4>[ 65.897521] r5:00000000 r4:c05e7680
<4>[ 65.897521] [<c000879c>] (start_kernel+0x0/0x2ec) from [<12c08034>] (0x12c08034)
<3>[ 245.957336] INFO: task rpcrouter:18 blocked for more than 120 seconds.
<3>[ 245.957824] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
<6>[ 245.958679] rpcrouter D c04067cc 0 18 2 0x00000000
<4>[ 245.960021] Backtrace:
<4>[ 245.961364] [<c0406124>] (schedule+0x0/0x7d4) from [<c00471f4>] (rr_read+0x178/0x1a4)
<4>[ 245.961883] [<c004707c>] (rr_read+0x0/0x1a4) from [<c00473ac>] (do_read_data+0x1c/0x7d0)
<4>[ 245.962799] [<c0047390>] (do_read_data+0x0/0x7d0) from [<c0083ab8>] (worker_thread+0x18c/0x23c)
<4>[ 245.963653] r8:da0c5f84 r7:da0a3788 r6:c0047390 r5:da0a3780 r4:da0c4000
<4>[ 245.966400] [<c008392c>] (worker_thread+0x0/0x23c) from [<c00878b4>] (kthread+0x84/0x8c)
<4>[ 245.967346] [<c0087830>] (kthread+0x0/0x8c) from [<c0074184>] (do_exit+0x0/0x6b0)
<4>[ 245.968200] r7:00000013 r6:c0074184 r5:c0087830 r4:da82fd70
<3>[ 365.967346] INFO: task rpcrouter:18 blocked for more than 120 seconds.
<3>[ 365.968231] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
<6>[ 365.969085] rpcrouter D c04067cc 0 18 2 0x00000000
<4>[ 365.970428] Backtrace:
<4>[ 365.971405] [<c0406124>] (schedule+0x0/0x7d4) from [<c00471f4>] (rr_read+0x178/0x1a4)
<4>[ 365.972290] [<c004707c>] (rr_read+0x0/0x1a4) from [<c00473ac>] (do_read_data+0x1c/0x7d0)
<4>[ 365.973205] [<c0047390>] (do_read_data+0x0/0x7d0) from [<c0083ab8>] (worker_thread+0x18c/0x23c)
<4>[ 365.973693] r8:da0c5f84 r7:da0a3788 r6:c0047390 r5:da0a3780 r4:da0c4000
<4>[ 365.976806] [<c008392c>] (worker_thread+0x0/0x23c) from [<c00878b4>] (kthread+0x84/0x8c)
<4>[ 365.977752] [<c0087830>] (kthread+0x0/0x8c) from [<c0074184>] (do_exit+0x0/0x6b0)
<4>[ 365.978240] r7:00000013 r6:c0074184 r5:c0087830 r4:da82fd70
I have the original source code from HTC along with the newest code from the Cryptomilk git but, I could use more data to help me trace this issue back to it's origin.
Any update guys?
Caro332 said:
Any update guys?
Click to expand...
Click to collapse
I'd like to know, too. I have been looking every day through internet for the solution - all are quiet. Seems like there is a little amount of people with WFS 2012 who want custom roms... Others don't bother. Why then HTC offers us unlocking of our bootloader if there is no alternative left?
marchelius said:
Hey guys, was just wondering..
What hardware changes are made in new WFS's ??
I think, there is something new in screen or GPU, because:
- CWM recovery 5.0.2.x recovery is with blank screen
- CWM Recovey 6.0.x.x doesn't work at all
- CM7 and CM9 build-in kernels doesn't start
- after replace kernel CM's roms starts, but touchscreen and 4 bottom buttons doesn't work
- old versions of CM7 starts, but screen is blank all the time (rom and touch works - I see this in [email protected])
I think there are changes in BOOT section of CM's - I wonder if it is possible to replace boot section and kernel from stock 2.3.5 rom.
Maybe then touchscreen will be working.
Maybe HTC provides some technical data about hardware changes in WFS's ???
Click to expand...
Click to collapse
Marchelius try the CWM in this post http://forum.xda-developers.com/showthread.php?t=1997465&page=3 as it worked for me
I have a wfs 2011 but whenever I flash cm Rom it boots okay but the screen remain unresponsive to touch.
please someone should help me .
Anyone else have a problem with USB host mode and copying big files?
If so, can we fix this?
I have tried formatting my drive in FAT32,NTFS, and ext2. But the result is always the same, the drive dies if I copy a file bigger than 30 or 40 MB. I have tried stock, Faux123, and francoKernel as well.
The drive doesn't die at a specific MB each time, but it is generally around 30 MB but sometimes makes it to 80 or even 140 MB one time. I am trying to off-load some 700MB movies.
Here is the kernel message error:
<6>[ 1920.842529] max17040 4-0036: online = 1 vcell = 3547500 soc = 22 status = 3 health = 1 temp = 370 charger status = 0
<3>[ 1926.574005] EXT4-fs (sda1): Unrecognized mount option "fmask=0702" or missing value
<3>[ 1926.594299] EXT4-fs (sda1): Unrecognized mount option "fmask=0702" or missing value
<3>[ 1926.649810] EXT4-fs (sda1): Unrecognized mount option "fmask=0702" or missing value
<3>[ 1927.740753] EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities
<6>[ 1927.773895] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem
<6>[ 1927.938781] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null)
<3>[ 1968.389251] L3 CUSTOM SRESP error with SOURCEMM2 info=0x84
<4>[ 1968.389434] ------------[ cut here ]------------
<4>[ 1968.389739] WARNING: at arch/arm/mach-omap2/omap_l3_noc.c:130 l3_interrupt_handler+0x31c/0x360()
<4>[ 1968.390045] L3 custom sresp error
<4>[ 1968.390197] Modules linked in:
<4>[ 1968.390686] [<c0055de4>] (unwind_backtrace+0x0/0xf8) from [<c00983a8>] (warn_slowpath_common+0x4c/0x64)
<4>[ 1968.390991] [<c00983a8>] (warn_slowpath_common+0x4c/0x64) from [<c0098454>] (warn_slowpath_fmt+0x30/0x40)
<4>[ 1968.391326] [<c0098454>] (warn_slowpath_fmt+0x30/0x40) from [<c0074898>] (l3_interrupt_handler+0x31c/0x360)
<4>[ 1968.391632] [<c0074898>] (l3_interrupt_handler+0x31c/0x360) from [<c00d45fc>] (handle_irq_event_percpu+0x50/0x178)
<4>[ 1968.391967] [<c00d45fc>] (handle_irq_event_percpu+0x50/0x178) from [<c00d4760>] (handle_irq_event+0x3c/0x5c)
<4>[ 1968.392150] [<c00d4760>] (handle_irq_event+0x3c/0x5c) from [<c00d6aec>] (handle_fasteoi_irq+0xbc/0x164)
<4>[ 1968.392456] [<c00d6aec>] (handle_fasteoi_irq+0xbc/0x164) from [<c00d3f50>] (generic_handle_irq+0x2c/0x40)
<4>[ 1968.392791] [<c00d3f50>] (generic_handle_irq+0x2c/0x40) from [<c004904c>] (asm_do_IRQ+0x4c/0xac)
<4>[ 1968.393096] [<c004904c>] (asm_do_IRQ+0x4c/0xac) from [<c004eb08>] (__irq_svc+0x48/0xe4)
<4>[ 1968.393402] Exception stack(0xc0799f28 to 0xc0799f70)
<4>[ 1968.393554] 9f20: c0799f70 3b9aca00 4c534d85 000001ca 4c4bda2c 000001ca
<4>[ 1968.393859] 9f40: 000003ff c1192210 8000406a 412fc09a 00000000 00000000 00000000 c0799f70
<4>[ 1968.394042] 9f60: c007c690 c0068380 00000013 ffffffff
<4>[ 1968.394348] [<c004eb08>] (__irq_svc+0x48/0xe4) from [<c0068380>] (omap4_enter_idle_wfi+0x48/0xd4)
<4>[ 1968.394683] [<c0068380>] (omap4_enter_idle_wfi+0x48/0xd4) from [<c03af838>] (cpuidle_idle_call+0x94/0x118)
<4>[ 1968.394989] [<c03af838>] (cpuidle_idle_call+0x94/0x118) from [<c0050538>] (cpu_idle+0xbc/0xfc)
<4>[ 1968.395172] [<c0050538>] (cpu_idle+0xbc/0xfc) from [<c00088ac>] (start_kernel+0x298/0x2e8)
<4>[ 1968.395477] [<c00088ac>] (start_kernel+0x298/0x2e8) from [<80008040>] (0x80008040)
<4>[ 1968.395782] Board Information: Tuna HW revision: 09 (Maguro 8th Sample), cpu OMAP4460 ES1.1
<4>[ 1968.396087] ---[ end trace 33de6ebe35ad56b6 ]---
<6>[ 1970.874023] max17040 4-0036: online = 1 vcell = 3532500 soc = 22 status = 3 health = 1 temp = 380 charger status = 0
<6>[ 1993.138793] usb 1-1: reset high speed USB device number 2 using musb-hdrc
<6>[ 2000.347503] fsa9480 4-0025: cable detect change, from 'usb-host' to 'unknown/none'
<6>[ 2000.347717] usb 1-1: USB disconnect, device number 2
<4>[ 2000.350708] fsa9480 4-0025: irq fired, but nothing happened
<6>[ 2000.351989] fsa9480 4-0025: nothing attached, keeping ownership of port
<6>[ 2001.361236] max17040 4-0036: online = 1 vcell = 3585000 soc = 21 status = 2 health = 1 temp = 380 charger status = 0
<6>[ 2003.287322] sd 0:0:0:0: Device offlined - not ready after error recovery
<6>[ 2003.287597] sd 0:0:0:0: [sda] Unhandled error code
<6>[ 2003.287628] sd 0:0:0:0: [sda] Unhandled error code
<6>[ 2003.287658] sd 0:0:0:0: [sda] Result: hostbyte=0x01 driverbyte=0x00
<6>[ 2003.287689] sd 0:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 00 00 00 3f 00 00 08 00
<3>[ 2003.287719] end_request: I/O error, dev sda, sector 63
<3>[ 2003.287750] Buffer I/O error on device sda1, logical block 0
<4>[ 2003.287780] lost page write due to I/O error on sda1
<6>[ 2003.289154] sd 0:0:0:0: [sda] Result: hostbyte=0x01 driverbyte=0x00
<6>[ 2003.289459] sd 0:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 00 00 21 e7 00 00 08 00
<3>[ 2003.291625] end_request: I/O error, dev sda, sector 8679
<3>[ 2003.291778] Buffer I/O error on device sda1, logical block 1077
<4>[ 2003.292114] EXT4-fs warning (device sda1): ext4_end_bio:258: I/O error writing to inode 13 (offset 217088 size 4096 starting block 1085)
<3>[ 2003.297576] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.297851] EXT4-fs error (device sda1): __ext4_get_inode_loc:4823: inode #13: block 5: comm libestool.so: unable to read itable block
<2>[ 2003.299560] EXT4-fs error (device sda1) in ext4_reserve_inode_write:5663: IO failure
<3>[ 2003.299743] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.300415] EXT4-fs error (device sda1): ext4_read_block_bitmap:353: comm libestool.so: Cannot read block bitmap - block_group = 0, block_bitmap = 3
<3>[ 2003.300720] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.301116] EXT4-fs error (device sda1): ext4_discard_preallocations:3828: comm libestool.so: Error reading block bitmap for 0
<3>[ 2003.301391] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.301727] EXT4-fs error (device sda1): ext4_read_block_bitmap:353: comm libestool.so: Cannot read block bitmap - block_group = 0, block_bitmap = 3
<3>[ 2003.302032] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.302398] EXT4-fs error (device sda1): ext4_discard_preallocations:3828: comm libestool.so: Error reading block bitmap for 0
<3>[ 2003.302703] EXT4-fs (sda1): previous I/O error to superblock detected
<3>[ 2003.303802] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.304168] EXT4-fs error (device sda1): ext4_free_branches:4377: inode #13: block 536: comm libestool.so: Read failure
<3>[ 2003.305358] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.305755] EXT4-fs error (device sda1): __ext4_get_inode_loc:4823: inode #13: block 5: comm libestool.so: unable to read itable block
<2>[ 2003.306365] EXT4-fs error (device sda1) in ext4_reserve_inode_write:5663: IO failure
<3>[ 2003.306518] EXT4-fs (sda1): previous I/O error to superblock detected
<3>[ 2003.336242] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.336364] EXT4-fs error (device sda1): ext4_find_entry:934: inode #2: comm libestool.so: reading directory lblock 0
<3>[ 2003.411834] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2003.412017] EXT4-fs error (device sda1): __ext4_get_inode_loc:4823: inode #2: block 5: comm ngs.android.pop: unable to read itable block
<2>[ 2003.412414] EXT4-fs error (device sda1) in ext4_reserve_inode_write:5663: IO failure
<3>[ 2003.412567] EXT4-fs (sda1): previous I/O error to superblock detected
<3>[ 2008.311859] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2008.312194] EXT4-fs error (device sda1): __ext4_get_inode_loc:4823: inode #13: block 5: comm bdi-default: unable to read itable block
<3>[ 2008.313110] EXT4-fs (sda1): previous I/O error to superblock detected
<2>[ 2008.313415] EXT4-fs error (device sda1): __ext4_get_inode_loc:4823: inode #2: block 5: comm bdi-default: unable to read itable block
<6>[ 2025.582702] fsa9480 4-0025: cable detect change, from 'unknown/none' to 'usb-host'
<6>[ 2026.233337] usb 1-1: new high speed USB device number 3 using musb-hdrc
<3>[ 2026.388244] usb 1-1: device v090c p6200 is not supported
<6>[ 2026.388427] usb 1-1: New USB device found, idVendor=090c, idProduct=6200
<6>[ 2026.388763] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 2026.389068] usb 1-1: Product: Generic USB2.0 card
<6>[ 2026.389221] usb 1-1: Manufacturer: Silicon Motion, Inc.
<6>[ 2026.389373] usb 1-1: SerialNumber: 12345678901234567890
<6>[ 2026.392089] scsi1 : usb-storage 1-1:1.0
<6>[ 2030.177124] fsa9480 4-0025: cable detect change, from 'usb-host' to 'unknown/none'
<4>[ 2030.180053] fsa9480 4-0025: irq fired, but nothing happened
<6>[ 2030.181335] fsa9480 4-0025: nothing attached, keeping ownership of port
<6>[ 2031.197509] max17040 4-0036: online = 1 vcell = 3600000 soc = 21 status = 2 health = 1 temp = 370 charger status = 0
<6>[ 2034.948303] fsa9480 4-0025: cable detect change, from 'unknown/none' to 'usb-host'
<6>[ 2035.182495] usb 1-1: USB disconnect, device number 3
<6>[ 2045.606109] fsa9480 4-0025: cable detect change, from 'usb-host' to 'unknown/none'
<4>[ 2045.609100] fsa9480 4-0025: irq fired, but nothing happened
<6>[ 2045.610321] fsa9480 4-0025: nothing attached, keeping ownership of port
<6>[ 2046.627288] max17040 4-0036: online = 1 vcell = 3602500 soc = 21 status = 2 health = 1 temp = 370 charger status = 0
<4>[ 2048.832824] ------------[ cut here ]------------
<4>[ 2048.832916] WARNING: at drivers/usb/musb/musb_host.c:125 musb_h_tx_flush_fifo+0x78/0x84()
<4>[ 2048.833068] Could not flush host TX2 fifo: csr: 2003
<4>[ 2048.833160] Modules linked in:
<4>[ 2048.833404] [<c0055de4>] (unwind_backtrace+0x0/0xf8) from [<c00983a8>] (warn_slowpath_common+0x4c/0x64)
<4>[ 2048.833526] [<c00983a8>] (warn_slowpath_common+0x4c/0x64) from [<c0098454>] (warn_slowpath_fmt+0x30/0x40)
<4>[ 2048.833679] [<c0098454>] (warn_slowpath_fmt+0x30/0x40) from [<c0366d70>] (musb_h_tx_flush_fifo+0x78/0x84)
<4>[ 2048.833862] [<c0366d70>] (musb_h_tx_flush_fifo+0x78/0x84) from [<c0367724>] (musb_cleanup_urb+0xb0/0xd4)
<4>[ 2048.834014] [<c0367724>] (musb_cleanup_urb+0xb0/0xd4) from [<c0367990>] (musb_urb_dequeue+0xfc/0x13c)
<4>[ 2048.834167] [<c0367990>] (musb_urb_dequeue+0xfc/0x13c) from [<c03441b0>] (usb_hcd_unlink_urb+0x60/0xac)
<4>[ 2048.834350] [<c03441b0>] (usb_hcd_unlink_urb+0x60/0xac) from [<c035d938>] (usb_stor_stop_transport+0x48/0x60)
<4>[ 2048.834442] [<c035d938>] (usb_stor_stop_transport+0x48/0x60) from [<c035c36c>] (command_abort+0x80/0x84)
<4>[ 2048.834564] [<c035c36c>] (command_abort+0x80/0x84) from [<c02d50ec>] (scsi_error_handler+0x3a4/0x49c)
<4>[ 2048.834716] [<c02d50ec>] (scsi_error_handler+0x3a4/0x49c) from [<c00b227c>] (kthread+0x80/0x88)
<4>[ 2048.834899] [<c00b227c>] (kthread+0x80/0x88) from [<c0050148>] (kernel_thread_exit+0x0/0x8)
<4>[ 2048.835052] Board Information: Tuna HW revision: 09 (Maguro 8th Sample), cpu OMAP4460 ES1.1
<4>[ 2048.835144] ---[ end trace 33de6ebe35ad56b7 ]---
<6>[ 2048.837768] scsi 1:0:0:0: Device offlined - not ready after error recovery
I found a thread on TI site for the OMAP4460 that discusses an error like mine but the signature is not the same, seems there they were having a problem with the the TCP/IP stack becoming corrupted because the processor was allocating memory too fast. Something like that is happening here. All I really know is it has to do with the handling of the L3 cache.
I think this may have to do with the cpu trying to idle when it should not.
What kind of drive are you using? If its a portable usb hard drive then this could be a power issue.
It's not a portable HD, just usb sd card reader.
With further investigation I have found that the problem might stem from the x-loader being mismatched to the kernel, which is part of the bootloader.
I tried different bootloaders, but none made a difference.
Finally, I tried a different USB OTG cable, a slightly more expensive one, and it worked.
Hi everyone,
sorry for the lengthy post, but I wanted to be precise. Please read the whole of it, if you think you might be able to help. I love this phone but it's useless without WiFi for me. I am also sorry, if I unwittingly violated any forum rules. I tried the best I could.
Currently, I am having a severe issue with the WiFi of my HTC Desire Z. It won't turn on or do anything. First of all: I worked myself through all threads that I could find which were just remotely connected with this issue, also in forums concerning other devices. I still hope I overlooked something... Btw.: My phone is almost 3 years old and a German version. I don't remember what method I used to root it since it was one of the first things I did.
The aforementioned problem appeared right after the following incident: My phone went out of battery while I was listening to an audiobook via Audible. I put the phone in airplane mode some 10 minutes earlier to prevent this, very <irony>successfully<\irony>...
After rebooting, I tried to turn WiFi on, but it just kept telling me "turning wifi on". The switch turned grey and nothing happened. I tried rebooting, turning WiFi on and of several times as well as airplane mode. I flashed the following ROMs, some of which I have been using sometime earlier where WiFi has definitively been working: Andromadus JellyBean by Flinny (version 123, 133 if that matters), all CM stable releases, Andromadus Mimicri 1.50 together with the sugested WiFixIt. With these ROMs I did the same. I could not find any stock ROM that has been able to boot. I did not try to reverse root and s-off (seems pointless to me).
I update the Radio to (afaik most recent version) and I downgraded it a few other versions without any change. I also did a superwipe with the tools given on the following page and reinstalled the ROMs, to no avail: http://forum.xda-developers.com/showthread.php?t=1044992
I also tried different sim-cards (from UK and Germany), both with and without sim-card and sd-card. Also no success.
Bluetooth is working flawlessly. I have just copied a file from my Laptop over to my phone via BT, which is strange, because, as far as I know, both WiFi and BT use the same chips and the same antenna.
I pulled all the logs I found (logcat: main, event, radio; dmesg) and boiled it down to the driver not being able to be loaded. Please correct me, but the WiFi drivers come with the ROM, therefore it CANNOT be due to a faulty driver, since I installed some that worked months ago (tried this before and after flashing different radios).
I reckon that the following parts are the important ones, but I attached the complete logs (cover the boot process and me trying to turn WiFi on) to be on the safe side. As far as I understand, it just says that it tries to load the driver bot fails to attach some kind of module.
Dmesg:
<6>[ 45.185119] [WLAN] ## wifi_probe
<4>[ 45.185302] [WLAN][WRN] wifi_set_power = 1
<6>[ 45.185455] [WLAN]vision_wifi_power: 1
<6>[ 46.075988] [WLAN] wifi_set_carddetect = 1
<6>[ 46.076141] vision_wifi_set_carddetect: 1
<6>[ 46.076293] mmc1: Slot status change detected (0 -> 1)
<6>[ 46.089599] [WLAN] Dongle Host Driver, version 5.90.125.120
<6>[ 46.089599] Compiled in drivers/net/wireless/bcmdhd on Oct 1 2012 at 17:46:03
<4>[ 46.129547] mmc1: queuing unknown CIS tuple 0x91 (3 bytes)
<6>[ 46.129882] mmc1: new high speed SDIO card at address 0001
<6>[ 47.087982] [LED]pm8058_drvx_led_brightness_set: bank 3 brightness 0 +
<6>[ 47.088287] [LED]pm8058_drvx_led_brightness_set: bank 3 brightness 0 -
<6>[ 47.935516] [TP][email protected],797
<3>[ 48.187652] mmc1: CMD53: Data timeout
<6>[ 48.187927] mmc1: SDCC PWR is ON
<6>[ 48.188110] mmc1: SDCC clks are ON, MCLK rate=50000000
<6>[ 48.188262] mmc1: SDCC irq is enabled
<6>[ 48.188507] ===== SDCC-CORE: Register Dumps @base=0xec832000 =====
<6>[ 48.188629] Reg=0x00: 0x00000003, 0x00009b00, 0x15000004, 0x00001475.
<6>[ 48.188903] Reg=0x10: 0x00000035, 0x00001000, 0x00000000, 0x00000000.
<6>[ 48.189025] Reg=0x20: 0x00000000, 0x05f5e100, 0x00000004, 0x00000043.
<6>[ 48.189270] Reg=0x30: 0x00000004, 0x00400200, 0x00000000, 0x00a081ff.
<6>[ 48.189514] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000.
<6>[ 48.189666] Reg=0x50: 0x00000000, 0x00000000, 0x00000000, 0x00000000.
<6>[ 48.189910] Reg=0x60: 0x00000000, 0x00000000, 0x00000000, 0x00000000.
<6>[ 48.190063] mmc1: PIO mode
<6>[ 48.190307] mmc1: xfer_size=4, data_xfered=0, xfer_remain=4
<6>[ 48.190429] mmc1: got_dataend=0, prog_enable=0, wait_for_auto_prog_done=0, got_auto_prog_done=0
<4>[ 48.190917] [WLAN][WRN] F1 signature read @0x18000000=0xffffffff
<6>[ 48.797210] [TP][email protected],866
<6>[ 48.798217] [TP]calibration confirm with recal by position
<6>[ 48.823303] [TP]0x01 0x10 0xA8 0x85 0x00
<6>[ 48.835113] [TP]0x01 0x00 0xA8 0x85 0x00
<3>[ 50.226043] mmc1: CMD53: Data timeout
<6>[ 50.226226] mmc1: SDCC PWR is ON
<6>[ 50.226409] mmc1: SDCC clks are ON, MCLK rate=50000000
<6>[ 50.226684] mmc1: SDCC irq is enabled
<6>[ 50.226806] ===== SDCC-CORE: Register Dumps @base=0xec832000 =====
<6>[ 50.227081] Reg=0x00: 0x00000003, 0x00009b00, 0x15000004, 0x00001475.
<6>[ 50.227233] Reg=0x10: 0x00000035, 0x00001000, 0x00000000, 0x00000000.
<6>[ 50.227478] Reg=0x20: 0x00000000, 0x05f5e100, 0x00000004, 0x00000043.
<6>[ 50.227630] Reg=0x30: 0x00000004, 0x00000200, 0x00000000, 0x00a081ff.
<6>[ 50.227874] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000.
<6>[ 50.228149] Reg=0x50: 0x00000000, 0x00000000, 0x00000000, 0x00000000.
<6>[ 50.228271] Reg=0x60: 0x00000000, 0x00000000, 0x00000000, 0x00000000.
<6>[ 50.228546] mmc1: PIO mode
<6>[ 50.228668] mmc1: xfer_size=4, data_xfered=0, xfer_remain=4
<6>[ 50.228820] mmc1: got_dataend=0, prog_enable=0, wait_for_auto_prog_done=0, got_auto_prog_done=0
<4>[ 50.229370] [WLAN][WRN] dhdsdio_probe_attach: si_attach failed!
<4>[ 50.229644] [WLAN][WRN] dhdsdio_probe: dhdsdio_probe_attach failed
<4>[ 50.242645] [WLAN][WRN] dhd_module_init: wifi_fail_retry is true
<6>[ 50.247802] [WLAN] ## wifi_remove
<4>[ 50.247985] [WLAN][WRN] wifi_set_power = 0
<6>[ 50.248107] [WLAN]vision_wifi_power: 0
<6>[ 51.038665] [WLAN] wifi_set_carddetect = 0
<6>[ 51.038818] vision_wifi_set_carddetect: 0
<6>[ 51.038970] mmc1: Slot status change detected (1 -> 0)
<6>[ 51.039978] mmc1: card 0001 removed
<6>[ 51.041442] [WLAN] ## wifi_remove leave
Click to expand...
Click to collapse
Logcat main:
E/CommandListener( 115): Failed to open /proc/sys/net/ipv6/conf/wlan0/disable_ipv6: No such file or directory
E/WifiStateMachine( 294): Failed to disable IPv6: java.lang.IllegalStateException: command '1 interface ipv6 wlan0 disable' failed with '400 1 Failed to change IPv6 state (No such file or directory)'
...
I/WifiService( 294): WifiService starting up with Wi-Fi enabled
D/WifiService( 294): setWifiEnabled: true pid=294, uid=1000
D/WifiWatchdogStateMachine( 294): Disabling poor network avoidance for wi-fi only device
...
may times:
E/WifiHW ( 294): Supplicant not running, cannot connect
E/WifiHW ( 294): Supplicant not running, cannot connect
E/WifiStateMachine( 294): Failed to setup control channel, restart supplicant
Click to expand...
Click to collapse
Methinks it is a hardware issue and I am very close to taking the thing apart, which will possibly break something else... Second last comment: As I try to turn WiFi on via the status bar, it reboots after like one minute. Last comment: Is there any way to check whether it really is a hardware fault?
I apprecieate any comment intended to be helpful. Even when it is you telling me that it IS a hardware issue. If you need any further information, I am more than happy to provide it. I would also be happy to make the life of my phone-saviour more enjoyable with one or two pints of something, if we can arrange a meeting.
haha, i doubt ill be in germany any time soon... but i will be in greece in a month or so...
well it sounds like youre trying all the right things and it possibly is a hardware fault. but being you rooted 3 years ago you dont have true radio s-off, as it wasnt around.
if it were me, i would unroot, then follow the gfree method to downgrade and root via gfree, this will fully wipe out all partitions (except efs) and then flash a tried and true rom like cm7, hopefully all will be well at this point... if not, hardware...
Thank you for your advice. I did as you told me and went through the pain to reinstall stock Froyo as well as stock recovery and hboot. I also had s-on (at leats that's what hboot and gfree_verify said). Then I went to reroot it again, this time using gfree1.0 (which was definitely not what I used last time).
But unfortunately WiFi did not work neither with stock Froyo nor after rerooting and running CM7. Bluetooth still worked fine in every case... Log still says the exact same thing.
There is just two things left that might be worth a try, but it's a long shot. Could it be a problem with some data on the efs-partition that is messed up? As far as I understand it that is where android stores important information about IMEI, MAC-adress an the like. But I really do not know how to restore this partition even if it were the cause. Or could it be a problem with the RIL since that is what communicates with the radio? But I also do not know how to restore this if it were the cause (but it's just said that matching the RIL might just improve performance).
What's your opinion about this? Do you think that a look at the phone's insides might yield any results/certainty?
Unfortunetly if you never made a backup of your efs partition there is no way to restore this, you can back it up now, wipe it, restore and see if that helps but I doubt it.
Ril is matched when you downgraded so that's not it. Trutfully my best guess is hardware, sorry
Sent from my HTC Vision using xda premium
Unfortunately, I never made a backup of my /efs. I also tried wiping it, but no change.
The only sad thing is, that there is no adequate replacement...
I still don't get why BT is working and WiFi is not while both use the same chip, but that will stay a mystery forever unresolved.
Is there any way to close this tread? Somehow I don't see any.
Mine does what you are describing, but it's cause my gf dropped it
Sent from my SGH-T999 using xda premium
---------- Post added at 01:10 AM ---------- Previous post was at 01:08 AM ----------
And disconnected the wireless "modem"
The drop was pretty severe, however. I needed a whole new battery cover
Sent from my SGH-T999 using xda premium
op did you solved error ?
Nope, I could not solve the issue and I did not disassemble my phone and risk being left without one. So far, my mobile data plan has been sufficient and for large data, I access the internet via a USB-cable. I will get a new phone though when I am less busy at work.
Sent from my HTC Vision
I know this is a common problem, and this is the fourth time this happens to my phone, but since last summer I have no warranty left to keep my phone alive.
My phone has too many unexpected random reboots, since four days they are increasing heavily, the three other times this happened HTC replaced the mainboard. I am using Flinnys CM 11 Alpha 3 since its release, I know it is unstable, but these kinds of problems are new and reflashing this rom or CM 10.1 did not helped.
I searched a bit and I found out nothing positive, but are there chances JTag can fix this problem? I haven't detected any mmc error yet, and I want to keep this phone alive, but it isn't worth to buy a new mainboard. My phone is S-Off with Engineering HBoot.
I do not want to buy JTag cables/acessoires without a chance it could fix that, since I would need to import something to Germany and I think my phone is hardware damaged, hoping I am wrong.
In recovery mode I checked MMC: adb shell dmesg | grep mmc
Code:
<5>[ 0.000000] Kernel command line: board_vision.disable_uart2=0 board_vision.usb_h2w_sw=0 board_vision.disable_sdcard=0 diag.enabled=0 board_vision.debug_uart=0 smisize=0 userdata_sel=0 androidboot.emmc=true androidboot.baseband=26.13.04.19_M androidboot.cid=HTC__102 androidboot.batt_poweron=good_battery androidboot.carrier=HTC-GER androidboot.mid=PC1011000 androidboot.keycaps=qwerty androidboot.mode=recovery androidboot.serialno=[I]*removed*[/I] androidboot.bootloader=0.84.2000 no_console_suspend=1 console=null
<6>[ 7.228332] vision: vision_init_mmc
<3>[ 8.179473] mmc0: No card detect facilities available
<6>[ 8.180084] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 8.180328] mmc0: Platform slot type: MMC
<6>[ 8.180480] mmc0: 4 bit data mode disabled
<6>[ 8.180603] mmc0: 8 bit data mode enabled
<6>[ 8.180847] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 8.180999] mmc0: Slot eject status = 0
<6>[ 8.181121] mmc0: Power save feature enable = 1
<6>[ 8.181274] mmc0: DM non-cached buffer at ff00d000, dma_addr 0x0f518000
<6>[ 8.181396] mmc0: DM cmd busaddr 0x0f518000, cmdptr busaddr 0x0f518300
<6>[ 8.182434] mmc1: Qualcomm MSM SDCC at 0x00000000a3000000 irq 96,0 dma 8
<6>[ 8.182678] mmc1: Platform slot type: N/A
<6>[ 8.182800] mmc1: 4 bit data mode enabled
<6>[ 8.182952] mmc1: 8 bit data mode disabled
<6>[ 8.183197] mmc1: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 8.183349] mmc1: Slot eject status = 1
<6>[ 8.183593] mmc1: Power save feature enable = 1
<6>[ 8.183715] mmc1: DM non-cached buffer at ff00e000, dma_addr 0x0f519000
<6>[ 8.183990] mmc1: DM cmd busaddr 0x0f519000, cmdptr busaddr 0x0f519300
<6>[ 8.185363] mmc2: Qualcomm MSM SDCC at 0x00000000a3100000 irq 100,0 dma 8
<6>[ 8.185516] mmc2: Platform slot type: SD
<6>[ 8.185760] mmc2: 4 bit data mode enabled
<6>[ 8.185882] mmc2: 8 bit data mode disabled
<6>[ 8.186035] mmc2: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 8.186279] mmc2: Slot eject status = 0
<6>[ 8.186401] mmc2: Power save feature enable = 1
<6>[ 8.186676] mmc2: DM non-cached buffer at ff00f000, dma_addr 0x0f51b000
<6>[ 8.186798] mmc2: DM cmd busaddr 0x0f51b000, cmdptr busaddr 0x0f51b300
<6>[ 8.187072] mmc2: Polling status mode enabled
<6>[ 8.345214] mmc0: new high speed MMC card at address 0001
<6>[ 8.347290] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
<6>[ 8.348724] mmcblk0: p1 p2 p3 p4 < p5
<4>[ 8.635314] mmc2: high speed mode max_dtr = 50000000
<4>[ 8.635650] mmc2: host does not support reading read-only switch. assuming write-enable.
<6>[ 8.635894] mmc2: new high speed SDHC card at address e624
<6>[ 8.644683] mmcblk1: mmc2:e624 SU08G 7.40 GiB
<6>[ 8.645538] mmcblk1: p1
<6>[ 10.405792] EXT4-fs (mmcblk0p27): mounted filesystem with ordered data mode. Opts:
<3>[ 10.565460] EXT3-fs (mmcblk0p25): error: couldn't mount because of unsupported optional features (40)
<3>[ 10.567626] EXT2-fs (mmcblk0p25): error: couldn't mount because of unsupported optional features (40)
<6>[ 10.618499] EXT4-fs (mmcblk0p25): mounted filesystem with ordered data mode. Opts: (null)
<6>[ 19.993225] EXT4-fs (mmcblk0p25): mounted filesystem with ordered data mode. Opts:
<6>[ 20.125244] EXT4-fs (mmcblk0p26): mounted filesystem with ordered data mode. Opts:
<3>[ 20.269561] EXT4-fs (mmcblk1p1): VFS: Can't find ext4 filesystem
<3>[ 20.274169] EXT4-fs (mmcblk1): VFS: Can't find ext4 filesystem
my phone says goodbye ;(
It now rebooted or made a sudden shutdown in the last hour at least four times.
Do you get the reboots if you leave it in recovery or bootloader? Can you rule out a sticky power button? Have you been able to capture a logcat or last_kmsg when this happens? It may be fixable
Sent from my Nexus 4 using XDA Premium 4 mobile app
I haven't got any reboots in bootloader or recovery mode, but my phone is not in recovery for long time, but i do not have a good possibility to test it, since i need the phone powered on. My power button is not sticky, besides it has been replaced last year. No i have not been able to capture it yet, every time my phone has these problems i am not sitting next to my pc, i will try to get these. Thank you for your answer.
Since this morning I am running logcat and kmsg, but no reboots since i started capturing.
Full logs: kmsg.log logcat.log
Edit: Sorry I have seen you wanted last_kmsg, I have attached it now
log is very long so I hope I found all relevant information, don't know but this seems to be relevant:
Code:
E/ConsumerIrService( 1902): Can't open consumer IR HW Module, error: -2
[...]
E/FlpHardwareProvider( 1902): Error hw_get_module 'flp': -2
E/FlpHardwareProvider( 1902): Error hw_get_module 'flp': -2
I ran kmsg the first time, so I don't know what is relevant, but I think this could be, since it is returning over and over again:
Code:
<6>[ 745.429565] msm_vidc_enc: Inside vid_enc_open()
<4>[ 745.433837]
<4>[ 745.433837] res_trk_download_firmware(): Request firmware download
<6>[ 745.592529] Loading CONTROL_FW of FW_SIZE 9000
<6>[ 745.598175]
<6>[ 745.598175] msm_vidc_enc: Inside vid_enc_release()
<6>[ 745.598449]
<6>[ 745.598449] msm_vidc_enc: Inside vid_enc_close_client()
<6>[ 745.600219]
<6>[ 745.600250] msm_vidc_enc: Sending VCD_EVT_RESP_STOP to client
<6>[ 746.333374] [LS][CM3602] ALS value: 0x1, level: 0 #
<6>[ 747.293975] [LS][CM3602] ALS value: 0x0, level: 0 #
<6>[ 747.451019] call alarm, type 2, func alarm_triggered+0x0/0xd8, 1522302000000 (s 1522302000000)
<6>[ 747.548919] call alarm, type 3, func alarm_triggered+0x0/0xd8, 0 (s 0)
<6>[ 749.616058] call alarm, type 3, func alarm_triggered+0x0/0xd8, 1526265000000 (s 1526265000000)
<6>[ 750.089538] microp_led_pwm_brightness_set, data[1] = 0
<3>[ 750.597900] vid_enc_close_client:ERROR vcd_stop time outrc = 0
<6>[ 750.627227]
<6>[ 750.627227] msm_vidc_enc: Return from vid_enc_release()
<6>[ 750.672058] [CAM]msm_enqueue: queue event new max is 6
<6>[ 750.893615] call alarm, type 2, func alarm_triggered+0x0/0xd8, 1522302000000 (s 1522302000000)
<6>[ 750.895965] call alarm, type 2, func alarm_triggered+0x0/0xd8, 1526264000000 (s 1526264000000)
<6>[ 751.206268] call alarm, type 2, func alarm_triggered+0x0/0xd8, 1522302000000 (s 1522302000000)
<6>[ 751.206787] call alarm, type 2, func alarm_triggered+0x0/0xd8, 1526265000000 (s 1526265000000)
<6>[ 751.710205] call alarm, type 2, func alarm_triggered+0x0/0xd8, 1522302000000 (s 1522302000000)
<6>[ 751.710632] call alarm, type 2, func alarm_triggered+0x0/0xd8, 1526265000000 (s 1526265000000)
<4>[ 752.062774] send sigkill to 5943 (nt.android.mail), adj 764, size 6342
<6>[ 753.234069] call alarm, type 2, func alarm_triggered+0x0/0xd8, 1529883000000 (s 1529883000000)
<4>[ 753.447265] send sigkill to 5929 (droid.gallery3d), adj 647, size 4243
<4>[ 754.797363] send sigkill to 6155 (.bitspin.timely), adj 647, size 10701
<6>[ 755.095642] microp_led_pwm_brightness_set, data[1] = 45
<6>[ 760.327087] call alarm, type 3, func alarm_triggered+0x0/0xd8, 1536976000000 (s 1536976000000)
<6>[ 760.764038] call alarm, type 3, func alarm_triggered+0x0/0xd8, 1537413000000 (s 1537413000000)
<6>[ 760.990051] call alarm, type 3, func alarm_triggered+0x0/0xd8, 1537639000000 (s 1537639000000)
<6>[ 761.089080] call alarm, type 3, func alarm_triggered+0x0/0xd8, 1537738000000 (s 1537738000000)
<6>[ 762.833496] [CAM] vfe31_proc_general: V31_STOP
<6>[ 762.833587] [CAM]vfe_stop() enter
<6>[ 762.834442] [CAM]vfe_stop() exit
<6>[ 762.834625] [CAM] irq resetAckIrq
<6>[ 762.834747] [CAM] irq resetAckIrq
<6>[ 762.893371] [CAM]msm_release_frame: frame0
<6>[ 762.893463] [CAM]__msm_release:sync->opencnt:3
<6>[ 762.895507] [CAM]release frame atomic_set pmsm->opened as 0
<6>[ 762.895629] [CAM] msm_release_frame: draining queue frame
<6>[ 762.895812] [CAM]msm_release_frame,q->len = 0
<6>[ 762.903411] [CAM] msm_release_frame, completed
<6>[ 763.018707] [CAM] msm_pmem_table_add: type 15, paddr 0x2dd96000, vaddr 0x43b30000
<6>[ 763.031066] [CAM] msm_pmem_table_add: type 15, paddr 0x2dee8000, vaddr 0x43f4a000
<6>[ 763.036804] [CAM] msm_pmem_table_add: type 15, paddr 0x2e03a000, vaddr 0x4426a000
<6>[ 763.047454] [CAM] msm_pmem_table_add: type 15, paddr 0x2e18c000, vaddr 0x446a3000
<6>[ 763.069427] [CAM] msm_pmem_table_add: type 15, paddr 0x2e2de000, vaddr 0x44a4e000
<6>[ 763.085021] [CAM] msm_pmem_table_add: type 15, paddr 0x2e430000, vaddr 0x44de3000
<6>[ 763.094635] [CAM] msm_pmem_table_add: type 15, paddr 0x2e582000, vaddr 0x450a0000
<6>[ 763.103454] [CAM] msm_pmem_table_add: type 14, paddr 0x2e6d4000, vaddr 0x45237000
<6>[ 763.110900] [CAM] msm_pmem_table_add: type 14, paddr 0x2e826000, vaddr 0x45389000
<6>[ 763.116973] [CAM] msm_pmem_table_add: type 14, paddr 0x2e978000, vaddr 0x454db000
<6>[ 763.153625] [CAM] msm_pmem_table_add: type 14, paddr 0x2eaca000, vaddr 0x4562d000
<6>[ 763.171356] [CAM] msm_pmem_table_add: type 14, paddr 0x2ec1c000, vaddr 0x4577f000
<6>[ 763.180114] call alarm, type 2, func alarm_triggered+0x0/0xd8, 1539829000000 (s 1539829000000)
<6>[ 763.186645] [CAM] msm_pmem_table_add: type 14, paddr 0x2ed6e000, vaddr 0x458d1000
<6>[ 763.199859] [CAM] msm_pmem_table_add: type 14, paddr 0x2eec0000, vaddr 0x45a23000
<6>[ 763.225616] [CAM] msm_pmem_table_add: type 14, paddr 0x2f012000, vaddr 0x45b75000
<6>[ 763.241241] [CAM] msm_pmem_table_add: type 16, paddr 0x2f164000, vaddr 0x45cc7000
<4>[ 763.254211] [CAM]msm_pp_release: pp not in progress for 0
<6>[ 763.255645] [CAM] vfe31_proc_general: V31_RESET
<6>[ 763.255859] [CAM] irq resetAckIrq
<6>[ 763.263153] [CAM] vfe31_config_axi: mode = 3, bufnum1 = 3, bufnum2 = 3
<6>[ 763.286712] [CAM] vfe31_proc_general: V31_START
<6>[ 763.288665] [CAM] VFE opertaion mode = 0x2.
<6>[ 763.288848] [CAM] VFE output path out mode = 0x5.
<6>[ 763.344512] [CAM] irq camifSofIrq, count 1
<6>[ 763.354034] [CAM] irq startAckIrq
<6>[ 763.354278] [CAM] msm_camio_disable_csi_log
<6>[ 763.379516] [CAM]>>>>>>>>(2014-04-30 06:17:13.763715307 UTC)<<<<<<<
<6>[ 763.379791] [CAM]msm_open_common: open frame0
<6>[ 763.379882] [CAM] msm_open_common: rc 0
<4>[ 763.969879] send sigkill to 5738 (gle.android.gms), adj 647, size 5183
<6>[ 764.134490]
<6>[ 764.134490] msm_vidc_enc: Inside vid_enc_open()
<6>[ 764.193817] Loading CONTROL_FW of FW_SIZE 9000
<6>[ 764.206939]
<6>[ 764.206939] msm_vidc_enc: Inside vid_enc_release()
<6>[ 764.208923]
<6>[ 764.208953] msm_vidc_enc: Inside vid_enc_close_client()
<6>[ 764.209320]
<6>[ 764.209320] msm_vidc_enc: Sending VCD_EVT_RESP_STOP to clientsend sigkill to 6186 (nt.android.mail), adj 529, size 7345
<6>[ 764.723083] call alarm, type 3, func alarm_triggered+0x0/0xd8, 1541372000000 (s 1541372000000)
<4>[ 764.739593] send sigkill to 5086 (ndroid.settings), adj 529, size 5385
<6>[ 768.847198] microp_led_pwm_brightness_set, data[1] = 0
<3>[ 769.207122] vid_enc_close_client:ERROR vcd_stop time outrc = 0
<6>[ 769.237396]
The logcat would have to be running during reboot to get much out of it, so if its not easily replicable then try to get the kernel log. So right after reboot grab the last_kmsg, this should give the reason for the reboot
Sent from my Nexus 7 using XDA Premium 4 mobile app
Thank you for your help, I will see what I can do, but my phone is really annoying me. Everytime I am at home, and have the possibility to get logcat during reboot my phone runs perfectly, but when I am outside you can imagine what it does.
If I am not able to get a logcat soon or the problems suddenly stop, I will buy a new phone.
At home are you always on WiFi? Maybe there is an issue with your radio where switching between 3g/2g or whatever causes constant reboots?
Just a thought but maybe try flashing a new radio
Sent from my Nexus 7 using XDA Premium 4 mobile app
I am using latest radio 26.13.04.19_M since last summer and haven't had any problems yet. I will reflash it and if problems aren't gone I will try to downgrade. Perhaps something is messed up.
No I am not constantly on WiFi, besides my WiFi does not reach all rooms/floors so my phone sometimes switches to 3g. Also it is not constantly rebooting, it may work some hours, a day (only yesterday), or only half an hour, I am doing different actions, while getting reboots. Like sending a video with WhatsApp or something else, even if I do nothing, it is just laying around on a table.
Flashing new radio reduced the reboots, but they aren't gone. Now I also have network-connection issues, my phone disconnect itself from carrier (with full signal strength, my friends with same carrier have also full signal strength at the same time), I am missing important phone calls, so I flashed back 26.13.04.19_M, but the problem isn't gone. Force closes with apps which worked fine before (like WhatsApp) are increasing.
Since three days my phone does not recognize my original charger correctly, it needs about 4 hours to get 100%, wiping battery stats didn't helped. Perhaps it is more than three days, normally I plug in charger when I go sleeping. This is happening with two original batteries (one I bought last year).
I do not have any hope left I was wrong with hardware problem. So I will buy LG G2 on Tuesday, if I can't reduce the problems, I need a working phone.