"Wi-Fi unable to start" error appeared couple weeks ago.
I have tried everything - reflashing different images, radio, formatting ... etc.
Nothing helped.
In a desperate moment I tried something.
Here are the steps:
I made some progress and it seams that is pure software problem.
Currently I'm with G1/black Cyanogen 3.6.8.1, Recovery 1.4 and 8GB SD/class 4.
What I did is reformatting the SD card in 2 partitions 1st FAT32 and 2nd ext2 ~ 460MB.
Wiped before flashing cyanogen build and also I made sure that there is nothing on the ext2 partition.
When flashing finished I waited the phone to fully set up itself on the first boot ~5-7 min.
Then I tried the WiFi - it didn't start
The important and desperate thing I did was to go to su console in /system/lib/modules and tried to load wlan.ko manually (insmod wlan.ko) - it failed the 1st time.
Then I tried 2 times more and it loaded itself successfully (of course wifi connection is not established in that moment, because loading the module is just one step of the process).
I unloaded successfully (rmmod wlan) the module and tried to start WiFi again - gues what - It worked!
That is just partial solution of the problem, but shows that it is just a software problem.
I guess some timeouts appear and WiFi starting procedure is not so patient to wait for the module to start up and it's not retrying to unload and load again the module.
Good luck
Hope it will work on yours G1.
Cheers
this has been up on a google code bug report page for a while now. I had the same result when trying to start the module in the terminal
cyanogen's new 3.9.1 scary experimental build shows that he used a new wifi driver in the changelog but that hasn't helped me with this issue at all. I thought it might be a software conflict so I used a clean sd card, flashed my update.zip, and still had the same problem
I have tried Cyanogen 3.9.1 with the same result - it doesn't work for me.
I can't explain why it started to work again in 3.6.8.1
Anyway, try to copy all your important files (not system/applications created like thumbnails folder) to your PC, put the SD card to card reader connected to a PC and then do a full reformat to FAT32.
Partition the newly formatted SD card to FAT32 and EXT2 partitions.
Reformat partitions again, copy update.zip to your SD card.
Start up your G1 holding home button and do wipe ( I wiped 2-3 times just to be sure )
Do ext2 system repair from the repair menu.
Do not convert it to ext3.
Apply the update.zip and continue to the next steps I wrote above.
Hope that's info is useful for you.
Post the output of "dmesg" after you try to install the module. It will tell us whats going wrong. This is not normal at all and might be hardware related.
cssvb94 said:
but shows that it is just a software problem.
Click to expand...
Click to collapse
I don't see how you come to the conclusion that it is a software problem. Intermittence is typically a sign of a HARDWARE problem.
lbcoder said:
I don't see how you come to the conclusion that it is a software problem. Intermittence is typically a sign of a HARDWARE problem.
Click to expand...
Click to collapse
Simple, it works somethimes on some builds and it doesn't at all on others - same hardware, different software.
Anyway, I realy hope it's not hardware related ...
cyanogen said:
Post the output of "dmesg" after you try to install the module. It will tell us whats going wrong. This is not normal at all and might be hardware related.
Click to expand...
Click to collapse
Is that request for me or airmaxx?
I really don't want to reflash now when it's working.
In the moment when something goes wrong I'll post dmesg.
I've noticed "D/wlan_loader( 228): ConfigMge start rc = -1" couple times in dmesg output when it wasn't working and "D/wlan_loader( 228): ConfigMge start rc = 0" when it works.
after a clean install of cyanogen 3.9.1, i tried to start with in the gui, through settings menu. after it reported "unable to start wifi" this is my dmesg output....
Code:
<6>[ 695.675048] TIWLAN: Driver loading
<4>[ 695.679168] wifi_probe
<4>[ 695.681762] trout_wifi_power: 1
<4>[ 695.888366] trout_wifi_reset: 0
<4>[ 695.943084] trout_wifi_set_carddetect: 1
<7>[ 695.947265] mmc0: card_present 1
<6>[ 695.950744] mmc0: Slot status change detected (0 -> 1)
<3>[ 698.464202] mmc0: Command timeout
<4>[ 698.474548] mmc0: card claims to support voltages below the defined range. These will be ignored.
<4>[ 698.484191] mmc0: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.
<6>[ 698.497955] mmc0: new SDIO card at address 0001
<6>[ 698.508758] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 698.517639] tiwlan0 (): not using net_device_ops yet
<6>[ 698.530426] TIWLAN: Driver initialized (rc 0)
<3>[ 698.535705] mmc0: Data CRC error
<3>[ 698.539276] msmsdcc_data_err: opcode 0x00000035
<3>[ 698.544128] msmsdcc_data_err: blksz 4, blocks 1
<3>[ 698.549621] SDIO_SyncWrite: failed (-84)
<3>[ 698.554016] mmc0: Data CRC error
<3>[ 698.557586] msmsdcc_data_err: opcode 0x00000035
<3>[ 698.562713] msmsdcc_data_err: blksz 4, blocks 1
<3>[ 698.567718] SDIO_SyncWrite: failed (-84)
<3>[ 701.399383] mmc0: Data timeout
<3>[ 701.403289] SDIO_SyncRead: failed (-110)
<4>[ 701.407623] TIWLAN: invalid chip id = 0x 0 0 0 0!
<6>[ 701.412933] TIWLAN: Driver loaded
<4>[ 701.820495] select 226 (app_process), adj 15, size 3301, to kill
<4>[ 701.826873] send sigkill to 226 (app_process), adj 15, size 3301
<3>[ 704.165802] mmc0: Data timeout
<3>[ 704.169311] SDIO_SyncRead: failed (-110)
<3>[ 704.174041] TIWLAN: TIWLAN: Failed to start config manager
<6>[ 710.698730] RPC_TIME_TOD_SET_APPS_BASES:
<6>[ 710.698760] tick = 38620607
<6>[ 710.698760] stamp = 48907518449025024
<4>[ 735.120178] select 480 (app_process), adj 15, size 4338, to kill
<4>[ 735.126464] send sigkill to 480 (app_process), adj 15, size 4338
something i remembered earlier was that long ago, many roms and flashes prior (when I was still chasing after Hero and Rosie) i saw a wpa supplicant file had been installed on my fat32 partition, no system folder or anything just on the root of the card. i remember thinking at the time how odd this was and manually deleting the file prior to my next flash.
My problem may have started shortly thereafter but honestly don't remember, just grasping for straws here
cssvb94 said:
Simple, it works somethimes on some builds and it doesn't at all on others - same hardware, different software.
Anyway, I realy hope it's not hardware related ...
Click to expand...
Click to collapse
Really? That's not what you said before...
cssvb94 said:
I have tried everything - reflashing different images, radio, formatting ... etc.
Nothing helped.
Click to expand...
Click to collapse
Clearly, it is NOT related to the software since you TRIED CHANGING the software and it didn't help, and the SAME SOFTWARE works fine for everybody else, which means that it MUST be either USER ERROR, or HARDWARE DEFECT.
lbcoder said:
Really? That's not what you said before...
Clearly, it is NOT related to the software since you TRIED CHANGING the software and it didn't help, and the SAME SOFTWARE works fine for everybody else, which means that it MUST be either USER ERROR, or HARDWARE DEFECT.
Click to expand...
Click to collapse
Listen, I'm not here to argue and I don't have anything against you.
Why you are so catchy about that simple details?
I'm trying to help and share what I've been through.
If you are offended of something I said then - sorry.
Don't be such arrogant, capital letters don't work on me. =)
----------------------------------------------------------------------
This is cut from my dmesg :
WiFi starting OK
--- cut ---
<6>[ 268.613555] TIWLAN: Driver loading
<4>[ 268.617797] wifi_probe
<4>[ 268.620758] trout_wifi_power: 1
<4>[ 268.830261] trout_wifi_reset: 0
<4>[ 268.884521] trout_wifi_set_carddetect: 1
<7>[ 268.888824] mmc0: card_present 1
<6>[ 268.892303] mmc0: Slot status change detected (0 -> 1)
<3>[ 271.400268] mmc0: Command timeout
<4>[ 271.410339] mmc0: card claims to support voltages below the defined range. These will be ignored.
<4>[ 271.419982] mmc0: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.
<6>[ 271.436584] mmc0: new SDIO card at address 0001
<6>[ 271.446960] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 271.455352] tiwlan0 (): not using net_device_ops yet
<6>[ 271.464538] TIWLAN: Driver initialized (rc 0)
<4>[ 271.469909] TIWLAN: 1251 PG 1.2
<6>[ 271.473693] TIWLAN: Driver loaded
<3>[ 271.863403] mmc0: Data CRC error
<3>[ 271.866851] msmsdcc_data_err: opcode 0x00000035
<3>[ 271.871551] msmsdcc_data_err: blksz 512, blocks 1
<4>[ 271.877441] SDIO Write failure (-84)
<3>[ 271.883209] TIWLAN: TIWLAN: Failed to start config manager
--- cut ---
<6>[ 689.787445] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 689.795745] tiwlan0 (): not using net_device_ops yet
<6>[ 689.804901] TIWLAN: Driver initialized (rc 0)
<4>[ 689.810150] TIWLAN: 1251 PG 1.2
<6>[ 689.813690] TIWLAN: Driver loaded
<3>[ 690.153045] mmc0: Data CRC error
<3>[ 690.156463] msmsdcc_data_err: opcode 0x00000035
<3>[ 690.161163] msmsdcc_data_err: blksz 4, blocks 1
<4>[ 690.168182] SDIO Write failure (-84)
<3>[ 690.173889] TIWLAN: TIWLAN: Failed to start config manager
--- cut ---
Now new case: "Unable to stop Wi-Fi"
rmmod wlan throws back: "rmmod: delete_module 'wlan' failed (errno 11)"
lsmod returns: "wlan 566844 1 - Live 0xbf480000"
lbcoder, was there anything in my dmesg that confirmed it is indeed hardware, or anything useful at all in there?
after reading the reports on googlecode pages, i was leaning to hardware issue only because the problem is so rare and those people sent their g1's back in. I was really hoping this wasn't the case though.
I'd be happy with intermittent at this point, my wifi has not turned on in like 2 months my phone was purchased used (wifi worked fine at the time though) on craigslist so I can't return it to TMO
The CRC errors on mmc0 means that your sdcard is dying. It might seem unrelated but because how the way the G1 hardware works, this could be the problem. Yank your card and try it again.
No more WiFi
"Unable to stop" or "Unable to start" after reboot.
Tried with different SD card - no CRC errors and still no WiFi
for me the wifi turned on but it cant connect with a router... just write obtain ip address.. and after.. no connection
this is my log
<6>[ 175.583831] ept #2 out max:512 head:ffc0c100 bit:2
<6>[ 175.584289] ept #0 in max:64 head:ffc0c040 bit:16
<6>[ 175.585083] ept #1 in max:512 head:ffc0c0c0 bit:17
<6>[ 175.585510] ept #2 in max:512 head:ffc0c140 bit:18
<6>[ 175.586059] usb: notify offline
<6>[ 175.594207] usb: suspend
<6>[ 175.813262] usb: reset
<6>[ 175.815673] usb: portchange USB_SPEED_HIGH
<6>[ 175.967803] usb: reset
<6>[ 175.970092] usb: portchange USB_SPEED_HIGH
<6>[ 176.164825] usb_mass_storage usb_mass_storage: config #1
<6>[ 187.209259] request_suspend_state: wakeup (3->0) at 180968491210 (2009-07-
29 16:16:01.570098877 UTC)
<6>[ 188.333618] TIWLAN: Driver loading
<4>[ 188.334503] wifi_probe
<4>[ 188.334777] trout_wifi_power: 1
<4>[ 188.536346] trout_wifi_reset: 0
<4>[ 188.586914] trout_wifi_set_carddetect: 1
<7>[ 188.587432] mmc0: card_present 1
<6>[ 188.587738] mmc0: Slot status change detected (0 -> 1)
<3>[ 191.095031] mmc0: Command timeout
<4>[ 191.102386] mmc0: card claims to support voltages below the defined range.
These will be ignored.
<4>[ 191.103210] mmc0: SDIO card claims to support the incompletely defined 'lo
w voltage range'. This will be ignored.
<6>[ 191.112518] mmc0: new SDIO card at address 0001
<6>[ 191.118377] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 191.123901] TIWLAN: Driver initialized (rc 0)
<4>[ 191.125244] TIWLAN: 1251 PG 1.2
<6>[ 191.125701] TIWLAN: Driver loaded
<6>[ 192.657897] snd_set_volume 256 0 5
<6>[ 192.747344] snd_set_volume 256 0 5
<3>[ 198.871185] init: sys_prop: permission denied uid:1000 name:ro.config.noc
heckin
<6>[ 244.551879] TIWLAN: Driver unloading
<4>[ 244.553070] sdio_reset_comm():
<7>[ 244.631011] TIWLAN: Releasing SDIO resources
<7>[ 244.632324] TIWLAN: SDIO resources released
<4>[ 244.634918] wifi_remove
<4>[ 244.635406] trout_wifi_set_carddetect: 0
<7>[ 244.636199] mmc0: card_present 0
<6>[ 244.636627] mmc0: Slot status change detected (1 -> 0)
<6>[ 244.639465] mmc0: card 0002 removed
<4>[ 244.643585] trout_wifi_reset: 1
<4>[ 244.699401] trout_wifi_power: 0
<6>[ 244.905883] TIWLAN: Driver unloaded
<6>[ 246.548492] TIWLAN: Driver loading
<4>[ 246.549377] wifi_probe
<4>[ 246.549652] trout_wifi_power: 1
<4>[ 246.754119] trout_wifi_reset: 0
<4>[ 246.805236] trout_wifi_set_carddetect: 1
<7>[ 246.805786] mmc0: card_present 1
<6>[ 246.806060] mmc0: Slot status change detected (0 -> 1)
<3>[ 249.310638] mmc0: Command timeout
<4>[ 249.318481] mmc0: card claims to support voltages below the defined range.
These will be ignored.
<4>[ 249.319335] mmc0: SDIO card claims to support the incompletely defined 'lo
w voltage range'. This will be ignored.
<6>[ 249.326782] mmc0: new SDIO card at address 0001
<6>[ 249.332794] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 249.338226] TIWLAN: Driver initialized (rc 0)
<4>[ 249.339141] TIWLAN: 1251 PG 1.2
<6>[ 249.339599] TIWLAN: Driver loaded
<6>[ 994.061614] request_suspend_state: sleep (0->3) at 987820816650 (2009-07-2
9 16:29:28.422424317 UTC)
<4>[ 994.083801] deinit sharp panel
<4>[ 994.762908] save exit: isCheckpointed 1
<4>[ 994.765380] save exit: isCheckpointed 1
If you want help, get your details straight! If you contradict yourself all over the place, then nobody can possibly know what is going on and you won't get anywhere.
cssvb94 said:
Listen, I'm not here to argue and I don't have anything against you.
Why you are so catchy about that simple details?
Click to expand...
Click to collapse
You mention having tried flashing different software...
Have you tried flashing IMAGES (fastboot) or just update scripts (i.e. update.zip)?
If you haven't tried already, I suggest flashing the stock *engineering* bootloader 0.95.3000, ADP1-CRC1 images from www.htc.com -- the one that's labeled as "system image" (not the one labeled "recovery image", which is just an update.zip), and radio v2_22_19_26I (also from htc.com), write everything to the phone using fastboot, pull the battery, wait 10 minutes, and see what happens. IF it is a software problem, then this will *definitely* fix it. If it is a HARDWARE problem, then this will *definitely NOT* fix it. If the wifi starts working right after you write these things, *do not* conclude that it was a software problem since it could simply have gone intermittent-on. Keep the software like that and run it for at least a week to make sure the problem doesn't come back before making your conclusions.
Went back to stock 1.0 RC29 with original SPL, radio and bootloader and started from scratch.
Also formated SD card - only one partition FAT32.
Now I'm with ADP1.5 JF and WiFi is working most of the time.
So angry lbcoder what's your great verdict now? SOFTWARE or HARDWARE?
lbcoder said:
You mention having tried flashing different software...
Have you tried flashing IMAGES (fastboot) or just update scripts (i.e. update.zip)?
If you haven't tried already, I suggest flashing the stock *engineering* bootloader 0.95.3000, ADP1-CRC1 images from www.htc.com -- the one that's labeled as "system image" (not the one labeled "recovery image", which is just an update.zip), and radio v2_22_19_26I (also from htc.com), write everything to the phone using fastboot, pull the battery, wait 10 minutes, and see what happens. IF it is a software problem, then this will *definitely* fix it. If it is a HARDWARE problem, then this will *definitely NOT* fix it. If the wifi starts working right after you write these things, *do not* conclude that it was a software problem since it could simply have gone intermittent-on. Keep the software like that and run it for at least a week to make sure the problem doesn't come back before making your conclusions.
Click to expand...
Click to collapse
which is the commands for push the radio and the the adp1-crc1 image via fastboot?
i can t find ADP1-CRC1 images can you give me a url please?
success!!!!!!
the problem was the radio... i flashed 2 times the radio and now work!!!!!
thanks guyssss i love you aahahah
rock187 said:
the problem was the radio... i flashed 2 times the radio and now work!!!!!
thanks guyssss i love you aahahah
Click to expand...
Click to collapse
Great =)
Would you please post full step-by-step what you did.
10x in advance
It didn't work for me. I'm going to return my G1 back to the store I bought it, it's still under warranty.
Hi folks,
I'm hoping someone can help me get my head around loading drivers in android.
I'm very familiar with Linux, so I understand drivers compiled into the kernel vs loading modular drivers. I also understand module versions in that they should match the installed kernel.
I have a cyanogenmod ROM that was built for a device similar to mine except that the wifi/bt drivers do not work. I have a ROM where these DO work.
I have extracted the boot.img from each ROM and I'm trying to combine the kernel that works with the cyanogenmod boot.img to get a working device. But the drivers have me a bit stumped.
On the device that works, here is what I see during boot in dmesg:
Code:
<6>[ 2.273829] Bluetooth: HCI UART driver ver 2.2
<6>[ 2.278272] Bluetooth: HCI H4 protocol initialized
<6>[ 2.283084] Bluetooth: HCI BCSP protocol initialized
<6>[ 2.288045] Bluetooth: HCILL protocol initialized
<7>[ 2.292983] [wifi]: Select sdio wifi: bcm40183 !!
<7>[ 2.297878] [mmc_pm]: SDIO card gpio init is OK !!
<7>[ 2.302753] [mmc]: sunximmc_init
<7>[ 2.306208] [mmc]: sunxi mmc controller using config : 0xb
<7>[ 2.311762] [mmc]: sunxi-mmc.0: pdev->name: sunxi-mmc, pdev->id: 0
<7>[ 2.318190] [mmc]: mmc 0 power off !!
<7>[ 2.321978] [mmc]: mmc0 Probe: base:0xe8916000 irq:32 dma:0 pdes:0xe704c000, ret 0.
<7>[ 2.329650] [mmc]: sunxi-mmc.1: pdev->name: sunxi-mmc, pdev->id: 1
<7>[ 2.336069] [mmc]: mmc 1 power off !!
<7>[ 2.339801] [mmc]: mmc1 Probe: base:0xe8918000 irq:33 dma:0 pdes:0xe7050000, ret 0.
<7>[ 2.347496] [mmc]: sunxi-mmc.3: pdev->name: sunxi-mmc, pdev->id: 3
<7>[ 2.353876] [mmc]: mmc 3 power off !!
<7>[ 2.357601] [mmc]: mmc3 Probe: base:0xe891a000 irq:35 dma:0 pdes:0xe7054000, ret 0.
This is below the line that says
Code:
<7>[ 2.081010] insmod_device_driver
So I'm assuming this is a module that is being loaded. I have however compared the init.sun4i.rc on both and made sure I'm loading the same drivers. I'm also loading the kernel from the working ROM.
This is what I see in the broken setup:
Code:
<6>[ 2.261673] Bluetooth: HCI UART driver ver 2.2
<6>[ 2.266116] Bluetooth: HCI H4 protocol initialized
<6>[ 2.270928] Bluetooth: HCI BCSP protocol initialized
<6>[ 2.275891] Bluetooth: HCILL protocol initialized
<7>[ 2.280811] [mmc_pm]: no sdio card used in configuration
<7>[ 2.286118] [mmc]: sunximmc_init
<7>[ 2.289602] [mmc]: sunxi mmc controller using config : 0xb
<7>[ 2.295210] [mmc]: sunxi-mmc.0: pdev->name: sunxi-mmc, pdev->id: 0
<7>[ 2.301688] [mmc]: mmc 0 power off !!
<7>[ 2.305451] [mmc]: mmc0 Probe: base:0xe8916000 irq:32 dma:0 pdes:0xe704c000, ret 0.
<7>[ 2.313150] [mmc]: sunxi-mmc.1: pdev->name: sunxi-mmc, pdev->id: 1
<7>[ 2.319533] [mmc]: mmc 1 power off !!
<7>[ 2.323293] [mmc]: mmc1 Probe: base:0xe8918000 irq:33 dma:0 pdes:0xe7050000, ret 0.
<7>[ 2.330984] [mmc]: sunxi-mmc.3: pdev->name: sunxi-mmc, pdev->id: 3
<7>[ 2.337351] [mmc]: mmc 3 power off !!
<7>[ 2.341106] [mmc]: mmc3 Probe: base:0xe891a000 irq:35 dma:0 pdes:0xe7054000, ret 0.
So this seems to be complaining about no SD card being available - is this a correct assumption?
I also assume this is a card used for storage, and wifi/bt using the SDIO standard.
Would the wifi driver be being loaded from the SD card? If so, where? It may just be something else I need to add to the zip file for the new ROM.
When I compare dmesg between the two, I don't see anything obvious that loads differently, so it's got me stumped as to what's happening.
Can anyone shed some light on how the working ROM might be loading the bcm40183 driver?
in my android tablet I noticed how the /system folder is actually stored in nandd partition, and refered to by the main nand partition via a symlink. Since /system/vendor/modules (where my bcm40183 module is stored) is a symlink path to a location on a nand partition, I assume the OS reaches that location using a mmc device (maybe because it is flash memory after all). So your problem isn't about a missing SD card, but about a missing nand partition...or a broken link. Apparently, from one android version to the next, the number of partitions varies. On mine, there are 9 partitions!
Since you know about modules and versions, do you know how I could get that bcm40183 module working in linux? I can't find a kernel with that module on offer and I dont know how to add modules on already compiled kernels. I'd love to be able to insmod this bcm40183 version 3.0.8 in my sunxi-3.4 kernel...
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?
Folks,
Just got my Moto G Gen3. Everything appears to be working perfectly fine, but I get the below backtrace in dmesg if I reboot the phone with the USB cable plugged in. This is on stock, unrooted, Lollipop 5.1. Could you guys possibly check if you get the same message in your kernel ring buffers when you reboot with the cable in? It's probably a software issue so nothing to worry about, but since this is on the stock ROM - which I expect to be QA'd for bugs - the backtrace does have me a bit worried that I might have received a defective unit.
Code:
<3>[ 0.742295,0] i2c-msm-v2 78b5000.i2c: msm_bus_scale_register_client(mstr-id:86):0xb (ok)
<3>[ 0.743063,0] power_supply max170xx_battery: driver failed to report `present' property: -11
<4>[ 0.743170,0] thermal thermal_zone0: failed to read out thermal zone 0
<3>[ 0.743357,0] power_supply max170xx_battery: driver failed to report `present' property: -11
<4>[ 0.744315,0] Battery Temp State = 1
<3>[ 0.744347,0] power_supply max170xx_battery: driver failed to report `present' property: -11
<3>[ 0.748545,0] BMS: bms_get_adc: vadc not found - defer probe rc=-517
<3>[ 0.748551,0] BMS: qpnp_vm_bms_probe: Failed to get adc rc=-517
<6>[ 0.748565,0] spmi qpnp-vm-bms-ebfb6a00: Driver qcom,qpnp-vm-bms requests probe deferral
<3>[ 0.748706,0] CHG: qpnp_lbc_probe: Failed to read DT properties rc=-517
<6>[ 0.748718,0] spmi qpnp-linear-charger-ebfb6800: Driver qcom,qpnp-linear-charger requests probe deferral
<6>[ 0.749148,0] CBL: qpnp_cbldet_probe: Probe usb=1
<3>[ 0.749707,0] unable to find DT imem DLOAD mode node
<3>[ 0.749980,0] unable to find DT imem EDLOAD mode node
<3>[ 0.752453,0] qpnp_adc_tm_channel_measure: chip not valid
<3>[ 0.752463,0] fan5404x-charger 1-006b: tm disable failed: -19
<6>[ 0.753984,0] fan54046_otg_vreg: no parameters
<3>[ 0.754294,0] fan5404x_charger_probe: vadc not ready, defer probe
<4>[ 0.855673,0] ------------[ cut here ]------------
<4>[ 0.855688,0] WARNING: at ../../../../../../kernel/drivers/regulator/core.c:4144 regulator_unregister+0xb4/0xb8()
<4>[ 0.855694,0] Modules linked in:
<4>[ 0.855727,0] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.10.49-g5fbdf50 #1
<4>[ 0.855747,0] [<c010be5c>] (unwind_backtrace+0x0/0xec) from [<c01099cc>] (show_stack+0x10/0x14)
<4>[ 0.855760,0] [<c01099cc>] (show_stack+0x10/0x14) from [<c011bf5c>] (warn_slowpath_common+0x54/0x6c)
<4>[ 0.855772,0] [<c011bf5c>] (warn_slowpath_common+0x54/0x6c) from [<c011c140>] (warn_slowpath_null+0x1c/0x24)
<4>[ 0.855783,0] [<c011c140>] (warn_slowpath_null+0x1c/0x24) from [<c0436848>] (regulator_unregister+0xb4/0xb8)
<4>[ 0.855795,0] [<c0436848>] (regulator_unregister+0xb4/0xb8) from [<c06d6474>] (fan5404x_charger_probe+0x814/0xb58)
<4>[ 0.855808,0] [<c06d6474>] (fan5404x_charger_probe+0x814/0xb58) from [<c05eebd0>] (i2c_device_probe+0xa4/0xec)
<4>[ 0.855821,0] [<c05eebd0>] (i2c_device_probe+0xa4/0xec) from [<c04bab00>] (driver_probe_device+0x104/0x23c)
<4>[ 0.855832,0] [<c04bab00>] (driver_probe_device+0x104/0x23c) from [<c04bad08>] (__driver_attach+0x8c/0x90)
<4>[ 0.855844,0] [<c04bad08>] (__driver_attach+0x8c/0x90) from [<c04b8ff0>] (bus_for_each_dev+0x60/0x94)
<4>[ 0.855855,0] [<c04b8ff0>] (bus_for_each_dev+0x60/0x94) from [<c04ba27c>] (bus_add_driver+0x1c4/0x250)
<4>[ 0.855866,0] [<c04ba27c>] (bus_add_driver+0x1c4/0x250) from [<c04bb2e4>] (driver_register+0x78/0x140)
<4>[ 0.855876,0] [<c04bb2e4>] (driver_register+0x78/0x140) from [<c05eea78>] (i2c_register_driver+0x30/0xb8)
<4>[ 0.855886,0] [<c05eea78>] (i2c_register_driver+0x30/0xb8) from [<c010064c>] (do_one_initcall+0x108/0x158)
<4>[ 0.855899,0] [<c010064c>] (do_one_initcall+0x108/0x158) from [<c1000c14>] (kernel_init_freeable+0x138/0x1d8)
<4>[ 0.855911,0] [<c1000c14>] (kernel_init_freeable+0x138/0x1d8) from [<c0a35e40>] (kernel_init+0x8/0x14c)
<4>[ 0.855922,0] [<c0a35e40>] (kernel_init+0x8/0x14c) from [<c0105c38>] (ret_from_fork+0x14/0x3c)
<4>[ 0.855959,0] ---[ end trace 86e3ab8c74ad6457 ]---
<6>[ 0.925770,0] i2c 1-006b: Driver fan5404x-charger requests probe deferral
Thanks a ton! :fingers-crossed: