Comment # 10 on bug 1020965 from Michal Suchanek

(In reply to George Anchev from comment #9)
> (In reply to Michal Suchanek from comment #8)
> > Yes. the file is now at /sys/class/power_supply/ACAD/online
> > 
> > You wrote the custom script so you are responsible for maintaining it across
> > kernel versions. If you don't care to do it and want the script working
> > don't upgrade to kernel versions that deprecate and remove the interface you
> > use.
> 
> How can I know that such changes were made so that I can fix my scripts on
> time?
 a) follow kernel development
 b) strace a tool that gives the information you want like acpi(1)
 c) use the tool in the first place
> 
> > Did you try to debug the suspend with console_no_suspend? I did not see any
> > results of that posted here.
> 
> How do I do that? Where do I enter this option?

If you STFW for 'linux suspend debugging' you get lots of detailed information.

> 
> > Either way, Tumbleweed tracks upstream closely
> > in this regard so you should look for upstream instructions on debugging
> > suspend issues and report upstream bug for it.
> 
> I am not sure I understand this part. Is this not the right place to report
> bugs? Please explain if I need to report something additional. Thanks.

You need to report what's broken on your system because you have the system so
you are the only one who can find out.

And you need to report it to upstream Linux developers so they can fix it and
the fix gets to Tumbleweed through kernel updates.

With Tumbleweed it's unlikely that this error is something SUSE specific.
However, if workaround for this particular issue exists it can be applied in
the suspend scripts.

It would be nice to also report the bug number/git commit/workaround here so
other openSUSE users know about it but it's not strictly necessary.