Develop Bugs

[Q] dmesg errors on rooted roms

Hi there,
Could anyone explain me, this strange errors in dmesg log?
I checked and there aren't this errors on stock (don't rooted rom),
but after use unrevoked3 tool on this rom, errors appears in log,
also on pre-rooted teppic rom and another pre-rooted stock roms from here.
[...]
<3>[ 25.553009] msm_nand_erase: erase failed, 0x4d40000
<3>[ 25.553436] msm_nand_erase: erase failed, 0x4dc0000
<3>[ 25.553894] msm_nand_erase: erase failed, 0x4f80000
<4>[ 25.554199] yaffs_read_super: isCheckpointed 0
<3>[ 25.554687] msm_nand_write_oob 11a80000 800 1c failed -5
[a lot of same messages]
[a lot of same messages]
[a lot of same messages]
<3>[ 25.617645] msm_nand_write_oob 11afc800 800 1c failed -5
<4>[ 25.617828] save exit: isCheckpointed 1
<6>[ 25.632659] yaffs: dev is 32505861 name is "mtdblock5"
<6>[ 25.632781] yaffs: passed flags ""
[...]

[Q] sd-ext remounted as read-only on connectivity changes

Hey everyone,
I am having a strange problem with my sd-ext (ext4) partition for some time now.
The ROM I am using is ICS for Desire by Sandvold (Amarullz and a2sd), but I don't know whether this is strictly ROM related or not.
I have been getting some mass FCs over and over again, across different versions flashed after full wipes.
Today I found out that the problem is that the sd-ext partition is not properly mounted (read-only), but here is the weird part: it is properly mounted (read-write) using the recovery and is also properly mounted before I unlock the sim-card.
When I unlock the sim-card or otherwise change the connectivity (WLAN, mobile data, airplane mode) it remounts sd-ext as read-only.
I have already tried reformatting and repartioning the sd-card.
Any idea why the system is doing that or how I can prevent that from happening?
Thanks
\Update1:
Here is a part of dmesg, showing the error when I unlock the sim-card after a fresh reboot:
Code:
<6>[ 182.512451] active wake lock PowerManagerService
<6>[ 182.512481] active wake lock vbus_present
<6>[ 182.512481] active wake lock SMD_DS, time left 35
<6>[ 182.512481] [R] early_suspend end
<6>[ 190.756866] batt: 74%, 3884 mV, 290 mA (210 avg), 29.8 C, 1008 mAh
<3>[ 191.665740] mmc1: Data CRC error
<3>[ 191.665954] msmsdcc_data_err: opcode 0x00000019
<3>[ 191.666168] msmsdcc_data_err: blksz 512, blocks 16
<3>[ 191.666595] mmc1: DMA channel flushed (0x80000004)
<3>[ 191.666839] Flush data: 0000c003 3b2d8018 00000000 00400040 00370035 00008003
<6>[ 191.667266] mmc1: Controller has been re-initialiazed
<3>[ 191.672515] mmcblk0: error -84 transferring data, sector 6710376, nr 16, card status 0x900
<3>[ 191.672973] mmc1: Data timeout
<6>[ 191.673217] mmc1: Controller has been re-initialiazed
<3>[ 191.673797] end_request: I/O error, dev mmcblk0, sector 6710376
<3>[ 191.674041] end_request: I/O error, dev mmcblk0, sector 6710384
<3>[ 191.679138] Aborting journal on device mmcblk0p2-8.
<0>[ 191.687255] journal commit I/O error
<2>[ 191.726745] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:276: Detected aborted journal
<2>[ 191.727478] EXT4-fs (mmcblk0p2): Remounting filesystem read-only
<3>[ 191.984802] binder: 1268: binder_alloc_buf, no vma
<6>[ 191.985046] binder: 206:339 transaction failed 29201, size 4-0
<6>[ 191.985412] binder: send failed reply for transaction 79996 to 1268:1268
The weird thing is that I have been running the phone without any problem in airplane mode + WLAN for a whole day, until I tried to reactivate mobile connection again and do some tests with it.
It seems that the system only has a problem with the journal when it uses the mobile connection.
\Update2:
Here the dmesg message before I unlock the sim-card. No error message for sd-ext:
Code:
<6>[ 13.084991] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: noauto_da_alloc,data=ordered,commit=15,barrier=1,nouser_xattr,errors=continue
4EXT is also unable to find any errors with the sd-ext partition (I have used the recovery to format and partition the sd-card).
\Update3:
Ok I just reformatted and repartitioned the sdcard again using gparted and reflashed the ROM with a full wipe.
I am getting the same error again.

mmcblk0 I/O error – possible hardware problem?

Hello, guys!
This morning I found my phone with black screen and not responding to power button. I pulled the battery out and tried to boot. The phone only showed the "Google" text on the black screen for several minutes (five, may be ten minutes) and did not respond to any buttons. At this point I pulled the battery for the second time and tried the recovery mode. The stock recovery booted after about a minute of "Google" screen. In stock recovery the only option I tried first time was "Wipe cache". It showed a static image of "work-in-progress" with static progress bar for several seconds and then returned to main recovery screen. I tried the "reboot" and received the black screen with no buttons working.
Pulled the battery and tried normal boot, which stuck on black "Google" stage.
Ok, I connected the phone to my laptop, and booted TWRP via fastboot, it took a little longer to boot, but at least I managed to "adb-shell" it and grab dmesg output. This is the relevant part (containing "mmc" word):
Code:
<6>[ 2.828399] mmc0: new high speed MMC card at address 0001
...
<6>[ 2.829101] mmcblk0: mmc0:0001 VYL00M 14.6 GiB
<6>[ 2.829345] mmcblk0boot0: mmc0:0001 VYL00M partition 1 512 KiB
<6>[ 2.829681] mmcblk0boot1: mmc0:0001 VYL00M partition 2 512 KiB
<6>[ 2.835021] Reprogramming LPDDR2 timings to 400000000 Hz
<3>[ 2.836090] Power Management for TI OMAP4.
<6>[ 2.836334] OMAP4 PM: Static dependency added between MPUSS and DUCATI <-> L4_PER/CFG and L3_1.
<6>[ 2.836517] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13
<4>[ 2.837432] sr_init: No PMIC hook to init smartreflex
<6>[ 2.837799] smartreflex smartreflex.0: omap_sr_probe: SmartReflex driver initialized
<6>[ 2.838073] smartreflex smartreflex.1: omap_sr_probe: SmartReflex driver initialized
<6>[ 2.838317] smartreflex smartreflex.2: omap_sr_probe: SmartReflex driver initialized
<6>[ 2.838592] sr_class1p5_driver_init: OMAP4460: add 10mV margin for class 1.5
<6>[ 2.838928] SmartReflex class 1.5 driver: initialized (86400000ms)
<6>[ 2.839569] mmcblk0boot1: unknown partition table
<6>[ 2.840728] [MODEM_IF] PA EVENT : reset =0, pa=1
<6>[ 2.840972] mmcblk0boot0: unknown partition table
...
<4>[ 3.851135] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
<4>[ 3.899353] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
<6>[ 3.915679] mmc1: new high speed SDIO card at address 0001
<4>[ 3.917633] F1 signature read @0x18000000=0x16844330
<4>[ 3.927154] DHD: dongle ram size is set to 294912(orig 294912)
...
<3>[ 7.677093] mmcblk0: timed out sending r/w cmd command, card status 0xe00
<3>[ 7.677276] mmcblk0: not retrying timeout
<3>[ 7.677581] end_request: I/O error, dev mmcblk0, sector 1495040
<3>[ 7.677764] Buffer I/O error on device mmcblk0p11, logical block 0
<4>[ 7.678100] lost page write due to I/O error on mmcblk0p11
<6>[ 7.678802] EXT4-fs (mmcblk0p11): recovery complete
<6>[ 7.679138] EXT4-fs (mmcblk0p11): mounted filesystem with ordered data mode. Opts: (null)
<3>[ 8.737213] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
<3>[ 8.737304] mmcblk0: command error, retrying timeout
<3>[ 8.737426] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
<3>[ 8.737548] mmcblk0: command error, retrying timeout
<3>[ 8.737701] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
<3>[ 8.737762] mmcblk0: command error, retrying timeout
<3>[ 8.737915] mmcblk0: timed out sending r/w cmd command, card status 0x400e00
...
and a lot of I/O errors with mmcblk0 block device
Reading from /dev/block/mmcblk0 constantly fails, even the first sectors (dd if=/dev/block/mmcblk0 of=/dev/null).
I pulled the battery out, left the phone and rushed to the work.
With my little knowledge it looks like broken sdcard itself or sdcard controller. Does it make any sense? Is it possible to repair it easily? I realize I cannot simply replace sdcard, as it most likely soldered in the board, but how hard is it to replace if I have the equipment and spare parts?
Another question: as I can boot TWRP recovery via fastboot, is it theoretically possible to find and boot a custom kernel, which does not require internal storage at all, like some stripped kernel which works only in RAM, but still provides the basic functions like phone calling, wifi browsing and something like this?
Any help would be greatly appreciated!

Try restoring your phone to stock using ODIN
http://forum.xda-developers.com/showthread.php?t=1827685
I think the PIT file should repair your partition table if it's just a software problem

Thanks for the tip. I guess I will try odin methods only as as a last resort since it may void my warranty. I am still positive about sending my unit to the service center in January.
At the moment fastboot methods do not work if they try to actually write something. fastboot boot works pretty good.

Looks like a bad partition, ODIN back to factory wont void your warranty. All it does is reset your phone to the stock image, that's probably what they'll do when you send it in for warranty repair. Save yourself the time and trouble.

Bad blocks is something software won't fix. This is a hardware problem with the flash memory and it needs replaced.

I had something like this happen when I was formatting my /data partition in TWRP. I did a factory reset and it was like "wiping /data without wiping /data/media" and just to be on the safe side I wiped /data and it froze and when I got control back it said that it couldn't format it or anything so I ended up restoring the factory image and that fixed everything.

varet tviengt
Once again, just to be on the safe side, I will not try ODIN factory reset just yet. As it may be the hardware problem and I may end up with phone-triangle-computer state, in which case my warranty might be rejected like I messed something up myself blah-blah-blah.
The problem with the warranty is that I should go to my home, and I am now several thousands kilometers away from it on a vacation. So I will just wait for it.

I'm having the exact same problems for the last few weeks. Did you fix it? If so, how?

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

I have a GNexus 4.2.2 stock and I have reboot problem from the last week.
in the last_kmsg(attached) I read many references to mmc problems, for example
Code:
[ 5213.429595] mmcblk0: timed out sending r/w cmd command, card status 0x900
[ 5213.429779] mmcblk0: not retrying timeout
[ 5213.429901] end_request: I/O error, dev mmcblk0, sector 2450976
[ 5213.430084] end_request: I/O error, dev mmcblk0, sector 2450984
[ 5213.430175] end_request: I/O error, dev mmcblk0, sector 2450992
[ 5213.430328] end_request: I/O error, dev mmcblk0, sector 2451000
[ 5213.430450] end_request: I/O error, dev mmcblk0, sector 2451008
[ 5213.430603] end_request: I/O error, dev mmcblk0, sector 2451016
[ 5213.430694] end_request: I/O error, dev mmcblk0, sector 2451024
[ 5213.430847] end_request: I/O error, dev mmcblk0, sector 2451032
[ 5213.431091] Aborting journal on device mmcblk0p12-8.
I have already restore the Factory Images from Google developer, but I don't solve.
Is damage the memory or is a software problem?

up

Any news here? Since a few days I'm experiencing the same problem .

I have sane issue ! Any info for us ?
Inviato dal mio Galaxy Nexus usando Tapatalk 4

I am experiencing this problem too. Often apps crash when SQLite tries to write something to disk: Disk I/O error (code 1034).
I'm also getting random reboots and corrupted files.
This happens both with CM11-M2 and stock 4.3 ROM, so I don't think it's a software problem.
Do you think the internal storage is dying? Is there something I can do? Thanks!

WiFi not working on on ANY ROM

Hi everyone,
sorry for the lengthy post, but I wanted to be precise. Please read the whole of it, if you think you might be able to help. I love this phone but it's useless without WiFi for me. I am also sorry, if I unwittingly violated any forum rules. I tried the best I could.
Currently, I am having a severe issue with the WiFi of my HTC Desire Z. It won't turn on or do anything. First of all: I worked myself through all threads that I could find which were just remotely connected with this issue, also in forums concerning other devices. I still hope I overlooked something... Btw.: My phone is almost 3 years old and a German version. I don't remember what method I used to root it since it was one of the first things I did.
The aforementioned problem appeared right after the following incident: My phone went out of battery while I was listening to an audiobook via Audible. I put the phone in airplane mode some 10 minutes earlier to prevent this, very <irony>successfully<\irony>...
After rebooting, I tried to turn WiFi on, but it just kept telling me "turning wifi on". The switch turned grey and nothing happened. I tried rebooting, turning WiFi on and of several times as well as airplane mode. I flashed the following ROMs, some of which I have been using sometime earlier where WiFi has definitively been working: Andromadus JellyBean by Flinny (version 123, 133 if that matters), all CM stable releases, Andromadus Mimicri 1.50 together with the sugested WiFixIt. With these ROMs I did the same. I could not find any stock ROM that has been able to boot. I did not try to reverse root and s-off (seems pointless to me).
I update the Radio to (afaik most recent version) and I downgraded it a few other versions without any change. I also did a superwipe with the tools given on the following page and reinstalled the ROMs, to no avail: http://forum.xda-developers.com/showthread.php?t=1044992
I also tried different sim-cards (from UK and Germany), both with and without sim-card and sd-card. Also no success.
Bluetooth is working flawlessly. I have just copied a file from my Laptop over to my phone via BT, which is strange, because, as far as I know, both WiFi and BT use the same chips and the same antenna.
I pulled all the logs I found (logcat: main, event, radio; dmesg) and boiled it down to the driver not being able to be loaded. Please correct me, but the WiFi drivers come with the ROM, therefore it CANNOT be due to a faulty driver, since I installed some that worked months ago (tried this before and after flashing different radios).
I reckon that the following parts are the important ones, but I attached the complete logs (cover the boot process and me trying to turn WiFi on) to be on the safe side. As far as I understand, it just says that it tries to load the driver bot fails to attach some kind of module.
Dmesg:
<6>[ 45.185119] [WLAN] ## wifi_probe
<4>[ 45.185302] [WLAN][WRN] wifi_set_power = 1
<6>[ 45.185455] [WLAN]vision_wifi_power: 1
<6>[ 46.075988] [WLAN] wifi_set_carddetect = 1
<6>[ 46.076141] vision_wifi_set_carddetect: 1
<6>[ 46.076293] mmc1: Slot status change detected (0 -> 1)
<6>[ 46.089599] [WLAN] Dongle Host Driver, version 5.90.125.120
<6>[ 46.089599] Compiled in drivers/net/wireless/bcmdhd on Oct 1 2012 at 17:46:03
<4>[ 46.129547] mmc1: queuing unknown CIS tuple 0x91 (3 bytes)
<6>[ 46.129882] mmc1: new high speed SDIO card at address 0001
<6>[ 47.087982] [LED]pm8058_drvx_led_brightness_set: bank 3 brightness 0 +
<6>[ 47.088287] [LED]pm8058_drvx_led_brightness_set: bank 3 brightness 0 -
<6>[ 47.935516] [TP][email protected],797
<3>[ 48.187652] mmc1: CMD53: Data timeout
<6>[ 48.187927] mmc1: SDCC PWR is ON
<6>[ 48.188110] mmc1: SDCC clks are ON, MCLK rate=50000000
<6>[ 48.188262] mmc1: SDCC irq is enabled
<6>[ 48.188507] ===== SDCC-CORE: Register Dumps @base=0xec832000 =====
<6>[ 48.188629] Reg=0x00: 0x00000003, 0x00009b00, 0x15000004, 0x00001475.
<6>[ 48.188903] Reg=0x10: 0x00000035, 0x00001000, 0x00000000, 0x00000000.
<6>[ 48.189025] Reg=0x20: 0x00000000, 0x05f5e100, 0x00000004, 0x00000043.
<6>[ 48.189270] Reg=0x30: 0x00000004, 0x00400200, 0x00000000, 0x00a081ff.
<6>[ 48.189514] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000.
<6>[ 48.189666] Reg=0x50: 0x00000000, 0x00000000, 0x00000000, 0x00000000.
<6>[ 48.189910] Reg=0x60: 0x00000000, 0x00000000, 0x00000000, 0x00000000.
<6>[ 48.190063] mmc1: PIO mode
<6>[ 48.190307] mmc1: xfer_size=4, data_xfered=0, xfer_remain=4
<6>[ 48.190429] mmc1: got_dataend=0, prog_enable=0, wait_for_auto_prog_done=0, got_auto_prog_done=0
<4>[ 48.190917] [WLAN][WRN] F1 signature read @0x18000000=0xffffffff
<6>[ 48.797210] [TP][email protected],866
<6>[ 48.798217] [TP]calibration confirm with recal by position
<6>[ 48.823303] [TP]0x01 0x10 0xA8 0x85 0x00
<6>[ 48.835113] [TP]0x01 0x00 0xA8 0x85 0x00
<3>[ 50.226043] mmc1: CMD53: Data timeout
<6>[ 50.226226] mmc1: SDCC PWR is ON
<6>[ 50.226409] mmc1: SDCC clks are ON, MCLK rate=50000000
<6>[ 50.226684] mmc1: SDCC irq is enabled
<6>[ 50.226806] ===== SDCC-CORE: Register Dumps @base=0xec832000 =====
<6>[ 50.227081] Reg=0x00: 0x00000003, 0x00009b00, 0x15000004, 0x00001475.
<6>[ 50.227233] Reg=0x10: 0x00000035, 0x00001000, 0x00000000, 0x00000000.
<6>[ 50.227478] Reg=0x20: 0x00000000, 0x05f5e100, 0x00000004, 0x00000043.
<6>[ 50.227630] Reg=0x30: 0x00000004, 0x00000200, 0x00000000, 0x00a081ff.
<6>[ 50.227874] Reg=0x40: 0x00000000, 0x00000000, 0x00000000, 0x00000000.
<6>[ 50.228149] Reg=0x50: 0x00000000, 0x00000000, 0x00000000, 0x00000000.
<6>[ 50.228271] Reg=0x60: 0x00000000, 0x00000000, 0x00000000, 0x00000000.
<6>[ 50.228546] mmc1: PIO mode
<6>[ 50.228668] mmc1: xfer_size=4, data_xfered=0, xfer_remain=4
<6>[ 50.228820] mmc1: got_dataend=0, prog_enable=0, wait_for_auto_prog_done=0, got_auto_prog_done=0
<4>[ 50.229370] [WLAN][WRN] dhdsdio_probe_attach: si_attach failed!
<4>[ 50.229644] [WLAN][WRN] dhdsdio_probe: dhdsdio_probe_attach failed
<4>[ 50.242645] [WLAN][WRN] dhd_module_init: wifi_fail_retry is true
<6>[ 50.247802] [WLAN] ## wifi_remove
<4>[ 50.247985] [WLAN][WRN] wifi_set_power = 0
<6>[ 50.248107] [WLAN]vision_wifi_power: 0
<6>[ 51.038665] [WLAN] wifi_set_carddetect = 0
<6>[ 51.038818] vision_wifi_set_carddetect: 0
<6>[ 51.038970] mmc1: Slot status change detected (1 -> 0)
<6>[ 51.039978] mmc1: card 0001 removed
<6>[ 51.041442] [WLAN] ## wifi_remove leave
Click to expand...
Click to collapse
Logcat main:
E/CommandListener( 115): Failed to open /proc/sys/net/ipv6/conf/wlan0/disable_ipv6: No such file or directory
E/WifiStateMachine( 294): Failed to disable IPv6: java.lang.IllegalStateException: command '1 interface ipv6 wlan0 disable' failed with '400 1 Failed to change IPv6 state (No such file or directory)'
...
I/WifiService( 294): WifiService starting up with Wi-Fi enabled
D/WifiService( 294): setWifiEnabled: true pid=294, uid=1000
D/WifiWatchdogStateMachine( 294): Disabling poor network avoidance for wi-fi only device
...
may times:
E/WifiHW ( 294): Supplicant not running, cannot connect
E/WifiHW ( 294): Supplicant not running, cannot connect
E/WifiStateMachine( 294): Failed to setup control channel, restart supplicant
Click to expand...
Click to collapse
Methinks it is a hardware issue and I am very close to taking the thing apart, which will possibly break something else... Second last comment: As I try to turn WiFi on via the status bar, it reboots after like one minute. Last comment: Is there any way to check whether it really is a hardware fault?
I apprecieate any comment intended to be helpful. Even when it is you telling me that it IS a hardware issue. If you need any further information, I am more than happy to provide it. I would also be happy to make the life of my phone-saviour more enjoyable with one or two pints of something, if we can arrange a meeting.

haha, i doubt ill be in germany any time soon... but i will be in greece in a month or so...
well it sounds like youre trying all the right things and it possibly is a hardware fault. but being you rooted 3 years ago you dont have true radio s-off, as it wasnt around.
if it were me, i would unroot, then follow the gfree method to downgrade and root via gfree, this will fully wipe out all partitions (except efs) and then flash a tried and true rom like cm7, hopefully all will be well at this point... if not, hardware...

Thank you for your advice. I did as you told me and went through the pain to reinstall stock Froyo as well as stock recovery and hboot. I also had s-on (at leats that's what hboot and gfree_verify said). Then I went to reroot it again, this time using gfree1.0 (which was definitely not what I used last time).
But unfortunately WiFi did not work neither with stock Froyo nor after rerooting and running CM7. Bluetooth still worked fine in every case... Log still says the exact same thing.
There is just two things left that might be worth a try, but it's a long shot. Could it be a problem with some data on the efs-partition that is messed up? As far as I understand it that is where android stores important information about IMEI, MAC-adress an the like. But I really do not know how to restore this partition even if it were the cause. Or could it be a problem with the RIL since that is what communicates with the radio? But I also do not know how to restore this if it were the cause (but it's just said that matching the RIL might just improve performance).
What's your opinion about this? Do you think that a look at the phone's insides might yield any results/certainty?

Unfortunetly if you never made a backup of your efs partition there is no way to restore this, you can back it up now, wipe it, restore and see if that helps but I doubt it.
Ril is matched when you downgraded so that's not it. Trutfully my best guess is hardware, sorry
Sent from my HTC Vision using xda premium

Unfortunately, I never made a backup of my /efs. I also tried wiping it, but no change.
The only sad thing is, that there is no adequate replacement...
I still don't get why BT is working and WiFi is not while both use the same chip, but that will stay a mystery forever unresolved.
Is there any way to close this tread? Somehow I don't see any.

Mine does what you are describing, but it's cause my gf dropped it
Sent from my SGH-T999 using xda premium
---------- Post added at 01:10 AM ---------- Previous post was at 01:08 AM ----------
And disconnected the wireless "modem"
The drop was pretty severe, however. I needed a whole new battery cover
Sent from my SGH-T999 using xda premium

op did you solved error ?

Nope, I could not solve the issue and I did not disassemble my phone and risk being left without one. So far, my mobile data plan has been sufficient and for large data, I access the internet via a USB-cable. I will get a new phone though when I am less busy at work.
Sent from my HTC Vision

[Q] Having random crashes. Can't find too much in the kmsg.

Alright so lately I'm having some issues with my phone.
It randomly crashes all the time. Whenever that happens i need to format the system partition and need to reflash everything. I tried flashing multiple kernels but the problem just persists.
Sometimes it completely crashes other times i think it stays on but does nothing until i pull out the battery and after i boot backup up (after reflashing everything.) my background has been reset and my wifi networks wiped.
Could this be software related or hardware related? Since the phone is pretty old (Took it over from someone i know).
This is the only thing that i find in the kernel og that may cause the problem:
Code:
<4>[ 4960.491485] omap_hwmod: ipu: failed to hardreset
<6>[ 4960.500305] omap-iommu omap-iommu.0: ducati: version 2.1
<6>[ 4960.613525] rpmsg_omx rpmsg6: conn rsp: status 0 addr 101
<4>[ 4960.671600] omap_hwmod: iva_seq0: failed to hardreset
<6>[ 4960.683227] rpmsg_omx rpmsg-omx1: local addr assigned: 0x402
<4>[ 4960.687438] omap_hwmod: iva_seq1: failed to hardreset
<6>[ 4960.691284] rpmsg_omx rpmsg6: conn rsp: status 0 addr 103
<6>[ 4960.857055] rpmsg_omx rpmsg-omx1: local addr assigned: 0x403
<6>[ 4960.858459] rpmsg_omx rpmsg6: conn rsp: status 0 addr 104
<3>[ 4961.406158] omap_tiler_alloc: failure to allocate address space from tiler
And then a whole bunch of messages about the low memory killer killing processes.