From: JimDiamond@ns.sympatico.ca   
      
   On 2022-04-10 at 07:56 ADT, User  wrote:   
   > On 4/8/2022 5:37 PM, Jim Diamond wrote:   
   >> On 2022-04-07 at 15:25 ADT, User  wrote:   
   >>> On 4/6/2022 8:08 PM, Jim Diamond wrote:   
   >>>> On 2022-04-05 at 02:45 ADT, Henrik Carlqvist  wrote:   
   >>>>> On Mon, 04 Apr 2022 21:17:57 -0300, Jim Diamond wrote:   
   >>>>>> I've hunted around a bit, but don't see any obvious reasons for this. (I   
   >>>>>> define "diffing the code of 5.15.19 with 5.15.27" as "not obvious".)   
   >>>>>> /proc/acpi/wakeup is the same in both 5.15.19 and .27.   
   >>>>>   
   >>>>> If you are willing to do the work, it might be easier to diff only   
   >>>>> between the two kernel versions where this change happened, for example   
   >>>>> between 5.15.23 and 5.15.24.   
   >>>>>   
   >>>>> The quickest way to find where the change happened is to  do a binary   
   >>>>> search for that point. Now you know that 5.15.19 work as before and   
   >>>>> 5.15.27 works at after. What about the version in the middle in between?   
   >>>>> That would be 5.15.23. Once you have tested with kernel 5.15.23 you will   
   >>>>> know if the next step is to search between 5.15.19 and 5.15.23 or between   
   >>>>> 5.15.23 and 5.15.27.   
   >>   
   >>    
   >>   
   >>>> I don't know how many people are reading this newsgroup these days,   
   >>>> but I am somewhat intrigued if I am the only person having this issue.   
   >>>> I had previously posted this to alt.os.linux since it is not   
   >>>> slackware-specific (it also happens to me with the artix system I was   
   >>>> using while waiting for 15.0 to appear).  However, sadly that group is   
   >>>> mostly full of spam these days.   
   >>   
   >>>   
   >>> I did some testing on my laptop running Slackware 15.0 with 5.15.27.   
   >>>   
   >>> Suspend to RAM   
   >>> - Awakens on opening the case   
   >>> - Does nothing on removing/attaching power   
   >>   
   >> Thanks for the report.  Can you tell me what sort of processor you   
   >> have?  (In short, AMD or Intel?  And further, the model number if you   
   >> don't mind.)   
   >>   
   >> Cheers.   
      
   > Its a 10th Gen Intel   
      
   Thanks.  Not a surprise, now that I know it is an issue with how some   
   AMD systems handle AC power events.   
      
                                   Jim   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)