Anyone know anything about this line i keep seeing in my kernel boot up logs?
kgsl_ioctl_rb_issueibcmds| invalid cmd buffer ibaddr 000171b0 sizedwords 1
It seems that the boot process encounters this and starts re-processing from the htc-acoustic peice onwards, until the above is encountered. Stuck in a loop.
Any help is much appreciated. Thanks
Related
Anyone know anything about this line i keep seeing in my kernel boot up logs? This is an ICS kernel for the mecha
kgsl_ioctl_rb_issueibcmds| invalid cmd buffer ibaddr 000171b0 sizedwords 1
It seems that the boot process encounters this and starts re-processing from the htc-acoustic peice onwards, until the above is encountered. Stuck in a loop.
Any help is much appreciated. Thanks
I've compiled it without any errors and applied the necessary patches too. I used cm12.0's boot.img so that I can get logcat (can't get logcat from cm12.1's boot.img). But whenever I try to boot cm12.1, it stucks at bootlogo and never goes ahead. I can get logs from adb but can't figure out, can you help me fix this problem while booting? Here's the logcat: https://paste.ee/p/A5GHK
I contacted a developer and he said that the problem is in this line:
Code:
[ 01-27 10:33:43.634 116: 116 E/HAL ]
load: module=/vendor/lib/hw/gralloc.mt6589.so
dlopen failed: library "libcorkscrew.so" not found
But I'm not sure on how to fix it, I applied a patch regarding libcorkscrew but then too can't fix that. Help me please. Thank you
I used CatLog in Debug mode to no avail. I can't figure out what's causing the Random Restarts problem. I've even reflashed my whole system.
The problem with CatLog is that it needs to write to disk to record the log. When I set it to write every 50 or 20 lines, I successfully reproduced a random restart while it's logging, but when I look at the log, it only recorded the 50 or 20 lines PRIOR to the random restart. I need at least the last 3 lines.
When I set it to record every 1 line (this should work in theory), it goes into a "log loop" logging it's own log as a log. So in other words, it logs that it's logging every time it logs a line. This makes the log file useless as I need to go on living for hours until I successfully produce the next random restart by accident, which I can't do as this will fill up my whole disk and may cause me a bigger problem in a matter of an hour or two, I assume.
Instead of catlog use logcat through terminal.
Code:
su
logcat > "your sdcard path here"/log.txt
Or
logcat | grep E/ > "your sdcard path here"/log.txt
Then you have either a full log or an error log. Or for debug only replace E/ with D/
DestructoS said:
Instead of catlog use logcat through terminal.
Code:
su
logcat > "your sdcard path here"/log.txt
Or
logcat | grep E/ > "your sdcard path here"/log.txt
Then you have either a full log or an error log. Or for debug only replace E/ with D/
Click to expand...
Click to collapse
How will that help? And when do I do that? Before the incident so it's logged, or afterwards so it's written to this specified file?
Sorry logcat before the incident as logcat doesn't stop until something explictly stops it and as you are piping it to file as it goes you will get a log until the last entry before reboot. It won't solve the problem but at least you will have a log.
DestructoS said:
Sorry logcat before the incident as logcat doesn't stop until something explictly stops it and as you are piping it to file as it goes you will get a log until the last entry before reboot. It won't solve the problem but at least you will have a log.
Click to expand...
Click to collapse
Thanks. Exactly what I need. I hope it works.
early console in decompress_kernel
input_data: 0x01556101
input_len: 0x004eb1fd
output: 0x01000000
output_len: 0x00a30490
run_size: 0x00adc000
Decompressing Linux... Parsing ELF... No relocation needed... done.
Booting the kernel.
same message displayed both the time first i tried with the 64 bit version then the 32 bit
please help.
Same happend to after updating to 2.0.402
and besides from that message, below appears this:
.
[ 0230018] Failed to find cpu0 device node
Detecting android-x86... foun at /dev/sda7
Checking data partition ...
[email protected]_x86_64:/ #
Hi everyone,
I have recently been trying to port Ubuntu Touch to our beloved surnia.
I'm using the phablet-5.1 tree with AOSP-5.1 device, vendor, kernel and other repositories.
I managed to finish the build with the kernel config adapted to work with Ubuntu. (using jamino's phablet-porting-scripts (on github) and patching some files about uid/gid errors). But this isn't the problem, the default defconfig causes the same problems.
I can confirm my kernel/e3 recovery both work and can mount partitions etc, but only when I'm using the
Code:
fastboot boot recovery.img
command AND my custom boot.img isn't flashed to the device.
When trying to boot the recovery directly from the phone I get a
Code:
Error: Failed to load kernel!
error message in the bootloader log.
If my boot.img is flashed to the phone, whatever file I try to load with
Code:
fastboot boot
, I get an error from my computer :
Code:
booting...
FAILED (remote failure)
but no error from the phone
I had to replace the prebuilt gcc toolchains in the android source tree with my system's ones, could it cause the problem?
I'm quite new to android development and all so please don't blame me if the fix is obvious.
Thanks in advance