| 10 Apr 2024 |
 wt | If you do have the hardware, have you noticed it failing after cycling the bluetooth service or after warm reboots? | 19:33:12 |
|  curtisos joined the room. | 21:08:59 |
| 11 Apr 2024 |
 adamw | jforbes: pbrobinson pointed out https://lore.kernel.org/all/CAMj1kXHgvv0FYZXsFm8KisXuR6t47-nXtgOs0Gyva4MJEJ_4Ow@mail.gmail.com/ in 6.8.5, seems kinda bad, maybe we shouldn't push 6.8.5 stable... | 16:49:06 |
 jforbes | @adamw has anyone seen that in Fedora? I mean, we don't build with any gcc plugins configured on, so I would assume not | 16:54:37 |
| jforbes | CONFIG_GCC_PLUGIN_LATENT_ENTROPY is not set
CONFIG_GCC_PLUGIN_RANDSTRUCT is not set
CONFIG_GCC_PLUGINS is not set
CONFIG_GCC_PLUGIN_STACKLEAK is not set
| 16:56:48 |
| jforbes | Ugh, sorry. it doesn't like "# CONFIG_FOO is not set" | 16:57:18 |
| jforbes | * "# CONFIG_GCC_PLUGIN_LATENT_ENTROPY is not set"
"# CONFIG_GCC_PLUGIN_RANDSTRUCT is not set"
"# CONFIG_GCC_PLUGINS is not set"
"# CONFIG_GCC_PLUGIN_STACKLEAK is not set" | 16:58:50 |
| *  knurd actually checked Fedora earlier today when he noticed that and concluded that it should not be affected (but of course might be wrong with that) -- and otherwise he would have made noise already | 17:01:55 |
| jforbes | Yeah, there are some interesting issues with gcc_plugins that made it not so perfect for Fedora. Difficult for users building out of tree modules as I recall | 17:04:15 |
| knurd | jforbes: FWIW, I don't mind too much, but maybe commit messages with summaries like "Add AMD PMF bug" and "Add CVE fix for 6.8.5" are not the wisest: they make kinda sense in the kernel-ark context, but they end up in the kernel.spec %changelog – and there things like this more than once made me "what is this?"; not sure if that's just me or if anybody actually cares | 18:09:46 |
| jforbes | knurd: good point. realistically I suppose a more generic "add bug(s) to BugsFixed" might make more sense | 18:11:03 |
 nirik | hey, jforbes. Hope your doing well. :) Wanted to update you about the kernel01 replacement... it was supposedly delivered, but no one can tell us for sure. We have someone who is going to be onsite next week and I am asking them to look for it. If we find it, should we bring it up as kernel02 and let you migrate? or can we just pull kernel01 and replace it? | 19:05:03 |
| jforbes | nirik: If migrate isn't too much trouble, it would be wonderful. Otherwise, I can make do if I need to | 19:31:22 |
| jforbes | I am officially back on Monday as well | 19:31:43 |
| nirik | ok. Yeah, I think we can make migrate work... we are pulling some other boxes, so can rack it in one of those places. | 19:32:36 |
|  miyon joined the room. | 20:13:16 |
| adamw | jforbes: sorry, when did you say you planned to do a kernel build with the nouveau and bt fixes? just aligning my ducks. :D | 21:34:12 |
| nirik | https://koji.fedoraproject.org/koji/buildinfo?buildID=2436096 | 21:35:10 |
| jforbes | adamw: I started them during the meeting, just waiting for aarch64 to finish up | 21:35:47 |
| adamw | ah, awesome | 21:35:53 |
| jforbes | adamw: I edited the existing 6.8.5 update to get the 301 build and added the bluetooth bug. I did not add the nouveau bug because this isn't really a full fix, just makes it much better. | 22:03:30 |
| adamw | jforbes: okay. since the pmf and bt bugs are on the fe list it'll still show up fine there, so shouldn't be a problem | 23:26:46 |
| 12 Apr 2024 |
| wt | There is a bluetooth bug? It is related to hci_qca or btqca? | 06:45:43 |
| * knurd by chance noticed a lot of lines like "binutils-2.41/bfd/archures.c: Cannot stat: No such file or directory" in recent build logs and wonders if he should be concerned | 10:09:09 |
| knurd | (like in https://kojipkgs.fedoraproject.org//packages/kernel/6.8.5/301.fc40/data/logs/x86_64/build.log ) | 10:09:25 |
| adamw | huh, https://bugzilla.redhat.com/show_bug.cgi?id=2274770 is weird, and seems most likely to be in kernel...trying to confirm | 18:48:33 |
| adamw | wt: https://bugzilla.redhat.com/show_bug.cgi?id=2274047 | 18:54:41 |
 Farchord (Steve Cossette) | Bluetooth seems to be generally an issue, isn't it...? had to do some troubleshooting for my MX Master 3 mouse a couple weeks ago | 20:11:47 |
| Farchord (Steve Cossette) | ended up blisting a kernel module lol | 20:12:00 |
| wt | bluetooth is very...iffy | 22:56:03 |
