<alyssa---->
They started about a week or so ago (?) inexplicably
<alyssa---->
I have seen the freeze occur even at the TTY login screen (so it's not X or panfrost or anything)
<alyssa---->
That leaves ... the kernel itself, and systemd/early daemons, I guess
<alyssa---->
But I haven't upgraded the kernel for a while and this problem is new
<alyssa---->
It's also worth noting, it's only happening on one of my RK3399 devices (the other one, identical in most respects -- also mainline -- is unaffected)
<alyssa---->
The problem appears to be aggravated when playing music (over USB headset) but that might be spurious.
<anarsoul>
sounds like hardware issue to me
<alyssa---->
anarsoul: Possibly
<alyssa---->
I'm tempted to blame the mrvl wifi
<alyssa---->
Since about a week ago I've been physically elsewhere (holiday season)
<alyssa---->
And the wifi from the internal chip is painfully slow
<alyssa---->
(Ethernet is fine)
<alyssa---->
Other devices on the network here show similar symptoms for the slowness -- the router definitely has an issue
<anarsoul>
try it with some usb wifi dongle?
<alyssa---->
(Oddly, yet other wifi devices on the network seem to be unaffected. Maybe about which frequency etc)
<alyssa---->
anarsoul: I disconnected wifi (didn't even dsiable -- just disconnected from the network -- am now over Ethernet) and playing music and such --- no freeze. Which is compelling info in and of itself
<anarsoul>
but wifi is likely sitting on sdio?
<alyssa---->
Mm
<alyssa---->
Further credence for that theory -- my other Kevin is connected over Ethernet exclusively, so it's not hitting any wifi code paths in the kernel, so it explains why that's fine
<anarsoul>
I just don't know the way it can freeze the system
<alyssa---->
But ... I *have* connected to this wifi network on this kevin on internal wifi before, with no freeze issues
<alyssa---->
But that was on a ChromeOS kernel, this is mainline.
<alyssa---->
So I think that definitely poitns a finger at some detail of the mrvl driver in mainline?
nsaenz has joined #linux-rockchip
nsaenz has quit [Remote host closed the connection]
nsaenz has joined #linux-rockchip
<anarsoul>
maybe?
<alyssa---->
No idea where to even begin writing a bug report, unfortunately -- the intersection of the mainline marvell wifi driver and this insanely buggy router
<anarsoul>
try using wifi on your device that haven't seen freezes yet
<anarsoul>
if it's buggy driver it should eventually freeze
<alyssa---->
Let's see.
<alyssa---->
I don't think I have the driver compiled in the kernel for that machine.
<alyssa---->
Then again ... reimaging both machines might be a good Christmas present to myself ;)
<alyssa---->
Ok, just disconnected ethernet and switch to slow wifi ... still hasn't frozen but let's see
<alyssa---->
(Side evidence: earlier when I was on Ethernet, wifi was *also* connected. So it's not simply being connected, it's actually using wifi?)
<alyssa---->
Of course, another possibility is that it's the connection's spped/unreliability confusing something (probably in userspace ... e.g. some Interent-dependent daemon timing out, or something silly)