Hello Roman, On Fri, Nov 21, 2025 at 11:11:39AM +0200, Roman Savochenko wrote: > 21.11.25 10:35, Uwe Kleine-König: > > On Thu, Nov 20, 2025 at 06:45:48PM +0200, Roman Savochenko wrote: > > > 20.11.25 10:38, Uwe Kleine-König: > > > > On Wed, Nov 19, 2025 at 08:23:31PM +0200, Roman Savochenko wrote: > > > > > 19.11.25 19:05, Uwe Kleine-König: > > > > > > On Wed, Nov 12, 2025 at 06:19:07PM +0200, Roman Savochenko wrote: > > > > > > > 12.11.25 17:03, Christian König: > > > > > > > > On 11/12/25 15:28, Roman Savochenko wrote: > > > > > > > > > 12.11.25 13:14, Uwe Kleine-König: > > > OK, and what do you want from me? > > Quoting an earlier mail in that thread: > > > > Can you try which Debian kernel was the last one working fine > > respective the first being broken in this regard? You can find > > all kernels on https://snapshot.debian.org/. Please ask if it's > > unclear how to do that. > > I have told that as the kernel in Debian 11. Is that the last working or the first broken? The last kernel in Debian 11 (i.e. buster) is 5.10.218-1. Or do you mean the last in buster-security which would be 5.10.244-1? Or do you mean the one that Debian 11.0 was released with, that would be 5.10.46-4 (I think)? The kernels before and after that are depending on what you meant above 5.10.216-1 or 5.10.237-1 or 5.10.46-3 and 5.10.221-1 or 5.13.9-1~exp1 or 5.10.46-5. Which one do you mean? The gist to take away here is: Don't specify kernel versions as "the one in Debian 11" or "kernel 5" but use the proper kernel (package) version. Everything else is too fuzzy for me to work with. > > > Must I say you the exact commit or what, > > > or you are waiting I must recompile all kernels with 294457 commits? > > > > > > I say you in what way the problem related through the stable kernels in > > > Debian releases and that is exactly assigned to the major versions of the > > > Linux kernel, even for broken v5.19 which can include backports from 6! > > Yeah, you keep talking about Linux 3, 4, 5 and 6. These categories cover > > several years of development each and thus are not helpful to locate the > > change that broke your setup. Unless it is really 5.19 that was good and > > 6.0 that is bad which limits the amount of changes from: > > I keep talking that only for understanding the problem depth and not for > fixing that in 4 kernels! > > That is, there can be simpler to apply that workaround. > > > . This is still a lot and we might ask you to do more tests to further > > limit the set of candidate commits that are broken on your end. > > OK, ask. That depends on the answers for the questions I already asked and that are still not answered in a way that I can ask the followup questions. > > > > Can you please confirm that 5.19.x (e.g. a kernel package from > > > > https://snapshot.debian.org/package/linux/5.19.11-1/) works fine and > > > > 6.0.x (e.g.https://snapshot.debian.org/package/linux/6.0.12-1/) > > > > doesn't? (Or a similar statement with other consecutive mainline > > > > versions.) > > > 5.19.0 has this problem in view of hanging. > > You lost me here. What is "problem in view of hanging"? Are we talking > > about more than one problem? Or different variants of the same problem? > > We talk about different variants, and the hanging I saw also on one 6 kernel > just after installing Debian 13 and that is why #1118349 I opened about the > hanging but not rebooting in the initial report #879992. Here is our language problem again. I fail to parse that sentence. > > > > Note that even that might not be enough to spot the problem and you > > > > might have to get your hands dirty then and compile development kernels > > > > and test them. > > > Note, my hands in that "dirty" are 22 years already and I hoped I will not > > > get their at least on Linux kernel again — http://oscada.org/wiki/Special:MyLanguage/Sub-projects/Automation_Linux_distributive > > > . :) > > > > > > And I have resolved the problem for myself by the option "radeon.dpm=0" in > > > all my Live Disks. If you want to tell that is my problem, throw it away and > > > reject the workaround!:) > > There might be a misconception about the roles involved here. > > > > In my eyes the situation is as follows: You have a problem. > > I have resolved the problem for myself far ago. > > > I (and possibly others) offer to help. > > To help for other with same hardware, since I can fix that for myself if I > need. ?? > > For now your problem report isn't in a form that I can act upon. So it's in your interest to provide the > > information that I ask for. If you don't want to do that, that's fine, > > and I won't have sleepless nights about it. The likely outcome is that > > the problem isn't addressed. > > Whether I don't provide you all information beyond "get my hand in the > dirty"? :) ?? > > Parts of the misunderstanding here might also be a language barrier. So > > maybe try to get some help in the kernel community that speaks your > > native tongue. > > So, English isn't native one for you? :) Right, and I doubt it's yours either. Or you would be the first native English speaker in my career that I fail to understand when communicating about Linux topics. (The only other explanations for that I can come up with are a) you suffer from dyslexia; or b) you write glibberish on purpose to annoy.) PSA: This is my last mail to you for this bug until you come up with a statement like: I tested Debian kernel image package version a.b.c-d and its broken with the following symptoms: [....]. The kernel image that occurs in the list on https://snapshot.debian.org/package/linux/ directly after that (i.e. version e.f.g-h) doesn't show these symptoms. Best regards Uwe
Attachment:
signature.asc
Description: PGP signature