01:30 <bamse> steev: you're saying that we don't need that feature anymore?

05:35 <jhovold> steev: yeah, the nvme timeout issue is a known one. Haven't had time to look too much at that yet. Wait for a couple of 60s timeouts to expire and you can reboot from a rescue shell depending on your initramfs.

05:37 <jhovold> steev: regarding the display issue; sounds odd, but perhaps doing so is more likely to trigger a probe deferral. No time to look at that any more for a while either.

12:22 <steev> bamse: maybe we do? i just wanted it to build and that had gone away at some point

13:14 <jenneron[m]> bamse: Hi. I'm not sure you've seen my messages, but i have graphic artifacts on my Samsung Galaxy Book S. It's a hardware issue, since it also happens in windows. also, a bad thing is that someone who tested kernel for me says he had something similar in linux (but not in windows). is it possible that something in kernel + dtb affected hardware? it seems unlikely, but i'm asking just in case

13:50 <bamse> jenneron[m]: i've always expected that things could break due to misconfiguration, but i've not seen it happen yet...and i don't see why this problem would occur

13:51 <jenneron[m]> bamse: also, one more note, GPU performance is different from boot to boot in linux

13:51 <bamse> jenneron[m]: i've seen a couple of cases where the system starts crashing etc...

13:51 <jenneron[m]> so, it may be related to dvfs stuff

13:51 <bamse> jenneron[m]: interesting

14:26 <steev> bamse: i'm saying maybe because i haven't looked into it further, i just happened to look over and see that the thinkpad had rebooted instead of slept

14:26 <steev> i was far too tired last night to be useful

14:46 <robclark> jenneron[m]: do the artifacts go away if you power off and then reboot into windows? A warm reboot could preserve some state, either in the panel or display controller, etc

15:00 <jenneron[m]> robclark: still happens after cold boot

15:36 <steev> well, that's unfortunate, there's nothing in the logs at all about why it rebooted

15:38 <steev> and it doesn't seem like it's suspending actually does it, because manually suspending works

15:43 <jenneron[m]> pierro78: has anything like above happened to you?

15:44 <jenneron[m]> I think next time we try linux on your galaxy book s is only when we have dvfs support for gpu

16:48 <jenneron[m]> <jenneron[m]> "bamse: also, one more note..." <- it could happen because EFI firmware sets wrong GPU voltage + frequency and Linux just uses that

16:48 <jenneron[m]> i had run glmark2 not long before it happened

16:48 <jenneron[m]> (not long before artifacts started)

16:53 <robclark> I'd be pretty surprised if efi stuff touches the gpu at all

16:54 <robclark> normally the GMU controls the GPU freq and interconnect votes (on behalf of the CPU)

16:55 <robclark> you can use fdperf from mesa build to watch gpu freq.. not sure if there is a good way to monitor interconnect/ddr speeds (as those can also be implicated in gpu perf)

17:01 <steev> srinik: if you get some free time, can you poke at the c630? for some reason, with 6.0, everything *seems* like it should be working, but there's no audio output (and booting into 5.19 there is)

17:04 <steev> srinik: https://paste.debian.net/1252573

17:09 <jenneron[m]> robclark: bamse i've connected an external display and it's fine

17:09 <jenneron[m]> however this is probaly not very useful information

17:56 <pierro78> <jenneron[m]> pierro78: has anything like above happened to you? <= no I ve never seen anything like this

19:12 <macc24> is it my config or did internal display on lazor is broken for everyone on 6.0-rc3?

19:50 <robclark> macc24: you probably need the three reverts from https://gitlab.freedesktop.org/drm/msm/-/commits/msm-next-external-fixes/

19:54 <macc24> robclark: thanks! i'll try that tomorrow