Hi,
I have an issue with my Desire, it randomly reboots atleast once an hour
I have tried running a logcat, but heres the problem: When the phone has power connected it won't reboot.
So how to I catch the last entries in the log?
aLogcat wont work since it only save the log file every 15 minutes.
Anyone?
DISCLAIMER:
I am running CM7#36 and I know it has those issues, others have reported them. And I'm confident that it will be solved in a future release. But I would like to know anyway how or if I can get a logcat without power connected or what type of file that could be usefull.
I am one of the many who have been experiencing the random reboots. I have seen talk about it, but have not seen anyone really looking into why this is happening. Some people claim it happens only when docked, or when SD card is in etc. Yet others post that they still get the reboots without doing those things either.
I have been monitoring my reboot problem very closely. I have yet to determine the cause other than it only happens when the device is put into sleep mode manually or automatically, and I am looking for some help from some of the DEV's around here.
When our TF's do this reboot, it is a system crash. When this happens, a ROMDUMP file is placed on the internal "sd card".
These can be viewed with a simple txt editor, like windows notepad. I myself can not read the code and understand what info it is revealing to me. According to an Asus tech on the phone this file can tell you what went wrong and made the device reboot. However the buggers won't tell you crap over the phone and want me to send the device in with the ROMDUMP files.
When I try and read the files, I do see one thing in common, in 99% of them, right near the end of the file, or the very last line before the crash, this line is present,
Kernel panic - not syncing: Fatal exception in interrupt
<2>[ 162.985309] CPU1: stopping
If our reboot issue is kernal based, which would indicate it's a firmware issue;
I was thinking one of the talented DEV's around here could fix us up.
Hell maybe even just a reflash of the current firmware would fix the issue.
Anyway, if a DEV around here want to or willing to look into this, I have some ROM dumpfiles they can look at, just send me a PM.
For reference,
I have a B60K modle
Stock 3.1
GPS 1.3.1
Wifi 5.1.42
BluT 6.17
Kernal 2.6.36.3-00001-gf377a2b [email protected] #1
Build HMJ37.US_epad-8.4.4.5.2-20110603
Thanks.
I don't have any more dumps recently, deleted them so I can't pull up and see what mine said to give you, but wanted to just say I was having these multiple times a day every day and it started once I bought an AData 16GB SDCard for the dock. Then I ended up removing that card and bought a MicroSD 16GB card instead and it has quit doing the random reboots, so definitely seemed to be something with my SDCard in the dock.
Post your whole log here (as .txt or .zip) and I will look at it.
I've had these once or twice but have always deleted the file.
The Kernel Panic is the kernel's way of telling you that something unrecoverable has happened and the integrity of the whole OS is in question. Think of a kernel panic like a BSOD on Windows.
I've never seen that specific one before, but a quick Google search indicates it may be a problem with I/O operations - like bad RAM or a bad SD card.
sassafras
Thanks for the response. I have included 4 RAMDUMP files. I find these 4 special because they all happened in quick succession. Four separate reboots all within 8 mins of each other without any interaction of the device myself. I never touched the device, I just sat there and staring at the device rebooting 4 times in 8 mins. On the final reboot the device never came back on. AT this point I picked up the device and had to hold the power button down for over 10 seconds for the device to come back on to an Asus splash screen. This was mins after I did a fresh factory reset via the OS options internally then a hard reset using the hardware buttons.
...It's a bug alright...
It doesn't seem to be caused by the same problem though, just that the watchdog program invokes a kernel panic and reboots. Weird. I'll backtrace it later and see what's up.
sassafras
went a whole day without a reboot. I did have an odd lock up/freeze at the lock screen where i couldnt unlock the device or get it to rotate the screen. It was locked up tight. Held hte power button down for 20 secs before it shut down. Rebooted, no new RAMdump created. No issues since.
sassafras_, Did you have any luck reading those ramdumps?
I did - sort of.
They're all related to the watchdog program assuming it's soft locked up. Which it may very well have been, but since you weren't using the device at the time, it's hard to know for sure.
The function's that were called immediately prior to the fault were different, which to me indicates that it's just buggy software. Honestly, without doing a backtrace I wouldn't know, but I can't without a system.map from around the time of the lockup. I'm going to assume it's just buggy code from 3.1 and wait and see if the 3.2 release lowers the rate of these. If not, then maybe I'll do some more digging.
sassafras
sassafras_ said:
I did - sort of.
They're all related to the watchdog program assuming it's soft locked up. Which it may very well have been, but since you weren't using the device at the time, it's hard to know for sure.
The function's that were called immediately prior to the fault were different, which to me indicates that it's just buggy software. Honestly, without doing a backtrace I wouldn't know, but I can't without a system.map from around the time of the lockup. I'm going to assume it's just buggy code from 3.1 and wait and see if the 3.2 release lowers the rate of these. If not, then maybe I'll do some more digging.
sassafras
Click to expand...
Click to collapse
Is there any progress on this issue? I bougth a brand new tf and during day random reboots maybe 50 times. And that romdumps are appeared on my internal storage. I dont have external sd by the way. Im stuck.
Hi.
Im having a same problem with my Transformer. Its a week old B60 and its reboots probably 50 times a day and give me log files.
Also im using Honeycomb 3.2
I really want to find out what is going on
i guess its a hardware issue or something.
i'm going to give back my TF today and take back a new one.
if i get same errors, i'll let you know.
I posted a workaround that helps immensely for rooted tablets somewhere around here. I can't find it tonight, but it's in one of the other 'random reboot' threads.
sassafras
sassafras_ -
Did you ever find anything with this issue? I am on my second TF and it is exhibiting the same random reboot while sleeping issue as the first. I know you have a post on another thread indicating how to tell the kernel to ignore "oops" conditions - have you received any feedback on how that is working? I assume this requires root access, I haven't yet rooted my device.
I have collected a few ramdump log files, but as of now only one out of 6 shows a kernel panic. I am new to Android, and I am trying to make sense of the dump logs. It appears that these dumps are maintained in a ring buffer, so the last entries are usually somewhere in the middle, is that correct? All of them also have some garbage at the end, but I assume that is just another effect of the ring buffer strategy.
Like I said, I am new to Android, but I am a long time embedded and real-time programmer, and pretty handy in Linux. It seems to me that the log files aren't providing enough information, but I'm not sure how to debug kernel/system crashes in Android. If anyone could point me in the right direction of where I should look next to get more information on these crashes, perhaps we could get to the bottom of this problem.
From what I can tell via the logs, when the TF is sleeping, it wakes up from time to time for various reasons, then suspends when it is done. It looks like it is during this wake/suspend cycle that something occasionally goes wrong and causes the tablet to reboot.
I am hoping that this is a software/firmware issue (or a hardware issue that can be worked-around with software), because I really like the TF platform and this issue makes keeping apps like IM or email running while it the device sleeps kinda iffy.
Any help from the awesome experts here at XDA would be greatly appreciated, and I look forward to learning more of the gory details and inner workings of Android.
I have had the same issues. Configuring the kernel to ignore oops only helped a bit. The tf would still freeze in standby eventually (once a day or so). My supplier (i.e. not Asus) replaced it and my new tf (a SBK v2 one, unfortunately) has not rebooted once in 2+ weeks. So my guess is that it was a hardware issue (memory, something not coming out of backup mode properly, ...?). Not sure if one could work-around it in software.
Now, this was probably not very helpful but I thought I'd share my experience here. And possibly my tf suffered from an entirely different defect, although the symptoms were the same (ramdump logs from random reboots in standby, independent from wifi on/off, sync on/off, and lots of other settings I tried).
flipflipflip -
Thanks for your reply! I was hoping that it wasn't a hardware issue, and since I got two in a row with the identical problem I was thinking that maybe a software fix could get around it. After reading about your experience, I went ahead and returned it and ordered another one from a different source. Hopefully the third time's a charm!
I'm keeping my fingers crossed that this one is not an SBK v2, but I'll be happy just to have one without sleep-apnea!
This did give me a chance to load up ADB and poke around a bit under the hood of the last one, so if nothing else it is a learning experience. Hopefully I will have something to contribute to the community once I get my hands on a working device.
I know it's been a while (had a big work-related headache), but just wanted to post and let people know that I finally received a TF101 (B50!!) that seems to be working just fine - so I guess it was just a combination of bad luck and a hardware issue after all.
The only issue I have now is that sometimes when it is sleeping, it loses its internet connection (it still seems to be connected to the AP) - but I think I can work around that.
Cheers!
Hey folks, I have a problem (obviously).
I seem to have a problem that when I play Gamedev story, I sometimes get this freeze of all the software, and all of a sudden my phone turns off completely. I've already tried looking into things like overheating of the battery or the CPU but neither seems to be the problem yet. I can't seem to find anything on this critical error happening with the software I'm running. I have a SE Xperia X10 with 2.3.3 running. So here's my question to you guys: What's going on and how can I fix it?
Connect it to a computer use logcat (google "adb logcat") to view what the android log prints when your phones freezes.
Right. It happened again twice just now (once during gamedev story and once after it rebooted and I just started aLogcat). What should I look for in the log?
Kinan Eldari said:
Right. It happened again twice just now (once during gamedev story and once after it rebooted and I just started aLogcat). What should I look for in the log?
Click to expand...
Click to collapse
General errors, stuff out of the ordinary.
Collects some logs when it crashes, post them to pastie.org
and post the links in this thread. i will try to help.
here's the log after the most recent crashes (once again during gamedev story and once more after rebooting). I have no idea what the startup lines are for the OS, nor can I seem to find the logged command for starting the game. : (
I feel horribly inept right now...
Anyway, the forum doesn't seem to allow me to post links just yet and I hope this works.
pastie dot org / 2412136 dot js
dots are obvious and ofcourse you need to remove the spaces.
http://www.pastie.org/2412136.js
doesnt work
Alright. Just uploaded the .txt file then. Thanks up front for all the effort you're putting into this. : )
Having issues with my phone crashing randomly, I recorded a logcat before the crash trying to get information but I have no idea how to read it. Maybe someone can help out.
Thanks
Describe "crash"
rootSU said:
Describe "crash"
Click to expand...
Click to collapse
Will be doing something and the phone will just shut off. Varies on what I'm doing...browsing chrome... Playing a game...etc. Then phone wont come back on unless I plug it in. The battery is never dead when it shuts off or when I plug it in and reboot it.
Have a look at last_kmsg log immediately after it happens. Logcat only really shows what android is doing not what kernel is doing.
too much
Code:
E/PowerHAL(753): touch_boost: failed to send: No such file or directory
messages, I know it;s not much of an issue and that the mpdecisions are trying to overwrite and thus failing, but try
1.Changing kernel
2.Reverting to stock
Hi, I'll explain my problem quick. a week ago my Nexus 5 rebooted for no reason, upon rebooting I noticed something weird: app data configurations (app data not belonging to the user accesible memory) were all reset, it was like all apps had been freshly installed but left my pictures music and those things untouched. Wifi was working perfectly fine at this point, some form of data corruption I guess. Upon manually rebooting hoping it would come back to normal I found out wifi was behaving strangely, it would take a couple of seconds to turn on and off. After further reboots it stayed greyed out and didn't respond anymore.
So I began reading about the many possible causes and fixes. Tried reinstalling rom, reflashing kernel, going back to stock through flashing stock images through fastboot, rebooting, different radios. Nothing helped, so I decided to go a bit further and mess with the persist folder, first I checked permissions were ok and reset them anyway, then I wiped manually through a file explorer, finally I decided to do what was suggested here https://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576 with some success. Wifi was still greyed out after a fresh rom install but after some reboots it would pick up and work perfectly, until the next reboot. Then it didn't work anymore. I should note I backed up the files in persist through a file explorer and then manually pasted and set permissions (didn't know you could make an .img file of it) dunno if that has anything to do. They aren't corrupted it seems.
Unplugging the battery briefly fixed it for a day, then the next day the same problem came back without me doing anything.
Some more info:
-I have a working original EFS backup from before it crashed.
-Phone was rooted running CM11 when it happened, been using that rom for 2 years with EX kernel.
-It was a bit low on space (about 400mb left) when it happened, about 300mb were freed after it crashed. I have a hard time believing this could have caused it but maybe?
-It's global D821 16gb version
-GPS has always been wonky (if that has anything to do with it)
-IMEI and IMEID haven't changed.
-Calls and data work fine.
-When either wifi or bt work they show their correct, original addresses, only once wifi showed 02:00:00:00:00:00.
-Rebooting changes little, but powering off then waiting a few seconds and turning it on sometimes brings bt back.
-Leaving the battery unplugged almost fixed it, brought it back for some hours, went to sleep and when I woke up it was gone again.
-When performing the "e2fsck /dev/block/..." command above I wasn't prompted to fix any errors I think, output was "clean, 31/1024 files, 1125/4096 blocks" and the "make_ext4fs /dev/block/..." command reformats it without issue.
So yeah, I've tried everything save baking the mobo cause I'd rather be able to sell a semi working device than a bricked one
Any other thing I could try? Or way to check if it is indeed a hardware issue? im attaching a Liveboot log if it's of any use. Thanks beforehand.
uh I can't find the way to upload the log
how is one supposed to attach a file? im on my desktop with latest chrome