1 |
Please don't top-post. |
2 |
|
3 |
On Wednesday, January 13, 2021 11:32:44 AM CET Igor Mróz wrote: |
4 |
> You mean 100%? Nope, all looks normal. I even tried to build elogind with |
5 |
> policykit USE, but with no luck. loginctl shows that session/seat is active |
6 |
> all the time. |
7 |
> |
8 |
> Igor |
9 |
> |
10 |
> |
11 |
> On Mon, 11 Jan 2021 20:05:20 +0100 |
12 |
> |
13 |
> "J. Roeleveld" <joost@××××××××.org> wrote: |
14 |
> > On 11 January 2021 19:33:55 CET, "Igor Mróz" <mrozigor@××.pl> wrote: |
15 |
> > >I don't even know where to search. |
16 |
> > > |
17 |
> > >I tried to SSH to 'frozen' laptop, but as I wrote earlier - there is |
18 |
> > >nothing suspicious in dmesg or xorg logs. Only difference is in 'ps' |
19 |
> > >i.e. process '[kworker/u16:0-i915]' changed to |
20 |
> > >'[kworker/u16:0-events_unbound]' and some other kworkers received new |
21 |
> > >PIDs (like those have been restarted). |
22 |
> > > |
23 |
> > >Igor |
24 |
> > > |
25 |
> > > |
26 |
> > > |
27 |
> > >On Mon, 11 Jan 2021 15:01:41 +0100 |
28 |
> > > |
29 |
> > >"J. Roeleveld" <joost@××××××××.org> wrote: |
30 |
> > >> On Monday, January 11, 2021 2:22:27 PM CET Holger Hoffstätte wrote: |
31 |
> > >> > On Mon, 11 Jan 2021 13:49:35 +0100, Igor Mróz wrote: |
32 |
> > >> > > I don't really know - I haven't installed anything. Now I'm not |
33 |
> > > |
34 |
> > >really |
35 |
> > > |
36 |
> > >> > > sure if this is problem with suspension or just screen resuming |
37 |
> > > |
38 |
> > >after |
39 |
> > > |
40 |
> > >> > > "turning" it off. I also don't have Nvidia card. |
41 |
> > >> > > |
42 |
> > >> > > Igor |
43 |
> > >> > |
44 |
> > >> > Try running xorg-server with +suid. |
45 |
> > >> |
46 |
> > >> That should not be necessary for suspend/resume. |
47 |
> > >> I have that flag disabled (as per default) on my laptop and that one |
48 |
> > > |
49 |
> > >gets |
50 |
> > > |
51 |
> > >> suspended regularly. |
52 |
> > >> |
53 |
> > >> -- |
54 |
> > >> Joost |
55 |
> > |
56 |
> > Anything running at 100÷? |
57 |
> > |
58 |
> > Check "top" when ssh'd in |
59 |
|
60 |
Reason I asked: On one of my systems, I have the occasional issue where a |
61 |
screenlock-task is "hanging" and using 100% CPU. |
62 |
Killing that, restores the screen back to normal. |
63 |
|
64 |
-- |
65 |
Joost |