ChanServ 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
<kuruczgy[m]>
I already got such a crash a couple times on 6.14-rc2 and 6.14-rc4. Today I could get it repeatedly by disconnecting from a wifi network.
<anthony25>
I think so, there was quite some work for ath12k on the linux-wireless mailing list
<anthony25>
I have the same freezes due to wifi
<tobhe_>
anthony25: yeah I saw that I missed that one
<tobhe_>
not sure if that is what broke the yoga though
<anthony25>
I don't know if it helps, I had hard reboots before just by stressing the CPU for long enough with a bad airflow
<anthony25>
aka: compiling a kernel in bed after a mr proper :D
<tobhe_>
it certainly is something we want yeah
chrisl has quit [Ping timeout: 480 seconds]
<anthony25>
I meant I don't know if GPU throttling would have prevented the problem in that case, or if it creates heat elsewhere (CPU, for example) that creates instability
<anthony25>
in that case = what hogliux describes
<anthony25>
but whatever, hogliux should try with this patch
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
crimars has joined #aarch64-laptops
crisma has quit [Read error: Connection reset by peer]
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
leiflindholm has quit [Read error: Connection reset by peer]
leiflindholm has joined #aarch64-laptops
tobhe has joined #aarch64-laptops
tobhe_ has quit [Ping timeout: 480 seconds]
sibis has joined #aarch64-laptops
<sibis>
@maz: arm sbsa is emulated by gunyah ...
<sibis>
on x1e platforms
jglathe_volterra has quit [Quit: Leaving]
jglathe_x13s has quit [Remote host closed the connection]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
enyalios_ has joined #aarch64-laptops
enyalios has quit [Ping timeout: 480 seconds]
jhovold has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
lucanis has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
SpieringsAE has joined #aarch64-laptops
<SpieringsAE>
has anyone here ever used the ntc_thermistor driver? I've been fooling around with it but I cannot get it to probe correctly:
<SpieringsAE>
[ 21.763298] initcall ntc_thermistor_driver_init+0x0/0x1000 [ntc_thermistor] returned 0 after 526 usecs
<SpieringsAE>
I put a kprintf at the start of the probe function but nada. I've ten double checked if the compatible is correct
chrisl has joined #aarch64-laptops
<LiangQi[m]>
robclark: tobhe_ no idea about the glmark2-wayland hang(on both GNOME and Plasma 6.1). But glmark2(x11) works fine.
chrisl has quit [Ping timeout: 480 seconds]
<ektor5>
LiangQi[m]: you may have some logs in journalctl when the freeze happened, could be that glmark2 is making the GPU hang/crash
<maz>
sibis: thanks for confirming. it'd be really good to make that clear in the DT so that people stop wondering why they end-up with random crashes.
<maz>
also, I presume that there is an actual (non-SBSA) watchdog somewhere, and it would be good to document it too.
srinik has joined #aarch64-laptops
davidinux has quit [Ping timeout: 480 seconds]
davidinux has joined #aarch64-laptops
jglathe_angrybox has quit [Quit: Leaving]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
frontin has quit [Ping timeout: 480 seconds]
<LiangQi[m]>
ektor5: robclark glmark2-wayland hang after [terrain] on Thinkpad T14s Gen6 Snapdragon
<HdkR>
steev: It's pretty cool that they released the sources
xyzabc has quit [Remote host closed the connection]
xyzabc has joined #aarch64-laptops
xyzabc has quit [Ping timeout: 480 seconds]
<KieranBingham[m]>
This feels like a silly question as I'm sure it is, and the bios handles booting from selected devices, but is it 'safe' to completely erase /dev/nvme0n1 internal ssd on x13s ?
<KieranBingham[m]>
The EFI etc is all just loadable - nothing specific to boot process that can't be replaced right? (I still haven't been able to fix my laptop boot, so I've been booting from the USB stick all week - which hasn't been helped by the fact that I'm travelling in switzerland for work)
<robclark>
I believe that others have replaced the nvme in x13s, which sorta implies "important" stuff like uefi implmentation is on spi flash or similar
<robclark>
rather than a special partition on the nvme
<robclark>
there are devices that have special partitions on ufs (idk if it is ever done w/ nvme), deleting those would be bad(TM)
<craftyguy>
I've replaced the nvme in my x13s and haven't noticed anything broken because of it
<robclark>
it would be pretty obvious if you deleted the bios ;-)
<KieranBingham[m]>
Thanks - I was worried about 'ESP' ... but indeed it looks like that's just the EFI partition that gets loaded once EFI is running, so 'can be replaced'.
<KieranBingham[m]>
Interestingly, I have a USB drive with fedora plugged in, while I'm trying to reinstall/grub updates - and now I think I see the result of what's happening. os-prober no longer sees my main nvme drive as containing a linux distro ... which is annoying because it's there ;-)
<robclark>
yeah, esp is just the efi system partition... you need one but you can recreate it
<KieranBingham[m]>
And as yet I can't get fedora live iso or raw images to boot. The only thing I can boot is the ubuntu plucky iso - where the installer segfaults!