00:28 <steev> konradybcio: yeah, it only happens for me on torvalds, so whatever it is, is fixed in next i guess :) i'll poke when i have time

02:52 <bamse> steev: nice, didn't think anyone had tested it...as there was no t-b ;)

03:32 <jlinton> Uh, just tossing this out there, but btmgmt on the x13s is inverting the public-address setting. So if one tries to actually set a mac AA:BB:CC:DD:EE:FF it needs to be set as FF:EE:DD:CC:BB:AA

05:41 <steev> bamse: i don't know how to "properly" test it, but yeah, it has been in my 6.6 and 6.7 trees for a while

06:55 <travmurav[m]> jlinton: I believe bluetooth address is little-endian (inverted) by convention, so perhaps it accepts BE but prints LE?

07:02 <travmurav[m]> jlinton: or hm, I think you're right, need to set in LE and it prints "normal" BE representation

07:02 <travmurav[m]> which is the same for the local-bd-address property in dt

07:35 <jbowen> Finally! https://paste.centos.org/view/raw/8ce8b311

10:01 <danielt> Is there a "well known thing" I have to do when changing from v6.3 to v6.4 on a Yoga C630? I'm seeing RCU soft lockup reports jamming the boot when I made the switch.

10:02 <danielt> I'll launching a bisect in the mean time...

14:51 <steev> danielt: in looking... i don't have a 6.4 tree for the c630, and i *think* i might have run into something similar... but i do have a recent 6.6 tree, and it doesn't have those rcu lockups

15:09 <konradybcio> seen that on some other 845

15:09 <konradybcio> occasionally on other snapdragons

18:18 <jlinton> travmurav[m]: Just to be clear, I don't think this is a btmgmt problem as it maintains the address format on !x13s machines I tried it on. AKA the input address, matches the `btmgmt info` address, matches the addresses displayed on 3rd party devices which are scanning/pairing. Its only on the x13s (and presumably other things with the btqca(?) driver) that I see the problem.

18:21 <jlinton> Also, I can change it on the fly without restarting bluetooth on the amd machine I just tested it on, which isn't true on the x13s.

21:44 <steev> konradybcio: i think it's some sort of race (the messages from yesterday) - i just rebooted 3 times (once was the *very random freeze when gnome should start and the system reboots on its own) and haven't seen the messages in any of the 3

21:44 <steev> oh no, for some reason they just weren't printed on the screen, but they're there. disregard previous statement :(

22:05 <konradybcio> you can probably make your testing faster if you disable gdm on startup temporarily

22:58 <steev> yeah, throwing 3 in the command line would definitely speed it up