11:54 <mort_> sooo modemmanager causes my wifi driver to crash

11:54 <mort_> I feel like that shouldn't happen

13:44 <konradybcio> if you expect somebody to help you, you need to provide more information than "computer bad"!

13:49 <mort_> well, here's a log: https://p.mort.coffee/KMx

13:50 <mort_> I run ModemManager, do nothing with it, some seconds later the driver (or firmware?) crashes

13:52 <steev> lumag: i tried enabling external display on the c630 again, and something a bit odd happens - internal display comes up, but wifi ends up broken, and i end up with this dmesg (stack trace in it is about 680 lines in) - any ideas on patches i might be missing? https://paste.debian.net/hidden/47720223/

13:58 <lumag> steev, yes. There was a patch for that. Let me find it.

13:59 <lumag> steev, I think f2c7ca890182d24ac817fa321489346000271c5c should have fixed that

14:05 <steev> lumag: isn't that for the bottom one, not the missing clk?

14:06 <lumag> steev, yes

14:06 <lumag> I missed the clk one :-)

14:06 <steev> ah, i meant the top one, but that's good to know for the bottom one since i see that message on the x13s too

14:08 <lumag> We'd have to make sure that it is picked for point (stable) releases.

14:08 <steev> i think it's only 6.3 that i see it in

14:10 <lumag> Yep

14:10 <lumag> But the patch in question is in drm-misc-next IIRC, so it is not going to be merged into 6.3.0

14:23 <steev> oh then yes, would recommend it once its in :)

14:43 <lumag> steev, also note, that external display will not work with gnome-shell on wayland, blame mutter

14:43 <steev> lumag: si, i'm in that thread

14:44 <steev> there's a hacky workaround to force the msm driver to do things the i915 way too from travmurav[m]

14:45 <steev> https://github.com/steev/linux/commit/64a8c401bbd6a9508f24f59a5053bb4b280622a2

18:46 <steev> lumag: hm, with f2c7ca8901 applied (no external display), every time the display shuts off... the c630 reboots

18:48 <steev> this is on xorg, not wayland

18:49 <steev> my test is, i boot the c630, login, let it play my startup sound (so i know if audio is working or not), then hit meta+l to lock the screen, display turns off and then a little while later, it's booted back to grub prompt

18:50 <steev> and, unfortunately, there is nothing in the logs

18:52 <lumag> I will try testing that

18:52 <lumag> steev, I don't think the screen-disable path is well tested

18:53 <steev> the same thing does not happen on the x13s, fwiw

18:53 <steev> i pushed my tree to https://github.com/steev/linux/commits/c630-v6.3-rc6 the config i use is just defconfig+docker options enabled

18:55 <steev> i wonder if

18:55 <steev> i'm gonna try punting trav's patch for the mutter stuff, since i'm not using wayland currently anyway

18:56 <lumag> which one?

18:56 <steev> https://github.com/steev/linux/commit/a437ee810eccb0fcbb8c70085f58c4678d4586d4

18:56 <lumag> ah, the kernel one

18:56 <lumag> I hoped there is something for the mutter

18:56 <steev> i wish mutter had a proper fix, but that's outside my skillset, sadly

18:56 <lumag> For me too.

18:57 <steev> i run the same patch on the x13s though, since the c630 tree is based on the x13s tree i use (i was lazy)

19:03 <steev> nope, it's not that :) okay, i'll just revert and deal with the warn on

19:19 <steev> lumag: don't look into it, i reverted that patch and it's still happening so it might be something in userland that is broken

21:06 <steev> lumag: it's probably mutter, although i dunno why it causes a reboot, because swaylock is just fine with the display turning off