Kernel crash 2025120401

nandohyphen1

After updating my 6a to 2025120401 it rebooted twice and the kernel crashed. If I reboot it, it always reboots twice and the kernel crashes. Here's the crash log.
https://drive.proton.me/urls/GVH03XFDYR#4pu8CbWv8dTc

de0u

nandohyphen1 It's not clear to me what that's about.

This may be the heart of the matter: Oops - BUG: Fatal exception: comm:NDK MediaCodec_ PC:kmem_cache_free_bulk+0x964/0xa30 LR:kmem_cache_alloc_bulk+0x3b4/0x408

Is there a MediaCodec oops in the crash log every time?

Novalissoide

nandohyphen1 I recommend this setting, go;
Settings > System > System update > Require battery above warning level: ON

nandohyphen1

de0u Is there a MediaCodec oops in the crash log every time?

Yes, it looks like there is. All the crash logs are identical to the first one I posted.

de0u

nandohyphen1 All the crash logs are identical to the first one I posted.

Skeptical. Every time somebody is in wl_cfg80211_up?

nandohyphen1

de0u here's another crash log. It looks identical to me. I don't know why.
https://drive.proton.me/urls/R6RCCKTR5W#vHHbh28ksTI4

Question, How do you read crash logs (like what to look for?). I'd be interested in knowing what to look at in the logs so I can diagnose the problems when I get logs. ;)

de0u

nandohyphen1 Here's another crash log. It looks identical to me. I don't know why.

It looks identical because it is byte-for-byte identical. It is genuinely implausible that two different crash dumps would be identical down to the time stamps, so I can't help suspecting that's two copies of the same crash log.

de0u

nandohyphen1 Question, How do you read crash logs (like what to look for?).

I'm not really qualified to interpret Linux kernel crash logs. I can fake it to a limited degree based on experience over some years with BSD and Plan 9. If there's a panic message, start there. Look at the kernel stack traces to what was going on.

It helps to have written some kernel code. A careful read of a couple of kernel internals books (e.g., the Love book and the FreeBSD book) would also help.

nandohyphen1

My phone was getting pretty low on battery as well as it updated and I didn't realise it until after I rebooted it (it had 6%). Now that I think about it,maybe that caused it? It seems like it had enough battery to boot,but it rebooted twice. I'm just charging it up now. Maybe that will stop the crashes (hopefully!).

CleverDogo

Thought I'd share my kernel crash log to help out OP. I'd wager it's a coincidence though.
Updated to 2025120401 with my 7a. No boot loop though.
Crashed once, rebooted, and booted fine. Even after a manual restart it has been fine and running the past half hour.
Linky link:
https://drive.proton.me/urls/A4MS01FEK0#1Q6cGWGIYpii

de0u

CleverDogo At a glance what I see is Oops - BUG: Fatal exception: comm:app_process64 PC:kmem_cache_free_bulk+0x964/0xa30 LR:kmem_cache_alloc_bulk+0x3b4/0x408.

It is somewhat interesting that both of you, on different devices, seem to be reporting a crash in kmem_cache_free_bulk. Perhaps a developer will take a look.

nandohyphen1

I've charged my phone up overnight, and tried rebooting it. It did not crash. Maybe that was the problem? It was super low and I didn't realize it when it updated.