19:00:04 #startmeeting 19:00:04 Meeting started Wed Jun 3 19:00:04 2026 UTC. The chair is carnil. Information about MeetBot at https://wiki.debian.org/MeetBot. 19:00:04 Useful Commands: #action #agreed #help #info #idea #link #topic. 19:00:08 hi 19:00:15 Hi 19:00:19 #chair bwh 19:00:19 Current chairs: bwh carnil 19:00:44 bwh: IIRC waldi and ukleinek cannot attend today 19:01:04 So let'start into meeting, maybe shorter today 19:01:12 is there anything you want to pick up before the buglist? 19:01:42 We should maybe talk about bookworm going over to LTS 19:02:50 The plan is to handover regular security support to LTS after 3 years, so the current discussion onging between the various teams is on 12th june LTS team takes over security support for bookworm, while still making sure that until the last point release 19:02:57 right 19:03:11 updates do not interfere with finalizing work on bookworm's last point release and bookworm-pu requests 19:03:37 so specific for src:linux I guess you are happy to continue with the 6.1.y imports? 19:04:01 Just let me know when you are ready for me to take over, I suppose 19:04:27 ok, I'm not sure what we should do with 6.1.175 19:05:07 if there were not so many flux of incoming issues given the size of it i would have said we make that for the last point release in one months time, but that does not look realisitc 19:05:32 I am still only just over half-way through reviewing 5.10.258. I expect there to be some other regressions there that also apply to 6.1.175 19:06:13 if you want I can just stop here and leave it in yours hand starting today (and if you appreciate a helping hand I can still contribute for a while for 6.1.y as well, but making sure I do not get into your way for your LTS contribution) 19:06:29 bwh: yes you are much better in tracking all those regressions, thanks for that a lot! 19:06:49 I think I am better at finding them, not so much keeping track of everything 19:07:24 bwh: do we want to discuss those details outside the meeting? But baseline 12th june is the formal date of ending regular security support, start of LTS team for bookworm 19:07:50 I think we don't need to go into more detail right now 19:07:58 ok 19:08:24 next small topic would be the pipeline jobs failing, in particular piuparts 19:09:02 it fails all down as well for trixie: https://salsa.debian.org/carnil/linux/-/jobs/9711799 so at first glance it does not look it is "our fault", but it is blocking right now on automatic merges for our MRs 19:09:46 I have not tried to understand it yet, as only this evening I came to the point to have the build job actually running properly (after clearing runner caches and restarting again) 19:09:59 but something broke 19:10:15 Well this smells like a general bug in the pipeline 19:11:20 https://salsa.debian.org/salsa-ci-team/pipeline/-/work_items/574 19:12:11 So, unless one of us is going to work on that we should probably just wait 19:12:33 ok, so good let's move on to the bugs then 19:13:03 #topic #1126671: (S, ) linux-image-6\.17\.13+deb13-amd64: Disconnect root (path=/) during heavy load on NvME, partial corruption on NTFS.crash soon but not yet 19:13:12 I have recorded: 19:13:17 Waiting for timeslot from @benh and/or @waldi. 19:13:26 No, almost all my time has been spent on reviewing 5.10.258 19:14:07 "but I'm sure things will calm down next week" 19:14:15 so no timeslot available so far, can I leave this still to you and waldi ok? 19:14:19 yes 19:14:48 #action when timeslot available, either bwh or waldi will look into debugging #1126671 19:14:57 #topic #1138242: (S, ) linux-image-6.12.90+deb13.1-riscv64-dbg and linux-image-6.12.90+deb13.1-s390x-dbg have an undeclared file conflict 19:15:18 helmut filled this new one with a file conflict 19:16:02 is it actually possible here to have proper conflict relation between packages without having us to explode the relationsships? 19:16:08 No we can't do that 19:16:34 We have to make sure that all files include the ABI string somewhere 19:17:08 #action bwh will investigate #1138242 to find which files don't depend on the ABI string 19:17:19 thanks Ben 19:17:33 #topic #1130845: (i, uM) linux-image-6.18.12+deb13-amd64: kernel panic after plugging a 5 Bay USB Docking Station (DS-5R15) with BTRFS disks 19:17:46 1. Still unclear if this was a regression. Asked for logs get through netconsole. 19:17:58 2. I think we should wait here for the reporter following up to the questions 19:18:17 #topic #1135235: (i, M) linux-image-6.19.13+deb14-amd64: Reoccuring host crash "Invalid SPTE change" with gaming win kvm/qemu guest and device passthrough (forwarded: lore.kernel.org) 19:18:45 The reporter followed upstream's instruction to build kernel with CONFIG_VMAP_STACK=y and CONFIG_KASAN=y 19:19:01 and we are now waiting for the test results/reproducing steps 19:19:12 so IMHO nothing to do for us at the moment 19:19:18 They did ask a question in the last message 19:19:47 ah good point 19:19:50 How to check whether KASAN is active. Which I think it always is with CONFIG_KASAN=y? 19:21:42 https://docs.kernel.org/dev-tools/kasan.html suggests that, and there are other boot parametesrs to influence the panic control and reporting 19:21:47 yeah 19:22:04 let me take an action to at least respond to this question from the reporter before we go into wait mode again 19:22:26 #action carnil will followup on the KASAN question from the reporter in #1135235 19:22:53 #topic #1137107: (i, Mu) netfs local_bh_enable in hard IRQ via cachefiles read completion (merged with #1137105, #1137106) 19:23:09 ukleinek: said last time: We'd need a way to reproduce. Wait for David Howells to maybe reply. 19:23:37 the reporter seems not in position though to test as well other kernels other than in the repository? 19:24:04 so wait on getting some input from upstream is fine 19:24:08 Well, tough luck I suppose 19:24:28 but we need to convince the reporter to be ble to test other kernels 19:24:39 otherwise I do not see how we can move forward 19:24:55 I'll also tag it unreproducible and we can close it later if nothing happens 19:24:58 should we tag this unreproducible ? 19:25:10 he same thinking, good please go ahead with that 19:25:15 done 19:25:27 #topic #1137142: (i, u) linux-image-amd64: Screen goes black dozen of seconds after resume from suspend state on ThinkPad T16 2023 19:25:57 Do you want to keep an action for this searching the ML for similar reports? 19:26:19 OK 19:26:41 #action bwh ill search ML for similar reports to #1137142 19:26:54 #topic #1137272: (i, M) linux-image-amd64: Missing sound on Lenovo x9-15 (and possibly other Lunar Lake laptops) 19:27:23 no feedback from reporter, but I took the liberty to merge the bugreport with #1136179 as we were pretty confident already that it's the same 19:27:43 #topic #1138755: (i, ) Subject: amdgpu: RX 640 hangs right after VCE initialization on kernel 6.12 (i5-11400F, no iGPU) 19:27:47 new report 19:27:57 03linux 05debian/latest 06Ben Hutchings * [update] merge request !1942: [amd64] Enable CONFIG_PINCTRL_CS42L43 and CONFIG_SPI_CS42L43 explicitly * 14https://salsa.debian.org/kernel-team/linux/-/merge_requests/1942 19:28:16 as reporter can easily reproduce the issue I asked if reporter is willing to bisect and gave instructions 19:28:35 re #1137272, I just tagged the MR for backport since ukleinek said 6.12 and 7.0 were affected 19:28:49 wait I would say, unless you have some ideas what to propose as well 19:28:56 Let me catch up... 19:29:02 bwh: ack re #1137272 makes sense 19:29:39 OK, I will just tag this moreinfo 19:29:55 good, and then let's wait 19:30:08 #topic #1127588: (n, M) linux-image-6.18.9+deb14-amd64: Cannot hibernate after some time of work 19:31:02 waldi: asked for /proc/{mem,slab}info which got provided by reporter, so as for last time needs now us again to followup. I *think* waldi would still try to have a look 19:31:26 Can we assign that action in absentia? 19:31:40 not really it is unfair 19:32:05 #action bwh will follow up to #1127588 if waldi does not 19:32:10 I can try to have a look in between if I can make something out of it 19:32:14 ok fine as well :) 19:32:26 #topic #1135748: (n, ) linux-image-6.12.85+deb13-amd64: suspend to disk crashes after resume 19:32:38 Thanks to TJ, I still look up PM related way. 19:32:40 Tj gave instructions to use the Debugging hibernation and suspend instructions and report back anything significant from logs. 19:32:48 hi yunseongkim[m], welcome 19:32:58 I tagged it moreinfo and suggest we wait for replies 19:33:36 #topic #1136792: (n, M) linux-image-7.0.4+deb13-amd64: ipv6 temp addresses renew prematurely when removing interface (merged with #1136793) 19:33:48 no followup yet to the questions/answer from waldi -> wait 19:34:10 #topic #1137275: (n, ) linux-image-7.0.7+deb13-amd64: No sound after update kernel to 7.0.7 (stable-backports) from 6.12.86, missed firmware-realtek 19:34:39 ukleinek asked for a bisection, now need to wait for the results 19:34:52 right 19:35:17 #topic #1137548: (n, MRu) linux-image-6.12.90+deb13-amd64: kernel NULL deref in cap_capable() during /proc//stat read causes system hang via orphaned spinlock 19:35:45 I guess we can wait as noted as there was no followup to your questions yet 19:36:05 I'm still not really awaere of reported regressions for the ptrace fix 19:36:26 (but there is so much on the regressions and stable lists which I might have missed a report) 19:36:59 if you neither are aware of reports, let's just wait 19:37:30 ok 19:37:32 I think it was just a coincidence that the ptrace fix and this weird crash happened around the same time 19:37:34 #topic #1138033: (n, ) linux-image-7.1-loong64 dmesg has Call Trace Workqueue: events drm_fb_helper_damage_work [drm_kms_helper] 19:38:23 ukleinek: looked at it, there seems to be an upstream report/suggested patch as well upstream, related to https://lore.kernel.org/dri-devel/20260519092420.1124348-1-zhengxingda@iscas.ac.cn/ . ukleinek asked to add a Closes references to our bug so it will fall on the radar when it lands and we can add a bug closer 19:38:32 other than that I think nothing remains on our end to do 19:38:35 great 19:38:44 that were the src:linux bugs 19:39:00 #topic #1011089: (n, M) nfs-utils: old configs /etc/default/nfs-* should have warnings 19:39:17 (and the stable-update script really should look for Closes: https://bugs.debian.org/... automatically) 19:39:21 this just got on the list again becuase a user said to please consider non-systemd users 19:39:38 bwh: that is a nice idea! 19:40:37 I don't agree with the bug report and I think we should close it 19:41:00 let's close it 19:41:15 The initial report says "In other words, they are ignored when systemd is used, and the configuration should be done in /etc/nfs.conf in that case." 19:41:47 which might have been true at the time but now there is nothing that overrides nfs.conf 19:42:38 as of 1:2.6.3-1 19:43:05 Will you close it or shall I? 19:43:22 Oh I replied first so I'll close it 19:43:33 thanks :)