Hey guys,
I own a Moto G 4G and like to use it with a 64 GB SD card. The card is formatted as FAT32 and recognized. I can even play music from it and things.
My problem is, that the music will start to stutter after some minutes of phone sleep. I already rooted the phone and noticed that the kernel is going nuts when this stuttering happens. It will throw out a zillion of error messages:
Code:
<3>[54290.420034,0] mmc1: data txfr (0x00200000) error: -84 after 2 ms
<6>[54290.420218,0] sdhci: =========== REGISTER DUMP (mmc1)===========
<6>[54290.420315,0] sdhci: Sys addr: 0x00000100 | Version: 0x00003e02
<6>[54290.420488,0] sdhci: Blk size: 0x00007200 | Blk cnt: 0x00000100
<6>[54290.420585,0] sdhci: Argument: 0x03bb396a | Trn mode: 0x0000003b
<6>[54290.420757,0] sdhci: Present: 0x03f80206 | Host ctl: 0x00000017
<6>[54290.420855,0] sdhci: Power: 0x0000000f | Blk gap: 0x00000000
<6>[54290.421027,0] sdhci: Wake-up: 0x00000000 | Clock: 0x00000007
<6>[54290.421124,0] sdhci: Timeout: 0x00000008 | Int stat: 0x00000000
<6>[54290.421295,0] sdhci: Int enab: 0x03ff800b | Sig enab: 0x03ff800b
<6>[54290.421392,0] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
<6>[54290.421565,0] sdhci: Caps: 0x2329c8b2 | Caps_1: 0x00008007
<6>[54290.421662,0] sdhci: Cmd: 0x0000123a | Max curr: 0x00000000
<6>[54290.421834,0] sdhci: Resp 1: 0x30303030 | Resp 0: 0x00000900
<6>[54290.421931,0] sdhci: Resp 3: 0x00000900 | Resp 2: 0x10dbdb04
<6>[54290.422102,0] sdhci: Host ctl2: 0x0000000c
<6>[54290.422199,0] sdhci: ADMA Err: 0x00000003 | ADMA Ptr: 0x23f40070
<6>[54290.422374,0] mmc1: clk: 50000000 clk-gated: 0 claimer: mmcqd/1 pwr: 14
<6>[54290.422471,0] mmc1: rpmstatus[pltfm](runtime-suspend:usage_count:disable_depth)(0:0:0)
<6>[54290.422643,0] sdhci: ===========================================
<3>[54290.427199,0] mmcblk1: error -84 transferring data, sector 62601578, nr 256, cmd response 0x900, card status 0xb00
I already RMA'd the card, so it's not hardware related. I just noticed that those error messages also appear when music play "normally" on that 64 GB card, but when they occur to often in a short time, stuttering begins.
I also another 8 GB card and it's working fine without any errors/stuttering.
My question now is: Does the card just have a bad hardware design leading to such errors or is my phone screwed? Can anyone please interpret those error messages?
Thank you!
Some mmc drivers have problems with the timings of some cards ; e.g. my Nook Simple Touch has problems with class 10 cards and logs similar errors. I swapped a class 6 card in instead, and the problems went away.
cowbutt said:
Some mmc drivers have problems with the timings of some cards ; e.g. my Nook Simple Touch has problems with class 10 cards and logs similar errors. I swapped a class 6 card in instead, and the problems went away.
Click to expand...
Click to collapse
Thanks, I already thought that. I've already ordered a new card by another manufacturer which is slower but still Class 10 (since SDXC cards are at least class 10). I hope this one will work I'll report if it arrives
Edit: It just arrived and I already sent it back. The new card was not recognized at all and when it was, it was dismounted again. Damnit...
Related
My sensation keeps restarting randomly.
I've tried:
- Reflashing firmware 3.33, 3.32
- Other roms: Miui v4, cm10, cm9, Darksense, ARDHD, stock, gingerbread cm7.
- New battery
- Battery card trick
Sometimes it turns off completely and I can't turn it back on without pulling the battery out and putting it back in.
Moon2 said:
My sensation keeps restarting randomly.
I've tried:
- Reflashing firmware 3.33, 3.32
- Other roms: Miui v4, cm10, cm9, Darksense, ARDHD, stock, gingerbread cm7.
- New battery
- Battery card trick
Sometimes it turns off completely and I can't turn it back on without pulling the battery out and putting it back in.
Click to expand...
Click to collapse
I need more information, so I ask you do these things.
OK. First:
Code:
adb shell
dmesg > /sdcard/DMESG.txt
Attach the DMESG.txt file from your SDCard.
Code:
adb logcat > Logcat.txt
Wait for phone to randomly restart (sorry) and attach the logcat file.
Secondly:
Current HBOOT version? Kernel if flashing manually?
DennisBold said:
I need more information, so I ask you do these things.
OK. First:
Code:
adb shell
dmesg > /sdcard/DMESG.txt
Attach the DMESG.txt file from your SDCard.
Code:
adb logcat > Logcat.txt
Wait for phone to randomly restart (sorry) and attach the logcat file.
Secondly:
Current HBOOT version? Kernel if flashing manually?
Click to expand...
Click to collapse
I'd previously logged the logcat twice before it restarted and also have a last_kmsg of when it happened. It doesn't seem to reboot when I'm in recovery.
HBoot: 1.29.0000, S-off
Kernel: Stock, faux, sebastian (happens on all of them)
I'm having the same problem with my sensation with alternative battery!!! Please help!!!
It just happened again and I've got another logcat, I'll try and do the dmesg now.
I've tried letting the phone sleep without wifi/3g, taking sd card out, formatting it.
Moon2 said:
I'd previously logged the logcat twice before it restarted and also have a last_kmsg of when it happened. It doesn't seem to reboot when I'm in recovery.
HBoot: 1.29.0000, S-off
Kernel: Stock, faux, sebastian (happens on all of them)
Click to expand...
Click to collapse
I thought the pyramid had Adreno 220?
Code:
D/libEGL ( 1113): loaded /system/lib/egl/libGLESv2_adreno200.so
What ROM do you currently have installed?
DennisBold said:
I thought the pyramid had Adreno 220?
Code:
D/libEGL ( 1113): loaded /system/lib/egl/libGLESv2_adreno200.so
What ROM do you currently have installed?
Click to expand...
Click to collapse
Miui v4
I've seen that library used on different phones with adreno on them, I don't think the 200 has a bearing on the type found on the phone.
Moon2 said:
Miui v4
Click to expand...
Click to collapse
Is your GPS enabled, and does this happen when your GPS is disabled?
Moon2 said:
Miui v4
I've seen that library used on different phones with adreno on them, I don't think the 200 has a bearing on the type found on the phone.
Click to expand...
Click to collapse
Never really looked at that, well, the only thing I can connect it with is GPS.
DennisBold said:
Is your GPS enabled, and does this happen when your GPS is disabled?
Click to expand...
Click to collapse
I've tried it with wifi, 3g, bluetooth, gps, auto-sync all turned off and it still happens.
Moon2 said:
I've tried it with wifi, 3g, bluetooth, gps, auto-sync all turned off and it still happens.
Click to expand...
Click to collapse
(From First Logcat)
Code:
D/GpsLocationProvider( 241): [handleMessage] message :7
D/GpsLocationProvider( 241): [handleMessage] UPDATE_LOCATION
D/GpsLocationProvider( 241): handleUpdateLocation
D/lib_locapi( 241): loc_eng_inject_location, accuracy = 48.0
(Second Logcat)
Code:
D/GpsLocationProvider( 242): [handleMessage] message :7
D/GpsLocationProvider( 242): [handleMessage] UPDATE_LOCATION
D/GpsLocationProvider( 242): handleUpdateLocation
D/lib_locapi( 242): loc_eng_inject_location, accuracy = 52.0
Logcat ends a minute not long after that.
On a side note, do you have AdFree installed?
DennisBold said:
(From First Logcat)
Code:
D/GpsLocationProvider( 241): [handleMessage] message :7
D/GpsLocationProvider( 241): [handleMessage] UPDATE_LOCATION
D/GpsLocationProvider( 241): handleUpdateLocation
D/lib_locapi( 241): loc_eng_inject_location, accuracy = 48.0
(Second Logcat)
Code:
D/GpsLocationProvider( 242): [handleMessage] message :7
D/GpsLocationProvider( 242): [handleMessage] UPDATE_LOCATION
D/GpsLocationProvider( 242): handleUpdateLocation
D/lib_locapi( 242): loc_eng_inject_location, accuracy = 52.0
Logcat ends a minute not long after that.
On a side note, do you have AdFree installed?
Click to expand...
Click to collapse
No, I've tried all of the roms with & without adding any apps.
Moon2 said:
No, I've tried all of the roms with & without adding any apps.
Click to expand...
Click to collapse
There's not exactly any errors other than this on dmesg.
Code:
<3>[ 475.735900] init: cannot execve('/system/bin/DxDrmServerIpc'): Permission denied
That isn't really a problem. Neither are these:
Code:
E/MobileDataStateTracker( 242): Error mapping networkType 23 to apnType.
Code:
D/MobileDataStateTracker( 242): internet: mMobileDataState=DISCONNECTED mTeardownRequested=false got [AnyDataCSC] : type=internet state=DISCONNECTED reason=dataDetached apn=null roaming=false unavailable=true NetworkType=0 NetworkTypeName=UNKNOWN entitleError=0 apnCarrier=null
I've just installed cm9 and run the logcat to just before it rebooted.
Moon2 said:
I've just installed cm9 and run the logcat to just before it rebooted.
Click to expand...
Click to collapse
Run Fix Permissions in recovery.
Also, send me another DMESG. Not during/while the phone is crashing.
DennisBold said:
Run Fix Permissions in recovery.
Also, send me another DMESG. Not during/while the phone is crashing.
Click to expand...
Click to collapse
It seems to reboot more frequently on a non-sense rom like cm9/10 than sense based roms like Miui or arhd and I don't think its rebooted or shutdown yet if it's been plugged in to charger/computer.
Moon2 said:
It seems to reboot more frequently on a non-sense rom like cm9/10 than sense based roms like Miui or arhd and I don't think its rebooted or shutdown yet if it's been plugged in to charger/computer.
Click to expand...
Click to collapse
Thanks.
Can you try:
Code:
adb shell
dmesg | grep mmc
And copy and paste the results?
You should see:
Code:
[email protected]:/ # dmesg | grep mmc
dmesg | grep mmc
[email protected]:/ #
---------- Post added at 08:04 PM ---------- Previous post was at 07:33 PM ----------
Could you run?
Code:
cat /sys/class/block/mmcblk0/device/name
Code:
[email protected]:/ $ dmesg | grep mmc
dmesg | grep mmc
1|[email protected]:/ $ cat /sys/class/block/mmcblk0/device/name
cat /sys/class/block/mmcblk0/device/name
MLL00M
Moon2 said:
Code:
[email protected]:/ $ dmesg | grep mmc
dmesg | grep mmc
1|[email protected]:/ $ cat /sys/class/block/mmcblk0/device/name
cat /sys/class/block/mmcblk0/device/name
MLL00M
Click to expand...
Click to collapse
Flash an RUU (preferably Gingerbread) and see if it makes any difference?
Run this from stock and see if you still have errors
Code:
adb shell
dmesg | grep mmc
logcat | grep mmc
DennisBold said:
Flash an RUU (preferably Gingerbread) and see if it makes any difference?
Run this from stock and see if you still have errors
Code:
adb shell
dmesg | grep mmc
logcat | grep mmc
Click to expand...
Click to collapse
Code:
dmesg | grep mmc
Code:
<5>[ 0.000000] Kernel command line: poweron_status=1 board_pyramid.disable_ua
rt3=0 diag.enabled=0 board_pyramid.debug_uart=0 userdata_sel=0 androidboot.emmc=
true androidboot.pagesize=2048 androidboot.baseband=10.14.9035.01_M androidboo
t.cid=11111111 androidboot.batt_poweron=good_battery androidboot.carrier=ALL and
roidboot.mid=PG5813000 androidboot.keycaps=qwerty androidboot.dq=FAIL androidboo
t.mode=normal androidboot.serialno=SH191V463715 androidboot.bootloader=1.17.1111
zygote_oneshot=off msm_watchdog.enable=1 console=ttyHSL0 androidboot.hardware=p
yramid no_console_suspend=1
<6>[ 0.335052] pyramid: pyramid_init_mmc
<6>[ 0.907806] Create /proc/emmc OK.
<3>[ 2.389921] mmc0: No card detect facilities available
<6>[ 2.390287] mmc0: Qualcomm MSM SDCC at 0x0000000012400000 irq 136,0 dma 18
<6>[ 2.390379] mmc0: Platform slot type: MMC
<6>[ 2.390562] mmc0: 8 bit data mode enabled
<6>[ 2.390654] mmc0: 4 bit data mode disabled
<6>[ 2.390745] mmc0: polling status mode disabled
<6>[ 2.390928] mmc0: MMC clock 400000 -> 48000000 Hz, PCLK 0 Hz
<6>[ 2.391020] mmc0: Slot eject status = 0
<6>[ 2.391203] mmc0: Power save feature enable = 1
<6>[ 2.391294] mmc0: DM non-cached buffer at ff007000, dma_addr 0x5751b000
<6>[ 2.391386] mmc0: DM cmd busaddr 0x5751b000, cmdptr busaddr 0x5751b300
<6>[ 2.391966] mmc1: Qualcomm MSM SDCC at 0x0000000012180000 irq 134,654 dma
20
<6>[ 2.392149] mmc1: Platform slot type: SD
<6>[ 2.392240] mmc1: 8 bit data mode disabled
<6>[ 2.392332] mmc1: 4 bit data mode enabled
<6>[ 2.392515] mmc1: polling status mode disabled
<6>[ 2.392607] mmc1: MMC clock 144000 -> 48000000 Hz, PCLK 0 Hz
<6>[ 2.392790] mmc1: Slot eject status = 0
<6>[ 2.392881] mmc1: Power save feature enable = 1
<6>[ 2.392973] mmc1: DM non-cached buffer at ff008000, dma_addr 0x5751c000
<6>[ 2.393156] mmc1: DM cmd busaddr 0x5751c000, cmdptr busaddr 0x5751c300
<6>[ 2.393644] mmc2: Qualcomm MSM SDCC at 0x00000000121c0000 irq 133,0 dma 21
<6>[ 2.393736] mmc2: Platform slot type: N/A
<6>[ 2.393919] mmc2: 8 bit data mode disabled
<6>[ 2.394010] mmc2: 4 bit data mode enabled
<6>[ 2.394102] mmc2: polling status mode disabled
<6>[ 2.394285] mmc2: MMC clock 400000 -> 48000000 Hz, PCLK 0 Hz
<6>[ 2.394377] mmc2: Slot eject status = 1
<6>[ 2.394468] mmc2: Power save feature enable = 1
<6>[ 2.394651] mmc2: DM non-cached buffer at ff009000, dma_addr 0x5751d000
<6>[ 2.394743] mmc2: DM cmd busaddr 0x5751d000, cmdptr busaddr 0x5751d300
<6>[ 2.513761] mmc0: new high speed MMC card at address 0001
<6>[ 2.526975] mmcblk0: mmc0:0001 MLL00M 2.25 GiB
<6>[ 2.527555] mmcblk0: p1 p2 p3 p4 < p5 p6
<6>[ 2.568296] EXT4-fs (mmcblk0p22): INFO: recovery required on readonly file
system
<6>[ 2.568662] EXT4-fs (mmcblk0p22): write access will be enabled during reco
very
<4>[ 2.666654] mmc1: high speed mode max_dtr = 50000000
<4>[ 2.667081] mmc1: host does not support reading read-only switch. assuming
write-enable.
<6>[ 2.667264] mmc1: new high speed SD card at address 1234
<6>[ 2.667753] mmcblk1: mmc1:1234 SA02G 1.83 GiB
<6>[ 2.668149] mmcblk1: p1
<6>[ 2.697813] EXT4-fs (mmcblk0p22): recovery complete
<6>[ 2.705625] EXT4-fs (mmcblk0p22): mounted filesystem with ordered data mod
e. Opts: (null)
<7>[ 3.291562] EXT4-fs (mmcblk0p23): ext4_orphan_cleanup: deleting unreferenc
ed inode 22945
<7>[ 3.292050] EXT4-fs (mmcblk0p23): ext4_orphan_cleanup: deleting unreferenc
ed inode 22946
<6>[ 3.292416] EXT4-fs (mmcblk0p23): 2 orphan inodes deleted
<6>[ 3.292691] EXT4-fs (mmcblk0p23): recovery complete
<6>[ 3.334836] EXT4-fs (mmcblk0p23): mounted filesystem with ordered data mod
e. Opts: nodelalloc
<6>[ 3.389493] EXT4-fs (mmcblk0p24): recovery complete
<6>[ 3.397031] EXT4-fs (mmcblk0p24): mounted filesystem with ordered data mod
e. Opts: nodelalloc
<6>[ 3.516964] EXT4-fs (mmcblk0p27): recovery complete
<6>[ 3.521115] EXT4-fs (mmcblk0p27): mounted filesystem with writeback data m
ode. Opts: nodelalloc
<6>[ 20.862468] mmc2: Slot status change detected (0 -> 1)
<7>[ 20.915202] mmc2: queuing CIS tuple 0x91 length 3
<6>[ 20.915446] mmc2: new high speed SDIO card at address 0001
Code:
logcat | grep mmc
I've left it running for a few mins but nothings showing up.
Its still not showing anything, but I'm attaching a logcat on stock gb upto the point it restarted.
have compiled a driver for the tablet P3110, but then
ifconfig wlan0 up
<4>[58561.661071] C1 [ ifconfig]
<4>[58561.661102] C1 [ ifconfig] Dongle Host Driver, version 1.15.11
<4>[58561.661132] C1 [ ifconfig] Compiled in drivers/net/wireless/bcmdhd/src on Nov 27 2013 at 18:58:47
<4>[58562.437103] C0 [ ifconfig] dhdsdio_htclk: HT Avail timeout (1000000): clkctl 0x50
<4>[58562.437133] C0 [ ifconfig] dhd_bus_init: clock state is wrong. state = 1
<4>[58562.437255] C0 [ ifconfig] dhd_bus_start failed bus is not ready
What's the problem?
I'm interested in this topic, been wanting to do this with this tablet as well.
Subscribed!
Please make works that driver , monitor mode
Following
Help!!!!
This driver and bin files for CM_10.2 (Galaxy TAB 3110), but when I do:
insmod ./dhd.ko iface_name=wlan0 firmware_path=./bcm4330_sta.bcmon.bin nvram_path=/system/etc/wifi/nvram_net.txt
lsmod
dhd 392776 0 - Live 0x00000000
pvrsrvkm_sgx540_120 385106 60 - Live 0x00000000
ifconfig wlan0 up
error: SIOCSIFFLAGS (Operation not permitted)
Hello,
I've had a few reboots and debugging the problem, I've discovered this:
last_kmsg:
----
[90978.707145] mmc1: data txfr (0x00100000) error: -110 after 671 ms
[90978.707258] sdhci: =========== REGISTER DUMP (mmc1)===========
[90978.707300] sdhci: Sys addr: 0x80000008 | Version: 0x00003802
[90978.707373] sdhci: Blk size: 0x00007200 | Blk cnt: 0x00000008
[90978.707413] sdhci: Argument: 0x003f0a10 | Trn mode: 0x0000002b
[90978.707486] sdhci: Present: 0x01e80100 | Host ctl: 0x00000035
[90978.707526] sdhci: Power: 0x0000000b | Blk gap: 0x00000000
[90978.707598] sdhci: Wake-up: 0x00000000 | Clock: 0x00000007
[90978.707639] sdhci: Timeout: 0x0000000c | Int stat: 0x00000000
[90978.707680] sdhci: Int enab: 0x03ff800b | Sig enab: 0x03ff800b
[90978.707752] sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[90978.707793] sdhci: Caps: 0x642dc8b2 | Caps_1: 0x00008007
[90978.707864] sdhci: Cmd: 0x0000193a | Max curr: 0x00000000
[90978.707905] sdhci: Resp 1: 0x00000000 | Resp 0: 0x00000900
[90978.707978] sdhci: Resp 3: 0x00000900 | Resp 2: 0x00000000
[90978.708017] sdhci: Host ctl2: 0x00000003
[90978.708057] sdhci: ADMA Err: 0x00000003 | ADMA Ptr: 0x35a40008
[90978.708128] mmc1: clk: 200000000 clk-gated: 0 claimer: mmcqd/1 pwr: 10
[90978.708199] mmc1: rpmstatus[pltfm](runtime-suspend:usage_count:disable_depth)(0:0:0)
[90978.708239] sdhci: ===========================================
[90978.712431] mmcblk0: error -110 transferring data, sector 4131344, nr 8, cmd response 0x900, card status 0x100c02
[90978.712514] end_request: I/O error, dev mmcblk0, sector 4131344
[90978.712559] end_request: I/O error, dev mmcblk0, sector 4131344
[90978.712667] Aborting journal on device mmcblk0p28-8.
[90978.713769] journal commit I/O error
[90978.714748] done.
---
---
[90979.265686] EXT4-fs error (device mmcblk0p28): ext4_journal_start_sb:328: Detected aborted journal
[90979.265968] EXT4-fs (mmcblk0p28): Remounting filesystem read-only
[90979.267079] Kernel panic - not syncing: EXT4-fs panic from previous error
[90979.267085]
[90979.267243] [<c010de1c>] (unwind_backtrace+0x0/0x144) from [<c09fd44c>] (dump_stack+0x20/0x24)
[90979.267385] [<c09fd44c>] (dump_stack+0x20/0x24) from [<c09fde5c>] (panic+0x9c/0x21c)
[90979.267526] [<c09fde5c>] (panic+0x9c/0x21c) from [<c030f298>] (__ext4_abort+0xe0/0xf4)
[90979.267668] [<c030f298>] (__ext4_abort+0xe0/0xf4) from [<c030f624>] (ext4_journal_start_sb+0xa0/0x1a4)
[90979.267757] [<c030f624>] (ext4_journal_start_sb+0xa0/0x1a4) from [<c02f7920>] (ext4_dirty_inode+0x24/0x50)
[90979.267905] [<c02f7920>] (ext4_dirty_inode+0x24/0x50) from [<c028c4ec>] (__mark_inode_dirty+0x3c/0x1e0)
[90979.268048] [<c028c4ec>] (__mark_inode_dirty+0x3c/0x1e0) from [<c02f5538>] (ext4_setattr+0xd0/0x414)
[90979.268192] [<c02f5538>] (ext4_setattr+0xd0/0x414) from [<c027e6a4>] (notify_change+0x198/0x2b8)
[90979.268336] [<c027e6a4>] (notify_change+0x198/0x2b8) from [<c0262264>] (chown_common+0x7c/0x94)
[90979.268477] [<c0262264>] (chown_common+0x7c/0x94) from [<c0262fd8>] (sys_fchown+0x74/0x98)
[90979.268563] [<c0262fd8>] (sys_fchown+0x74/0x98) from [<c0107300>] (ret_fast_syscall+0x0/0x30)
[90979.268701] CPU0: stopping
[90979.268752] [<c010de1c>] (unwind_backtrace+0x0/0x144) from [<c09fd44c>] (dump_stack+0x20/0x24)
[90979.268836] [<c09fd44c>] (dump_stack+0x20/0x24) from [<c010c890>] (handle_IPI+0x198/0x1cc)
[90979.268919] [<c010c890>] (handle_IPI+0x198/0x1cc) from [<c0100590>] (gic_handle_irq+0xb0/0xf4)
[90979.269003] [<c0100590>] (gic_handle_irq+0xb0/0xf4) from [<c0106f00>] (__irq_svc+0x40/0x70)
[90979.269047] Exception stack(0xed7add28 to 0xed7add70)
[90979.269121] dd20: 00000004 00000004 00000004 00000001 ed7addac c2401bc0
[90979.269164] dd40: c2401bc0 013d1000 c2401bc8 00000001 00000001 ed7add9c 00000002 ed7add70
[90979.269236] dd60: c011969c c01e02c0 20000113 ffffffff
[90979.269312] [<c0106f00>] (__irq_svc+0x40/0x70) from [<c01e02c0>] (generic_exec_single+0x7c/0xa0)
[90979.269358] [<c01e02c0>] (generic_exec_single+0x7c/0xa0) from [<c01e06f0>] (smp_call_function_single+0x10c/0x1e8)
[90979.269435] [<c01e06f0>] (smp_call_function_single+0x10c/0x1e8) from [<c01e0ca0>] (smp_call_function_many+0x248/0x298)
[90979.269511] [<c01e0ca0>] (smp_call_function_many+0x248/0x298) from [<c01e0d40>] (smp_call_function+0x50/0x7c)
[90979.269591] [<c01e0d40>] (smp_call_function+0x50/0x7c) from [<c070ac0c>] (cpuidle_latency_notify+0x28/0x30)
[90979.269670] [<c070ac0c>] (cpuidle_latency_notify+0x28/0x30) from [<c01b9df0>] (notifier_call_chain+0x54/0x94)
[90979.269748] [<c01b9df0>] (notifier_call_chain+0x54/0x94) from [<c01ba270>] (__blocking_notifier_call_chain+0x58/0x70)
[90979.269829] [<c01ba270>] (__blocking_notifier_call_chain+0x58/0x70) from [<c01ba2b0>] (blocking_notifier_call_chain+0x28/0x30)
[90979.269914] [<c01ba2b0>] (blocking_notifier_call_chain+0x28/0x30) from [<c01cfd28>] (pm_qos_update_target+0xf0/0x13c)
[90979.269996] [<c01cfd28>] (pm_qos_update_target+0xf0/0x13c) from [<c01cff74>] (pm_qos_update_request+0x64/0x94)
[90979.270080] [<c01cff74>] (pm_qos_update_request+0x64/0x94) from [<c0729bf0>] (sdhci_disable+0x58/0x5c)
[90979.270131] [<c0729bf0>] (sdhci_disable+0x58/0x5c) from [<c070daa0>] (mmc_release_host+0xb0/0xc8)
[90979.270181] [<c070daa0>] (mmc_release_host+0xb0/0xc8) from [<c0722c40>] (mmc_blk_issue_rq+0x298/0x7a4)
[90979.270262] [<c0722c40>] (mmc_blk_issue_rq+0x298/0x7a4) from [<c0723aec>] (mmc_queue_thread+0xb0/0x17c)
[90979.270348] [<c0723aec>] (mmc_queue_thread+0xb0/0x17c) from [<c01b3690>] (kthread+0x98/0xa4)
[90979.270434] [<c01b3690>] (kthread+0x98/0xa4) from [<c0107f60>] (kernel_thread_exit+0x0/0x8)
[90980.270823] Rebooting in 5 seconds..
[90985.272517] Going down for restart now
[90985.273319] Calling SCM to disable SPMI PMIC arbiter
No errors detected
Boot info:
Last boot reason: kernel_panic
---
As far as I can tell, the device has problems writing to flash memory and panics. Is there a way to assing "bad blocks" to certain parts of the flash to make sure the OS won't try to write there any more?
Any way to do a manual fsck?
I'm proficient in Linux, but haven't had much contact with ARM based embedded devices so far.
RMA it, your flash storage seems to have died.
ApTeM said:
RMA it, your flash storage seems to have died.
Click to expand...
Click to collapse
Did some research and managed to fsck the filesystems through adb shell. Also, using linaro kernel now. Haven't had any random reboots after this.
Might have been a problem with the FS or a kernel hickup. Who knows.
If the problem returns then I probably have no other options than to RMA it, yes.
The problem is that the phome was bought through UK Play store by my sister and I live in Estonia myself. So RMA is a bit problematic
I'm in a worse boat - my phone was bought in the US and I live in eastern Europe.
What's wrong with yours?
m3ph1570 said:
What's wrong with yours?
Click to expand...
Click to collapse
11 dead pixels.
m3ph1570 said:
Did some research and managed to fsck the filesystems through adb shell. Also, using linaro kernel now. Haven't had any random reboots after this.
Might have been a problem with the FS or a kernel hickup. Who knows.
If the problem returns then I probably have no other options than to RMA it, yes.
The problem is that the phome was bought through UK Play store by my sister and I live in Estonia myself. So RMA is a bit problematic
Click to expand...
Click to collapse
Could you expand on the part how you fixed it? Especially the fsck part
Thanks
tasubo said:
Could you expand on the part how you fixed it? Especially the fsck part
Thanks
Click to expand...
Click to collapse
https://en.wikipedia.org/wiki/Fsck
The utility is available in TWRP.
Wasn't really able to fix it. The storage on my phone has some bad sectors and I experience some random reboots still. Haven't figured out a way to mark those sectors bad manually.
Because of the random reboots, I can't encrypt my storage (password protected boot). It'd be stuck at the password prompt after every reboot in my pocket.
Hi I'm facing same problem as you, even with a similar kmsg bug report, were you able to fix it?
Code:
Checking Boot Mode ... SDMMC
REVISION: 1.0
REVISION: 1.0
MMC Device 0: 7691 MB
[ERROR] response timeout error : 00000104 cmd 1
[ERROR] response timeout error : 00000104 cmd 1
MMC Device 1: 0 MB
MMC Device 2 not found
*** Warning - using default environment
Hit any key to stop autoboot: 0
reading kernel..device 0 Start 1063, Count 10240
MMC read: dev # 0, block # 1063, count 10240 ... 10240 blocks read: OK
completed
reading RFS..device 0 Count 11303, Start 2048
MMC read: dev # 0, block # 11303, count 2048 ... 2048 blocks read: OK
completed
Boot with zImage
## Loading init Ramdisk from Legacy Image at 41000000 ...
Image Name: Android Ramdisk Image
Image Type: ARM Linux RAMDisk Image (uncompressed)
Data Size: 167666 Bytes = 167666 Load Address: 40800000
Entry Point: 40800000
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.0.31-g3370a7c ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP PREEMPT Fri Feb 21 21:47:51 MST 2014
CPU: ARMv7 Processor [410fc0f4] revision 4 (ARMv7), cr=10c5387d
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: ARNDALE
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Memory policy: ECC disabled, Data cache writealloc
S3C24XX Clocks, Copyright 2004 Simtec Electronics
s3c_register_clksrc: clock audiocdclk has no registers set
audiocdclk: no parent clock specified
EXYNOS5: PLL settings, A=1400000000, B=1333090909, C=333000000
M=1600000000, E=96000000, V=300000000, G=533000000
EXYNOS5: ARMCLK=1400000000, CDREX=800000000, ACLK400=533000000
ACLK333=333000000, ACLK266=266666666, ACLK200=200000000
ACLK166=166500000, ACLK66=66666666
uclk1: source is mout_mpll_user (6), rate is 200000000
uclk1: source is mout_mpll_user (6), rate is 200000000
uclk1: source is ext_xtal (0), rate is 6000000
uclk1: source is mout_mpll_user (6), rate is 200000000
sclk_usbdrd30: source is mout_mpll (0), rate is 66666666
sclk_fimd: source is ext_xtal (0), rate is 24000000
aclk_266_gscl: source is aclk_266 (1), rate is 266666666
sclk_g3d: source is mout_mpll_user (0), rate is 800000000
sclk_sata: source is mout_mpll_user (0), rate is 66666666
sclk_gscl_wrap0: source is ext_xtal (0), rate is 24000000
sclk_gscl_wrap1: source is ext_xtal (0), rate is 24000000
sclk_cam0: source is ext_xtal (0), rate is 24000000
sclk_cam1: source is ext_xtal (0), rate is 24000000
PERCPU: Embedded 7 pages/cpu @c2036000 s7744 r8192 d12736 u32768
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 519938
Kernel command line: console=ttySAC2,115200n8 vmalloc=512M androidboot.console=ttySAC2
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 2047MB = 2047MB total
Memory: 1839508k/1839508k available, 256620k reserved, 1735680K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xfea00000 - 0xffe00000 ( 20 MB)
vmalloc : 0xd6800000 - 0xf6000000 ( 504 MB)
lowmem : 0xc0000000 - 0xd6000000 ( 352 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.init : 0xc0008000 - 0xc0043000 ( 236 kB)
.text : 0xc0043000 - 0xc0724000 (7044 kB)
.data : 0xc0724000 - 0xc07876a0 ( 398 kB)
.bss : 0xc07876c4 - 0xc08e7978 (1409 kB)
SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
Preemptible hierarchical RCU implementation.
NR_IRQS:552
Console: colour dummy device 80x30
Calibrating delay loop... 2795.11 BogoMIPS (lpj=6987776)
[ 0.045000] pid_max: default: 32768 minimum: 301
[ 0.045000] Mount-cache hash table entries: 512
[ 0.045000] Initializing cgroup subsys debug
[ 0.045000] Initializing cgroup subsys cpuacct
[ 0.045000] Initializing cgroup subsys freezer
[ 0.045000] CPU: Testing write buffer coherency: ok
[ 0.045000] hw perfevents: enabled with ARMv7 Cortex-A15 PMU driver, 7 counters available
[ 0.085000] CPU1: Booted secondary processor
[ 0.095000] Brought up 2 CPUs
[ 0.095000] SMP: Total of 2 processors activated (5590.22 BogoMIPS).
[ 0.100000] gpio: GPZ has no PM function
[ 0.100000] print_constraints: dummy:
[ 0.100000] NET: Registered protocol family 16
[ 0.105000] SMDK MAIN Board Rev 0.2 (ADC value:783)
[ 0.110000] ath6kl_set_platform_data ~~~~~~~~~~~~~~~~
[ 0.110000] hw-breakpoint: debug architecture 0x5 unsupported.
[ 0.110000] exynos5_pmu_init: PMU supports 52XX(98)
[ 0.110000] S3C Power Management, Copyright 2004 Simtec Electronics
[ 0.115000] EXYNOS5: Initializing architecture
[ 0.115000] s3c-adc samsung-adc-v4: attached adc driver
[ 0.115000] samsung-pd samsung-pd.0: power domain registered
[ 0.115000] samsung-pd samsung-pd.1: power domain registered
[ 0.115000] samsung-pd samsung-pd.8: power domain registered
[ 0.115000] samsung-pd samsung-pd.9: power domain registered
[ 0.115000] samsung-pd samsung-pd.10: power domain registered
[ 0.115000] samsung-pd samsung-pd.11: power domain registered
[ 0.115000] s3c24xx-pwm s3c24xx-pwm.0: tin at 66666666, tdiv at 66666666, tin=divclk, base 0
[ 0.115000] EXYNOS ASV PMIC MAXIM Detected!
[ 0.115000] VDD_ARM[SG FUSED] ASV group is 6
[ 0.115000] VDD_INT[SG FUSED] ASV group is 6
[ 0.115000] VDD_MIF[SG FUSED] ASV group is 2
[ 0.115000] VDD_G3D[SG FUSED] ASV group is 6
[ 0.135000] bio: create slab <bio-0> at 0
[ 0.135000] print_constraints: VDD_1.8V: 1800 mV
[ 0.135000] print_constraints: DC_5V: 5000 mV
[ 0.135000] print_constraints: VDD_3.3V: 3300 mV
[ 0.135000] print_constraints: DC_5V: 5000 mV
[ 0.135000] rdev_init_debugfs: DC_5V: Failed to create debugfs directory
[ 0.135000] print_constraints: CAM_SENSOR_0: 1800 mV
[ 0.135000] SCSI subsystem initialized
[ 0.140000] usbcore: registered new interface driver usbfs
[ 0.140000] usbcore: registered new interface driver hub
[ 0.140000] usbcore: registered new device driver usb
[ 0.140000] s5m87xx 0-0066: S5M MFD Detected. DEVICE ID = 5
[ 0.140000] print_constraints: vdd_ldo4: 1800 mV
[ 0.145000] print_constraints: vdd_mif range: 950 <--> 1300 mV at 1100 mV
[ 0.145000] print_constraints: vdd_arm range: 800 <--> 1350 mV at 1200 mV
[ 0.145000] print_constraints: vdd_int range: 900 <--> 1200 mV at 1200 mV
[ 0.145000] print_constraints: vdd_g3d range: 700 <--> 1300 mV at 1200 mV
[ 0.145000] print_constraints: vdd_ldo11 range: 1900 mV
[ 0.145000] print_constraints: vdd_ldo14 range: 1900 mV
[ 0.145000] s5m87xx 0-0066: S5M87xx MFD probe done!!!
[ 0.145000] s3c-i2c s3c2440-i2c.0: i2c-0: S3C I2C adapter
[ 0.145000] s3c-i2c s3c2440-i2c.7: i2c-7: S3C I2C adapter
[ 0.150000] s3c-i2c s3c2440-i2c.2: i2c-2: S3C I2C adapter
[ 0.150000] s3c-i2c s3c2440-i2c.3: i2c-3: S3C I2C adapter
[ 0.150000] s3c-i2c s3c2440-i2c.4: i2c-4: S3C I2C adapter
[ 0.150000] s3c-i2c s3c2440-i2c.5: i2c-5: S3C I2C adapter
[ 0.150000] s3c-i2c s3c2440-hdmiphy-i2c: i2c-8: S3C I2C adapter
[ 0.150000] Advanced Linux Sound Architecture Driver Version 1.0.24.
[ 0.150000] Bluetooth: Core ver 2.16
[ 0.150000] NET: Registered protocol family 31
[ 0.150000] Bluetooth: HCI device and connection manager initialized
[ 0.150000] Bluetooth: HCI socket layer initialized
[ 0.150000] Bluetooth: L2CAP socket layer initialized
[ 0.150000] Bluetooth: SCO socket layer initialized
[ 0.150000] Switching to clocksource mct-frc
[ 0.151036] Switched to NOHz mode on CPU #0
[ 0.154969] Switched to NOHz mode on CPU #1
[ 0.155058] cfg80211: Calling CRDA to update world regulatory domain
[ 0.168386] NET: Registered protocol family 2
[ 0.168544] IP route cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.169053] TCP established hash table entries: 65536 (order: 7, 524288 bytes)
[ 0.169759] TCP bind hash table entries: 65536 (order: 7, 786432 bytes)
[ 0.170546] TCP: Hash tables configured (established 65536 bind 65536)
[ 0.170554] TCP reno registered
[ 0.170564] UDP hash table entries: 256 (order: 1, 8192 bytes)
[ 0.170580] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[ 0.170784] NET: Registered protocol family 1
[ 0.170914] Trying to unpack rootfs image as initramfs...
[ 0.176996] Freeing initrd memory: 160K
[ 0.177086] PMU: registered new PMU device of type 0
[ 0.177237] Exynos5 : ARM Clock down on idle mode is enabled
[ 0.177554] Loaded driver for PL330 DMAC-0 s3c-pl330
[ 0.177563] DBUFF-64x8bytes Num_Chans-8 Num_Peri-1 Num_Events-32
[ 0.177644] Loaded driver for PL330 DMAC-1 s3c-pl330
[ 0.177651] DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[ 0.177727] Loaded driver for PL330 DMAC-2 s3c-pl330
[ 0.177734] DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[ 0.183261] highmem bounce pool size: 64 pages
[ 0.183466] ashmem: initialized
[ 0.191472] fuse init (API version 7.16)
[ 0.191787] msgmni has been set to 203
[ 0.192563] io scheduler noop registered
[ 0.192571] io scheduler deadline registered
[ 0.192607] io scheduler cfq registered (default)
[ 0.405053] s5p-mipi-dsim s5p-mipi-dsim: DSI Master driver has been completed.
[ 0.405064] s5p-mipi-dsim s5p-mipi-dsim: DSI Master state is stop state
[ 0.677067] s5p-mipi-dsim s5p-mipi-dsim: mipi-dsi driver(RGB mode) has been probed.
[ 0.677416] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 0.735283] s5pv210-uart.0: ttySAC0 at MMIO 0x12c00000 (irq = 16) is a S3C6400/10
[ 0.750067] s5pv210-uart.1: ttySAC1 at MMIO 0x12c10000 (irq = 20) is a S3C6400/10
[ 0.765066] s5pv210-uart.2: ttySAC2 at MMIO 0x12c20000 (irq = 24) is a S3C6400/10
[ 1.662745] console [ttySAC2] enabled
[ 1.680066] s5pv210-uart.3: ttySAC3 at MMIO 0x12c30000 (irq = 28) is a S3C6400/10
[ 1.701966] mali mali-t604.0: Probed as mali0
[ 1.705550] UMP: UMP device driver r1p0-04rel0 loaded
[ 1.715955] brd: module loaded
[ 1.720571] loop: module loaded
[ 1.722300] ============ gps power probe !!!!! ===============
[ 1.728459] ============ gps power reset !!!!! ===============
[ 1.735146] print_constraints: AVDD1: at 3000 mV
[ 1.739564] print_constraints: DCVDD: at 1000 mV
[ 1.744579] wm8994 3-001a: WM8994 revision C
[ 1.755066] wm8994 3-001a: No interrupt specified, no interrupts
[ 1.759988] i2c-core: driver [wm8994] using legacy suspend method
[ 1.765666] i2c-core: driver [wm8994] using legacy resume method
[ 3.035047] mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 392157Hz, actual 390625HZ div = 64)
[ 3.085099] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[ 3.133326] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[ 3.141667] wm8994-codec wm8994-codec: Failed to request Mic1 short IRQ: -22
[ 3.148673] mmc1: new high speed SDHC card at address b368
[ 3.154087] wm8994-codec wm8994-codec: Failed to request Mic2 detect IRQ: -22
[ 3.161247] usb 1-3.2.4: new high speed USB device number 4 using s5p-ehci
[ 3.168184] wm8994-codec wm8994-codec: Failed to request Mic2 short IRQ: -22
[ 3.175242] mmcblk0: mmc1:b368 MS 7.51 GiB
[ 3.180693] mmcblk0: p1 p2 p3 p4
[ 3.210042] mmc_host mmc2: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[ 3.228610] asoc: wm8994-aif1 <-> samsung-i2s.0 mapping ok
[ 3.233332] ALSA device list:
[ 3.235603] #0: Arndale
[ 3.238224] GACT probability NOT on
[ 3.241672] Mirror/redirect action on
[ 3.245349] u32 classifier
[ 3.248028] Actions configured
[ 3.251375] Netfilter messages via NETLINK v0.30.
[ 3.256080] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[ 3.262784] ctnetlink v0.93: registering with nfnetlink.
[ 3.267414] NF_TPROXY: Transparent proxy support initialized, version 4.1.0
[ 3.274338] NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.
[ 3.280192] mmc_host mmc2: Bus speed (slot 0) = 50000000Hz (slot req 392157Hz, actual 390625HZ div = 64)
[ 3.289939] xt_time: kernel timezone is -0000
[ 3.295867] IPv4 over IPv4 tunneling driver
[ 3.299490] GRE over IPv4 demultiplexor driver
[ 3.303431] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 3.308464] arp_tables: (C) 2002 David S. Miller
[ 3.312922] TCP cubic registered
[ 3.316714] NET: Registered protocol family 10
[ 3.323136] Mobile IPv6
[ 3.324117] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 3.329657] IPv6 over IPv4 tunneling driver
[ 3.335051] mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[ 3.344917] NET: Registered protocol family 17
[ 3.347923] NET: Registered protocol family 15
[ 3.352395] Bluetooth: RFCOMM socket layer initialized
[ 3.357420] Bluetooth: RFCOMM ver 1.11
[ 3.361179] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 3.366436] Bluetooth: BNEP filters: protocol multicast
[ 3.371651] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 3.377705] NET: Registered protocol family 35
[ 3.382475] rfkill_gpio rfkill_gpio: arndale-bt device registered.
[ 3.388263] EXYNOS5250: Adaptive Support Voltage init
[ 3.390070] mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 392157Hz, actual 390625HZ div = 64)
[ 3.402598] EXYNOS5250(SG): ORIG : 6 MOD : 0 RESULT : 6
[ 3.407866] VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0
[ 3.415519] Registering SWP/SWPB emulation handler
[ 3.420272] DVFS : VDD_ARM Voltage table set with 6 Group
[ 3.425628] VDD_ARM : L0, 0 uV
[ 3.428275] VDD_G3D : Voltage table set with 6 Group, exynos_lot_id : 0
[ 3.435246] VDD_ARM : L1, 0 uV
[ 3.438262] VDD_ARM : L2, 0 uV
[ 3.441313] VDD_ARM : L3, 0 uV
[ 3.444329] VDD_ARM : L4, 0 uV
[ 3.447378] VDD_ARM : L5, 1212500 uV
[ 3.450932] VDD_ARM : L6, 1175000 uV
[ 3.454468] VDD_ARM : L7, 1125000 uV
[ 3.458039] VDD_ARM : L8, 1087500 uV
[ 3.461596] VDD_ARM : L9, 1062500 uV
[ 3.465145] VDD_ARM : L10, 1024999 uV
[ 3.468769] VDD_ARM : L11, 1000000 uV
[ 3.472424] VDD_ARM : L12, 975000 uV
[ 3.475978] VDD_ARM : L13, 950000 uV
[ 3.479516] VDD_ARM : L14, 937500 uV
[ 3.483183] VDD_ARM : L15, 912500 uV
[ 3.486638] VDD_ARM : L16, 900000 uV
[ 3.490191] VDD_ARM : L17, 900000 uV
[ 3.493728] VDD_ARM : L18, 900000 uV
[ 3.497301] VDD_ARM : L19, 900000 uV
[ 3.500853] VDD_ARM : L20, 900000 uV
[ 3.504737] [ 6 ] Memory is not LPDDR type.
[ 3.508627] DVFS : VDD_INT Voltage table set with 6 Group
[ 3.513942] DVFS : VDD_INT Voltage of L0 level is 975000
[ 3.519323] DVFS : VDD_MIF Voltage table set with 0 Group
[ 3.524685] DVFS : VDD_MIF Voltage of L0 level is 1037500
[ 3.531095] Failed to init busfreq.
[ 3.533758] exynos_integrated_dvfs_hotplug_init, max(1700000),min(200000)
[ 3.540515] ** temperature set value **
[ 3.540518] Throttling stop_temp = 82 start_temp = 85
[ 3.540523] Waring stop_temp = 95 start_tmep = 103
[ 3.540526] Tripping temp = 110
[ 3.540529] Hw_tripping temp = 113
[ 3.540532] Trhottling freq = 800000 Warning freq = 200000
[ 3.568542] TC_voltage stop_temp = 13 Start_temp = 10
[ 3.573656] exynos5250_find_busfreq_by_volt: req_volt has no value.
[ 3.579891] get_busfreq_value error
[ 3.583358] exynos_tmu_init: cpufreq_level[14], busfreq_value[0]
[ 3.590362] Tmu Initialization is sucessful...!
[ 3.596374] s3c-fb exynos5-fb.1: window 2: fb
[ 3.600574] s3c-fb exynos5-fb.1: window 1: fb
[ 3.604953] s3c-fb exynos5-fb.1: window 0: fb
[ 3.612644] otg_wakelock_init: No OTG transceiver found
[ 3.616432] s3c-rtc exynos-rtc: setting system clock to 2000-01-01 00:00:02 UTC (946684802)
[ 3.624923] Freeing init memory: 236K
[ 3.636324] init: could not import file 'init.mt6620.rc' from '/init.arndale.rc'
[ 3.642471] init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
[ 3.782918] init: cannot open '/initlogo.rle'
[ 3.905808] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 3.930212] ASIX USB Ethernet Adapter:v4.4.0 21:45:46 Feb 21 2014
[ 3.930246] <6> http://www.asix.com.tw
[ 3.939341] eth%d: status ep1in, 8 bytes period 11
[ 3.961136] EXT4-fs (mmcblk0p4): warning: checktime reached, running e2fsck is recommended
[ 3.971457] eth0: register 'asix' at usb-s5p-ehci-3.2.4, ASIX AX88772A USB 2.0 Ethernet, 00:00:00:00:00:00
[ 3.980628] EXT4-fs (mmcblk0p4): recovery complete
[ 3.987703] EXT4-fs (mmcblk0p4): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=panic
[ 5.610836] EXT4-fs (mmcblk0p3): warning: checktime reached, running e2fsck is recommended
[ 6.010442] EXT4-fs (mmcblk0p3): recovery complete
[ 6.114691] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,noauto_da_alloc,errors=panic
[ 6.186538] init: cannot find '/system/bin/rild', disabling 'ril-daemon'
[ 6.237436] init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
[ 6.266535] adb_open
[ 6.267283] mtp_bind_config
[ 6.270272] adb_bind_config
[ 6.275425] android_work: did not send uevent (0 0 (null))
[email protected]:/ $ [ 7.293438] LOW resolution is reported
[ 7.491024] ion_share_mmap: trying to map larger area than handle has available
[ 7.498863] ion_share_mmap: trying to map larger area than handle has available
[ 13.729169] warning: `zygote' uses 32-bit capabilities (legacy support in use)
[ 14.505784] request_suspend_state: wakeup (3->0) at 14505776635 (2000-01-01 00:00:13.384388132 UTC)
[ 14.514760] init: untracked pid 1426 exited
[ 14.518119] init: untracked pid 1431 exited
[ 16.843227] request_suspend_state: wakeup (0->0) at 16843219718 (2000-01-01 00:00:15.721830799 UTC)
[ 16.851963] init: untracked pid 1806 exited
[ 16.856005] init: untracked pid 1805 exited
[ 22.096914] request_suspend_state: wakeup (0->0) at 22096905679 (2000-01-01 00:00:20.975517177 UTC)
[ 22.107107] init: untracked pid 2003 exited
[ 22.109837] init: untracked pid 2004 exited
[ 1.771653] Uniform Multi-Platform E-IDE driver
[ 1.776367] ide-gd driver 1.18
[ 1.779439] rdac: device handler registered
[ 1.783403] hp_sw: device handler registered
[ 1.787594] emc: device handler registered
[ 1.791672] alua: device handler registered
[ 1.798285] ahci ahci: AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl platform mode
[ 1.804559] ahci ahci: flags: ncq sntf pm led clo only pmp pio slum part ccc apst
[ 1.812112] VDD_G3D : Voltage table set with 0 Group, exynos_lot_id : 0
[ 1.819530] scsi0 : ahci_platform
[ 1.822325] ata1: SATA max UDMA/133 mmio [mem 0x122f0000-0x122fffff] port 0x100 irq 179
[ 1.830444] usbcore: registered new interface driver asix
[ 1.835421] usbcore: registered new interface driver cdc_ether
[ 1.841244] usbcore: registered new interface driver net1080
[ 1.846859] usbcore: registered new interface driver cdc_subset
[ 1.852751] usbcore: registered new interface driver zaurus
[ 1.858210] cdc_ncm: 04-Aug-2011
[ 1.861517] usbcore: registered new interface driver cdc_ncm
[ 1.867040] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.873738] s5p-ehci s5p-ehci: S5P EHCI Host Controller
[ 1.878753] s5p-ehci s5p-ehci: new USB bus registered, assigned bus number 1
[ 1.885804] s5p-ehci s5p-ehci: irq 135, io mem 0x12110000
[ 1.900055] s5p-ehci s5p-ehci: USB 0.0 started, EHCI 1.00
[ 1.904418] hub 1-0:1.0: USB hub found
[ 1.907722] hub 1-0:1.0: 3 ports detected
[ 1.912129] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 1.917910] s5p-ohci s5p-ohci: Already power on PHY
[ 1.922707] s5p-ohci s5p-ohci: s5p OHCI
[ 1.926529] s5p-ohci s5p-ohci: new USB bus registered, assigned bus number 2
[ 1.933551] s5p-ohci s5p-ohci: irq 135, io mem 0x12120000
[ 1.994539] hub 2-0:1.0: USB hub found
[ 1.996836] hub 2-0:1.0: 3 ports detected
[ 2.001359] exynos-xhci exynos-xhci: EXYNOS xHCI Host Controller
[ 2.006805] exynos-xhci exynos-xhci: new USB bus registered, assigned bus number 3
[ 2.014545] exynos-xhci exynos-xhci: irq 136, io mem 0x12000000
[ 2.020648] hub 3-0:1.0: USB hub found
[ 2.023941] hub 3-0:1.0: 1 port detected
[ 2.028109] exynos-xhci exynos-xhci: EXYNOS xHCI Host Controller
[ 2.033840] exynos-xhci exynos-xhci: new USB bus registered, assigned bus number 4
[ 2.041828] hub 4-0:1.0: USB hub found
[ 2.045105] hub 4-0:1.0: 1 port detected
[ 2.049467] usbcore: registered new interface driver cdc_acm
[ 2.054641] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 2.062612] Initializing USB Mass Storage driver...
[ 2.067596] usbcore: registered new interface driver usb-storage
[ 2.073446] USB Mass Storage support registered.
[ 2.078242] usbcore: registered new interface driver usbserial
[ 2.083848] usbserial: USB Serial Driver core
[ 2.088257] USB Serial support registered for pl2303
[ 2.093253] usbcore: registered new interface driver pl2303
[ 2.098655] pl2303: Prolific PL2303 USB to serial adaptor driver
[ 2.104882] s3c-udc : S3C HS USB OTG Device Driver,(c) 2008-2009 Samsung Electronics
[ 2.104887] s3c-udc : version 15 March 2009
[ 2.118676] android_usb gadget: Mass Storage Function, version: 2009/09/11
[ 2.124077] android_usb gadget: Number of LUNs=1
[ 2.128700] lun0: LUN: removable file: (no medium)
[ 2.133901] android_usb gadget: android_usb ready
[ 2.138214] Registered gadget driver 'android_usb'
[ 2.142973] s3c-usbgadget s3c-usbgadget: Already power on PHY
[ 2.148722] ata1: SATA link down (SStatus 0 SControl 300)
[ 2.155169] android_work: did not send uevent (0 0 (null))
[ 2.159788] android_work: did not send uevent (0 0 (null))
[ 2.165478] mousedev: PS/2 mouse device common for all mice
[ 2.171679] input: gpio-keys as /devices/platform/gpio-keys.0/input/input0
[ 2.178534] input: unidisplay_ts as /devices/platform/s3c2440-i2c.7/i2c-7/7-0041/input/input1
[ 2.186571] Unidisplay touch driver registered successfully
[ 2.192568] S3C24XX RTC, (c) 2004,2006 Simtec Electronics
[ 2.197219] s3c-rtc exynos-rtc: rtc disabled, re-enabling
[ 2.202511] s3c-rtc exynos-rtc: rtc clk out disabled, re-enabling
[ 2.208607] s3c-rtc exynos-rtc: warning: invalid RTC value so initializing it
[ 2.216038] using rtc device, s3c, for alarms
[ 2.219868] s3c-rtc exynos-rtc: rtc core: registered s3c as rtc0
[ 2.226016] usb 1-3: new high speed USB device number 2 using s5p-ehci
[ 2.232633] i2c /dev entries driver
[ 2.237173] Linux media interface: v0.10
[ 2.239962] Linux video capture interface: v2.00
[ 2.244540] many: s5k4ecgx_mod_init
[ 2.248067] S5P MFC V4L2 Driver, (c) 2010 Samsung Electronics
[ 2.253925] s5p-mfc s5p-mfc-v6: decoder registered as /dev/video6
[ 2.259866] s5p-mfc s5p-mfc-v6: encoder registered as /dev/video7
[ 2.266269] exynos-mdev.0: Media0[0xcbb9f800] was registered successfully
[ 2.272709] exynos-mdev.1: Media1[0xcbb9e000] was registered successfully
[ 2.279452] exynos-mdev.2: Media2[0xcbb9c800] was registered successfully
[ 2.286290] s5p-mipi-csis.0
[ 2.286294] : s5pcsis_probe : csis0 probe success
[ 2.293716] s5p-mipi-csis.1
[ 2.293719] : s5pcsis_probe : csis1 probe success
[ 2.301588] S5K4ECGX 4-0056: s5k4ecgx_init_formats:
[ 2.305904] S5K4ECGX 4-0056: s5k4ecgx_init_parameters:
[ 2.311100] S5K4ECGX 4-0056: s5k4ecgx_stop_auto_focus: single AF Off command Setting
[ 2.365942] hub 1-3:1.0: USB hub found
[ 2.368283] hub 1-3:1.0: 3 ports detected
[ 2.465059] exynos-mdev.1: Registered sensor subdevice S5K4ECGX
[ 2.469520] [INFO]flite_probe:2485: FIMC-LITE0 probe success
[ 2.475456] [INFO]flite_probe:2485: FIMC-LITE1 probe success
[ 2.481042] [INFO]flite_probe:2485: FIMC-LITE2 probe success
[ 2.488508] hdmiphy init start
[ 2.490246] i2c i2c-2: attached exynos hdcp into i2c adapter successfully
[ 2.496958] i2c-core: driver [exynos_hdcp] using legacy suspend method
[ 2.503354] i2c-core: driver [exynos_hdcp] using legacy resume method
[ 2.509773] Samsung HDMI output driver, (c) 2010-2011 Samsung Electronics Co., Ltd.
[ 2.517577] s5p-hdmi exynos5-hdmi: hdmiphy i2c bus number = 8
[ 2.523407] hdmiphy_probe start
[ 2.526238] s5p-hdmiphy 8-0038: probe successful
[ 2.640185] s5p_hpd_kobject_uevent: sent uevent HDMI_STATE=offline
[ 2.644976] s5p-hdmi exynos5-hdmi: probe sucessful
[ 2.649804] Samsung TV Mixer driver, (c) 2010-2011 Samsung Electronics Co., Ltd.
[ 2.657294] s5p-mixer s5p-mixer: probe start
[ 2.661375] s5p-mixer s5p-mixer: resources acquired
[ 2.666162] s5p-mixer s5p-mixer: added output 'S5P HDMI connector' from module 's5p-hdmi'
[ 2.674302] usb 1-3.2: new high speed USB device number 3 using s5p-ehci
[ 2.681155] s5p-mixer s5p-mixer: registered layer mxr0_graph0 as /dev/video16
[ 2.688259] s5p-mixer s5p-mixer: registered layer mxr0_graph1 as /dev/video17
[ 2.695329] s5p-mixer s5p-mixer: registered layer mxr1_graph2 as /dev/video18
[ 2.702438] s5p-mixer s5p-mixer: registered layer mxr1_graph3 as /dev/video19
[ 2.709375] s5p-mixer s5p-mixer: mixer0 create links
[ 2.714319] s5p-mixer s5p-mixer: mixer1 create links
[ 2.719273] s5p-mixer s5p-mixer: mixer links are created successfully
[ 2.725714] s5p-mixer s5p-mixer: probe successful
[ 2.730452] S5P CEC for Exynos4 Driver, (c) 2009 Samsung Electronics
[ 2.736923] s5p-tvout-cec s5p-tvout-cec: probe successful
[ 2.742213] exynos-rot exynos-rot: ++rot_probe
[ 2.746655] exynos-rot exynos-rot: rotator registered successfully
[ 2.752743] Initialize JPEG driver
[ 2.756217] s5p-jpeg s5p-jpeg: JPEG driver is registered to /dev/video12
[ 2.762823] s5p-jpeg s5p-jpeg: JPEG driver is registered to /dev/video11
[ 2.769756] Samsung Graphics 2D driver, (c) 2011 Samsung Electronics
[ 2.775814] samsung-fake-battery samsung-fake-battery: samsung_fake_bat_probe
[ 2.783793] S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics
[ 2.788889] s3c2410-wdt s3c2410-wdt: watchdog inactive, reset disabled, irq enabled
[ 2.796914] device-mapper: uevent: version 1.0.3
[ 2.801289] device-mapper: ioctl: 4.20.0-ioctl (2011-02-02) initialised: [email protected]
[ 2.809353] Bluetooth: HCI UART driver ver 2.2
[ 2.813756] Bluetooth: HCI H4 protocol initialized
[ 2.818516] Bluetooth: HCI BCSP protocol initialized
[ 2.823603] Bluetooth: HCILL protocol initialized
[ 2.828155] Bluetooth: HCIATH3K protocol initialized
[ 2.833298] hub 1-3.2:1.0: USB hub found
[ 2.837295] hub 1-3.2:1.0: 4 ports detected
[ 2.841175] cpuidle: using governor ladder
[ 2.845821] cpuidle: using governor menu
[ 2.849271] dw_mmc dw_mmc.0: Using internal DMA controller.
[ 2.854679] mmc0: no vmmc regulator found
[ 2.858882] dw_mmc dw_mmc.0: Version ID is 241a
[ 2.863130] dw_mmc dw_mmc.0: DW MMC controller at irq 139, 32 bit host data width, 128 deep fifo
[ 2.871956] dw_mmc dw_mmc.2: Using internal DMA controller.
[ 2.877444] mmc1: no vmmc regulator found
[ 2.881607] dw_mmc dw_mmc.2: Version ID is 241a
[ 2.885935] mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[ 2.890048] dw_mmc dw_mmc.2: DW MMC controller at irq 141, 32 bit host data width, 128 deep fifo
[ 2.890139] dw_mmc dw_mmc.1: Using internal DMA controller.
[ 2.890175] mmc2: no vmmc regulator found
[ 2.890674] dw_mmc dw_mmc.1: Version ID is 241a
[ 2.890699] dw_mmc dw_mmc.1: DW MMC controller at irq 140, 32 bit host data width, 128 deep fifo
[ 2.891141] sdhci: Secure Digital Host Controller Interface driver
[ 2.891148] sdhci: Copyright(c) Pierre Ossman
[ 2.891598] mshci: Mobile Storage Host Controller Interface driver
[ 2.891606] mshci: Copyright (c) 2011 Samsung Electronics Co., Ltd
[ 2.891617] Error: Driver 'dw_mmc' is already registered, aborting...
[ 2.892259] S5P ACE Driver, (c) 2010 Samsung Electronics
[ 2.961557] ACE: ecb-aes-s5p-ace
[ 2.964695] ACE: cbc-aes-s5p-ace
[ 2.967946] ACE: ctr-aes-s5p-ace
[ 2.971175] ACE: sha1-s5p-ace
[ 2.974071] ACE: sha256-s5p-ace
[ 2.977145] ACE driver is initialized
[ 2.981281] usbcore: registered new interface driver usbhid
[ 2.986280] usbhid: USB HID core driver
[ 2.990492] logger: created 256K log 'log_main'
[ 2.994724] logger: created 256K log 'log_events'
[ 2.999428] logger: created 256K log 'log_radio'
[ 3.004034] logger: created 256K log 'log_system'
[ 3.010131] Samsung Audio Subsystem Driver, (c) 2011 Samsung Electronics
exynos5250
I am having problems getting my Arndale board to launch. I have installed 3 different versions of ubuntu to try and make the proper build environment. either the board stalls while launching, or i get a boot loop with a re-occurring code that i am not sure what it is. My log is posted above with the re-occurring code. If anyone can tell me what i am doing wrong i would really appreciate it. I had to ask one of the moderators to put my log in for me. As a new member i am not allowed to post links yet and it seems to think there are links in my log. The way in which i had to get the log to him was through pm and in 3 parts, so the log is a little jumbled up. I will straighten it out as soon as i can.
I have already went about retrying my build environment so i will not be able to exactly reproduce this error but i have come to a similar wall roughly 3 times now. If details are needed as to how i am setting up my build environment i can certainly provide them.
Also if I am not mistaken the Arndale exynos5250 shares alot of it's hardware with the nexus 10 including the ASOP? so if this is a possible route to go i would love to know. Basically all i am looking to do is set up my board with the crypto twofish patch, and three modules for CDC-ACM, PL2303, and one for the EasyCAP.
I am having a problem figuring out how to set my mac address for the built in Ethernet as well, potentially a patch for a Ethernet radio button as well.
Thank you.
A little more detail
So I had originally purchased this board around a year and a half ago. I had problems getting the paid apps to work and the gps module was faulty. It took me around a month to properly get a u-boot built to flash the board and by that time my return on the gps module had lapsed. I continued to try and properly set up a build environment to compile the kernel and system, but with little success. I had lost all hope of this board ever becoming anything useful, and had successfully wasted around 500$.
Fast forward a year and a half and i stumble across an article detailing how to implement a usb GPS. The GPS unit was only around 20$ shipped so i figured why not give it a try. It was successful, a little slow on the refresh rate but successful never the less. This is around the time i was determined to make my 500$ paperweight into something of value. I had decided to start looking into making it a car-droid-pc. I had also came across a post on the arndale forum stating that the paid apps could be fixed via a crypto twofish patch (I have still yet to see whether or not i am applying it correctly)
Some of the elements i wish to apply to my project consist of a thermally controlled relay, resistive control to keyboard module (steering wheel control), OBD2 to usb (pl2303 chip), reverse camera via EasyCAP tuner, some way to implement bluetooth calling, and perhaps A2DP or wireless network for music streaming (A2DP could go hand in hand with bluetooth calling)
If anyone is interested in more details of the project i am happy to go into further detail.
on a side note
I was trying to read through my log to see if any of it made sense to me and i cam across something interesting.
Linux version 3.0.31-g3370a7c ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP PREEMPT Fri Feb 21 21:47:51 MST 2014
however when i run arm-none-linux-gnueabi-gcc -print-search-dirs | grep libraries | sed 's/:/\n/g' i get back
libraries
=/usr/local/arm-2009q3/bin/../lib/gcc/arm-none-linux-gnueabi/4.4.1/
/usr/local/arm-2009q3/bin/../lib/gcc/
/usr/local/arm-2009q3/bin/../lib/gcc/arm-none-linux-gnueabi/4.4.1/../../../../arm-none-linux-gnueabi/lib/arm-none-linux-gnueabi/4.4.1/
/usr/local/arm-2009q3/bin/../lib/gcc/arm-none-linux-gnueabi/4.4.1/../../../../arm-none-linux-gnueabi/lib/
/usr/local/arm-2009q3/bin/../arm-none-linux-gnueabi/libc/lib/arm-none-linux-gnueabi/4.4.1/
/usr/local/arm-2009q3/bin/../arm-none-linux-gnueabi/libc/lib/
/usr/local/arm-2009q3/bin/../arm-none-linux-gnueabi/libc/usr/lib/arm-none-linux-gnueabi/4.4.1/
/usr/local/arm-2009q3/bin/../arm-none-linux-gnueabi/libc/usr/lib/
all listed as 4.4.1 which is what the wiki instructs to do, so why is it that i am getting a gcc version of 4.6.x ??? rather than 4.4.1
I know it's a dead platform pretty much but here goes... I have a mangled GT-N8010. It's been fine for years, I even rooted it and installed nerdyblonde's blissrom image middle of last year. All of a sudden out of nowhere I get bootloop.
It's got TWRP on it and I notice that most of the partitions mount ro even though I have selected for them to be rw. Then I realise that they mount rw to start with then transition to ro due to filesystem errors. From dmesg:
Code:
<6>[ 806.261839] c0 binder: 1803:1803 transaction failed 29189, size 0-0
<6>[ 806.455283] c0 Atmel MXT1664S 3-004a: P: id[0]
<6>[ 806.519815] c0 Atmel MXT1664S 3-004a: R: id[0] M[0]
<3>[ 806.527889] c2 mmc0: mshci_check_sbc_status cmd response crc error
<3>[ 806.527925] c2 mmc0: it occurs a critical error on eMMC it'll try to recover eMMC to normal state
<6>[ 806.712682] c2 mmc0: recovering eMMC has been done
<3>[ 806.712698] c2 brq->sbc.opcode=23,brq->cmd.opcode=18.
<3>[ 806.712706] c2 brq->sbc.error=-110,brq->cmd.error=0, brq->stop.error=0,brq->data.error=0.
<3>[ 806.712747] c2 mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x900
<3>[ 806.712755] c2 mmcblk0: not retrying timeout
<3>[ 806.712813] c2 end_request: I/O error, dev mmcblk0, sector 6008856
<3>[ 806.712908] c2 CMD aborting case in MMC's block layer ret 0.
<3>[ 806.712916] c2 mmcblk0: CMD18, ARG=0x5bb018.
<3>[ 806.712921] c2 packed CMD type = 0.
<3>[ 806.712926] c2 mmc0, request returns 4.
<2>[ 806.713152] c1 EXT4-fs error (device mmcblk0p12): ext4_find_entry:934: inode #2: comm ls: reading directory lblock 0
<3>[ 806.713166] c1 Aborting journal on device mmcblk0p12-8.
<2>[ 806.713176] c1 EXT4-fs (mmcblk0p12): Remounting filesystem read-only
<6>[ 807.261975] c0 binder: 1803:1803 transaction failed 29189, size 0-0
<6>[ 808.262113] c0 binder: 1803:1803 transaction failed 29189, size 0-0
<6>[ 809.262253] c0 binder: 1803:1803 transaction failed 29189, size 0-0
<6>[ 810.262394] c0 binder: 1803:1803 transaction failed 29189, size 0-0
So my internal eMMC is broken. The broken sectors are all over the place too so I don't think I can partition around them with a custom PIT:
Code:
end_request: I/O error, dev mmcblk0, sector 180224
end_request: I/O error, dev mmcblk0, sector 209968
end_request: I/O error, dev mmcblk0, sector 1818496
end_request: I/O error, dev mmcblk0, sector 4685696
end_request: I/O error, dev mmcblk0, sector 5709696
end_request: I/O error, dev mmcblk0, sector 5726210
end_request: I/O error, dev mmcblk0, sector 6008856
end_request: I/O error, dev mmcblk0, sector 30769024
I think I have the latest 4.4.2 Samsung bootloader so what I can do from the bootloader is limited (basically just boot into odin/download mode or into TWRP - no fastboot. Obviously due to failed eMMC I get loads of NAND failures trying to do things with odin.
I would like to make use of the tablet for another 6 months or so, so has anyone ever had any success booting one of these from SD card?
Damn, sorry this should have gone in the Q&A forum. Could someone move it please? Sorry!
Use the report button .