robclark changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Chrome OS Trogdor Devices - Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630 - Lenovo ThinkPad X13s - and various other snapdragon laptops) - https://oftc.irclog.whitequark.org/aarch64-laptops
saekau[m] has left #aarch64-laptops [#aarch64-laptops]
cmeerw[m] has quit []
underpantsgnome[m] has quit []
amstan has quit [Quit: Client limit exceeded: 20000]
DocGalaxyBlock[m] has quit [Quit: Client limit exceeded: 20000]
Guest8012 has quit [Quit: Client limit exceeded: 20000]
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
hexdump01 has quit []
hexdump0815 has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
sally has joined #aarch64-laptops
heapheap has quit [Ping timeout: 480 seconds]
luxio_39[m] has quit [Quit: Client limit exceeded: 20000]
<Jasper[m]>
Gonna try and rescue my arch install
<Jasper[m]>
Okay I did that, reinstalled the kernel aswell
<Jasper[m]>
But it still reboots after unlocking LUKS, I have no idea why it does that
<Jasper[m]>
Is there a way to retrieve logs for when that happens? I don't want to fix the install afain hahaha
_[m]1 has quit []
heapify has joined #aarch64-laptops
heapify has quit [Quit: heapify]
agl7 has joined #aarch64-laptops
bankbank_ has joined #aarch64-laptops
bankbank has quit [Read error: Connection reset by peer]
bankbank_ has quit [Quit: Leaving]
<juergh>
robclark, Seeing this with 6.5-rc4 on a x13s. I just realized that it's been around for a while and I forgot to report it:-(
<juergh>
UBSAN: array-index-out-of-bounds in /build/mantic/drivers/gpu/drm/msm/msm_gem_vma.c:105:11
sally has quit [Remote host closed the connection]
laine has joined #aarch64-laptops
laine has quit [Ping timeout: 480 seconds]
srinik has quit [Killed (NickServ (Too many failed password attempts.))]
srinik has joined #aarch64-laptops
<Jasper[m]>
I've been trying to get some patches together from upstream, the mailinglist and otherwise to get mainline running on the Pixel C, but I'm running into a problem where enabling cros-ec's platform drivers and sensorhub basically throws up some interrupt related error and I can't easily figure out what the problem is. Anyone have an idea what's happening here?