From: dchmelik@gmail.com   
      
   On Sun, 30 Nov 2025 19:58:18 -0000 (UTC), Petri Kaukasoina wrote:   
      
   > David Chmelik   wrote:   
   >>The ProcPS people told me it's a kernel issue.  If that's it (and not   
   >>just a possible defect in new hardware) how do I go about reporting this   
   >>to the Linux kernel itself without being told it's not enough   
   >>information.   
   >   
   > You can find the change in kernel that is responsible for the issue. The   
   > instructions are here:   
   >   
   > https://docs.kernel.org/admin-guide/bug-bisect.html   
   >   
   > After you have found the offending commit, you can report it, for   
   > example,   
   > here:   
   >   
   > https://bugzilla.kernel.org/   
      
   Well, I only use normally-numbered long-term/stable/user, not hash-   
   numbered commit/experimental/testing versions, but I'll follow   
   instructions further up that guide.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)